Quality Inn Price Gateway to Moab National Parks

Suiteness Logo

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

A stay at Quality Inn Price Gateway to Moab National Parks places you in the heart of Price, within a 10-minute walk of Price Library and Peace Gardens. This hotel is 0.5 mi (0.8 km) from Utah State University Eastern Prehistoric Museum and 0.5 mi (0.8 km) from Price City Council.

5 suites at Quality Inn Price Gateway to Moab National Parks

5 suites

18 amenities at Quality Inn Price Gateway to Moab National Parks

  • 24-hour front desk
  • Braille or raised signage
  • Business center
  • Coffee/tea in common areas
  • Daily
  • Free breakfast
  • Free buffet breakfast
  • Free newspapers in lobby
  • Free self parking
  • Free WiFi
  • Number of indoor pools - 1
  • RV, bus, truck parking
  • Smoke-free property
  • Terrace
  • Uncovered parking
  • Upper floors accessible by stairs only
  • Vending machine
  • Wheelchair accessible – no

5 images of Quality Inn Price Gateway to Moab National Parks

  • Hotel exterior | Quality Inn Price Gateway to Moab National Parks
  • Hotel lobby | Quality Inn Price Gateway to Moab National Parks
  • Front desk | Quality Inn Price Gateway to Moab National Parks
  • Indoor pool | Quality Inn Price Gateway to Moab National Parks
  • Breakfast area | Quality Inn Price Gateway to Moab National Parks

Quality Inn Price Gateway to Moab National Parks reviews

3.9
502 reviews

Quality Inn Price Gateway to Moab National Parks Location

590 E Main St

Price, UT 84501 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. #}