Toronto Tree Removal: 4 Mistakes Homeowners Make (And How to Fix Them)

Toronto's tree rules can change. The City's permit page has the latest details.

In Toronto, the thing standing between you and that tree in your yard is a set of rules most homeowners don't know exist until they're already in trouble. The mistakes are expensive, sometimes in fines, sometimes in neighbours who won't speak to you again, sometimes in months of delay on what you thought was a Saturday job. 

To sort out what actually trips homeowners up, we talked to three Toronto arborists: Jason Francis of Amazing Tree Service, Chris Bark of Bark Brothers Tree Care, and Michael Addison of Mikey's Tree Care. Here are the four assumptions that cause the most grief.

"It's my tree, on my property, so I can cut it."

Not necessarily, and even if it is your tree, that doesn't mean you can take it down without permission.

Under Chapter 813 of the Toronto Municipal Code (the Toronto tree bylaw), you need a permit to injure or remove any private tree that's 30 cm or more in diameter. That's not a large tree. A healthy maple can hit that size in twenty to thirty years. If the trunk looks borderline, measure before you assume. If your property backs onto a ravine (check with this tool), the rules are even stricter. 

Jason says mid-project discovery of needing a permit happens more than people expect. When that happens, the work stops, the paperwork starts, and you are suddenly negotiating with the City.

The tree itself may not even be yours. Street trees are City-owned and protected at any size, regardless of how close they are to your property. Call 311 if you're not sure where the line falls. 

Michael Addison says this catches people constantly. "About 80% of the front-yard trees people call us about turn out to sit on the city easement, which means the city owns them." If that's your situation, there's an upside: you can ask the City to do the work, and they'll do it on their own schedule at no cost to you. You don't get to dictate exactly what happens, though. Their arborist decides whether the tree gets trimmed, left alone, or taken down. A private company can apply for authorization to work on a City tree, but the administrative time gets billed on top of the trimming, so it's rarely worth paying for something the City will eventually do for free.

"The neighbour's branches are over my yard, I'll just cut them."

You can trim back to the property line. You can't cross it, you can't step into their yard to do the work, and you can't kill the tree in the process.

Chris puts the rule plainly: "Whatever's over the fence is considered your tree, and you're able to do whatever you need to do to it within arboricultural standards." If a branch hanging over your yard falls and damages something, it's generally your insurance on the hook, though this is worth confirming with your insurer since policy specifics vary.

If the trunk itself straddles the line, the tree is jointly owned, and you need the neighbour's consent to do anything to it. If they say no, that's the end of it. The City won't mediate for you.

According to Jason, the neighbour-tree dispute is the most common conflict he sees, and it almost never starts with bad intent. Someone hires a crew, assumes the tree is theirs, and gets it trimmed or taken down. The neighbour comes home, sees what's happened, and that's when everyone discovers nobody actually knew where the property line was.

Most cases don't end up in court. Both sides gather what they have (surveys, photos, permits, arborist reports) and try to figure out what happened. If a mistake was made, there's usually some negotiation over compensation. Sometimes everyone agrees on a way forward and moves on. Sometimes the dispute drags on for months and the fence-line relationship never recovers.

"The roots are wrecking my foundation, so the City has to let me remove it."

The City's position on this is direct, “Tree roots do not cause lifts or cracks in properly-constructed and well-maintained infrastructure.” 

The pattern Jason sees is consistent. A homeowner notices cracks, sees a large tree close to the house, and assumes the two must be connected. By the time an engineer or arborist actually investigates, the story is usually more complicated. The cracks have company: poor drainage, an aging foundation, a leaking service line, soil that's been settling for years. 

Chris describes what a real diagnosis looks like: "You would need to have someone do an exploratory dig, a small one, just to see if the roots are right next to the foundation, and then have a structural engineer do a report saying yes, this is the problem." His point: an arborist alone can't tell you the tree is the cause. That's an engineer's call.

