San Francisco Short-Term Rental Certification, Explained

San Francisco short-term rental hosts must obtain certification through the city's process, administered with city guidance on sf.gov, before operating short-term rentals in the city. Certification creates a city record that platforms verify, and it is tied to the host, property and hosting pattern described in the application. A host who lists without certification, or whose certification does not match the actual hosting pattern, faces platform blocking and city enforcement.

Certification is not a general San Francisco business licence that covers any rental activity. It is specific to short-term rental hosting as defined by the city, for the property and pattern certified. Hosts should read the certification scope for their property carefully, and should not assume that a certification for one property or pattern covers another.

Certification applicants are typically hosts who live in the property as a primary residence, with hosted and unhosted patterns treated differently under city rules, including the 90-night cap for unhosted stays covered in its own guide. Hosts should confirm, from current sf.gov guidance, which pattern they fit: hosted, where the host is present, or unhosted, where the host is away but the stay remains within permitted limits. Misclassifying the pattern at certification stage creates a mismatch that later stays will expose.

Property type matters too. A single-family home, a condo unit and a multi-unit building unit may face different building, condo or lease conditions in addition to certification. Check building and lease permission before certifying for a pattern that the building forbids, since city certification does not override a building ban.

Apply through the San Francisco process described on sf.gov, following current forms and instructions, since forms change. Prepare primary-residence and property details, operator details and building notes before starting, and save the application confirmation and certification on receipt. If the city queries the application, answer the specific query with documents, rather than resubmitting unchanged details.

While certification is pending, do not list the property as certified, do not display a certification number not yet issued, and do not take covered short stays that depend on certification. A pending application is not certification. Hosts who need income during a pending period should consider lawful longer stays where applicable, rather than short stays requiring certification.

Once certified, add certification details to listings exactly as issued, on every platform, and check public display as a guest would. Platforms verify certification and may hold listings where details mismatch. A common mismatch is address format or host name differing between listing and city record; copy details from the certification, not from memory, and update listings the day certification details change.

SB 346 disclosure adds a city data layer: San Francisco, like other California cities, can compel platforms to disclose listing address, URL and parcel details and to carry licence and transient occupancy numbers. Hosts should therefore keep listing details aligned with city records, since disclosure makes mismatches visible to the city without a complaint.

Certification validity, renewal and update rules follow city guidance, which hosts should record with reminder dates. Changes in residence, property, hosting pattern or building situation may require an update or new certification. Check the update rule before operating under a changed pattern, and start renewal before expiry to avoid a lapse during which platforms may block listings.

Pattern drift is a particular risk: a hosted operation that gradually becomes unhosted, or an unhosted operation that exceeds its cap, drifts from its certification. An annual pattern review, comparing actual stays with the certified pattern, catches drift before it becomes enforcement. Note that review, with its date, in the property file.

Confirm pattern, building and lease permission, complete certification on sf.gov, align listings, set up stay and cap tracking, reconcile monthly, and recheck city guidance before each season. This guide is general information only, last verified on 26 October 2026.

Certification proves that the city has a record for the host and property as described in the application. It does not prove that a particular stay complied with that description, that building rules allowed the stay, that tax was correctly handled, or that neighbours were undisturbed. Each of those questions needs its own evidence: stay logs for stays, building permission for building, tax records for tax, guest management notes for neighbours. Hosts who present a certification as an answer to every question will be asked for the missing evidence anyway, and will have lost time.

That limit is worth stating plainly because certified hosts sometimes relax after certification, assuming the hardest step is done. Certification is the beginning of compliant operation, not its completion. The monthly habits that follow, stay logging, cap tracking, listing checks, tax reconciliation, are what keep a certified operation certified in substance. A certification with no operating records behind it is a certificate looking for a file.