California Enforcement, Fines and Permit Revocation

California short-term rental enforcement is city-led, with each city setting its own fine scales, revocation grounds and processes, and with platform disclosure under SB 346 giving cities better data to detect breaches. This guide does not state fine figures per city, because scales vary and change, and a single figure would mislead hosts in different cities. The general picture is that unpermitted letting, missing licence numbers, cap breaches, false listing details and tax failures are enforcement priorities, and consequences can include fines, listing removal and permit revocation.

Data-assisted enforcement is now central. Platform disclosure of address, URL, parcel and licence and transient occupancy numbers lets cities compare listings with permit and tax records systematically, without waiting for complaints. Hosts should assume that a visible listing is a comparable record, and that a pattern of unpermitted or over-cap letting will surface through data as well as through neighbour reports.

Triggers include listings without a city permit or certification, listings with a permit number that does not match the property, listings whose address or parcel details differ from city records, cap breaches shown by stay patterns, and neighbour complaints about noise, parking or turnover. Complaints remain important, especially in dense or coastal neighbourhoods, but data triggers now rival complaints in frequency. A host should manage both: accurate city records for data triggers, and guest management for complaint triggers.

Tax triggers form a third category. TOT shortfalls, missing transient occupancy numbers, or income records inconsistent with platform activity can prompt city or tax enquiries separately from permit enquiries. Hosts should keep permit, TOT and income files consistent on stay facts, so a query in one area does not reveal inconsistency in another.

If a city contacts a host, read the notice fully, note deadlines, and gather the property file: city permit, listing views, stay log, cap tracker, tax records and building permission. Answer the specific questions asked, with documents, rather than sending a general letter about hosting. Correct factual defects promptly, such as a listing number error, and document the correction. For classification or cap disputes, describe the actual pattern honestly and seek advice where the matter is complex.

Do not continue the allegedly breaching letting while disputing it without advice. Continuing can add further breaches and worsen fines or revocation risk. Pause the disputed pattern, consider lawful alternatives where applicable, and keep a note of the pause and its dates. That pause, documented, supports a later claim of responsible action.

Permit revocation, where it occurs, typically follows serious or repeated breaches, false information, or failure to comply with city conditions after warnings. Revocation ends lawful short letting for that property under that permit, and reapplication after revocation may be difficult or subject to waiting periods and stricter scrutiny, depending on city rules. Hosts facing revocation proceedings should seek advice promptly, since deadlines and appeal routes are often short and city-specific.

Revocation in one city does not automatically revoke permits in another city, since permits are city-specific, but a revocation record can affect future applications, platform standing and neighbour relations elsewhere. Portfolio hosts should therefore treat any revocation proceeding as portfolio-relevant: audit other properties for the same defect, brief managers, and fix systemic causes, not only the named property.

Platform removal often accompanies city enforcement, as platforms block listings with invalid permits or under city direction. Hosts should treat platform removal as a permit problem to fix at source, not as a platform dispute to bypass by re-listing. Re-listing a revoked or unpermitted property under altered details can be treated as evasion and can worsen city and platform consequences. Fix the city record, confirm verification, and then seek reinstatement through proper channels.

Keep platform removal messages with city correspondence in one incident file, with dates for each step. That file shows diligence, helps spot patterns, and supports any appeal. A host who can show removal, fix and reinstatement, with dates, demonstrates responsible hosting; a host who can show only repeated removals does not.

Prevention is city permit complete, listing details aligned with city records, cap tracked monthly, stay and tax records reconciled monthly, building permission checked, and neighbours managed. Add a seasonal city-portal recheck for each property's city, since city rules and SB 346 disclosure practices evolve. Those habits answer most enquiries before they start.

This guide is general information only, last verified on 26 October 2026, and is not legal advice for a specific enforcement case. Verify city fine and revocation rules for the address on the city portal before acting.