top of page

Perth Tree Removal Permit Guide 2026

  • Writer: Swift Trees Perth
    Swift Trees Perth
  • May 1
  • 13 min read

You’re usually reading about a tree removal permit when something has already forced the issue. A gum is leaning after a storm. Roots are lifting paving near the driveway. A builder has told you the block needs clearing before work starts. Or you’ve rung council and received three different answers, each wrapped in planning language that doesn’t sound like plain English.


That confusion is normal in Perth. The biggest problem isn’t just whether permits exist. It’s that the rules shift between councils, species, tree size, and the reason for removal. A tree that needs formal approval in one suburb may be treated very differently a few kilometres away.


The practical way to deal with it is simple. Work out whether the tree is likely to be classed as significant, check the local council trigger, then prepare evidence that matches the reason you want the tree removed. When people get into trouble, it’s usually because they skip one of those steps.


Why You Need a Tree Removal Permit in Perth


A tree removal permit is a bit like a building permit for your garden. It’s the formal check that says, “Before this mature tree comes out, someone needs to confirm the removal is justified, safe, and compliant with local rules.”


That can feel like red tape when the tree is on your land. In practice, councils use permits to balance two things that often pull in opposite directions. Property owners need safe, usable land. The wider community also needs shade, habitat, stormwater control, and streets that don’t get stripped bare one lot at a time.


A majestic, wide-canopy tree stands in front of residential houses with the text Protect Perth Trees overlayed.

The permit isn’t just about stopping removals


Perth’s permit system exists to filter out unnecessary removals while still allowing justified work. Western Australia’s tree removal permit system was formalised in the Environmental Protection Act 1986 and local planning schemes since 1995.


That tells you something important. The permit system isn’t there only to say no. It’s there to stop avoidable loss and force proper assessment before mature trees disappear from the urban canopy.


If you want a broader overview of how removal rules work locally, Swift Trees Perth’s Perth tree removal guide is a useful starting point.


Why councils care so much about mature trees


A mature tree does jobs a young replacement can’t do immediately. It throws shade over roofs and paving. It slows runoff. It supports birds and insects. It also changes the feel of an entire street.


In practical arboriculture terms, that’s why councils focus on significant trees rather than every small ornamental in a backyard. The larger the canopy and trunk, the more likely the tree has become part of the area’s amenity and ecology.


Practical rule: If the tree is large enough that neighbours would notice it gone, council may want a say before it’s removed.

Safety still matters


Permits don’t override genuine risk. If a tree has structural failure, root instability, heavy decay, or a target beneath it such as a house, fence, parked vehicle, or pedestrian area, safety becomes the central issue. Good permit systems make room for that.


What doesn’t work is treating every inconvenient tree as a hazard. Councils and assessors usually want evidence. A tree dropping leaves isn’t hazardous. A tree causing blocked gutters isn’t automatically hazardous. A tree with active failure indicators and a realistic target is different.


A permit process is really a decision tool. It separates preference from necessity, and it gives councils a way to protect Perth’s character without ignoring real risks on private property.


A Clear Checklist to See if Your Tree Needs a Permit


Most owners don’t need a legal lecture. They need a reliable way to triage the situation. Start with the points below. If you tick one or more, assume a tree removal permit may be required and check the relevant local rule before any cutting starts.


A person writing on a clipboard in front of a tree and house with a permit checklist

Check the size first


In many Perth councils, the first trigger is whether the tree meets the definition of a significant tree. A common threshold is a trunk girth of 0.5m or more measured at 1m above ground level, or for multi trunked trees a combined girth exceeding 1m. These mature specimens contribute up to 40% of Perth’s canopy cover, as noted in the DBCA urban forest report summary.


Use a tape measure, not a guess. I’ve seen plenty of owners underestimate trunk girth because they’re looking at height instead of circumference.


Quick self-check


  • Measure at the right height. Take the girth measurement at 1m above ground level. Measuring too low, especially near buttress roots, gives a false reading.

  • Check for multiple stems. If the tree splits low, councils may assess the combined girth rather than each stem separately.

  • Look at overall presence. Even where girth is the main trigger, very tall trees can attract closer scrutiny because of canopy impact and surrounding targets.


Check the species and status


