21 base districts · 4 uses
Self-storage and multifamily zoning in unincorporated Maricopa County AZ — all 21 districts
Every base district in this jurisdiction, with the use table read out of the ordinance of record and the section cited beside each answer. Base district only — overlays are not checked.
- Self-storage is permitted or conditionally allowed in 5 of 21 districts: C-2, C-3, IND-1, IND-2, IND-3.
- Multifamily is permitted or conditionally allowed in 10 of 21 districts: R-2, R-3, R-4, R-5, C-1, C-2, C-3, IND-1, IND-2, IND-3.
- Mixed use is permitted or conditionally allowed in 7 of 21 districts: R-5, C-1, C-2, C-3, IND-1, IND-2, IND-3.
- RV / boat storage is permitted or conditionally allowed in 4 of 21 districts: C-3, IND-1, IND-2, IND-3.
Every district
| District | Family | Self-storage | Multifamily |
|---|---|---|---|
| RURAL-190 | rural | Not allowed | Not allowed |
| RURAL-70 | rural | Not allowed | Not allowed |
| RURAL-43 | rural | Not allowed | Not allowed |
| R1-35 | single family | Not allowed | Not allowed |
| R1-18 | single family | Not allowed | Not allowed |
| R1-10 | single family | Not allowed | Not allowed |
| R1-8 | single family | Not allowed | Not allowed |
| R1-7 | single family | Not allowed | Not allowed |
| R1-6 | single family | Not allowed | Not allowed |
| R-2 | multifamily | Not allowed | Allowed, but only with a discretionary approval |
| R-3 | multifamily | Not allowed | Allowed, but only with a discretionary approval |
| R-4 | multifamily | Not allowed | Allowed, but only with a discretionary approval |
| R-5 | multifamily | Not allowed | Allowed, but only with a discretionary approval |
| C-O | commercial | Not allowed | Not allowed |
| C-S | commercial | Not allowed | Not allowed |
| C-1 | commercial | Not allowed | Allowed, but only with a discretionary approval |
| C-2 | commercial | Allowed, but only with a discretionary approval | Allowed, but only with a discretionary approval |
| C-3 | commercial | Allowed, but only with a discretionary approval | Allowed, but only with a discretionary approval |
| IND-1 | industrial | Allowed, but only with a discretionary approval | Allowed, but only with a discretionary approval |
| IND-2 | industrial | Allowed, but only with a discretionary approval | Allowed, but only with a discretionary approval |
| IND-3 | industrial | Allowed, but only with a discretionary approval | Allowed, but only with a discretionary approval |
Now find out whether it pencils in unincorporated Maricopa County AZ.
Pick a district above, then run the envelope: lot area, FAR or height, and the residual land value it supports. Free, in about a minute.
The quick screen is free and needs no account. The sample study is the seven-page deliverable the Feasibility Desk produces.
Known limitations of this transcription
Published in full, because a dataset that hides its own caveats is worth less than one that doesn't have any.
faris blank for all 21 districts by design, not by omission. A search of the full 272-page ordinance for "floor area ratio" and "FAR" returns zero hits — MCZO has no such concept. Intensity is governed by lot coverage + height + (residential only) minimum lot area per dwelling unit. This differs from the starter tables, where a blankfarmeans "not transcribed here, enter manually".- Self-storage is allowed in 5 of 21 districts and by right in none of them — C-2, C-3, IND-1, IND-2, IND-3, every one requiring a Plan of Development (§305).
max_du_per_acre_derivedis computed, not quoted (43,560 ÷ minimum lot area per dwelling unit). The ordinance states the per-unit minimum; it never prints a units-per-acre figure. The derived number ignores streets, easements and setbacks and will overstate achievable density. Do not underwrite a unit count on it.- Multifamily in commercial and industrial districts has no stated density cap. Neither the §504 nor the §506 standards table has a per-dwelling-unit lot area row, so nothing limits unit count there but coverage, height and parking. Those rows are marked
mediumconfidence. Multifamily reading as conditional in all three industrial districts is unusual and worth a call to the county before anyone relies on it. mixedis a derived category, not an MCZO category. §601 has no mixed-use listing. Everymixedrow is inferred from stacking separately-listed uses, except R-5, which rests on the express §501.3.2 clause importing the C-1 use list. Allmediumorlow.- The "outdoor storage / storage rental yards" use row was deliberately omitted rather than guessed — its label and cells straddled the row grouping during extraction. It matters for outdoor RV/boat yards; extract it properly before the first paid study.
- §811 (additional height regulations), §901 (hillside) and §905 (drainage) are not extracted. §811 in particular can modify the height maximums in
rules.csv. - Staleness risk here is annexation, not amendment. The ordinance text is fresh (effective 2026-01-09), but MCZO covers only unincorporated land and Phoenix-metro fringe parcels are annexed continuously. On annexation this dataset stops applying to that parcel. There is no amendment or annexation feed wired up.
Before you rely on this
base district only; overlays not checked — Luke AFB overlay can flip answers
This is a base-district reading of the ordinance text, transcribed from the source below. It is not a Zoning Verification Letter, not a determination by the jurisdiction, not legal advice, and not a substitute for asking the planning department about a specific parcel. Overlays, recorded plan conditions, rezoning stipulations and parcel geometry are not checked here, and any one of them can change the answer on this page.
Verify locally before you spend money. Call the planning counter, pull the parcel's zoning-map designation and its case history, and confirm the section cited above still reads the way it reads here.
Source of record
- Document
- Maricopa County Zoning Ordinance (MCZO)
- Publisher
- Maricopa County Planning and Development Department, 301 W. Jefferson St., Suite 170, Phoenix, AZ 85003
- Adopted
- Board of Supervisors, 2025-12-10 (ordinance first effective 1969-05-29; revised 2001, 2025)
- Effective
- 2026-01-09
- Retrieved
- 2026-08-11
- File
- 272 pages, 6,729,372 bytes,
application/pdf - SHA-256
e5276ceea6aa07c783c555531ced5eac31e201efbdfb097a69f228161f5f75ee- Sections used
- §501–§506 (districts + dimensional standards), §601 (use table), §305 (Plan of Development), §802 (parking)