Zoning › Arizona › Maricopa County › Mesa

Mesa, AZ Zoning

Euclidean-zoning. 34 districts · 6 overlays · 8 applicable state preemptions.

Overview

Code type
euclidean
Naming convention
mixed

Euclidean base zones (AG/RS/RSL/RM/NC/LC/GC/OC/MX/LI/GI/HI/PEP/DR/DB/DC/PS/PC/ID) under Title 11 of the Mesa City Code. Downtown has an opt-in Form-Based Code available to developers electing administrative review. Planned Area Development (PAD, Ch. 22) is used extensively for large master-planned communities (e.g., Hawes Crossing). RS-# and RSL-# district codes encode minimum lot size in 1,000s sf (RS-6 = 6,000 sf; RS-90 = 90,000 sf; RSL-2.5 = 2,500 sf). Mesa has two municipal airports (Falcon Field FFZ, Phoenix-Mesa Gateway IWA — the former Williams AFB, MAAMF-eligible successor) plus proximity to KPHX — airport overlays embedded in §11-19-5. | naming_convention_raw=lot-size-encoded-sf ; sub_flags_raw=[pad-heavy, arizona-housing-bills-2024, state-preemption-active, form-based-opt-in-downtown, multi-airport-adjacent] ; narrative_ref=narratives/mesa-az/fleet-20260419T073130-b2-08.json

Worth knowing
  • RS-# and RSL-# district naming encodes minimum lot size in 1,000s sf: RS-6 = 6,000 sf, RS-90 = 90,000 sf, RSL-2.5 = 2,500 sf. Consistent with standard Maricopa County / AZ naming convention (Chandler, Scottsdale, Tempe follow same pattern). RM-# does NOT encode lot size — it is a density-tier code (RM-2 lowest density through RM-5 highest). — [c§11-5; cross-confirmed via Chandler/Scottsdale/Tempe naming parallels]
  • Downtown Form-Based Code is OPT-IN, not mandatory. A developer in the downtown area may elect the FBC through a simple administrative approval process rather than going through the traditional use-based DR/DB/DC base zoning. This is relatively uncommon nationally — most FBCs either replace the underlying code or operate as mandatory overlays. Mesa's opt-in FBC gives downtown developers a choice of regulatory pathway. — [Downtown Mesa planning documents; city Planning & Zoning portal]
  • Airport overlay is EMBEDDED (§11-19-5), not a standalone chapter. Phoenix-Mesa Gateway Airport (IWA) and Falcon Field (FFZ) compatibility is handled through §11-19-5 and PAD conditions rather than a dedicated Airport Hazard Overlay chapter. This makes the airport's zoning impact less visible in the code structure than a named overlay. Particularly notable because Mesa has TWO municipal airports plus proximity to KPHX — a multi-airport federal preemption environment. — [c§11-19-5; Hawes Crossing PAD ordinance]

+ 9 more in Quirks & notes

Districts

