California Hosted Versus Unhosted Stays

Across California cities, hosted stays, where the host lives in the property during the stay, and unhosted stays, where guests occupy the whole property without the host present, are different operations with different permits, caps and neighbour impacts. Los Angeles home sharing, San Francisco certification and San Diego tiers all treat the distinction as central, though they express it differently. A host who does not label stays hosted or unhosted cannot track caps, permits or platform settings correctly, because those tools all depend on the distinction.

The distinction also affects guests. A hosted guest shares living space and expects host presence; an unhosted guest expects a private property. Listings that blur the distinction mislead guests and create complaints, cancellations and reviews that harm hosts. Label stays clearly in listings, in house rules and in stay logs, from the first booking.

Caps in California cities often apply differently to hosted and unhosted stays. San Francisco's 90-night cap applies to unhosted stays, while hosted stays follow different city treatment. Los Angeles home sharing's 120-night cap applies within its primary-residence model, which hosts should check for hosted and unhosted treatment on planning.lacity.gov. San Diego tiers sort hosted and whole-home patterns into different tiers. A host who applies one cap to both patterns, or who counts hosted nights against an unhosted cap, will mis-track in both directions.

Tracking therefore needs pattern labels. A stay log with a hosted or unhosted column, updated per stay, lets a host isolate unhosted totals, hosted totals and combined totals as each city requires. A log without that column forces a host to reconstruct patterns from memory at year end, which is unreliable and unpersuasive if a city queries a period.

Permits and certifications also follow the distinction. A certification or tier licence for hosted stays does not authorise unhosted stays, and vice versa, where cities separate them. Hosts who change pattern, for example from hosted room letting while living in the property to whole-home letting while away, must check whether a new permit, tier or certification update is needed before operating under the new pattern. Pattern change without permit change is a common multi-city enforcement trigger.

Platform settings follow permits: listing type, guest capacity, and pattern description should match the permit for that pattern. A hosted permit with a whole-home listing, or a whole-home licence with a hosted listing description, creates a mismatch that platforms and cities can spot. Align permit, listing and actual stay pattern as a trio, and update all three together when any one changes.

Neighbour impact differs by pattern. Hosted stays, with a present host managing noise and turnover, generally affect neighbours less than unhosted whole-home stays with frequent turnover and no occupant host. That difference explains why cities treat hosted stays more permissively in some respects, and why neighbour complaints focus more often on unhosted properties. Hosts operating unhosted stays should invest more in neighbour management: local contacts, guest rules, and prompt complaint response.

Safety also differs. A present host can respond to emergencies, alarms and guest issues immediately, while an unhosted property relies on guest knowledge, remote contacts and automated systems. Unhosted hosts should therefore provide clearer emergency information, safety equipment checks and local contact arrangements than hosted hosts need, and should test those arrangements before peak season.

Hosts who operate both patterns, sometimes hosted and sometimes unhosted for the same property, face the most complex tracking. Each stay must be labelled, each pattern's cap or tier condition tracked separately, and each listing version must match the pattern actually offered for those dates. A property listed simultaneously as hosted and unhosted on different platforms, for overlapping dates, creates confusion for guests, platforms and cities alike.

Mixed-pattern hosts should consider separate listing calendars per pattern, with dates clearly allocated, and a single combined stay log that labels each stay. That structure prevents double-booking across patterns and prevents a hosted night being counted as unhosted, or vice versa. Review mixed-pattern properties monthly, not annually, since pattern drift happens quickly.

Label every stay hosted or unhosted at booking, track caps per pattern per city, align permits and listings per pattern, set guest rules per pattern, reconcile monthly, and recheck city guidance for pattern definitions before each season. This guide is general information only, last verified on 26 October 2026.