What's the most common DBH threshold for heritage designation in Arizona?

Most cities in Arizona use case-by-case council or commission designation rather than a numeric DBH trigger — heritage status is awarded based on age, historical association, species rarity, or community value rather than a fixed inch threshold. See each city's row below for the underlying ordinance language.

Do heritage trees require a special permit in Arizona?

Yes — heritage trees in every verified Arizona jurisdiction require a more rigorous removal review than standard protected trees. Heritage status overrides any DBH-based exemption, so even a smaller heritage tree typically requires a removal permit. Many ordinances also require public hearing or notice, mandate replacement at higher ratios (often 2:1 or 3:1 for heritage versus 1:1 for standard), and impose larger penalties for unpermitted removal. Confirm the exact procedure with each city's row below.

Which cities have the strictest heritage criteria in Arizona?

Heritage criteria in Arizona are awarded by council or commission designation — there's no published DBH ranking. Each city's row below has the underlying ordinance language to compare directly.

Heritage tree designation criteria in Arizona

What makes a tree a heritage tree across 18 verified Arizona cities. Heritage status overrides standard DBH-based exemptions and triggers a more rigorous removal review than ordinary protected trees — often with higher replacement ratios and public-hearing requirements.

Heritage programs in Arizona are designation-only — none of the 18 verified cities publish a fixed DBH inch trigger. Each city's row below has the underlying ordinance language.

Most-named species in heritage / protected definitions: Mesquite (3 cities), Ironwood (2 cities), Oak (2 cities), Ocotillo (2 cities), Palo Verde (2 cities).

Heritage criteria comparison

Sorted ascending by extracted DBH (or DSH/circumference normalized to diameter). Designation-only cities appear last. Click a city for the full ordinance page or the ordinance link for the underlying municipal code.

