The Napa County Tree Ordinance: Permit Triggers, Protected Species, and Liability for Attorneys, Developers, and Property Owners

Protected Species

Napa County's ordinance protects trees through three parallel pathways — by oak species and overlay-zone status, by riparian setback, and by valley-oak agricultural status. On unincorporated Napa County parcels, any tree meeting any one of the thresholds below is protected, and the thresholds do not stack — a permit is required once a tree meets one of them. Removal without a permit, or removal of the wrong tree because the field identification collapsed the OW overlay and riparian setback distinction, is the most common pathway into a code-enforcement file. The protected species lines below are taken from the reference data on which this page is built; the same figures appear in the North Bay Tree Ordinance Reference. For a plain-language property-owner walkthrough of when a permit is required, how DBH is measured, what counts as a heritage tree, and how multi-trunk trees trigger protection, see the companion Tree-Protection Ordinance FAQ. Napa's canopy context — coast live oak and valley oak in the OW overlay, riparian bay/willow/cottonwood in the 100 ft. setback, and the broader North Bay species mix under recent drought stress — is summarized in the North Bay Urban-Forest Health 2025 brief.

• All oak species ≥ 5" DBH inside the Oak Woodland Combining District. Napa uses a 5" threshold — the lowest in the North Bay. Coast live oak, valley oak, black oak, and interior live oak are the four oaks most often seen on Napa hillsides. The trigger is keyed to the OW overlay rather than to the parcel itself; a 5" oak on a parcel outside the OW overlay is not protected for this reason. PBES reads the OW overlay map against the parcel APN at permit intake.
• Riparian trees ≥ 6" DBH within 100 ft. of a mapped stream. Napa's riparian setback is species-agnostic — bay laurel, willow, cottonwood, alder, and other species are all protected at 6" DBH where the tree sits within 100 ft. of a mapped stream, lake, or wetland. The 100 ft. is a horizontal setback measured from the stream bank or the ordinary high-water mark, not from the parcel line. Riparian review often triggers the Army Corps 404 / Regional Board 401 process where the project crosses waters-of-the-U.S. threshold.
• Valley oak (Quercus lobata) at any size on Agricultural Preserve / Agricultural Watershed land. Napa's any-size valley oak rule applies to Agricultural Preserve and Agricultural Watershed designated parcels — the same designation under the Williamson Act that frames much of Napa's vineyard acreage. A sapling valley oak inside an Ag Preserve is protected even though it sits well below 5" and well below 6". This is the threshold most often missed on vineyard-conversion and winery-expansion projects.
• General Plan Natural Resource Area overlays. Napa carries mapped Natural Resource Areas in the General Plan — habitat reserves, biological corridors, and water-supply watersheds. Disturbance within an NRA requires review under the County's Conservation, Development and Planning review even where no oak or riparian triggers apply, and the BRE requirement is the same. The NRI / Natural Resource Inventory is the controlling document at permit review.

Napa's overlay-driven thresholds are meaningfully different from Marin's and Sonoma's single-parcel species thresholds. A property owner who treats a 4" oak outside the OW overlay as a non-protected tree, then learns that the riparian setback attached to a downstream channel, has the same enforcement exposure as someone who removed a sapling valley oak on Ag Preserve land without checking the overlay map first. Verifying all three overlay statuses — OW designation, riparian setback, Ag Preserve / Agricultural Watershed — against the County GIS, and getting a written confirmation from an ISA-certified arborist, is the single most reliable way to avoid both.

Napa's species mix varies enough by parcel that an arborist walk should precede any vineyard-conversion or winery-expansion removal planning. PBES will not accept a contractor's verbal identification as evidence that a tree sat outside the protected-species lines.

Permit Triggers

A Napa County tree permit is required when any of the four triggers below is met. Napa reads § 18.108 in conjunction with the General Plan Natural Resource Area overlay and with the County's discretionary-permit framework, so a trigger drawn from vineyard conversion, winery expansion, or riparian restoration — even if the tree itself is being left in place — can still require a Biological Resource Evaluation and an arborist report through PBES.

For development projects, the permit trigger for construction-adjacent work attaches at the entitlement stage — before the grading permit is pulled and well before the building permit is issued. Waiting until framing or rough grading to engage an arborist is the most common pathway into a project-condition revocation. Documentation written before the equipment enters the site is the documentation that holds up under inspection and, if necessary, under cross-examination.

Removal Procedures

