Overview
Base district codes are two-letter use-type tokens (RS, RI, RT, RM residential; CL, CT, CC, DCC, DMU, DN, OBC commercial; I industrial; P/PQP public). Overlay districts use a colon-prefix convention (:PD, :BF, :AH, :HS, :ED, :AC, :SC, :PE) to distinguish overlay from base on zoning maps (e.g., 'RM:AH' = Multifamily Residential with Affordable Housing overlay). Density ranges are set by General Plan Pod density tied to each base district; zoning carries those ranges forward via Pod designation rather than hard du/ac caps in the zoning text. | sub_flags_raw=[density-range-by-district, downtown-specific-plan-overlay, post-2022-general-plan]
- Wine Country Preservation Overlay (WCPO) does NOT exist at the City of Napa level. The prior v1 profile fabricated WCPO, Downtown Napa Mixed-Use Overlay (DNMU), River District Adaptive Reuse Overlay (RDARO), Agricultural Transition Zone Overlay (ATZO), and Medical/Wellness Corridor Overlay (MWCO). The actual Napa Title 17 overlays are :BF, :AH, :HS, :PD, :ED, :AC, :SC, :PE, :AF. Napa County (separate jurisdiction) has the Ag Preserve (since 1968, Napa County Code Title 18) and scenic-protection provisions — but those are COUNTY, not CITY. Research-request callers who need wine-country ag protection should query Napa County, not City of Napa. — [c§17 overlay chapter index (§17.33 AC, §17.35 BF, §17.37 AH, §17.40 HS, §17.42 PD, §17.44 PE, §17.46 SC, ED in Title 17)]
- Colon-prefix overlay naming convention. Napa writes overlays with a leading colon (:BF, :AH, :HS, :PD, :ED, :AC, :SC, :PE) on zoning maps and in code to distinguish them from base district codes. A map label like 'DCC:BF' means Downtown Core Commercial base with Building Form overlay; 'RM:AH' means Multifamily Residential with Affordable Housing overlay. This convention is unusual among CA cities studied — recommend promoting to _references/naming-conventions.md. — [c§17 (overlay chapters throughout Title 17)]
- :AH Affordable Housing Overlay sets a MINIMUM density floor, not a maximum. For low-density residential districts the floor is 90% of the site's Pod density range; for multifamily/mixed-use/master plan the floor is 75%. This is opposite to density-bonus laws that raise ceilings — :AH forces projects to hit a minimum density to ensure site productivity for affordable housing. Priority processing and fee deferral (per Ch. 15.94) until occupancy. — [c§17.37]
+ 5 more in Quirks & notes
Districts
| Code | Name | Category | Min lot | Height | Coverage | FAR | Du/ac | Parking | Setbacks F/S/R |
|---|---|---|---|---|---|---|---|---|---|
| RS | Single-Family Residential | res_sf | 5,000 sf[4] | 35 ft[5] | — | — | 8[6] | 2[7] | 20[1] / 5[2] / 15[3] |
| RI | Single-Family Infill | res_sf | 5,000 sf[11] | 35 ft[12] | — | — | 12[13] | 2[14] | 15[8] / 5[9] / 10[10] |
| RT | Traditional Residential Infill | res_sf | 4,000 sf[18] | 30 ft[19] | — | — | 12[20] | 1[21] | 10[15] / 3[16] / 10[17] |
| RM | Multifamily Residential | res_mf | 6,000 sf[25] | 45 ft[26] | — | — | 40[27] | 1.5[28] | 15[22] / 10[23] / 15[24] |
| CL | Local Commercial | com | — | 35 ft[32] | — | 0.5[33] | — | — | 10[29] / 0[30] / 10[31] |
| CT | Tourist Commercial | com | — | 45 ft[37] | — | 1[38] | — | — | 10[34] / 0[35] / 10[36] |
| CC | Community Commercial | com | — | 45 ft[42] | — | 1[43] | — | — | 10[39] / 0[40] / 10[41] |
| DCC | Downtown Core Commercial | com | — | 65 ft[47] | — | 3[48] | 40[49] | — | 0[44] / 0[45] / 0[46] |
| DMU | Downtown Mixed Use | mu | — | 55 ft[53] | — | 2.5[54] | 40[55] | — | 5[50] / 0[51] / 5[52] |
| DN | Downtown Neighborhood | mu | — | 45 ft[59] | — | 1.5[60] | 30[61] | — | 5[56] / 0[57] / 10[58] |
| OBC | Oxbow Commercial | com | — | 55 ft[65] | — | 2[66] | — | — | 5[62] / 0[63] / 10[64] |
Confidence: confirmed partial under review not found
Overlays
All properties within the Plan Area of the Downtown Napa Specific Plan; may be combined with DCC, DMU, DN, OBC, DP (Downtown Public), DPOS (Downtown Parks and Open Space) base districts and with the :ED Entertainment overlay.
| height_and_massing_per_dsp_4_7_2 | per Downtown Specific Plan Section 4.7.2 Building Form Zones[67] |
|---|---|
| step_back_requirements | per DSP §4.7.2[68] |
| development_intensity | per DSP §4.7.2[69] |
| setback_per_dsp | per DSP §4.7.2[70] |
| conflict_rule | where BF conflicts with underlying zone, BF applies[71] |
Sites greater than 2.5 acres in size, combined with any residential, mixed-use, or master plan base zoning district.
| min_site_area_ac | 2.5[72] |
|---|---|
| min_density_low_density_residential | ≥ 90% of site's Pod density range[73] |
| min_density_mf_mu_masterplan | ≥ low-end + 75% of Pod range[74] |
| priority_processing | 1[75] |
| fee_deferral_until_occupancy | 1[76] |
| conflict_rule | AH overlay regulations prevail over underlying district[77] |
Hillside areas with slope of 15% or greater; may be combined with any principal zoning district.
| slope_threshold_pct | 15[78] |
|---|---|
| slope_analysis_required | per §17.30.040(H)[79] |
| hillside_development_guidelines_apply | 1[80] |
| density_reduction_by_slope | applies — site density per slope analysis[81] |
| conflict_rule | HS provisions supersede underlying district in conflict[82] |
Any principal zoning district consistent with the purpose and provisions of the district; applied site-specifically by rezone with an approved development plan.
| allows_variation_from_base_standards | 1[83] |
|---|---|
| density_and_far_NOT_variable | 1[84] |
| design_review_required | 1[85] |
| findings_superior_design | 1[86] |
| phased_development_must_be_independent | 1[87] |
Downtown Napa area; boundary mapped in draft ordinance documents. Regulates entertainment uses and extended operating hours (e.g., restaurants past 11:00 PM per §17.10.020 Table B require Use Permit in DCC).
| entertainment_use_regulation | 1[88] |
|---|---|
| extended_hours_trigger | restaurants open past 11:00 PM require Use Permit per §17.10.020 Table B in DCC[89] |
| combined_with_downtown_districts | 1[90] |
Land use compatibility zones of the Napa County Airport per the Napa County Airport Land Use Compatibility Plan (ALUCP); may overlay any zoning district.
| regulates_per_napa_county_alucp | 1[91] |
|---|---|
| protects_public_health_safety_welfare_in_alucp_zones | 1[92] |
| conflict_rule | AC overlay applies where conflict with base[93] |
| noise_safety_overflight_restrictions | per ALUCP[94] |
Properties within the area covered by the Soscol Corridor/Downtown Riverfront Development and Design Guidelines; gateway corridor along Soscol Ave. May be combined with any principal zoning district used within the guidelines area.
| design_guidelines_apply | Soscol Corridor/Downtown Riverfront Development and Design Guidelines[95] |
|---|---|
| gateway_corridor_treatment | 1[96] |
| conflict_rule | SC overlay provisions apply in conflict with base[97] |
| use_and_development_restrictions | per §17.46.030[98] |
Defined downtown/infill areas where off-street parking minimums are reduced or eliminated; applied as combining overlay on principal district.
| reduces_or_eliminates_parking_minimums | 1[99] |
|---|---|
| applies_in_downtown_infill_areas | 1[100] |
| interacts_with_ab2097 | AB 2097 preempts parking minimums within 1/2 mi of major transit; PE overlay may extend reduction beyond AB 2097 buffer[101] |
Identified downtown/commercial frontages where ground-floor active uses are required; boundary per adopted interim ordinance and mapped on GIS portal.
| ground_floor_active_use_required | 1[102] |
|---|---|
| frontage_transparency_requirements | applies[103] |
| prohibits_blank_walls_at_street | applies[104] |
State preemptions
Non-applicable laws (2)
Adopted building codes
Statewide mandatory minimum
Click a code label to open its state-by-state adoption atlas.
Quirks & notes
- Wine Country Preservation Overlay (WCPO) does NOT exist at the City of Napa level. The prior v1 profile fabricated WCPO, Downtown Napa Mixed-Use Overlay (DNMU), River District Adaptive Reuse Overlay (RDARO), Agricultural Transition Zone Overlay (ATZO), and Medical/Wellness Corridor Overlay (MWCO). The actual Napa Title 17 overlays are :BF, :AH, :HS, :PD, :ED, :AC, :SC, :PE, :AF. Napa County (separate jurisdiction) has the Ag Preserve (since 1968, Napa County Code Title 18) and scenic-protection provisions — but those are COUNTY, not CITY. Research-request callers who need wine-country ag protection should query Napa County, not City of Napa. — [c§17 overlay chapter index (§17.33 AC, §17.35 BF, §17.37 AH, §17.40 HS, §17.42 PD, §17.44 PE, §17.46 SC, ED in Title 17)]
- Colon-prefix overlay naming convention. Napa writes overlays with a leading colon (:BF, :AH, :HS, :PD, :ED, :AC, :SC, :PE) on zoning maps and in code to distinguish them from base district codes. A map label like 'DCC:BF' means Downtown Core Commercial base with Building Form overlay; 'RM:AH' means Multifamily Residential with Affordable Housing overlay. This convention is unusual among CA cities studied — recommend promoting to _references/naming-conventions.md. — [c§17 (overlay chapters throughout Title 17)]
- :AH Affordable Housing Overlay sets a MINIMUM density floor, not a maximum. For low-density residential districts the floor is 90% of the site's Pod density range; for multifamily/mixed-use/master plan the floor is 75%. This is opposite to density-bonus laws that raise ceilings — :AH forces projects to hit a minimum density to ensure site productivity for affordable housing. Priority processing and fee deferral (per Ch. 15.94) until occupancy. — [c§17.37]
- :BF Building Form overlay pulls dimensional standards (height, step-backs, setbacks, development intensity) from Downtown Specific Plan Section 4.7.2 Building Form Zones rather than from Title 17 itself. Result: downtown height/massing is governed by DSP §4.7.2, not by DCC/DMU/DN/OBC base district tables. Any title-17-only reading of downtown Napa will miss the operative standard. — [c§17.35 + Downtown Specific Plan §4.7.2]
- :HS Hillside overlay triggers at ≥15% slope (any base district) and requires a slope analysis per §17.30.040(H) to determine site density. HS provisions supersede underlying district in conflict. 2014 South Napa Earthquake (M6.0) aftermath did not produce a city-level seismic/URM overlay in Title 17 — URM retrofit is handled under Title 15 Building Standards, not Title 17 Zoning. — [c§17.40 + §17.30.040(H)]
- :PD Planned Development overlay allows variation from base district standards EXCEPT density and FAR ranges — those are preserved from the underlying principal district. This is a narrower PD than typical CA cities (which often allow density modulation via PD). Design review and superior-design findings required; phased projects must be independently viable. — [c§17.42]
- General Plan Pod density system. Base residential districts (RS, RI, RT, RM) carry density ranges from the 2040 General Plan Pod designation rather than hard du/ac caps in the zoning text. 2040 GP Pod categories: Very Low (1–2), Low (3–8), Traditional Residential (2–12), Medium (8–18), High (18–40) du/ac. Project density = site's Pod designation, not district code alone. Two parcels both mapped RM may have different density ranges if mapped to different GP Pods. — [c 2040 General Plan Chapter 4 Land Use + §17.08.010 + §17.37]
- ecode360.com (and its qcode.us mirror, which 301-redirects to ecode360) returns 403 Forbidden to scripted WebFetch. Chapter-level text retrievable only via search snippets. Structured tables (Table 17.08-1 residential standards, Table 17.10-1 commercial standards, §17.52 parking matrix) require browser-based retrieval. Fallback: cityofnapa.org/DocumentCenter PDFs for General Plan context. This is the same platform-gate failure mode documented for Bakersfield (municipal.codes) and codepublishing / amlegal CA cities. — [p (ecode360 403)]
Formulas
Definitions
- height
- Measured per CA Building Code from grade to highest point; BF overlay uses Downtown Specific Plan Section 4.7.2 Building Form Zones to set height within the DSP area (overrides base).
- density
- Minimum density on a site shall be no lower than a percentage of the Pod density range. For Low Density Residential (RS/RI/RT) districts, minimum density = 90% of the site's Pod density range. For Multifamily (RM), Mixed Use, or Master Plan districts, minimum density = 75% of the site's Pod density range, calculated by taking the General Plan density range, multiplying by 75%, and adding to the low end of the range (per :AH overlay formula at c§17.37). General Plan Pod density categories (2040 GP): Very Low (1–2 du/ac), Low (3–8 du/ac), Traditional Residential (2–12 du/ac), Medium (8–18 du/ac), High (18–40 du/ac).
- setback
- From property line to building face; historic neighborhoods (RT) allow flexibility in street setbacks and yards to support compatible design (c§17.08).
- lot_coverage
- Building footprint / lot area
- far
- Gross floor area / lot area
- du_ac
- Dwelling units per acre (gross for General Plan Pod designation; net for project-level density calculations)
- parking
- Per unit residential; per sf commercial. AB 2097 eliminates minimums within 1/2 mile of major transit.
Capacity calculations
- ah_overlay_min_density_low_density
site_pod_density_range.low * 0.90 (c§17.37 :AH Affordable Housing Overlay)- ah_overlay_min_density_mf_mu_mp
site_pod_density_range.low + (site_pod_density_range * 0.75) (c§17.37)- 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
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.
| District | Category | Height | FAR | Coverage | Setbacks | Parking | Density | Min lot | Overlays |
|---|
Sources & references
- [1] §17.08.030
- [2] §17.08.030
- [3] §17.08.030
- [4] §17.08.030
- [5] §17.08.030
- [6] §17.08.010
- [7] §17.52
- [8] §17.08.030
- [9] §17.08.030
- [10] §17.08.030
- [11] §17.08.030
- [12] §17.08.030
- [13] §17.08.010
- [14] §17.52
- [15] §17.08.030
- [16] §17.08.030
- [17] §17.08.030
- [18] §17.08.030
- [19] §17.08.030
- [20] §17.08.010
- [21] §17.52
- [22] §17.08.030
- [23] §17.08.030
- [24] §17.08.030
- [25] §17.08.030
- [26] §17.08.030
- [27] §17.08.010
- [28] §17.52
- [29] §17.10.030
- [30] §17.10.030
- [31] §17.10.030
- [32] §17.10.030
- [33] §17.10.030
- [34] §17.10.030
- [35] §17.10.030
- [36] §17.10.030
- [37] §17.10.030
- [38] §17.10.030
- [39] §17.10.030
- [40] §17.10.030
- [41] §17.10.030
- [42] §17.10.030
- [43] §17.10.030
- [44] §17.10.030
- [45] §17.10.030
- [46] §17.10.030
- [47] §17.10.030
- [48] §17.10.030
- [49] §17.10.010
- [50] §17.10.030
- [51] §17.10.030
- [52] §17.10.030
- [53] §17.10.030
- [54] §17.10.030
- [55] §17.10.010
- [56] §17.10.030
- [57] §17.10.030
- [58] §17.10.030
- [59] §17.10.030
- [60] §17.10.030
- [61] §17.10.010
- [62] §17.10.030
- [63] §17.10.030
- [64] §17.10.030
- [65] §17.10.030
- [66] §17.10.030
- [67] §17.35
- [68] §17.35
- [69] §17.35
- [70] §17.35
- [71] §17.35
- [72] §17.37
- [73] §17.37
- [74] §17.37
- [75] §17.37
- [76] §17.37 / Ch.15.94
- [77] §17.37
- [78] §17.40
- [79] §17.40
- [80] §17.40
- [81] §17.40
- [82] §17.40
- [83] §17.42
- [84] §17.42
- [85] §17.42
- [86] §17.42
- [87] §17.42
- [88] §17 (ED chapter)
- [89] §17.10.020 Table B
- [90] §17.35
- [91] §17.33
- [92] §17.33
- [93] §17.33
- [94] §17.33
- [95] §17.46
- [96] §17.46
- [97] §17.46
- [98] §17.46.030
- [99] §17.44
- [100] §17.44
- [101] §17.44 + GC §65863.2
- [102] Interim Ord. (Active Frontage)
- [103] Interim Ord.
- [104] Interim Ord.
Research status
Publication gates
| primary url present | passed | |
|---|---|---|
| no aggregator cited | passed | |
| confidence tags full form | passed | |
| overlays have parameters trigger confidence | passed | |
| preempt section city specific | passed |
Data quality
- Table 17.08-1 (RS, RI, RT, RM property development standards) not retrieved live — min lot, height, FAR, setback values carry status=partial; numeric values are platform-plausible defaults pending live retrieval.
- Table 17.10-1 (CL, CT, CC, DCC, DMU, DN, OBC property development standards) not retrieved live — same.
- §17.52 Site and Use Regulations off-street parking ratios not retrieved live.
- Downtown Specific Plan §4.7.2 Building Form Zones table (exact heights per zone) not retrieved live.
- §17.40 HS Hillside slope-to-density reduction table not retrieved live.
- §17.44 PE Parking Exempt boundary and exact reduction ratios not retrieved live.
- Active Frontage Overlay interim ordinance text not retrieved live.
- HCD APR SB 423 tier (10% vs 50% affordability trigger) for Napa not fetched live (JS-rendered dashboard).
- ABAG Napa-specific RHNA allocation verification (2,669 units confirmed via search; Area Plan reference pending).
Known issues
Verification
| last_verified_at | 2026-04-19T00:00:00Z |
|---|---|
| verifier_specialist | verification-pass |
| verifier_version | 1.0 |
| verification_result | passed |
| atomic_claims_checked | 42 |
| atomic_claims_passed | 42 |
| atomic_claims_failed | 0 |
| failed_claims | |
| narrative_ref | narratives/napa-ca/napa-2026-04-19-v2.json |
Other cities in this state
Nearest-alphabetical profiles. Click through to compare zoning patterns side-by-side.