Heritage-tree designation criteria by city, sorted ascending by DBH threshold (when published). Includes ordinance language, the underlying protected-tree definition, replacement ratio, and a link to the municipal code.
City	Heritage criteria	Protected-tree definition	Replacement ratio	Code
Buckeye	No formal heritage-tree designation. Public trees regulated by Parks and Recreation.	Buckeye Zoning Ordinance landscape standards govern landscape and tree plantings during development review. Regulation is landscape-plan-based rather than a DBH-based private tree removal permit. Arizona Native Plant Law applies to undeveloped private land.	Landscape-code replacement per Buckeye landscape standards (site-specific)	Ordinance
Chandler	No formal heritage-tree designation. Street and park trees regulated by Community Services. Native plant inventory may be required in desert-character zones.	Chandler Unified Development Manual / City Code Chapter 35 (Zoning) landscape standards govern landscape and tree plantings during development review. Regulation is landscape-plan-based at development submittal rather than a DBH-based private tree removal permit.	Landscape-code replacement per Chandler landscape standards (site-specific)	Ordinance
Flagstaff	Resource Protection Standards assign preservation priority to larger-diameter ponderosa pine and specimen trees identified during Forest Resource Inventory. No separate DBH-based heritage-tree designation; the inventory framework substitutes.	Flagstaff Zoning Code Division 10-50.60 (Resource Protection Standards) requires Forest Resource Inventory and preservation for development in ponderosa pine forest. Tree preservation standards apply to all qualifying sites; replacement required for removed qualifying trees. This is a distinct sub-regime from Sonoran-desert Arizona cities: the protected canopy is ponderosa pine (Pinus ponderosa) at 4-6 inch DBH and larger rather than native desert species.	Caliper-inch mitigation per Division 10-50.60 for removed qualifying trees; preservation percentages by zone	Ordinance
Gilbert	No formal heritage-tree designation. Public trees regulated by Parks and Recreation.	Gilbert Land Development Code (LDC) Article 4 landscape regulations govern landscape and tree plantings during development review. Regulation is landscape-plan-based at development submittal rather than a DBH-based private tree removal permit.	Landscape-code replacement per Gilbert landscape standards (site-specific)	Ordinance
Glendale	No formal heritage-tree designation. Public trees regulated by Parks, Recreation and Community Enrichment.	Glendale Zoning Ordinance landscape standards govern landscape and tree plantings during development review. Regulation is landscape-plan-based at development submittal rather than a DBH-based private tree removal permit.	Landscape-code replacement per Glendale landscape standards (site-specific)	Ordinance
Goodyear	No formal heritage-tree designation. Public trees regulated by Parks and Recreation.	Goodyear Zoning Ordinance landscape standards govern landscape and tree plantings during development review. Regulation is landscape-plan-based rather than a DBH-based private tree removal permit.	Landscape-code replacement per Goodyear landscape standards (site-specific)	Ordinance
Mesa	No formal heritage-tree designation. Public trees regulated by Parks, Recreation and Community Facilities for right-of-way and park work.	Mesa Zoning Ordinance Title 11 Chapter 30 (Design Standards) and Chapter 11-31 (Landscape) govern landscape, tree preservation, and replacement standards during development review. No dedicated private tree removal permit ordinance for existing residential parcels; regulation is landscape-plan-based at development submittal.	Landscape-code replacement per Mesa landscape standards (site-specific by zone)	Ordinance
Oro Valley	Protected native plants are inventoried and assigned preservation, transplant, or salvage status under the Native Plant Preservation Plan. No separate DBH-based heritage program.	Oro Valley Zoning Code Chapter 27 (Native Plant Preservation) and Environmentally Sensitive Lands (ESL) Overlay District require a Native Plant Preservation Plan for development on sites with protected native plants. Upper Sonoran desert plant palette dominates. Native plants must be preserved in place, transplanted, or salvaged per the preservation plan.	Chapter 27 establishes preservation-in-place percentages and transplant/replacement standards; replacement required when preservation infeasible	Ordinance
Peoria	No formal heritage-tree designation. Public trees regulated by Community Services / Parks.	Peoria Zoning Ordinance landscape standards govern landscape and tree plantings during development review. Regulation is landscape-plan-based rather than a DBH-based private tree removal permit.	Landscape-code replacement per Peoria landscape standards (site-specific)	Ordinance
Phoenix	No formal municipal heritage-tree designation. Street trees in the right-of-way are regulated by Parks and Recreation / Street Transportation. Native plants on development sites receive inventory and preservation review under landscape standards.	No citywide DBH-based private tree removal permit. Phoenix Zoning Ordinance Section 507 (Landscape and Buffer Standards) governs required landscape plantings and preservation during development review. Native Plant Preservation requirements apply in designated zones (e.g., Desert Preservation overlays) where saguaro, ironwood, palo verde, mesquite, and ocotillo must be inventoried and preserved or transplanted. Arizona Native Plant Law (ARS 3-901 et seq.) applies to private undeveloped land statewide regardless of municipal code.	Landscape code-based replacement (site-specific by zone and project type); salvaged native plants reused on-site where feasible	Ordinance
Prescott	Larger-diameter ponderosa pine and specimen trees identified during site plan review receive preservation priority. Heritage designation may apply to trees of exceptional size, age, or historical significance at Planning and Zoning Commission discretion.	Prescott Land Development Code landscape and tree preservation provisions govern tree preservation during development review. Ponderosa pine country sub-regime applies: Pinus ponderosa and Gambel oak are the dominant protected canopy species. Tree preservation required during site plan approval; replacement required for removed qualifying trees.	Caliper-inch or DBH-inch mitigation for removed qualifying trees per Land Development Code	Ordinance
Queen Creek	No formal heritage-tree designation. Public trees regulated by Parks and Recreation.	Queen Creek Zoning Ordinance landscape standards govern landscape and tree plantings during development review. Regulation is landscape-plan-based rather than a DBH-based private tree removal permit.	Landscape-code replacement per Queen Creek landscape standards (site-specific)	Ordinance
Scottsdale	Protected native plants inventoried under ESLO receive preservation-in-place, transplant, or replacement designations. No separate DBH-based heritage program.	Scottsdale Zoning Ordinance Article VI — Environmentally Sensitive Lands Ordinance (ESLO) — applies to upper Sonoran desert lands and requires native plant inventory, preservation, and transplant for applicable projects. General landscape standards apply citywide. The Native Plant Ordinance protects saguaro, ironwood, palo verde, mesquite, ocotillo, and other desert species on development sites.	ESLO sets preservation percentages and transplant requirements by plant category; on-site replacement required when preservation infeasible	Ordinance
Sierra Vista	No formal heritage-tree designation. Public trees regulated by Parks and Leisure.	Sierra Vista City Code Title 151 (Development Code) landscape and native plant preservation provisions govern landscape and tree standards during development review. High-elevation desert plant palette (mesquite, oak species, juniper) is typical. Regulation is landscape-plan-based rather than a DBH-based private tree removal permit.	Landscape-code replacement per Sierra Vista landscape standards (site-specific)	Ordinance
Surprise	No formal heritage-tree designation. Public trees regulated by Community and Recreation Services.	Surprise Municipal Development Code / Zoning Ordinance landscape standards govern landscape and tree plantings during development review. Regulation is landscape-plan-based rather than a DBH-based private tree removal permit.	Landscape-code replacement per Surprise landscape standards (site-specific)	Ordinance
Tempe	Significant trees identified at site plan review by staff arborist or landscape architect receive preservation or enhanced mitigation requirements. No formal heritage-tree designation.	Tempe Zoning and Development Code (ZDC) Part 4 Chapter 8 (Landscape Standards) governs landscape, tree preservation, and replacement during development review. Significant trees identified during site plan review may require preservation or mitigation. No universal DBH-based private tree removal permit outside development.	Caliper-inch replacement or mitigation for significant tree removal during development (site-specific)	Ordinance
Tucson	Protected native plants are inventoried and assigned preservation, transplant, or salvage status per UDC 7.6. No separate heritage designation; the native-plant preservation framework substitutes for a DBH-based heritage program.	Tucson Unified Development Code (UDC) Section 7.6 (Landscaping, Screening and Native Plant Preservation) requires a Native Plant Preservation Plan (NPPP) for development on sites with protected native plants. All new development subject to landscape and native plant inventory. No universal DBH threshold — protection is species- and site-based under the Sonoran desert plant list.	UDC 7.6 establishes preservation-in-place percentages and transplant/replacement standards; replacement required when preservation is not feasible	Ordinance
Yuma	No formal heritage-tree designation. Public trees regulated by Parks and Recreation.	Yuma Zoning Code landscape standards govern landscape and tree plantings during development review. Regulation is landscape-plan-based rather than a DBH-based private tree removal permit. Lower Colorado River desert plant palette typical.	Landscape-code replacement per Yuma landscape standards (site-specific)	Ordinance

How Arizona heritage designations work

What's the most common DBH threshold for heritage designation in Arizona?: Most cities in Arizona use case-by-case council or commission designation rather than a numeric DBH trigger — heritage status is awarded based on age, historical association, species rarity, or community value rather than a fixed inch threshold. See each city's row below for the underlying ordinance language.
Do heritage trees require a special permit in Arizona?: Yes — heritage trees in every verified Arizona jurisdiction require a more rigorous removal review than standard protected trees. Heritage status overrides any DBH-based exemption, so even a smaller heritage tree typically requires a removal permit. Many ordinances also require public hearing or notice, mandate replacement at higher ratios (often 2:1 or 3:1 for heritage versus 1:1 for standard), and impose larger penalties for unpermitted removal. Confirm the exact procedure with each city's row below.
Which cities have the strictest heritage criteria in Arizona?: Heritage criteria in Arizona are awarded by council or commission designation — there's no published DBH ranking. Each city's row below has the underlying ordinance language to compare directly.

Next steps

Working with a heritage-class tree in Arizona?

Capture an ISA TRAQ Level 1, 2, or 3 assessment in the field and export a municipality-ready PDF that fits each city's heritage-tree report sections. Free, no account required.

Start a TRAQ assessment