residential_sf 10cbd 6commercial 5residential_mf 4industrial 4special 4agricultural 1
CodeNameCategory Min lotHeight CoverageFAR Du/acParking Setbacks F/S/R
AGAgriculturalagricultural—[1]35 ft[2]———[3]2[4]— / — / —
RS-6Single Dwelling District 6residential_sf6,000 sf[8]30 ft[9]0.4[10]—7.26[11]2[12]20[5] / 5[6] / 20[7]
RS-7Single Dwelling District 7residential_sf7,000 sf[16]30 ft[17]0.4[18]—6.22[19]2[20]20[13] / 5[14] / 20[15]
RS-9Single Dwelling District 9residential_sf9,000 sf[24]30 ft[25]0.4[26]—4.84[27]2[28]20[21] / 7[22] / 25[23]
RS-15Single Dwelling District 15residential_sf15,000 sf[32]30 ft[33]0.35[34]—2.9[35]2[36]25[29] / 10[30] / 30[31]
RS-35Single Dwelling District 35residential_sf35,000 sf[40]30 ft[41]0.25[42]—1.24[43]2[44]40[37] / 15[38] / 40[39]
RS-43Single Dwelling District 43residential_sf43,000 sf[48]30 ft[49]0.25[50]—1.01[51]2[52]40[45] / 15[46] / 40[47]
RS-90Single Dwelling District 90residential_sf90,000 sf[56]30 ft[57]0.2[58]—0.48[59]2[60]50[53] / 20[54] / 50[55]
RSL-2.5Small Lot Single Dwelling 2.5residential_sf2,500 sf[64]30 ft[65]0.6[66]—17.4[67]2[68]10[61] / 3[62] / 10[63]
RSL-3Small Lot Single Dwelling 3residential_sf3,000 sf[72]30 ft[73]0.55[74]—14.5[75]2[76]10[69] / 3[70] / 10[71]
RSL-4Small Lot Single Dwelling 4residential_sf4,000 sf[80]30 ft[81]0.5[82]—10.9[83]2[84]15[77] / 3[78] / 15[79]
RM-2Multiple Dwelling District 2residential_mf—[88]30 ft[89]0.5[90]0.6[91]12[92]1.5[93]20[85] / 10[86] / 25[87]
RM-3Multiple Dwelling District 3residential_mf—[97]35 ft[98]0.55[99]0.8[100]18[101]1.5[102]20[94] / 10[95] / 25[96]
RM-4Multiple Dwelling District 4residential_mf—[106]45 ft[107]0.6[108]1.25[109]24[110]1.5[111]15[103] / 10[104] / 25[105]
RM-5Multiple Dwelling District 5residential_mf—[115]60 ft[116]0.7[117]2[118]35[119]1.5[120]15[112] / 10[113] / 25[114]
NCNeighborhood Commercialcommercial—30 ft[124]0.7[125]0.75[126]—3.5[127]10[121] / 0[122] / 10[123]
LCLimited Commercialcommercial—35 ft[131]0.75[132]1[133]—3.5[134]10[128] / 0[129] / 10[130]
GCGeneral Commercialcommercial—45 ft[138]0.8[139]1.5[140]—3.5[141]10[135] / 0[136] / 10[137]
OCOffice Commercialcommercial—45 ft[145]0.75[146]1.5[147]—3.3[148]15[142] / 10[143] / 15[144]
MXMixed Usecommercial—55 ft[152]0.8[153]2[154]35[155]1.75[156]5[149] / 0[150] / 10[151]
LILight Industrialindustrial—45 ft[160]0.7[161]1[162]—2[163]25[157] / 10[158] / 20[159]
GIGeneral Industrialindustrial—60 ft[167]0.75[168]1.5[169]—1.5[170]25[164] / 10[165] / 20[166]
HIHeavy Industrialindustrial—75 ft[174]0.75[175]2[176]——50[171] / 25[172] / 25[173]
PEPPlanned Employment Parkindustrial—65 ft[180]0.6[181]1.5[182]—3[183]30[177] / 15[178] / 25[179]
DR-1Downtown Residence District 1cbd—[187]35 ft[188]0.55[189]1[190]22[191]1.5[192]10[184] / 5[185] / 15[186]
DR-2Downtown Residence District 2cbd—[196]45 ft[197]0.65[198]2[199]35[200]1.25[201]5[193] / 0[194] / 10[195]
DR-3Downtown Residence District 3cbd—[205]65 ft[206]0.75[207]3[208]60[209]1[210]0[202] / 0[203] / 5[204]
DB-1Downtown Business District 1cbd—45 ft[214]0.85[215]2.5[216]45[217]2.5[218]0[211] / 0[212] / 5[213]
DB-2Downtown Business District 2cbd—65 ft[222]0.9[223]3.5[224]65[225]2.5[226]0[219] / 0[220] / 5[221]
DCDowntown Corecbd—100 ft[230]1[231]5[232]120[233]2[234]0[227] / 0[228] / 0[229]
PSPublic and Semi-Publicspecial—45 ft[238]0.5[239]1[240]——[241]25[235] / 15[236] / 25[237]
PCPlanned Communityspecial——[245]—[246]—[247]—[248]—[249]—[242] / —[243] / —[244]
ID-1Infill Development District 1special—[253]35 ft[254]0.55[255]1[256]20[257]1.5[258]10[250] / 5[251] / 15[252]
ID-2Infill Development District 2special—[262]45 ft[263]0.65[264]1.5[265]30[266]1.25[267]5[259] / 5[260] / 10[261]

Confidence: confirmed partial under review not found

Overlays

BIZ
Bonus Intensity Zone Overlay District (Density/FAR/Height Bonus)
SPEC
c§11-21-1 through §11-21-5 (Title 11, Ch. 21)

Floating overlay applied on a site-specific basis by City Council action; attaches to underlying base zones where Council has adopted supplemental regulations per §11-21-2.

PAD
Planned Area Development Overlay District
SPEC
c§11-22-1 through §11-22-5 (Title 11, Ch. 22)

Applied site-specifically through Council rezoning on property-owner request. Used extensively for large master-planned communities (Hawes Crossing, Eastmark expansion, Elliot Road Tech Corridor PADs, Longbow, Las Sendas).

HD_HL
Historic and Landmark Overlay Districts
SPEC
c§11-23-1 through §11-23-6 (Title 11, Ch. 23); Chapter 74 design review also applies to historic district ADUs

Council-designated historic districts (HD) and individually designated historic landmarks (HL) via Mesa Historic Property Register process. Three formal historic districts within the original square mile of Mesa plus four bordering districts (seven total).

DE
Downtown Events Overlay Zoning District
SPEC
c§11-24-1 through §11-24-2 (Title 11, Ch. 24)

Specific boundaries within downtown Mesa defined in §11-24-2 (event-focused corridors around the Mesa Arts Center and downtown venues).

FBC
Downtown Form-Based Code (Opt-In)
SPEC
Downtown Mesa planning documents; administered through Title 11 supplementary provisions as an opt-in overlay

A portion of Downtown Mesa where the Form-Based Code is available. Applies when a developer opts in via administrative approval; does not apply by default to all downtown parcels.

APT_OVR
Airport Compatibility Overlay (Embedded — Phoenix-Mesa Gateway + Falcon Field)
SPEC
c§11-19-5 (Title 11, Ch. 19); PAD conditions layer additional requirements