Some removals become more complex because of the species involved. In Perth, native trees such as tuart and marri often draw more attention, especially where local planning rules or biodiversity protections apply.


A practical mistake owners make is assuming a dead native tree is automatically exempt. It often isn’t. Species protection and local planning controls can still apply.


Check where the tree sits on the block


Location matters almost as much as size. A tree near a boundary, close to a dwelling, within a streetscape setting, or part of a redevelopment site is more likely to trigger assessment.


Use this location checklist:


  • Near structures. If the tree overhangs a roof, power service line, shed, pool area, or retaining wall, council may want a documented risk basis for removal.

  • Near the boundary. Trees affecting neighbouring land often create disputes. That doesn’t make them removable by default, but it does make evidence and documentation more important.

  • Part of a development site. If a builder, site development contractor, or demolition contractor is involved, planning conditions may apply before machinery even arrives.


A tree can be inconvenient without being approvable for removal. Councils usually respond better to documented defects, structural conflict, or approved development needs than to preference alone.

Check the reason for removal


The reason you give matters. “I want more light” is very different from “the root plate has lifted and the stem is moving under wind load”. One is subjective. The other can be inspected, photographed, and assessed.


These reasons are usually worth documenting clearly:


  1. Hazard concerns Include lean, cracking, cavities, dead scaffold limbs, root heave, or repeated branch failure.

  2. Building conflict Foundations, paving, drainage, fences, and approved building envelopes can all be relevant, but the conflict should be specific.

  3. Tree decline Dieback, fungal fruiting bodies, sparse canopy, or major deadwood may support the case if the decline is advanced.


When to stop guessing


If the tree is mature, native, close to a structure, or in a council area known for strict assessments, don’t rely on hearsay. Rules that apply in one street often don’t travel well to the next suburb.


The fastest way to avoid a bad decision is to assess the tree the way council will. Measure it properly, identify the species, note the site constraints, and match the reason for removal to observable evidence.


Navigating Different Council Rules Across Perth


The hardest part of the Perth tree removal permit process isn’t the form. It’s the patchwork. Owners hear “you need a permit” from one person and “not in this council” from another, and both may be right depending on the address.


That inconsistency is a real issue.


Perth Council Tree Permit Rules at a Glance (2026)



Why one suburb says yes and another says wait


Councils don’t all start from the same planning context. Inner urban councils tend to focus more on established streetscape, canopy retention, and redevelopment pressure. Outer councils may place more weight on different land use patterns, hazard management, or lower density residential blocks.


That’s why generic advice causes problems. “Trees under this size are fine” might be true in one area and wrong in another. “Dead trees never need a permit” is another common oversimplification that gets owners into trouble.


What usually changes from council to council


  • The trigger point. One council may use trunk girth. Another may use height, heritage listing, boundary impact, or planning overlay.

  • The documents required. Some councils want a straightforward application and photos. Others expect an arborist report, scaled site plan, and replacement proposal.

  • The exemption pathway. Emergency provisions can exist, but the threshold for using them properly varies.


What works in practice


Start with the site address. Confirm the local government area. Then test the tree against that council’s trigger before discussing removal options.


What doesn’t work is treating “Perth rules” as one single set of rules. They aren’t.


The address matters as much as the tree. Two similar marri trees can face different approval pathways because the local planning scheme is different.

For owners managing multiple properties, this matters even more. Strata managers, builders, and real estate agents often assume the paperwork can be reused from job to job. Sometimes the supporting material can be adapted, but the approval path still has to match the council.


Your Step-by-Step Guide to the Permit Application


Once you know a permit is likely required, the process becomes much easier if you treat it like a sequence instead of one big administrative task. Most stalled applications fail for the same reason. The owner submits too early, before the evidence is organised.


A five-step infographic guide detailing the process for applying for a local tree removal permit.

Start with the site and the rule


Before any form is lodged, confirm the exact council and the rule that applies to your address. That sounds obvious, but plenty of wasted time comes from reading the wrong council page or relying on old advice from a previous property.


Then identify the tree properly. Record the species if known, trunk size, location on site, and the reason removal is being sought. Clear photographs help from the start because they force everyone to talk about the same tree and the same defect.


Gather the documents before you submit


