Overview
Code type
form-based
Naming convention
composite-context-form-size
Denver is the most developed form-based code among Colorado cities. Three-component district naming: (1) first letter = Neighborhood Context [S Suburban / E Urban Edge / U Urban / G General Urban / C Urban Center / D Downtown]; (2) second component = use/form [SU Single Unit / TU Two Unit / TH Townhouse / RH Row House / MX-MU Mixed Use / RX Residential Mixed Use / MS Main Street]; (3) third component = lot-size suffix [A=3,000 / B=4,500 / C=5,500 / D=6,000 / E=7,000 / F=8,500 / G=9,000 / H=10,000 / I=12,000 sf] OR story/intensity limit [-2.5 / -3 / -5 / -8 / -12 / -20 stories]. Dimensional standards (height, setbacks, lot coverage) are defined PER BUILDING FORM, not per district — a key difference from euclidean codes. Front 65% / Rear 35% zone lot division with separate height and form standards. Block-Sensitive Primary Street Setback applies to all residential districts citywide. No FAR-based regulation in residential.
Worth knowing
- Denver DZC (2010) is the most developed form-based code among Colorado cities. Dimensional standards (height, setbacks, lot coverage) attach to Building Forms, not to districts. Reading a single 'setback' number per district is structurally wrong.
- Block-Sensitive Primary Street Setback (DZC Tip Sheet 1): new residential primary structures must match the two nearest reference lots on the same block face — creating context-sensitive setbacks citywide rather than a uniform number per district.
- Front 65% / Rear 35% zone lot division (§5.3): every residential zone lot formally divided into two height zones. In U-context: front zone 2.5 stories / 30 ft (with width bonus to 35 ft); rear zone 1 story / 17 ft. Unique in this study.
+ 11 more in Quirks & notes
Districts
res_sf 18mu 9res_mf 4
| Code | Name | Category | Min lot | Height | Coverage | FAR | Du/ac | Parking | Setbacks F/S/R |
|---|---|---|---|---|---|---|---|---|---|
| U-SU-A | U-SU-A | res_sf | 3,000 sf[1] | — | — | — | — | — | — / — / — |
| U-SU-A1 | U-SU-A1 | res_sf | 3,000 sf[2] | — | — | — | — | — | — / — / — |
| U-SU-A2 | U-SU-A2 | res_sf | 3,000 sf[3] | — | — | — | — | — | — / — / — |
| U-SU-B | U-SU-B | res_sf | 4,500 sf[4] | — | — | — | — | — | — / — / — |
| U-SU-B1 | U-SU-B1 | res_sf | 4,500 sf[5] | — | — | — | — | — | — / — / — |
| U-SU-B2 | U-SU-B2 | res_sf | 4,500 sf[6] | — | — | — | — | — | — / — / — |
| U-SU-C | U-SU-C | res_sf | 5,500 sf[7] | — | — | — | — | — | — / — / — |
| U-SU-C1 | U-SU-C1 | res_sf | 5,500 sf[8] | — | — | — | — | — | — / — / — |
| U-SU-C2 | U-SU-C2 | res_sf | 5,500 sf[9] | — | — | — | — | — | — / — / — |
| U-SU-E | U-SU-E | res_sf | 7,000 sf[10] | — | — | — | — | — | — / — / — |
| U-SU-E1 | U-SU-E1 | res_sf | 7,000 sf[11] | — | — | — | — | — | — / — / — |
| U-SU-H | U-SU-H | res_sf | 10,000 sf[12] | — | — | — | — | — | — / — / — |
| U-SU-H1 | U-SU-H1 | res_sf | 10,000 sf[13] | — | — | — | — | — | — / — / — |
| U-TU-B | U-TU-B | res_sf | 4,500 sf[14] | — | — | — | — | — | — / — / — |
| U-TU-B2 | U-TU-B2 | res_sf | 4,500 sf[15] | — | — | — | — | — | — / — / — |
| U-TU-C | U-TU-C | res_sf | 5,500 sf[16] | — | — | — | — | — | — / — / — |
| U-RH-2.5 | U-RH-2.5 | res_mf | — | 35 ft[17] | — | — | — | — | — / — / — |
| U-RH-3A | U-RH-3A | res_mf | — | 40 ft[18] | — | — | — | — | — / — / — |
| U-MX-2 | U-MX-2 | mu | — | 30 ft[19] | — | — | — | — | — / — / — |
| U-MX-3 | U-MX-3 | mu | — | 45 ft[20] | — | — | — | — | — / — / — |
| U-RX-5 | U-RX-5 | mu | — | 70 ft[21] | — | — | — | — | — / — / — |
| U-MS-* | U-MS-2 / U-MS-3 / U-MS-5 | mu | — | — | — | — | — | — | — / — / — |
| E-SU-* | E-SU-Dx (E Urban Edge SU line) | res_sf | — | — | — | — | — | — | — / — / — |
| E-RH-2.5 | E-RH-2.5 | res_mf | — | 35 ft[22] | — | — | — | — | — / — / — |
| E-MU-2.5 | E-MU-2.5 | mu | — | 35 ft[23] | — | — | — | — | — / — / — |
| S-SU-* | S-SU-* (Suburban SU line) | res_sf | — | — | — | — | — | — | — / — / — |
| S-RH-2.5 | S-RH-2.5 | res_mf | — | 35 ft[24] | — | — | — | — | — / — / — |
| S-MU-* | S-MU-3 / S-MU-5 / S-MU-8 / S-MU-12 / S-MU-20 | mu | — | — | — | — | — | — | — / — / — |
| G-* | G-MU / G-RO / G-RH (General Urban context) | mu | — | — | — | — | — | — | — / — / — |
| C-* | C-MX / C-RX / C-CCN / C-MS (Urban Center context) | mu | — | — | — | — | — | — | — / — / — |
| D-* | D-C / D-LD / D-AS / D-CV (Downtown context) | mu | — | — | — | — | — | — | — / — / — |
Confidence: confirmed partial under review not found
Overlays
CO
Conservation Overlay District
HPMap-based; applied to specific neighborhoods where Council has adopted Conservation Overlay via legislative rezoning to preserve existing neighborhood character. Examples include Potter Highlands CO, West Highland CO, Packard's Hill CO — each with individually adopted provisions.
| purpose | Protect and enhance existing neighborhood character in specific mapped areas |
|---|---|
| application | Additive to base zone district; may restrict otherwise-permitted uses or Building Forms |
| individual_adoption | Each CO adopted via separate Council ordinance with area-specific provisions (height caps, form restrictions, design criteria) |
| interaction_with_base | Where CO is more restrictive than base, CO prevails |
| examples | Potter Highlands CO, West Highland CO, Packard's Hill CO, East 7th Avenue CO |
UO
Use Overlay District
specMap-based; applied via Council legislative action to allow or restrict specific uses that would not otherwise be permitted or prohibited in the base zone district.
| purpose | Allow or restrict specific uses beyond base district permissions |
|---|---|
| application | Geographic-area-specific; additive or subtractive use list relative to base |
| typical_use | e.g., allow ground-floor commercial in an otherwise residential district, or restrict drive-throughs on a specific corridor |
| interaction_with_base | UO modifies base use list; dimensional standards of base district still apply unless UO explicitly modifies |
DO
Design Overlay District
specMap-based; applied via Council legislative action to apply additional design requirements (facade materials, building form, streetscape, transparency) in specific areas.
| purpose | Apply additional design requirements in specific areas |
|---|---|
| application | Area-specific; additive design standards on top of base Building Form |
| typical_controls | facade materials, transparency ratios, building form restrictions, streetscape requirements |
| examples | Stapleton (Central Park) Design Overlay, Lowry Design Overlay, Denver International Airport area design standards |
| interaction_with_base | DO layers on top of base Building Form standards; DO standards prevail where stated |
AIO
Airport Influence Overlay District
APProperties within Denver International Airport (DIA) influence area, primarily covering eastern Denver. Map-based; defined by FAA Part 77 imaginary surfaces + Denver-specific noise compatibility zones.
| purpose | Height restrictions, noise attenuation requirements, land-use compatibility near DIA |
|---|---|
| height_hazard | FAA Part 77 horizontal/conical/approach surfaces limit structure elevation |
| noise_attenuation | sound attenuation construction standards for noise-sensitive uses within mapped noise contours |
| land_use_compatibility | restrictions on noise-sensitive uses (residential, schools, hospitals) in high-noise zones |
| faa_notification | FAA Form 7460-1 notification required for structures penetrating imaginary surfaces |
| federal_overlay | Federal authority (FAA) overlaps — federal_state_conflict possible where state-law density preemption conflicts with AIO height cap |
FP
Floodplain Regulations (South Platte / Cherry Creek / Sand Creek / Bear Creek)
FPFEMA-mapped 100-year floodplain (Zone A/AE) + city-mapped floodways on South Platte River, Cherry Creek, Sand Creek, and Bear Creek. Triggered by FIRM panel location.
| bfe_freeboard | Denver requires freeboard above BFE per DRMC Ch. 56 for habitable structures (NFIP minimum +1 ft; confirm Denver-specific requirement) |
|---|---|
| floodway_prohibition | new habitable structures prohibited in regulatory floodway |
| critical_facilities | critical/essential facilities prohibited in 100-yr floodplain |
| basement_rule | basement finished floor must be above BFE+freeboard |
| nonresidential_floodproofing | commercial structures may dry-floodproof to BFE+freeboard in lieu of elevation |
HP
Historic Preservation (Local Landmarks + Historic Districts)
HPMap-based designation of individual local landmark properties and local historic districts (e.g., Curtis Park HD, Baker HD, Potter Highlands HD, Humboldt Street HD). Parallel regime outside DZC — administered by Denver Landmark Preservation Commission.
| design_review | Landmark Preservation Commission Certificate of Appropriateness required for exterior alterations to designated/contributing properties |
|---|---|
| demolition_review | Demolition of designated-or-contributing resource requires LPC review + Council confirmation |
| non_designated_demo_review | 50+ year non-designated structures may trigger demolition review period per DRMC Ch. 30 |
| adjacency_compatibility | new construction adjacent to designated resources evaluated for height/massing compatibility |
| materials_standards | exterior materials/window patterns/roof form must be compatible with historic context |
| regime_location | DRMC Ch. 30 (Municipal Code) — separate from DZC (Zoning Code); cross-reference required |
State preemptions
CO HB 24-1152 (ADU by-right statewide)applies
Qualifying condition
Denver population 716,577 (US Census PEP 2023 vintage); Denver is a member of the Denver Regional Council of Governments (DRCOG) MPO. HB 24-1152 trigger: (is_in_mpo=true) OR (population≥1,000 AND is_in_connected_metro=true). Both arms satisfied. Denver has permitted ADUs by-right in most residential districts pre-state-law via DZC §11.8.2; state law now additionally mandates it and preempts any HOA covenant prohibitions.
Effect
ADUs permitted by-right in all residential zones where detached house is permitted. No owner-occupancy requirement. No discretionary review allowed. Design standards no more restrictive than primary structure permitted. Applies to detached, attached, and internal ADUs.
CO HB 24-1313 (Housing in Transit-Oriented Communities)applies
Qualifying condition
Denver is in DRCOG MPO (city.is_in_mpo=true). Denver has extensive high-frequency transit: 10+ RTD light rail stations within city limits (C/D/E/F/H/R/W lines), forthcoming Colfax Ave BRT (2027 target), and 15-min-or-better bus corridors on Federal Blvd, Colfax, Broadway, Colorado Blvd. parcel.in_transit_center_or_corridor=true for thousands of parcels within 1/2 mi of rail stations and 1/4 mi of high-frequency bus stops. Statute declared matter of statewide concern, binding on home-rule cities per bill text; Denver is home-rule per Colorado Constitution Art. XX.
Effect
Denver must designate Transit Centers and Transit Corridors, and zone them to permit a minimum 40 du/ac average density floor across the designated acreage. Duplexes required by-right in all SF-zoned residential land in MPO cities — affects U-SU, E-SU, S-SU SF district lines. Denver City Council work stream on TOC compliance in 2024-2025.
CO HB 24-1304 (Minimum Parking Requirements near transit)applies
Qualifying condition
Denver is in DRCOG MPO. parcel.within_quarter_mile_transit=true for thousands of Denver parcels on RTD light rail lines (C/D/E/F/H/N/R/W) and high-frequency bus corridors (Federal/Colfax/Broadway/Colorado Blvd/Colfax BRT corridor). HB 24-1304 trigger: (is_in_mpo=true) AND (parcel.within_quarter_mile_transit=true). Both satisfied.
Effect
No local minimum parking requirements for qualifying multifamily + mixed-use development within 1/4 mi of transit. Local parking maxima + design standards remain allowed. Also preempts lot-size minima that would block qualifying projects.
Qualifying condition
Denver is in MPO (DRCOG) AND population 716,577 (Census PEP 2023) >> 1,000. Trigger satisfied via both OR-arms.
Effect
Denver must adopt a DOLA-coordinated Housing Needs Assessment + Housing Action Plan. Procedural preemption tied to state grant eligibility. Denver's Housing an Inclusive Denver + Expanding Housing Affordability programs partially align; formal SB 24-174 compliance requires DOLA-format deliverable.
Adopted building codes
Denver & state buildings; home rule elsewhere
Click a code label to open its state-by-state adoption atlas.
Quirks & notes
- Denver DZC (2010) is the most developed form-based code among Colorado cities. Dimensional standards (height, setbacks, lot coverage) attach to Building Forms, not to districts. Reading a single 'setback' number per district is structurally wrong.
- Block-Sensitive Primary Street Setback (DZC Tip Sheet 1): new residential primary structures must match the two nearest reference lots on the same block face — creating context-sensitive setbacks citywide rather than a uniform number per district.
- Front 65% / Rear 35% zone lot division (§5.3): every residential zone lot formally divided into two height zones. In U-context: front zone 2.5 stories / 30 ft (with width bonus to 35 ft); rear zone 1 story / 17 ft. Unique in this study.
- Height width bonus: +1 ft per 5 ft of lot width above 50 ft, max 35 ft front (§5.3). E.g., 60-ft-wide lot gains +2 ft to 32 ft front height.
- ADU south-orientation rule (§11.8.2): ADUs >1 story or >17 ft must be placed abutting the southernmost side setback line to preserve solar access for the north neighbor. Unusual solar-rights protection built into ADU placement.
- ADU footprint scales with lot size in U-SU-C1: <6,000 sf = 650 sf max; 6,000-7,000 sf = 864 sf max; >7,000 sf = 1,000 sf max. Graduated system rewarding larger lots.
- 'Denver Double' — practice of building a large ADU in the backyard became popular after 2023 ADU relaxation; now real estate vernacular.
- No rooftop decks in rear 35% in U-context (§5.3.5.2); permitted in G-context. Preserves neighbor backyard privacy.
- E-SU-DX suffix = increased height at rear of property allowed (Urban Edge context). Readable directly from zone code.
- D1 suffix (e.g., E-SU-D1) = ADU (cottage) permitted. Readable directly from zone code.
- ADUs allowed by-right citywide in most residential districts per DZC §11.8.2, pre-dating HB 24-1152 state mandate. No design review required for standard ADUs.
- Former Chapter 59 — a small set of properties still governed by the pre-2010 code (not DZC). Must check which code applies before analysis.
- No FAR in Denver DZC residential districts — form-based frame uses height + setback + lot coverage only. FAR values in v1 were hallucinated.
- Home-rule city under Colorado Constitution Article XX — state preemptions (HB 24-1152, HB 24-1313, HB 24-1304) explicitly apply to home-rule via statewide-concern declarations.
Formulas
Definitions
- height
- Measured grade to highest point of roof. In U- context residential: front 65% zone max 30 ft (2.5 stories), rear 35% zone max 17 ft (1 story); width bonus +1 ft per 5 ft of lot width above 50 ft; max 35 ft front [DZC §5.3].
- lot_coverage
- Building footprint / gross lot area, expressed as decimal. Varies by Building Form within district.
- far
- Not used in residential districts. DZC is form-based; density regulated via form + height + setback.
- du_ac
- Dwelling units per gross acre. Not explicitly capped in most residential districts; density emerges from minimum lot size + building form permissions.
- setback_front
- Per DZC Tip Sheet 1 (Block Sensitive Setbacks): new primary residential structure's front facade must not be closer to street than closest street-facing facade of primary structures on the TWO NEAREST reference lots on same block face. Minimum = lesser of two reference-lot setbacks. Administrative adjustment available.
- setback_side
- Varies by Building Form and Neighborhood Context; retrieve from applicable Context Article (3-8) Building Form table.
- setback_rear
- Varies by Building Form and Neighborhood Context. Rear 35% of zone lot triggers separate 1-story/17-ft height cap plus rear setback rules per §5.3.
- parking
- Not uniform per district; varies by use. Preempted to zero on qualifying MF/MU parcels within 1/4 mi transit per HB 24-1304.
Capacity calculations
- max_footprint_sf
lot_area_sf * lot_coverage (per applicable Building Form)- max_gfa_sf
NOT a function of FAR in Denver — constrained by form + height + setback envelope- buildable_width_ft
lot_width_ft - setback_side_ft * 2- buildable_depth_ft
lot_depth_ft - setback_front_ft - setback_rear_ft (block-sensitive front)- max_stories_approx
front 65%: max 2.5 stories / 30 ft + width bonus to 35 ft; rear 35%: 1 story / 17 ft [U- residential context §5.3]
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
Max height
— ft
——
Floor area ratio
—
——
Lot coverage
—%
——
Setbacks (F / S / R)
— ft
——
Parking
— /unit
——
Max density
— du/ac
——
Min lot size
— sf
——
Copy zoning profile
Loading…
| District | Category | Height | FAR | Coverage | Setbacks | Parking | Density | Min lot | Overlays |
|---|
Sources & references
Primary source
Citations
- [1] §5.2.2
- [2] §5.2.2
- [3] §5.2.2
- [4] §5.2.2
- [5] §5.2.2
- [6] §5.2.2
- [7] §5.2.2
- [8] §5.2.2
- [9] §5.2.2
- [10] §5.2.2
- [11] §5.2.2
- [12] §5.2.2
- [13] §5.2.2
- [14] §5.2.2
- [15] §5.2.2
- [16] §5.2.2
- [17] §5.3
- [18] §5.3
- [19] §5.4
- [20] §5.4
- [21] §5.4
- [22] §4
- [23] §4
- [24] §3
Research status
Publication gates
| primary url present | passed | https://www.denvergov.org/... is the city-hosted canonical; starts with https://; not an aggregator |
|---|---|---|
| no aggregator cited | passed | No Zoneomics/Steadily/SitePlanGuide/SitePlanCreator/Propwire/Zonara/Unzoned references; citations are DZC §, DRMC Ch., FAA Part 77, Colorado HB/SB bill URLs |
| confidence tags full form | passed | All confirmed values carry section citations (§5.2.2, §5.3, §11.8.2, §9.4.2-5, DRMC Ch. 30, DRMC Ch. 56); preempted fields carry preempting_law + preempted_value + preempted_effective_date triple; paired fields populated (not_captured carries not_captured_reason + quirks[] entry) |
| overlays have parameters trigger confidence | passed | All 6 overlays (CO, UO, DO, AIO, FP, HP) carry non-empty params, trigger, base_interaction, and citation |
| preempt section city specific | passed | state_preemptions_applicable[] is non-empty (4 entries); each has Denver-specific qualifying_condition_checked with numeric inputs (population 716,577 Census PEP 2023), MPO membership (DRCOG), and transit inventory (RTD rail C/D/E/F/H/R/W + Colfax BRT). NOT a link-stub. |
Data quality
40%completeness32 confirmed12 partial
Documented gaps
- Full Building Form dimensional tables per district — Articles 3-8 of DZC PDF; would require table-level extraction from the Complete DZC PDF
- Full enumeration of G- (General Urban), C- (Urban Center), D- (Downtown) districts — currently aliased; individual district rows when pipeline full-run budget allows
- Block-Sensitive Setback worked examples per zone district — DZC Tip Sheet 1 provides methodology but city does not publish lookup tables
- Conservation Overlay (CO) individual area parameters — each CO adopted via separate Council ordinance with area-specific provisions; not a single citywide parameter set
- HB 24-1313 Transit Center designation map — pending Denver adoption as part of 2024-2025 TOC Action Plan work stream; re-research Q3 2026 for adopted TC boundaries
- Former Chapter 59 parcel-level coverage map — need list of parcels not brought under DZC at 2010 adoption
- Downtown (D-) context height caps — governed by a combination of base story caps + view-plane overlays + Downtown zone lot amenity rules; §8.3 table-level fetch deferred
- Historic District boundaries (DRMC Ch. 30) — Curtis Park HD, Baker HD, Potter Highlands HD, Humboldt Street HD, etc. — need individual boundary maps for overlay trigger evaluation
Known issues
freshness:volatiledata:gaps-present
Other cities in this state
Nearest-alphabetical profiles. Click through to compare zoning patterns side-by-side.