Properties within the Airport Influence Area (AIA) of Phoenix-Mesa Gateway Airport (IWA — former Williams AFB, now civil/joint-use with Arizona Air National Guard operations) and Falcon Field (FFZ — municipal general-aviation airport) in northeast Mesa. Also subject to FAA Part 77 imaginary surfaces for both airports.

State preemptions

AZ HB 2720 — Middle Housing By-Right in Single-Family Zones (2024)applies
Qualifying condition
Mesa population 511,000 (Census ACS 2023 5-yr estimate, vintage 2023) ≥ 70,000 threshold → fourplex tier applies. Not tribal land status. Arithmetic: 511,000 ≥ 70,000 → TRUE for all four tiers (30k duplex, 70k triplex, 70k fourplex, 70k max-units-4 cap). Primary data: Census PEP 2023. Threshold: A.R.S. §9-462 as amended by HB 2720 (2024). | local_status=IN PROGRESS — Mesa in process of amending Title 11 ordinances for HB 2720 compliance. ADU component already implemented via Ord. 5883 (Sept 2024, §11-31-3 ADU amendments). Full middle-housing by-right implementation in SF zones pending. Airport Influence Area (>65 dB AICUZ) parcels near IWA / Falcon Field subject to federal-state conflict carve-out — HB 2720 mandate yields to FAA/AICUZ restrictions per §11-19-5 (this is the MAAMF × HB 2720 pattern documented for Glendale). ; preempting_law=AZ HB 2720 (2024) — A.R.S. Title 9, Chapter 4 amendments ; preempted_value_citation=c§11-5 Mesa SF dimensional tables (max density prior to HB 2720 floor)
Effect
Mesa must permit duplex, triplex, and fourplex by-right in the majority of single-family zones (RS-6, RS-7, RS-9, RS-15 — the principal urban SF districts; RS-35/43/90 are larger-lot less common). Minimum unit cap floor = 4 units per lot in majority of SF zones. Cannot impose discretionary review (no variance, CUP, or public hearing required). Cannot impose design standards that effectively prohibit middle housing.
AZ HB 2297 — Accessory Dwelling Units By-Right (2024)applies
Qualifying condition
Mesa population 511,000 (Census ACS 2023, vintage 2023) ≥ 75,000 threshold → HB 2297 applies. Not tribal. Primary data: Census PEP 2023. Threshold: A.R.S. §9-461.18 (HB 2297). | local_status=COMPLIANT — Mesa Ord. 5883 (Sept 2024) codified ADU by-right at §11-31-3 consistent with HB 2297. Historic District ADUs (HD/HL overlay) still subject to Ch. 74 design review — notable local restriction layered on top of state floor. Airport AICUZ >65 dB contours trigger HB 2928 STR/ADU carve-out for those parcels. ; preempting_law=AZ HB 2297 (2024) — A.R.S. §9-461.18 ; preempted_value_citation=c§11-31-3 (Ord. 5883, Sept 2024)
Effect
ADUs permitted by-right on all single-family, multifamily, townhouse, and mixed-use lots citywide. Cities cannot require owner-occupancy, cannot impose minimum lot size beyond underlying zone, cannot charge impact fees exceeding proportional share, cannot impose parking requirement for ADU. State floor: 5 ft minimum setback. Mesa Ord. 5883 (Sept 2024) implemented: ADU max GFA = lesser of 75% of primary GFA or 1,000 sf; ADU must have independent entrance; no minimum lot size to establish an ADU.
AZ HB 2721 — Minimum Lot Size Reductions (2024)applies
Qualifying condition
Mesa population 511,000 (Census ACS 2023, vintage 2023) ≥ 70,000 threshold → HB 2721 applies. Not tribal. Primary data: Census PEP 2023. Threshold: HB 2721 §§ lot-size provisions. | local_status=IN PROGRESS — Mesa's Title 11 amendments for HB 2721 compliance underway. Current RS-# dimensional tables pre-date the state mandate. Implementation pathway likely mirrors Chandler's Middle Housing Overlay District (1-mile CBD buffer) approach or citywide SF dimensional-table amendment. Verify current ordinance status on next freshness pass. ; preempting_law=AZ HB 2721 (2024) ; preempted_value_citation=c§11-5 RS-# dimensional tables (pre-amendment)
Effect
Mesa must permit SF lots with minimum lot size no larger than 5,000 sf and minimum lot width no larger than 50 ft in the majority of SF zones. Impacts RS-6 (already 6,000 sf — may require downshift or documented compliance via majority-zone analysis), RS-7, RS-9, RS-15. RSL-2.5/3/4 already comply. Large-lot RS-35/43/90 zones may retain higher minimums outside the 'majority' test.
AZ HB 2110 — Commercial-to-Residential Adaptive Reuse (2024)applies
Qualifying condition
Statewide mandate; no population threshold. Not tribal. Mesa is a municipality subject to commercial-to-residential adaptive reuse ministerial approval requirement. | local_status=IN PROGRESS — Mesa Title 11 implementing provisions for HB 2110 ministerial pathway expected but specific implementing chapter/section not retrieved. Ch. 71 design review may be layered where objective standards only. Adaptive-reuse activity concentrated in downtown Main Street (DB-1/DB-2/DC) and older GC corridors. ; preempting_law=AZ HB 2110 (2024) ; preempted_value_citation=c§11-6 commercial use tables (pre-amendment)
Effect
Commercial buildings (GC, LC, OC, MX) and qualifying office structures may convert to residential without rezoning and without public hearing (ministerial approval). Cities must provide ministerial pathway for qualifying conversions. Discretionary review waived for qualifying commercial-to-residential adaptive reuse.
AZ HB 2447 — Middle-Housing Ministerial Approval (2024, companion to HB 2720/2721)applies
Qualifying condition
Statewide; companion to HB 2720/2721 requiring ministerial (not discretionary) approval of middle-housing site plans based on objective design standards. Mesa subject as a city implementing HB 2720/2721. | local_status=IN PROGRESS — will be codified as part of HB 2720/2721 implementing amendments. Current Ch. 71 design review must be modified to use only objective standards for middle-housing projects. ; preempting_law=AZ HB 2447 (2024) ; preempted_value_citation=c§11, Ch. 71 (design review — discretionary aspects)
Effect
Mesa's middle-housing site-plan review must be administrative — no variance, CUP, or public hearing required. Objective design standards only (design criteria that can be measured without discretion). Reduces permitting cycle from typical PAD amendment (~6-8 months) to administrative review (weeks).
AZ HB 2928 — Short-Term Rentals & Airport Noise Carve-Out (2022, amended 2024)applies
Qualifying condition
Statewide preemption of STR regulation with carve-outs for parcels inside airport AICUZ >65 dB DNL contours. Mesa is subject. Airport-noise carve-out relevant because Mesa has IWA AICUZ contours in SE Mesa and Falcon Field AIA in NE Mesa. | local_status=Mesa registers STRs per state framework with city-level health/safety licensing. Airport-noise carve-out applies to portions of SE Mesa (IWA >65 dB AICUZ) and NE Mesa (Falcon Field AIA); exact contour extent requires coordination with IWA Airport Authority and Mesa Airport Operations for Falcon Field. ; preempting_law=AZ HB 2928 (2022, amended 2024) ; preempted_value_citation=Local STR regulatory authority (preempted except for health/safety/tax)
Effect
Mesa cannot ban STRs in residential zones; may impose health/safety licensing and tax registration only. STR restrictions (and possibly ADU STR-use restrictions) may be layered inside IWA AICUZ >65 dB and Falcon Field AICUZ-equivalent contours. ADUs inside >65 dB may be excluded from HB 2297 STR-use relief.
AZ Prop 207 — Private Property Rights Protection Act (2006)applies
Qualifying condition
Statewide; requires compensation for regulations that reduce property value. Mesa is subject. | local_status=Mesa follows statewide practice of avoiding blanket downzoning. No documented Prop 207 claims history retrieved. Framework effect rather than field-level preemption. ; preempting_law=A.R.S. §12-1131 et seq. (Proposition 207, 2006) ; preempted_value_citation=Local authority to downzone without compensation
Effect
Chilling effect on downzoning and new restrictive overlays in Mesa. Limits city's ability to tighten zoning without compensation claims. Contributes to Mesa's use of PAD (Ch. 22) as the primary development pathway — negotiated master plans avoid Prop 207 triggers because the property owner consents to the regulation in exchange for development rights.
Federal FAA Part 77 + AICUZ + MAAMF — Multi-Airport Height & Noise Preemption (Falcon Field + Phoenix-Mesa Gateway + proximity to KPHX)applies
Qualifying condition
Mesa has airport_influence_zones = [{kind: Part_77, airport: KFFZ Falcon Field}, {kind: Part_77, airport: KIWA Phoenix-Mesa Gateway}, {kind: AICUZ, airport: KIWA}, {kind: Part_77, airport: KPHX Phoenix Sky Harbor (Class B airspace extends over W Mesa)}]. Phoenix-Mesa Gateway (KIWA) is the successor to Williams AFB (closed 1993) and currently hosts AZ Air National Guard operations — MAAMF-eligibility should be verified with AZ Dept of Real Estate and DoD. Falcon Field (KFFZ) is a Mesa municipal general-aviation airport. KPHX is not inside Mesa but its Class B airspace and Part 77 surfaces extend over west Mesa. | local_status=Mesa handles federal/state conflict via §11-19-5 airport overlay embedding + PAD-level avigation easement and noise-disclosure covenant requirements. No standalone dedicated 'Airport Hazard Overlay' chapter — airport compatibility distributed across §11-19-5 and PAD conditions. Recommend structured airport-influence-zone table with per-parcel Part 77 surface lookup for development review. MAAMF qualification for IWA AZ ANG operations is the specific cross-check to run on next freshness pass. ; preempting_law=14 CFR Part 77; DoD AICUZ Program (DoDI 4165.57); A.R.S. §28-8461 et seq. (AZ MAAMF) ; preempted_value_citation=c§11-5 / c§11-6 / c§11-7 max_height_ft per base district (superseded where Part 77 surface is lower)
Effect
Federal preemption layer — FAA Part 77 imaginary surfaces generate parcel-specific height ceilings around all three airports (primary, horizontal, conical, approach, transitional surfaces). IWA AICUZ noise contours (>65 dB DNL) trigger disclosure requirements and federal-state conflict resolution for HB 2720/2721/2297 by-right housing (FAA compliance is the binding ceiling). MAAMF (if IWA qualifies as a military airport preservation zone via AZ ANG operations) adds state-layer protection of AFB-adjacent operations. §11-19-5 embeds the city-side airport compatibility requirements (avigation easements, noise-disclosure covenants, APZ use-compatibility). HB 2928 STR/ADU airport-noise carve-out operates through this same AICUZ layer. Federal-state conflict pattern: HB 2720/2721/2297 mandates yield to FAA/AICUZ where in direct conflict (analogous to Glendale's MAAMF × HB 2720 resolution and Chandler's Art. XXXV airport carve-out).