Michael Addison's experience lines up. In years of work he's seen only a couple of cases where a tree actually damaged a foundation. What trees more reliably wreck is everything lower-stakes and closer to the surface: old clay sewer pipes, ground-level hardscaping, retaining walls. Foundation cracks, he says, are far more often the work of settling, and roots rarely start a crack on their own. Where they do harm is an opening that's already there: a root finds an existing crack and widens it over time.

That doesn't mean trees never damage foundations. They sometimes do. It means the evidence usually points to several factors working together, and the City wants to see that evidence before signing off on removing a mature tree.

"Once I get the permit, I pay, I cut, I'm done."

A removal permit is conditional on replanting. The replacement tree is protected by the bylaw from the day it goes in the ground. Cash-in-lieu, $583 per tree, only applies when your lot genuinely can't fit a replacement. It isn't a fee you can choose to pay instead of planting. The City requires the new tree wherever there's room, and only takes the money when there isn't.

Jason says most homeowners aren't thinking about any of this when they first call. "It's usually just 'this tree is a problem, get it out.' The idea that they might have to plant a new one, or pay for one, often doesn't come up until later, sometimes after the permit process starts."

Once it does, the math changes. Removal stops being a one-time fix. And the replacement isn't a sapling from the garden centre. Michael Addison points out that the City wants a 50-millimetre tree, which with its root ball runs 300 to 400 pounds. "Almost nobody is planting that themselves." Supplied, delivered, and planted, he puts it around $1,250 plus HST. He's quick to add that this isn't money down the drain: a good mature tree is an asset, and the replacement becomes one too. But it does mean removal is rarely the cheap, clean fix people picture. Between the takedown, the stump, and the new tree, the costs stack up.

For a tree that's genuinely hazardous or causing real damage, none of that changes the decision. For a tree that's more in the "annoying" category, the added cost is sometimes enough that it's worth considering whether you can leave it alone, or just prune it.

What the process actually looks like, start to finish

The order most homeowners assume, call a tree company, get a quote, deal with the City afterward, is backwards. 

Before any of this, settle one question: whose tree is it? If it's in your backyard, it's almost certainly yours, and the steps below apply. If it's in the front yard, call 311 first to confirm ownership. Everything that follows assumes the tree is actually yours to deal with.

Here's the order that works once you have confirmed ownership:

1. Decide whether the tree is a real hazard or just an inconvenience. This shapes everything downstream, including whether the City will approve the removal at all.

   
   

2. Call a certified arborist for an assessment. Sometimes it's a site visit; sometimes it's a written report. An arborist report is a mandatory document in the permit application, so the professional comes before the paperwork. Chris says the level of detail required by the city usually results in the assessment being around $500.

   
   

3. Submit the permit application. Online or in-person. If it's a boundary or neighbour-tree situation, there's a 15-business-day notice to the other owner, then a second notice at least 15 days before the permit issues.

   
   

4. Wait on the City review. This is the step that surprises people. In Jason's experience, "that inspection phase is what slows everything down the most. Not the arborist, not the homeowner, and not even the tree company, it's waiting for the city to actually come out, review the situation, and sign off." The wait runs from a couple of weeks to over a month, depending on the City's backlog and the complexity of the case.

   
   

5. Book the removal. Only after approval. Skipping ahead doesn't save time; it lands you back at the City stage with the work half-done.

   
   

Start to finish, expect weeks, not days. Plan around that.

And if your tree just needs pruning?

No permit is needed to prune, as long as it's done to good arboricultural practice and the goal is the tree's health. That's the real space where you can work without a permit and, if the job is modest, without a pro.

The signs you can judge yourself are the obvious ones: clearly dead branches, limbs rubbing the roof, anything growing into hydro lines. Some problems need a trained eye: internal decay, root issues, structural weakness in the canopy. None of that is visible from the ground. If you're not sure which category you're in, an arborist visit is cheaper than guessing wrong.