Short-term rental rules in Phoenix.

Arizona state law (ARS §9-500.39) preempts most outright STR bans, but lets cities impose registration, sales-tax, and nuisance-response requirements. Phoenix uses every lever the statute leaves open.

Last reviewed against current municipal sources on 2026-05-20.

What hosts should know locally.

Phoenix’s STR license requires a permit number, transaction-privilege-tax registration, a 24-hour emergency contact, and a verified mailing address. Notice of the listing goes to every adjacent property owner — neighbors know it’s an STR before the first guest arrives.

The "party-house ordinance" gives the city escalating penalties for nuisance complaints. Three substantiated complaints in a 12-month window can suspend the permit. Hosts who don’t set rules early get caught by the second or third complaint.

Confirm before you list

Local rules change — confirm current requirements with your city before you list. This page is a market-context summary and a house-rules starting point, not a legal source or a substitute for Phoenix's own Arizona guidance.

Rules tuned to this market.

A Phoenix host should be explicit about the no-event posture, noise norms (sound carries in the Valley), pool-use rules, and the 24-hour contact. Each item the guest signs is one less item the city can attach to a nuisance file.

Peak season (Oct–Apr) draws sports-event tourism that tests occupancy caps and outdoor sound. The signed acknowledgment puts those rules on the file before the guest arrives.

Phoenix — tuned house-rules angles starting points
Occupancy Overnight occupancy is the reservation count; no unregistered overnight guests.
Quiet hours Quiet hours 10pm–8am; outdoor amplified sound prohibited after 10pm.
No events No parties, events, or commercial photo shoots without prior written approval.
Pool & spa Pool and spa used only as instructed; no glass containers in the pool area.
Local compliance Guest acknowledges Phoenix STR licensing rules and the 24-hour contact.
Full house-rules PDF free, no signup

These are starting points to adapt — not legal advice, and not specific to any one Arizona ordinance. Edit the wording and any amounts to your property and what your platform and city allow.

A tuned template is disclosure. Not agreement.

A house-rules block in your listing is disclosure — it proves the rule existed. It does not prove the guest who booked your Phoenix place ever saw that specific rule or agreed to it. What sits in the file as evidence after an incident, and what shows good-faith compliance in a regulated market, is acknowledgment: the guest confirming each rule and each fee individually, with a timestamp, before check-in.

PreArrive turns the tuned rules above into a packet the guest signs in about ninety seconds. They tap each rule and each fee to acknowledge it, draw a signature, and you get a PDF certificate — disclosure and acknowledgment in one file, with a two-event audit trail and a content hash. It is evidence, not a verdict: it does not litigate a dispute or decide a code question for you, but it puts a traceable record behind every stay.

Sign every Phoenix guest. Before they check in.

Build a packet from these rules once, send it on every reservation. Free covers one property. No credit card.

Confirm directly with Phoenix.

This page is a plainspoken summary. The municipal sources below are where the actual rules live. If something here disagrees with the source, the source is right — let us know and we'll re-review.

Page reviewed 2026-05-20.

If you also host in other cities.

The same disclosure-versus-acknowledgment gap shows up across every active STR market. Each city below has a plain-language local summary and a house-rules angle tuned to that market.

Want all of them in one place? See PreArrive for regulated-market hosts.

Related, if you're going deeper.