Cambria Landing Inn & Suites

Suiteness Logo

The only place to book connecting hotel rooms and suites. Here's how.

Located in Cambria, Cambria Landing Inn & Suites is by the ocean, within a 15-minute walk of Leffingwell Landing and Moonstone Beach Park. This hotel is 1.4 mi (2.2 km) from Nitt Witt Ridge and 5.6 mi (9.1 km) from William Randolph Hearst State Park.

6 suites at Cambria Landing Inn & Suites

6 suites

31 amenities at Cambria Landing Inn & Suites

  • Bicycle rentals nearby
  • Braille or raised signage
  • Daily
  • Firepit
  • Fireplace in lobby
  • Free breakfast
  • Free continental breakfast
  • Free self parking
  • Free WiFi
  • Front desk (limited hours)
  • Golfing nearby
  • Golf lessons available nearby
  • Hiking/biking trails nearby
  • Housekeeping on request
  • Kayaking nearby
  • Luggage storage
  • Mountain biking nearby
  • Multilingual staff
  • Number of hot tubs - 2
  • Off-street parking
  • Parasailing nearby
  • Proposal/romance packages available
  • Sailing nearby
  • Scooter/moped rentals nearby
  • Smoke-free property
  • Surfing/bodyboarding nearby
  • Water skiing nearby
  • Wheelchair accessible
  • Wheelchair accessible (may have limitations)
  • Wheelchair-accessible registration desk
  • Windsurfing nearby

2 images of Cambria Landing Inn & Suites

  • exterior | Cambria Landing Inn & Suites
  • Cambria Landing | Cambria Landing Inn & Suites

Cambria Landing Inn & Suites reviews

4.3
1000 reviews

Cambria Landing Inn & Suites Location

6530 Moonstone Beach Dr

Cambria, CA 93428 US

1 (855) 282-1325

{# Hotel structured data. Every interpolated value goes through |json, which supplies its own quotes. Do NOT add quotes around a — the filter emits them, and writing them twice produces """value""". The reason is not style. This block used to interpolate values raw, so any hotel whose suite descriptions contained a line break emitted invalid JSON and Google discarded the whole thing — which was seven of our ten highest-impression hotel pages. Names came out with "&" in them for the same reason: HTML escaping applied where JSON escaping was needed. #}