—Short-term rental rules · Sedona
Sedona is a small town with national-park-grade tourism — and every house is across the street from someone’s home. The city has been one of the most vocal opponents of Arizona’s preemption law (ARS §9-500.39) and pushes every regulatory lever the statute still allows, including a public-registry permit, a transaction-privilege-tax license, and neighbor-notification mailers before a permit issues.
Last reviewed against current municipal sources on 2026-05-20.
01The Sedona context
Sedona’s permit program runs through Community Development. Every permitted listing sits on a public registry neighbors can search by address — a deliberate transparency choice to make the program self-policing. The city has gone to court and to the legislature multiple times trying to get the preemption law softened; the rule set you have today is the one shaped by that long fight.
The red-rock bowl is acoustically alive. Conversational volume on a back patio is audible a quarter mile up the canyon at night. Wedding-and-photo-shoot tourism is the biggest commercial-event pressure point — Sedona draws destination weddings, and "stayed at an STR, hosted a small wedding" is the most common complaint pattern.
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 Sedona's own Arizona guidance.
02The house-rules angle
A Sedona host should be specific about commercial use — no weddings, no photo shoots, no influencer brand work without prior written approval and a separate permit. Trailhead parking choreography and respecting dark-sky outdoor lighting are the local-flavor items that out-of-state guests miss. Each is its own complaint surface; each narrows with concrete acknowledgment.
The high season runs Mar–May and Sep–Nov; that is when the neighbor-flagging pattern peaks. The signed acknowledgment is the host’s on-the-record receipt that they set the expectation, not an after-the-fact reconstruction.
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.
03Put the rules on the file
A house-rules block in your listing is disclosure — it proves the rule existed. It does not prove the guest who booked your Sedona 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.
Build a packet from these rules once, send it on every reservation. Free covers one property. No credit card.
04Verify with the source
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.
05Other regulated markets
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.
06Keep reading