The Napa removal procedure is administered through PBES with the Conservation, Development and Planning Division reviewing the discretionary end. A complete application typically includes the items below — and the application does not move forward until each is in writing.

• Pre-application consultation with PBES. Napa PBES offers a pre-application consultation for any project involving a discretionary permit, vineyard conversion affecting trees, riparian setback work, or disturbance within a General Plan Natural Resource Area. The pre-app meeting is not formally required for a single oak removal, but it is the only venue where PBES staff will give informal written feedback before the formal submittal — and informal feedback is dramatically cheaper to incorporate than corrections during permit review.
• Biological Resource Evaluation with arborist component. Napa requires a BRE — distinct from a stand-alone arborist report — for any discretionary permit that touches a protected tree, riparian setback, or Natural Resource Area. The BRE combines biologist and arborist findings; the arborist component identifies species, DBH, health/structure, and protected-status against the current OW overlay and riparian setback maps. The BRE is reviewed alongside the underlying discretionary permit rather than as a separate submittal.
• Written arborist report from an ISA Certified Arborist. The report must include a tree inventory with species, DBH, and health/structural condition; a protected-status determination for each tree — including the OW overlay, riparian setback, Ag Preserve / Agricultural Watershed, and any General Plan NRA overlay; a recommendation on removal, pruning, or retention; and — for construction-adjacent removals — a Tree Protection Plan covering the trees being retained. PBES does not accept reports from non-ISA-certified consultants for protected-tree permitting.
• Army Corps 404 / Regional Board 401 coordination for riparian work. Where a riparian removal or grading activity crosses waters-of-the-U.S. thresholds, the County requires Section 404 / 401 coordination to run in parallel with the County's discretionary review. The County rarely approves tree removal in the 100 ft. riparian setback without a clean 404 / 401 finding, and the public-notice posting on the federal side often outpaces the County's process.
• Site plan, photograph set, and replanting plan. Napa attaches the tree permit to the discretionary-permit lane rather than reviewing it as a stand-alone application; the same substrate of documentation is required, with the replanting plan reviewed against the County's 3:1 valley-oak / 2:1 other-oak standard and against the County's $500–$1,500 / inch DBH in-lieu fee schedule. A photograph set with at least two angles per tree and reference markers visible in the frame is the County's standard.
• Public notice and conditions of approval where discretionary review applies. Napa's discretionary review carries its own public-notice posting and a hearing before the Planning Commission, Conservation, Development and Planning. Conditions of approval are issued as part of the discretionary permit, conditions that the County can revoke at its discretion if § 18.108 review surfaces unpermitted work on the parcel — independent of any stand-alone tree permit.
• Post-removal replanting at 3:1 valley oak / 2:1 other oaks. On-site replacement at the County's two-tier ratio is PBES's default — 3:1 caliper-inch for valley oak, 2:1 for other oaks. Where on-site planting is infeasible — vineyard redevelopment, subdivision setback, documented hardship — an in-lieu fee path is available; the fee is set by County resolution and is paid into the tree-replacement fund at the County's $500–$1,500/inch DBH rate. Fees are not a waiver; they are an alternative path with their own documentation requirement.

For projects that involve multiple trees — or that touch both the OW overlay and a riparian setback review — scheduling the application to align with the design team's entitlements submittal avoids the situation where the tree review is the long pole on the permit timeline. Tree review on straightforward removals runs a single review cycle; riparian reviews with 404 / 404 coordination, and discretionary entitlements on vineyard conversion, typically run two to three review cycles.

Liability Exposure

Liability under the Napa County tree ordinance sits on three tracks. Each track has its own evidence rules, its own limitation period, and its own preferred documentation format. The arborist who writes the contemporaneous record is the same person who, in many cases, will be asked to defend that record years later — which is why independent arborist documentation, captured before any dispute crystallizes, is the artifact that survives.

Civil Code § 3346 — neighbor damage claims. California Civil Code § 3346 governs civil liability for damage caused by the failure of a tree. Foreseeability is the controlling concept: if the tree owner knew or should have known that the tree posed an unreasonable risk of failure, liability attaches. The contemporaneous arborist record — written before the failure, not after — is the strongest evidence on foreseeability, particularly on a parcel inside the OW overlay or the riparian setback where the owner's failure to commission a § 18.108 review is itself relevant to actual knowledge. A TRAQ-level report written for a Napa PBES permit application two years before a failure is materially stronger evidence on the owner's actual knowledge than an arborist report commissioned after the claim has been filed. The companion arborist-disputes guide walks through the full evidence chain for property-damage claims.