Adopted building codes

No statewide code; city-level

IBC
Local adoption
IRC
Local adoption
NEC
2017
IFC
Local adoption
IECC (Residential)
Local
IECC (Commercial)
Local

Click a code label to open its state-by-state adoption atlas.

Quirks & notes

  • RS-# and RSL-# district naming encodes minimum lot size in 1,000s sf: RS-6 = 6,000 sf, RS-90 = 90,000 sf, RSL-2.5 = 2,500 sf. Consistent with standard Maricopa County / AZ naming convention (Chandler, Scottsdale, Tempe follow same pattern). RM-# does NOT encode lot size — it is a density-tier code (RM-2 lowest density through RM-5 highest). — [c§11-5; cross-confirmed via Chandler/Scottsdale/Tempe naming parallels]
  • Downtown Form-Based Code is OPT-IN, not mandatory. A developer in the downtown area may elect the FBC through a simple administrative approval process rather than going through the traditional use-based DR/DB/DC base zoning. This is relatively uncommon nationally — most FBCs either replace the underlying code or operate as mandatory overlays. Mesa's opt-in FBC gives downtown developers a choice of regulatory pathway. — [Downtown Mesa planning documents; city Planning & Zoning portal]
  • Airport overlay is EMBEDDED (§11-19-5), not a standalone chapter. Phoenix-Mesa Gateway Airport (IWA) and Falcon Field (FFZ) compatibility is handled through §11-19-5 and PAD conditions rather than a dedicated Airport Hazard Overlay chapter. This makes the airport's zoning impact less visible in the code structure than a named overlay. Particularly notable because Mesa has TWO municipal airports plus proximity to KPHX — a multi-airport federal preemption environment. — [c§11-19-5; Hawes Crossing PAD ordinance]
  • No minimum lot size to establish an ADU (post-Ord. 5883, Sept 2024). Unlike many cities, Mesa explicitly removed minimum lot size requirements to establish an ADU. ADUs are permitted on any qualifying residential lot regardless of size. This is consistent with and in places exceeds the HB 2297 floor. — [c§11-31-3 (Ord. 5883, Sept 2024)]
  • ADU max size = lesser of 75% of primary GFA OR 1,000 sf. On small lots with small primary dwellings, the 75%-of-primary rule constrains ADU size more than the absolute 1,000 sf cap. This produces a size floor tied to the primary structure — small primary = small ADU. — [c§11-31-3 (Ord. 5883, Sept 2024)]
  • Historic District ADUs require Chapter 74 design review in addition to the §11-31-3 by-right ADU framework. While HB 2297 mandates ADUs statewide, Mesa HD/HL overlay parcels face additional design review under Ch. 74. This is a notable local-restriction-layered-on-state-mandate pattern that must comply with HB 2297's 'cannot impose design standards that effectively prohibit' test. — [c§11-23; c§11-31-3; c§11 Ch. 74]
  • Design review is codified in Chapter 71. Mesa has a design-review chapter that applies to certain nonresidential projects and higher-density multifamily / attached SF projects. Design review may also be imposed as a condition of special use or other permits. Under HB 2447 (2024), this chapter must use objective standards only for middle-housing projects. — [c§11 Ch. 71]
  • Multi-airport federal-state conflict pattern. Mesa is adjacent to three airports: Phoenix-Mesa Gateway (KIWA, former Williams AFB, now civil/joint-use with AZ ANG), Falcon Field (KFFZ, municipal GA), and Phoenix Sky Harbor (KPHX, Class B airspace over west Mesa). The HB 2720/2721/2297 by-right housing mandates yield to FAA Part 77 surfaces and AICUZ noise contours where in direct conflict. This is the federal-state conflict resolution pattern (FED_PART77 × HB 2720) analogous to Glendale MAAMF × HB 2720 and Chandler IWA Art. XXXV airport carve-out — applied at Mesa via §11-19-5 embedding. MAAMF eligibility for IWA (AZ ANG operations) is the open-question cross-check. — [c§11-19-5; FAA Part 77 (14 CFR); IWA AICUZ; A.R.S. §28-8461 (MAAMF framework)]
  • Bonus Intensity Zone (BIZ, Ch. 21) is a FLOATING overlay attached by Council action, not a mapped overlay. Council may attach BIZ to specific parcels to permit density/FAR/height increases above base-zone maximums with supplemental regulations. Not by-right — requires Council rezoning for attachment. — [c§11-21-1 through §11-21-5]
  • Mesa's historic district count: 3 formal historic districts within the original square mile plus 4 bordering districts (7 total). High density of historic-overlay coverage within the Mesa 1-square-mile 1890s townsite. Design-review layering and HD/HL ADU Ch. 74 overlay affect a significant portion of downtown-adjacent SF parcels. — [c§11-23; Downtown Mesa resources]
  • Planned Area Development (PAD, Ch. 22) is heavily used for large master-planned tracts in east Mesa (Eastmark, Hawes Crossing) and Elliot Road Tech Corridor. Consistent with Maricopa County PAD-dominance pattern (Chandler, Gilbert). Any parcel-level zoning analysis in east Mesa must check PAD status first; base-zone analysis alone is insufficient for most post-1990 master-planned parcels. — [c§11-22-1 through §11-22-5]
  • Prop 207 (2006) chills downzoning statewide. Contributes to Mesa's use of PAD (Ch. 22) as the primary development pathway — negotiated master plans avoid Prop 207 triggers because the property owner consents to the regulation in exchange for development rights. Base-zone amendments are rare; regulatory flexibility flows through PAD and BIZ overlays rather than base-zone rewrites. — [AZ Prop 207 (2006); Mesa zoning amendment history]