Across major Perth councils, permit processing times average 20 to 30 business days for standard applications. Where significant native trees such as tuart or marri require detailed arborist reports and public consultation, the process can extend to 60 days, according to WA local government reporting.


That timeline is why preparation matters. If the application goes in half complete, the clock rarely helps you. It usually slows you down because council comes back asking for more detail.


The core documents often include:


  • Application form. Complete every field that relates to the tree, the owner, and the reason for proposed removal.

  • Site plan. Show the tree in relation to the house, boundaries, crossover, paving, retaining walls, and nearby targets.

  • Photographs. Use wide shots and close-ups. Good photos show scale, defect location, and target area.

  • Arborist assessment. This becomes especially important when the argument is based on safety, structural defect, or species-specific issues.


If timing matters for a project, it also helps to plan the work window properly. This guide on the best time to remove trees in Perth can help you line up approval timing with practical site access and seasonal conditions.


Submit to the right department


Different councils route these applications through planning, parks, development services, or local laws. That internal pathway is council-specific, which is another reason generic online advice often misses the mark.


When the application is lodged, keep a copy of everything. If council asks follow-up questions, answer them against the original material rather than rewriting the case from scratch.


A clean submission usually includes


  1. The correct property details

  2. The correct tree identified on the plan

  3. A clear reason for removal

  4. Evidence that supports that reason

  5. Any replacement or mitigation detail required by council


A permit officer can’t approve what they can’t verify. If the tree, defect, or site impact isn’t obvious on paper, expect questions.

What happens during review


Council may assess the paperwork only, or they may inspect the site. In some cases they’ll ask for more evidence, particularly if the justification is weak, the species is protected, or neighbours may be affected.


Approval can come with conditions. Those conditions might limit the scope of work, require replacement planting, or set a timeframe for when the work must be carried out. Read those conditions carefully before booking machinery or a removal crew.


If the permit is refused


A refusal doesn’t always mean the tree can never be removed. Sometimes it means the application didn’t prove the point strongly enough. Other times, council may support pruning, canopy reduction, monitoring, or root management instead of full removal.


That’s where a lot of owners lose momentum. They assume refusal means the end of the road, when often it means the evidence or proposed management approach needs to change.


Assembling a Winning Application Package


The strongest tree removal permit applications don’t read like sales pitches. They read like evidence. That’s the difference between a package that moves smoothly and one that sits in a review queue while council asks basic follow-up questions.


An assessor usually wants to answer three things quickly. Which tree is being discussed. Why removal is being requested. Whether the evidence supports that request.


The arborist report carries most of the weight


If there’s one document that changes outcomes, it’s the arborist report. It identifies the defect, explains the risk, links the defect to the target, and sets out why removal is preferred over pruning, monitoring, or retention.


The most useful reports tend to include:


  • Clear tree identification. Species, dimensions, and precise site location.

  • Observed defects. Decay, included bark, cracking, root plate movement, dead scaffold limbs, heaving soil, stem damage, or significant decline.

  • Target assessment. What the tree could strike if it fails, and how often that target is occupied.

  • Management options. Removal, staged reduction, pruning, habitat retention, exclusion zones, or monitoring, with reasons for the recommended option.


Photos and plans need to do real work


Owners often attach photos that prove only one thing: there is a tree. That isn’t enough. Photos need to show defect detail and context. A close-up of a cavity matters. So does a wide shot showing the cavity over a car bay, pedestrian path, or roofline.


The same applies to the site plan. Councils want orientation. They need to see where the tree stands relative to structures, boundaries, and surrounding constraints. A rough hand sketch can be enough in some cases, but only if it’s legible and accurate.


Good documentation reduces argument. The stronger the visual record, the less room there is for misunderstanding.

What usually weakens an application


A weak application often has one of these problems:


  • The reason is emotional rather than assessable. “It’s too messy” won’t carry much weight.

  • The defect is asserted but not shown. If root damage or instability is claimed, the supporting evidence needs to be visible or professionally described.

  • The tree is large and native, but the paperwork is thin. That mismatch often leads to requests for more information.


What councils respond to best


Councils usually respond best when the file is organised, specific, and proportionate to the tree involved. A modest backyard ornamental may need straightforward supporting material. A mature native tree near a boundary or development site usually needs a more disciplined submission.