Insurer subrogation posture. When a tree falls across a property line and the homeowner's carrier pays a property-damage claim, the carrier's subrogation investigation typically reaches for arborist documentation six to twelve months after the loss — by which point the original site conditions have changed substantially. A pre-existing TRAQ assessment, written for an unrelated reason (a BRE submittal, a vineyard-conversion due-diligence engagement, HOA portfolio review, or a § 18.108 review), is the single strongest counter to a subrogation claim that the failure was foreseeable and preventable. The subrogation-report guide outlines the five non-negotiable report elements that survive that post-loss review.

Code-enforcement liability. Removal without a permit, or removal of a tree whose protected-species status was misidentified against the current OW overlay, riparian setback, or Ag Preserve maps, exposes the property owner to administrative fines under Napa County Code § 1.36, project-condition revocation on a pending discretionary permit, mandatory revegetation at the 3:1 valley-oak / 2:1 other-oak caliper-inch formula, and full site restoration at the applicant's expense. The § 18.108 enforcement record is a public record; it follows the parcel through any subsequent sale and can affect the discretionary-permit posture for years. The same is true of stand-level restoration required after a riparian-setback or vineyard-conversion violation.

For projects where the boundary between permit triggers and civil liability is genuinely blurred — vineyard conversion adjacent to a riparian setback, or a valley-oak removal on Ag Preserve land where the project later fails — the contemporaneous arborist documentation is the only evidence that resolves both tracks at once. The companion Tree Protection Zones guide covers the construction-adjacent side, and the North Bay Tree Ordinance Reference places Napa's § 18.108 in context with the surrounding nine jurisdictions.

Enforcement & Penalties

Enforcement under § 18.108 is administered through PBES with the Code Enforcement division handling the underlying violation. The two pathways interact: a permit denial does not exempt the property owner from enforcement on the trees affected by the unauthorized work, and an enforcement action does not automatically convert into a permit approval for the same trees.

• Administrative fines under Napa County Code § 1.36. The base penalty is set by § 1.36 and is applied per violation rather than per parcel. Repeat violations compound rather than resetting at a single per-tree ceiling, and a vineyard-conversion project that hits multiple § 18.108 triggers can carry meaningful budget exposure across more than one jurisdiction or penalty track.
• Revocation of project conditions on discretionary permits. Where the unpermitted work touches a discretionary entitlement — a use permit, a vineyard-conversion EIR, or a winery-expansion modification — PBES has the authority to revoke or condition the entitlement independently of any stand-alone tree permit. The revocation power is the practical lever behind § 18.108: a property owner who ignores a stop-work or a Code Enforcement finding can find the underlying discretionary permit rolled back to a clean permit cycle.
• Mandatory revegetation at the 3:1 valley-oak / 2:1 other-oak caliper-inch ratio. Where a violation has been confirmed, the County requires a revegetation plan at the 3:1 valley-oak / 2:1 other-oak formula, with replacement species, location, and ratios set by PBES. The violator does not select the species or the location. Mitigation bank credits through the County program are available but are not a substitute on willful violations.
• Full site restoration at the applicant's expense. Where unauthorized work has damaged retained trees or where the site's pre-violation condition can be re-established, the County may require site restoration at the applicant's expense. Restoration is independent of both the fine and the in-lieu fee, and is not creditable against the replanting requirement. Site restoration is the most common path on vineyard-conversion and riparian-setback violations.
• Stop-work and revocation on active construction violations. A stop-work is issued when the violation is discovered mid-construction on a discretionary permit. The order holds until the violation is documented, mitigated, and — for protected trees — replanted or fees paid. Stop-work orders delay the entire project, not only the tree-protected portion; the practical effect is that every trade on site is paused until resolution.

The cleanest defense against enforcement is documentation written before the violation would occur — a pre-removal arborist report, a pre-construction BRE keyed to the current OW overlay and riparian setback maps, or a TRAQ assessment from a prior permit cycle. Documentation written after the violation cannot establish that the work was authorized or reasonable at the time it was performed; the County reads it as evidence of the violation itself. For HOA and commercial portfolios that already carry multi-tree exposure under § 18.108, recurring on-site monitoring — quarterly or annual walks, a written risk update keyed to overlay changes, and a priority response window — is the structural alternative, with subscription tiers and a no-charge 20-minute scoping call detailed on the tree-risk monitoring pricing page.

Request a consultation

Submit the form below to start a consultation intake. We will respond at the email you provide within one business day to scope the engagement. There is no fee for the intake call.