Formulas

Definitions

height
Measured from finished grade to highest point of structure; excludes chimneys, mechanical equipment screens, antennas per Mesa definitions
lot_coverage
Building footprint / lot area
far
Gross floor area / lot area
du_ac
Dwelling units / net acre (excluding right-of-way)
setback_front
Front property line to nearest building face
setback_side
Side property line to nearest building face
setback_rear
Rear property line to nearest building face
parking
Off-street spaces per dwelling unit (residential) or per 1,000 sf (commercial); varies by use
adu_size_cap
Accessory dwelling unit max GFA = lesser of 75% of primary residence GFA OR 1,000 sf [c§11-31-3; Ord. 5883, Sept 2024]

Capacity calculations

max_footprint_sf
lot_area_sf * lot_coverage
max_gfa_sf
lot_area_sf * far
buildable_width_ft
lot_width_ft - setback_side_ft * 2
buildable_depth_ft
lot_depth_ft - setback_front_ft - setback_rear_ft
max_stories_approx
max_height_ft / 10

Massing explorer

Interactive 3D comparison across every district. Drag to orbit, scroll to zoom, use the slider to walk districts, and toggle applicable overlays in the right-side panel.

—
—
Sort by —
LOW
HIGH
drag to orbit · scroll to zoom
Max height
— ft
——
Floor area ratio
—
——
Lot coverage
—%
——
Setbacks (F / S / R)
— ft
——
Parking
— /unit
——
Max density
— du/ac
——
Min lot size
— sf
——
◄
prev
►
next
Copy zoning profile
Loading…
District Category Height FAR Coverage Setbacks Parking Density Min lot Overlays

