What the 180-night cap actually is

Under Toronto Municipal Code Chapter 547 (Licensing and Registration of Short-Term Rentals), a registered STR can be operated in one of two modes:

The distinction matters because the rule reads differently depending on which mode applies. Operators running both modes inside the same registered STR only count entire-mode nights toward the 180. Operators running partial-mode only have no night limit at all under this rule.

The cap is calendar-year, not rolling. It resets on January 1 regardless of when the operator's registration was issued, regardless of when in the year the operator started or stopped using entire mode, and regardless of how the operator's own booking calendar runs.

In plain English

If you ever rent out your whole place while you're away, you get 180 of those nights per year before you're in violation. If you only ever rent rooms while you're living there, the 180 doesn't apply to you at all.

What counts toward the cap and what doesn't

The 180-night cap is narrower than it looks at first read. Not every booking on the calendar counts.

Counts toward the 180

Does not count toward the 180

The most common mistake here is counting "available" nights instead of "rented" nights — the inverse of the actual rule. The cap doesn't care how often the property could have been booked; it cares about nights it actually was.

How operators end up over the cap

The 180-night cap doesn't catch operators who are trying to run an aggressive year-round entire-home STR — those operators know what they're doing and structure their year around it. The cap catches operators who weren't paying close attention to a number that, until they crossed it, didn't matter to their business.

Three patterns we see often enough to call out:

1. Heavy January–March cluster

Winter bookings in Toronto are unpredictable. Operators fill what they can fill. A strong Q1 — let's say 50 nights between January and March — eats more than a quarter of the cap before the year's high season has even started. Operators who paid no attention to the cap in years they were comfortably under it suddenly find themselves trying to manage what's left in May.

2. Listings left unblocked through low-yield months

Operators who don't manually manage their calendars often leave summer months open by default. Even short, ad-hoc bookings — three nights here, four nights there — add up faster than the operator counts. The pattern shows up most often in operators who use one platform exclusively and check the dashboard in dollars rather than nights.

3. Permit-year vs. calendar-year confusion

An operator who registered in April assumes the 180-night clock starts from April. It doesn't. The clock starts January 1 and resets every January 1, regardless of when in the year the registration was issued. An operator who started in April and operated heavily through the back half of the year may already have used most of their cap before they're even halfway through their first registration cycle.

The underlying issue

None of these patterns are illegal in themselves. They become a registration issue the moment the entire-mode nights cross 180 in a calendar year. The number is precise, and once it's crossed, the calendar can't be rolled back.

What being over the cap means

Going over 180 entire-mode nights in a calendar year is a violation of Chapter 547. The City has ways to verify night counts through reported data and audit processes. When the count gets flagged, the operator's file moves into the same administrative pathway covered in our Intent-to-Revoke guide — a written notice, a 10-day response window, and a final decision by the City's designated decision-maker.

The City isn't required to send a warning before opening that pathway. The cap is a published rule and operators are expected to know it.

The simpler version: the 180 is a hard line. Operators on either side of it are in very different positions for the rest of the year. Operators who realize partway through a year that they're about to cross it should stop accepting entire-mode bookings — not finish the calendar and hope.

The instinct to "absorb a few extra nights"

The most consistent way operators turn a cap question into a revocation question is by treating 180 as a target rather than a ceiling. The 181st entire-mode night already changes the conversation. The 220th changes it permanently. There is no version of "I went over by a little" that reads neutrally in the file.

How Permit Ready Pros helps

The 180-night cap is one of the things we monitor for clients on a continuous basis. Not because it's complicated — it isn't — but because the operators who get into trouble with it almost always didn't realize they were close. By the time the count gets flagged in a routine review, it's a much harder conversation than the one that would have happened in September if someone had been counting.

What that looks like in practice for our Full Compliance clients:

We're a compliance consulting service — not a law firm. We're honest about what your situation looks like before you pay us anything. If the count you're carrying is already over the line and there's a notice on file, we'll tell you what's realistic in your case and what isn't.

Running close to the cap, or already got a notice tied to it? Reach out — every situation is different. We can take a look at your current count and tell you whether there's still time to land the year compliant.

Stay inside the 180-night cap year-round

Full Compliance is the tier built around continuous tracking — night-count monitoring across platforms, early warnings before you cross the cap, and response support if the City asks.