—Short-term rental rules · Bend
Bend runs a three-type STR permit system. Type 1 is host-occupied; Type 2 is unhosted in a residential zone, capped with a 250-foot minimum spacing between listings; Type 3 is unhosted in a resort-zoned area, less constrained but in narrower geographies.
Last reviewed against current municipal sources on 2026-05-20.
01The Bend context
The 250-foot spacing rule for Type 2 listings is the city’s main tool for keeping STRs from clustering on residential streets. Once one Type 2 permit is issued on a block, the next one can only sit 250+ feet away. Permits are listing-specific and don’t transfer.
Bend’s growth and outdoor-rec appeal drive event-tourism traffic — Cycle Pub, brewery tours, Mountain Bike Race Series weekends. The no-event rule has to be specific or guests will treat the listing as a base camp for a gathering.
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 Bend's own Oregon guidance.
02The house-rules angle
A Bend host should be explicit about which permit type the listing is, the occupancy cap, the no-event rule for event-weekend tourism, and the snow-and-fire posture the high desert demands. Acknowledgment on each tightens the no-event story before the guest pulls up.
High-desert fire risk is real in summer; smoke from outdoor fires drifts and gets reported. A specific no-outdoor-fire rule during burn restrictions matters.
These are starting points to adapt — not legal advice, and not specific to any one Oregon 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 Bend 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