Sources & references

Primary source
Mesa City Code, Title 11 — Zoning Ordinance
Current through 2026-04-01; Ord. 5883 (Sept 2024, ADU amendments, §11-31-3); HB 2720/2721 implementation ongoing · retrieved 2026-04-19
Citations
  1. [1] c§11-5 Title 11 Ch. 5
  2. [2] c§11-5
  3. [3] c§11-5
  4. [4] c§11-6 Mesa parking standards
  5. [5] c§11-5
  6. [6] c§11-5
  7. [7] c§11-5
  8. [8] c§11-5 (district code encodes min lot sf — Mesa/Maricopa County convention)
  9. [9] c§11-5
  10. [10] c§11-5
  11. [11] c§11-5
  12. [12] c§11-6
  13. [13] c§11-5
  14. [14] c§11-5
  15. [15] c§11-5
  16. [16] c§11-5 (district code encodes min lot sf)
  17. [17] c§11-5
  18. [18] c§11-5
  19. [19] c§11-5
  20. [20] c§11-6
  21. [21] c§11-5
  22. [22] c§11-5
  23. [23] c§11-5
  24. [24] c§11-5
  25. [25] c§11-5
  26. [26] c§11-5
  27. [27] c§11-5
  28. [28] c§11-6
  29. [29] c§11-5
  30. [30] c§11-5
  31. [31] c§11-5
  32. [32] c§11-5
  33. [33] c§11-5
  34. [34] c§11-5
  35. [35] c§11-5
  36. [36] c§11-6
  37. [37] c§11-5
  38. [38] c§11-5
  39. [39] c§11-5
  40. [40] c§11-5
  41. [41] c§11-5
  42. [42] c§11-5
  43. [43] c§11-5
  44. [44] c§11-6
  45. [45] c§11-5
  46. [46] c§11-5
  47. [47] c§11-5
  48. [48] c§11-5
  49. [49] c§11-5
  50. [50] c§11-5
  51. [51] c§11-5
  52. [52] c§11-6
  53. [53] c§11-5
  54. [54] c§11-5
  55. [55] c§11-5
  56. [56] c§11-5
  57. [57] c§11-5
  58. [58] c§11-5
  59. [59] c§11-5
  60. [60] c§11-6
  61. [61] c§11-5
  62. [62] c§11-5
  63. [63] c§11-5
  64. [64] c§11-5 (RSL naming encodes min lot sf)
  65. [65] c§11-5
  66. [66] c§11-5
  67. [67] c§11-5
  68. [68] c§11-6
  69. [69] c§11-5
  70. [70] c§11-5
  71. [71] c§11-5
  72. [72] c§11-5
  73. [73] c§11-5
  74. [74] c§11-5
  75. [75] c§11-5
  76. [76] c§11-6
  77. [77] c§11-5
  78. [78] c§11-5
  79. [79] c§11-5
  80. [80] c§11-5
  81. [81] c§11-5
  82. [82] c§11-5
  83. [83] c§11-5
  84. [84] c§11-6
  85. [85] c§11-5
  86. [86] c§11-5
  87. [87] c§11-5
  88. [88] c§11-5
  89. [89] c§11-5
  90. [90] c§11-5
  91. [91] c§11-5
  92. [92] c§11-5
  93. [93] c§11-6 MF parking with guest supplement
  94. [94] c§11-5
  95. [95] c§11-5
  96. [96] c§11-5
  97. [97] c§11-5
  98. [98] c§11-5
  99. [99] c§11-5
  100. [100] c§11-5
  101. [101] c§11-5
  102. [102] c§11-6
  103. [103] c§11-5
  104. [104] c§11-5
  105. [105] c§11-5
  106. [106] c§11-5
  107. [107] c§11-5
  108. [108] c§11-5
  109. [109] c§11-5
  110. [110] c§11-5
  111. [111] c§11-6
  112. [112] c§11-5
  113. [113] c§11-5
  114. [114] c§11-5
  115. [115] c§11-5
  116. [116] c§11-5
  117. [117] c§11-5
  118. [118] c§11-5
  119. [119] c§11-5
  120. [120] c§11-6
  121. [121] c§11-6
  122. [122] c§11-6
  123. [123] c§11-6
  124. [124] c§11-6
  125. [125] c§11-6
  126. [126] c§11-6
  127. [127] c§11-6 Mesa parking standards
  128. [128] c§11-6
  129. [129] c§11-6
  130. [130] c§11-6
  131. [131] c§11-6
  132. [132] c§11-6
  133. [133] c§11-6
  134. [134] c§11-6
  135. [135] c§11-6
  136. [136] c§11-6
  137. [137] c§11-6
  138. [138] c§11-6
  139. [139] c§11-6
  140. [140] c§11-6
  141. [141] c§11-6
  142. [142] c§11-6
  143. [143] c§11-6
  144. [144] c§11-6
  145. [145] c§11-6
  146. [146] c§11-6
  147. [147] c§11-6
  148. [148] c§11-6 office parking
  149. [149] c§11-6
  150. [150] c§11-6
  151. [151] c§11-6
  152. [152] c§11-6
  153. [153] c§11-6
  154. [154] c§11-6
  155. [155] c§11-6
  156. [156] c§11-6 mixed-use residential parking
  157. [157] c§11-6
  158. [158] c§11-6
  159. [159] c§11-6
  160. [160] c§11-6
  161. [161] c§11-6
  162. [162] c§11-6
  163. [163] c§11-6
  164. [164] c§11-6
  165. [165] c§11-6
  166. [166] c§11-6
  167. [167] c§11-6
  168. [168] c§11-6
  169. [169] c§11-6
  170. [170] c§11-6
  171. [171] c§11-6
  172. [172] c§11-6
  173. [173] c§11-6
  174. [174] c§11-6
  175. [175] c§11-6
  176. [176] c§11-6
  177. [177] c§11-6
  178. [178] c§11-6
  179. [179] c§11-6
  180. [180] c§11-6
  181. [181] c§11-6
  182. [182] c§11-6
  183. [183] c§11-6
  184. [184] c§11-7
  185. [185] c§11-7
  186. [186] c§11-7
  187. [187] c§11-7 Downtown districts
  188. [188] c§11-7
  189. [189] c§11-7
  190. [190] c§11-7
  191. [191] c§11-7
  192. [192] c§11-6 + downtown reduction factors
  193. [193] c§11-7
  194. [194] c§11-7
  195. [195] c§11-7
  196. [196] c§11-7
  197. [197] c§11-7
  198. [198] c§11-7
  199. [199] c§11-7
  200. [200] c§11-7
  201. [201] c§11-6
  202. [202] c§11-7
  203. [203] c§11-7
  204. [204] c§11-7
  205. [205] c§11-7
  206. [206] c§11-7
  207. [207] c§11-7
  208. [208] c§11-7
  209. [209] c§11-7
  210. [210] c§11-6
  211. [211] c§11-7
  212. [212] c§11-7
  213. [213] c§11-7
  214. [214] c§11-7
  215. [215] c§11-7
  216. [216] c§11-7
  217. [217] c§11-7
  218. [218] c§11-6 downtown reduction
  219. [219] c§11-7
  220. [220] c§11-7
  221. [221] c§11-7
  222. [222] c§11-7
  223. [223] c§11-7
  224. [224] c§11-7
  225. [225] c§11-7
  226. [226] c§11-6
  227. [227] c§11-7
  228. [228] c§11-7
  229. [229] c§11-7
  230. [230] c§11-7 (subject to airport overlay §11-19-5 where applicable)
  231. [231] c§11-7
  232. [232] c§11-7
  233. [233] c§11-7
  234. [234] c§11-6 downtown core maximum reduction
  235. [235] c§11-5
  236. [236] c§11-5
  237. [237] c§11-5
  238. [238] c§11-5
  239. [239] c§11-5
  240. [240] c§11-5
  241. [241] c§11-6 varies by use
  242. [242] c§11-5 + master plan
  243. [243] c§11-5 + master plan
  244. [244] c§11-5 + master plan
  245. [245] c§11-5 + approved master plan
  246. [246] c§11-5 + approved master plan
  247. [247] c§11-5 + approved master plan
  248. [248] c§11-5 + approved master plan
  249. [249] c§11-6 + master plan standards
  250. [250] c§11-5
  251. [251] c§11-5
  252. [252] c§11-5
  253. [253] c§11-5
  254. [254] c§11-5
  255. [255] c§11-5
  256. [256] c§11-5
  257. [257] c§11-5
  258. [258] c§11-6 infill reduction
  259. [259] c§11-5
  260. [260] c§11-5
  261. [261] c§11-5
  262. [262] c§11-5
  263. [263] c§11-5
  264. [264] c§11-5
  265. [265] c§11-5
  266. [266] c§11-5
  267. [267] c§11-6

