—Short-term rental rules · Breckenridge
Breckenridge zones its STR market explicitly: where the property sits on the zoning overlay determines what license class is available, and the caps are real.
Last reviewed against current municipal sources on 2026-05-20.
01The Breckenridge context
Zone 1 — the resort core — broadly permits short-term rental, with the license class focused on operator conduct rather than supply limits. Zone 2 — transitional neighborhoods adjacent to the core — operates under a cap on the number of active licenses, with new applicants placed on a waitlist when the cap is reached. Zone 3 — established residential — is largely restricted to owner-occupied use.
A property does not change zones because a property line moves; hosts buying into Breckenridge for STR income tune their underwriting to the zone the parcel is in, and the practical value of a Zone 2 license rises and falls with the waitlist.
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 Breckenridge's own Colorado guidance.
02The house-rules angle
In a tiered-cap market the operator’s reputation with the town is an asset that compounds: clean enforcement record, no repeat complaints, prompt response to issues. The rules most likely to be tested are the ski-season classics — parking in winter, noise from larger group bookings, and trash management on turnover days.
A signed acknowledgment that calls out the zone-specific license class plus the standard noise and occupancy rules gives you something to put in a complaint response file. It is what a host wants in a market where each complaint is a small mark against a license they want to keep.
These are starting points to adapt — not legal advice, and not specific to any one Colorado 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 Breckenridge 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