New York City Local Law 18 Fines and Enforcement

Local Law 18 enforcement in New York City is led by the Office of Special Enforcement, with platforms also required to verify registration and remove unregistered listings. This guide does not state a fine tariff, because penalties depend on the breach, history and process, and a single figure would mislead. The general picture is that unregistered letting, absent-host letting under 30 days, guest-limit breaches and false registration details are enforcement priorities, and consequences can include fines, listing removal and orders affecting future hosting.

Enforcement is data-assisted. Platform verification, listing data and complaint reports give OSE a picture of which units are let, how often, and under what registration. A host should assume that a visible listing is a visible record, and that a pattern of unregistered or non-compliant letting will surface through data as well as through complaints. Invisibility is not a compliance strategy in a data-reported system.

Triggers include listings without OSE registration, listings with a registration that does not match the unit, hosted claims contradicted by occupancy evidence, guest counts above 2, and neighbour complaints about turnover, noise or building impact. Complaints are a particularly common trigger: a neighbour who notices frequent short-stay turnover in a building may report it, and that report can prompt a check of registration, presence and guest records for the unit.

Platform data can also trigger enforcement without a complaint. A unit let frequently through platforms, with a registration gap or a pattern inconsistent with hosted stays, may be identified through reported activity. Hosts should therefore keep their own stay logs consistent with platform activity, so any data-triggered query can be answered from records rather than reconstructed.

If OSE contacts a host, read the enquiry fully, note deadlines, and gather the unit file: registration confirmation, listing views, stay log, guest lists, building permission and presence notes. Answer the specific questions asked, with documents, rather than sending a general letter about hosting. If a factual error is identified, correct it promptly and document the correction. If the enquiry turns on classification or presence, describe the actual pattern honestly and seek advice where the answer is complex.

Do not continue allegedly non-compliant letting while disputing an enquiry without advice. Continuing can add further breaches and worsen the outcome. Pausing covered short stays while the matter is resolved, and considering lawful longer stays where applicable, is usually wiser than accumulating exposure. Keep all OSE correspondence and note every date.

Platform removal often arrives before or alongside OSE action. A listing removed for lack of registration should be treated as a registration problem to fix, not as a platform dispute to win by re-listing. Re-listing the same unit under different details to bypass removal can be treated as evasion and can worsen enforcement. The correct sequence is to fix registration or presence, confirm verification, and then seek reinstatement through the platform's stated process.

Hosts should keep platform removal messages with OSE correspondence, since the two together tell the full story of an incident. A host who can show a removal, a fix and a reinstatement, with dates, demonstrates diligence. A host who can show only repeated removals without fixes demonstrates the opposite.

Repeat breaches escalate in seriousness and in platform consequences. A second unregistered period after a first warning, or continued absent-host letting after a presence query, will be treated as deliberate rather than mistaken. Platform account standing can also suffer across properties, not only for the unit named. Portfolio hosts should audit all units after any enforcement contact, to ensure the same defect does not exist elsewhere.

That audit should cover registration, presence claims, guest limits, listing capacity and building permission for every unit. Fixing only the named unit while leaving a sibling unit with the same defect invites a second case that could have been prevented. Brief managers on the lesson as well, since manager-created listings are a common source of repeat defects.

Prevention is registration complete, presence genuine, guest limit enforced, listings accurate, stay logs monthly, and building permission checked. Add neighbour management: clear guest rules, a local contact, and prompt response to concerns. Those habits answer most enquiries before they start. Recheck OSE guidance on nyc.gov before each season.

This guide is general information only, last verified on 26 October 2026, and is not legal advice for a specific enforcement case.