Research status

Publication gates

primary url presentpassedhttps://library.municode.com/az/mesa/codes/code_of_ordinances present in profile.source.primary_url; starts with https; Title 11 landing page resolves via municode platform.
no aggregator citedpassedNo zoneomics/steadily/siteplanguide/propwire/zonara/unzoned/siteplancreator references. All citations are Title 11 chapter/section references (c§11-X), AZ session law (HB 2720/2721/2110/2297/2447/2928/Prop 207), federal (14 CFR Part 77; DoDI 4165.57; A.R.S. §28-8461 MAAMF), or city-hosted amendment ordinances (Ord. 5883).
confidence tags full formpassedAll confirmed/partial claims carry c§X.Y.Z form citations (e.g., c§11-21-1 through §11-21-5, c§11-31-3, c§11-19-5) or explicit {value, status, citation, reason|search_performed|derivation} structure. Bare [confirmed] or [p]-shorthand tags eliminated from v1 format. All overlays have status + citation fields populated.
overlays have parameters trigger confidencepassedAll 6 overlays (BIZ, PAD, HD_HL, DE, FBC, APT_OVR) have non-empty parameters[] arrays (3-7 entries each), geographic_trigger populated with specific boundary/trigger language, status ∈ {confirmed, partial} with reason when partial, and citation populated with c§X.Y.Z form. Federal FAA/Part 77/AICUZ/MAAMF represented in state_preemptions_applicable[] as a federal_state_conflict entry with federal_overlay_refs.
preempt section city specificpassedstate_preemptions_applicable[] contains 8 city-specific entries: HB 2720 (middle housing), HB 2297 (ADU), HB 2721 (min lot size), HB 2110 (adaptive reuse), HB 2447 (ministerial approval), HB 2928 (STR + airport noise), Prop 207 (framework), and Federal FAA Part 77 + AICUZ + MAAMF (multi-airport preemption). Each entry carries qualifying_condition_checked (with numeric inputs, vintage, threshold), effect, effective_date, local_status (Mesa-specific implementation state), preempting_law, preempted_value_citation, and federal_overlay_refs. Profile does NOT link-stub to arizona.md; all applicability decisions computed from Census PEP 2023 primary data per preemption discipline (anti-FM-9 roster-trust).

Known issues

freshness:volatile

Verification

last_verified_at2026-04-19T08:05:00Z
verifier_specialistverification-pass
verifier_version1.0
verification_resultpassed_with_partials
atomic_claims_checked71
atomic_claims_confirmed28
atomic_claims_partial38
atomic_claims_not_found5
failed_claims
notesv1 extraction largely held; format transformation preserved knowledge while upgrading confidence structure. High-confidence claims: RS/RSL naming convention (lot-size-encoded), ADU Ord. 5883 rules (§11-31-3), BIZ/PAD/HD/DE/APT_OVR chapter structure, airport-embedded pattern (§11-19-5). Partial claims: base-district dimensional-table numeric values (Municode JS rendering blocks extraction — verify on next freshness pass with direct PDF or plain-HTML retrieval). 5 fields explicitly not_found with search_performed documented (AG lot coverage/setbacks, HI parking).

Other cities in this state

Nearest-alphabetical profiles. Click through to compare zoning patterns side-by-side.

BuckeyeChandlerGilbertGlendaleGoodyearPeoriaPhoenixScottsdale