In practice, the winning package is the one that saves the assessor time. It gives them a clear factual basis to approve, condition, or refuse the work without having to guess what the applicant really means.


Understanding Permit Costs and Penalties


Most owners focus on the cost of removal. Fair enough. But the permit side matters because it changes the total risk of the job.


There are usually two categories of cost. The first is the legitimate cost of doing the process properly. The second is the much uglier cost of getting it wrong.


The normal costs of compliance


Depending on the council and the tree, you may be dealing with an application fee, the cost of an arborist report, and sometimes replacement or bond conditions. Those aren’t pleasant extras, but they’re predictable.


For budgeting the physical removal itself, this Perth tree removal cost guide is a useful companion to the permit side of the job.


Typical compliance costs may include:


  • Council application fees. These vary by local authority and the kind of assessment involved.

  • Arborist documentation. More detailed reports are usually required when the tree is significant, native, hazardous, or linked to development.

  • Replacement conditions. Some approvals require replanting or other mitigation after removal.


The cost of non-compliance is worse


In Perth, unpermitted removal can attract serious penalties. Verified local data shows fines can reach $50,000 for significant trees, with enforcement action taken in multiple cases across Perth suburbs and substantial penalties issued under planning controls. That’s before you factor in delays to a build, neighbour disputes, or having to defend an avoidable mistake.


There’s also a hidden cost owners often miss. If a tree is removed before approval and the site later enters a planning process, the missing tree can become part of the problem. What looked like a shortcut at the start can complicate the next approval stage.


Why permits are usually the cheaper path


A proper permit pathway gives you clarity. You know whether the tree can come out, what conditions apply, and what supporting documents you need before machinery arrives. That’s far cheaper than paying for rushed works, legal headaches, or failed scheduling because council has stepped in after the fact.


The permit is part of risk management. It protects the owner as much as the tree.


Perth Tree Permit Questions Answered


Some of the most important permit questions come from edge cases. The tree is dead. A storm has split it. Your neighbour says it’s your problem. These aren’t unusual situations, but they’re the ones where bad assumptions cause the most grief.


Do I need a permit for a dead tree


Sometimes yes. A common point of confusion is the rule for dead or hazardous trees. Protected native species like tuart and marri may still require a permit from the Department of Biodiversity, Conservation and Attractions even if dead, while a non-native tree posing an imminent, certified risk can often be removed under emergency provisions without the full planning pathway, as outlined in DBCA guidelines for WA tree permit situations.


That means “dead” is not the whole test. Species and local controls still matter.


What about a tree that’s dangerous after a storm


Emergency removal can be allowed where there is an immediate and properly documented risk. The key word is documented. Take clear photos before work starts if it’s safe to do so, record what failed, and keep any written advice from an arborist or contractor.


Don’t stretch the emergency category beyond what it really covers. A storm-damaged tree with active splitting over a driveway is one thing. A tree that merely looks rough after wind is another.


If the tree can wait safely for assessment, treat it as a standard permit matter. If it cannot wait safely, document first and act within the emergency pathway that applies.

Can I remove a neighbour’s tree if it crosses the fence


No, annoyance alone does not justify it. Boundary issues and overhangs are common, but they don’t erase permit rules or ownership rights. If the tree is protected, significant, or subject to local controls, those issues still need to be handled lawfully.


The practical route is usually to document the problem, speak with the neighbour, and get professional advice on whether pruning, root management, or a formal application is the proper next step.


Do fallen trees need a permit


If a tree has already failed completely, the permit question often shifts from “can it be removed” to “what still needs to be reported or documented”. Councils may still expect notification, especially if the failed tree was protected or if the stump, root plate, or replacement obligations remain relevant.


What should I do first if I’m unsure


Do three things in order:


  1. Photograph the tree and surrounding area

  2. Confirm the council area and whether the tree appears significant or protected

  3. Get an arborist opinion before authorising major cutting


That sequence avoids the most common mistakes. It also gives you a usable record if council, an insurer, or a neighbour later asks what happened and why.



If you need help working out whether a tree removal permit applies, or you want the job assessed properly before you speak to council, contact Swift Trees Perth. We can help with practical tree maintenance advice, hazard assessment, documentation support, and safe tree work across the Perth metro area.


Comments


bottom of page