Fontana Zoning, Planning & Building Codes

Last reviewed: July 3, 2026

Overview

Fontana’s land-use regulations are codified as Chapter 30 — ZONING AND DEVELOPMENT CODE, which organizes zoning districts, overlays, development standards, and entitlement procedures for the city. The Code’s purpose is to implement the General Plan, manage building intensity and design, and regulate permitted uses across downtown, residential, commercial, industrial and special planning areas (§ 30‑1) . This page explains where to find the rules in the Fontana code and how the major district families, standards, overlays, and permit paths operate in practice.

How Fontana's code is organized

• The Zoning and Development Code is published as Chapter 30 of the Municipal Code and opened with the Code’s purpose and definitions in § 30‑1 and the definitions article (Division 4) .
• The established zoning districts are listed in Table No. 30‑408 and introduced at § 30‑408 (the legal Zoning District Map is on file with Community Development) .
• Administrative divisions: Article and Division headers separate (a) administration and enforcement (applications, pre‑apps), (b) development standards (tables such as Table No. 30‑613 and Table No. 30‑536), (c) use regulations (use tables such as Table No. 30‑430/30‑489), and (d) special districts/overlays and specific plans (separate divisions for overlays and area plans) — see the organization referenced throughout Chapter 30 (for example § 30‑412 and the area plan rules at § 30‑50 et seq.) .
• Practical navigation: look up the district name in Table No. 30‑408 (the table entry cites the Article where that district’s standards live) and then open the Article/Division called out in § 30‑408 to find the district‑specific tables and standards .

(First internal links — see “parking”, “development standards”, “design review”, “overlay districts”, “ADUs”, and the state building code” used below.)

Zoning district families

Fontana’s code establishes the following core district families (Table No. 30‑408; bolded below are the district labels you will see on the zoning map) § 30‑408 :

• Residential: R‑E, R‑1, R‑2, R‑3, R‑4, R‑5, R‑PC — base development standards for these appear in the residential Article (Article V) and in general development tables such as Table No. 30‑613 (§ 30‑613) .
• Commercial / Mixed Use: C‑1, C‑2, RMU, and form‑based code FBC districts for downtown/walkable corridors — permitted uses and use matrices live in the use regulation tables referenced at § 30‑489 and Table No. 30‑430/30‑430A for commercial/mixed use zones (§ 30‑489) .
• Industrial / Business Park: M‑1, M‑2, plus specialized business park controls in overlay divisions — industrial lot dimensions, heights, lot coverage and FAR are in the M‑district tables (see § 30‑535 / Table No. 30‑536 for the M‑1/M‑2 standards) .
• Public / Open Space: P‑PF, P‑UC, OS‑N, OS‑R with their specific lot and height rules in Table No. 30‑613 (§ 30‑613) .
• Overlay and special designations: the Code establishes multiple overlays such as ACO (Auto Center Overlay), ESO (Emergency Shelter Overlay), Hillside Overlay, R‑4 Overlay, Valley Business Park Overlay, and Warehouse Distribution / Logistics Overlay — each overlay has its own division and modifies Chapter 30 where shown (§ 30‑408; see overlay divisions throughout Chapter 30) .

Bold note: Downtown and walkable mixed‑use areas are governed by a Form‑Based Code (FBC) sub‑system called out in Table No. 30‑408 and described in the downtown Article (see § 30‑408 and the downtown/ FBC map at § 30‑405–406) .

Citywide development standards (high level)

• Where the general rules live: citywide conformance and permit basics are in § 30‑412 (no structure or land use may be built or used except as permitted in the zone and only after required permits are secured) . Required frontage and lot‑creation rules are at § 30‑413 / § 30‑414 .
• Setbacks and projections: the Code lists setbacks, permitted projections, and staggered front setbacks in the development standards divisions (for example § 30‑438 on staggered setbacks, § 30‑441 on projections into setbacks) . Industrial and business parks have their own setback tables referenced in Table No. 30‑536.B/30‑536.C and described in § 30‑535–536 (M‑district standards) .
• Height / lot coverage / FAR: typical maximums are set per district — e.g., industrial M‑1/M‑2: 75 ft max height, 60% lot coverage, 0.60 FAR as shown in § 30‑535 / Table No. 30‑536 ; overlay standards differ (see overlays below). The Valley Business Park overlay caps height at 60 ft, lot coverage 60%, and a base FAR 0.55 (§ 30‑663) . The Warehousing/Logistics overlay lists a 60‑foot height, 50% coverage and base FAR 0.50 with minimum lot sizes (§ 30‑650) .
• Parking policy: Fontana requires off‑street parking per Article XI; the general parking requirement is stated in the residential and mixed‑use development standards (“off‑street parking shall be provided as required by Article XI”) (§ 30‑440, § 30‑496) — see the Code’s parking tables for counts by use and special parking setbacks noted for major road frontages (§ 30‑440; § 30‑496; parking setbacks note at § 30‑536 and other tables) . Link to the City’s parking topic here: the Code’s parking rules are collected in Article XI and in district tables — first mention: parking.
• Landscaping, screening and low‑impact development requirements are in the development standards divisions (see § 30‑614, § 30‑668 and associated landscaping tables), including minimum landscape setbacks and sight‑line/screening requirements for loading and parking areas (§ 30‑614; § 30‑668) .
• Sign regulations are referenced back to Chapter 3 for on‑site signs; the Code repeatedly points permitted sign rules to Chapter 3 (for example § 30‑442 and sections in district divisions) .

(First mention link for development standards: development standards. First mention link for the state building code: California Building Standards Code.)

Design standards, discretionary review, and design process

• Design review and administrative site plan review are required for many types of projects (district and overlay divisions routinely state whether a proposal must go through design review or administrative site plan review). For example, development in the Valley Business Park overlay is subject to design review or administrative site plan review pursuant to Article II, Divisions X and XI (§ 30‑661) , and many overlays mirror that requirement. Consult the City’s design review entry in the Code for procedure and submittal rules — first mention: design review.
• Planned Unit Development (PUD) and area plans: PUD procedures, intent and thresholds are in the PUD division (Division 24) with authority and process described at § 30‑323–326 (minor PUDs allowed by right in some zones; major PUDs need Planning Commission action) . Area plans must include text and maps and follow the submittal checklist and public hearing paths set out in the area plan rules (§ 30‑50 et seq.; § 30‑51; § 30‑52) .
• Discretion and conditions: Divisions explicitly allow the Director, Planning Commission or Council to impose conditions to meet overlay intent or to increase separation/protection between uses (examples are found in multiple overlay divisions such as § 30‑663 and overlay sections) .

Specific plans & overlays (what matters in Fontana)

Fontana uses both Specific/Area Plans and numerous overlays to tailor rules to districts. Representative, operative examples from the Code:

• Form‑Based Code (FBC) / Downtown Area Plan — the downtown and walkable mixed‑use subdistricts are organized as FBC in Table No. 30‑408 and mapped in § 30‑405–406; these areas are governed by FBC standards and a downtown area plan § 30‑405–406 .
• Auto Center Overlay (ACO) — a multi‑area overlay that prescribes unique design, signage and permitted uses for the northern “auto center” planning areas; see the Auto Center Overlay division and its authorization and permitted uses (§ 30‑635–640) . (First mention link for overlays: overlay districts.)
• Valley Business Park Overlay — prescriptive standards (max 60 ft height, 60% lot coverage, base FAR 0.55, minimum lot area 1 acre) and design review requirement (§ 30‑663) .
• Warehouse Distribution / Logistics Overlay — large‑lot logistics corridor standards (minimum lot size 4 acres, max height 60 ft, lot coverage 50%, base FAR 0.50) and required site review (§ 30‑648–650) .
• R‑4 Overlay — flexible overlay created to encourage affordable medium/high density housing close to transit; the R‑4 overlay’s applicability and intent are at § 30‑663.1 with cross references to multiple R‑4 development sections (§ 30‑663.1 – 30‑663.3) .
• Emergency Shelter Overlay / Entertainment Center Overlay / Hillside Overlay / Medical Center Overlay — each overlay has its own division; for recent examples see the overlay divisions added/amended in the code (e.g., the Entertainment Center Overlay § 30‑663.4 – .6) .

Specific plans and area plan requirements (what they must contain and how they are processed) are laid out in the Area Plan division — the area plan submittal checklist and the requirement for a pre‑application meeting are in § 30‑50 – 30‑52 .

Building permits & review pathway (practical orientation)

• Basic rule: you cannot build or change use without the permits and approvals required by the Zoning and Development Code and other laws (§ 30‑412) .
• Typical flow for a private development: 1) read the base zone standards in the Article indicated by Table No. 30‑408 (§ 30‑408), 2) confirm allowed uses in the applicable use table (examples at § 30‑489 / Table No. 30‑430), 3) determine whether project triggers design review / administrative site plan / conditional use permit (overlay and district divisions specify this; see e.g., § 30‑661 for Valley Business Park and § 30‑635–640 for Auto Center), 4) submit the entitlement and building permit package — Chapter 30 explicitly requires pre‑application meetings where an area plan is being filed and lists submittal items for area plans at § 30‑51 – 30‑52 .
• Required public frontage and lot creation: building permits generally need lots to abut a dedicated public street unless legal nonconforming lots have recorded access easements (§ 30‑413) .
• Design review and administrative site plan review are the first discretionary filters for site compatibility — follow the procedures in Article II; many overlays cite that design review must be used (see § 30‑661; § 30‑649 for warehousing overlay design review requirement) .
• Code enforcement: a permit issued in violation of the Code is null and void — the Code emphasizes compliance and accuracy in entitlement approvals (§ 30‑412) .

(First mention link for the state building rules that the local building permits must align with: California Building Standards Code.)

State housing laws in Fontana — ADUs, density bonus, SB‑9, rent rules

• Accessory dwelling units (ADUs / JADUs): Fontana’s ADU rules are consolidated in § 30‑467 (Accessory dwelling units and junior accessory dwelling units). The local ADU section incorporates state law compliance language, applies to ADU/JADU applications submitted on or after Jan 1, 2025, and states that an ADU conforming to the section will not be deemed inconsistent with the general plan, will not exceed density, and will not be required to correct unrelated nonconforming zoning conditions (§ 30‑467(a)–(b)) . Specific local ADU standards (setbacks, unit sizes, parking exceptions, impact fee rules and utility connection rules) are spelled out in the ADU subsection language (e.g., 4‑foot side/rear setback minimums, one parking space per ADU with enumerated exceptions, impact fee waivers or proportional fees under certain sizes) — see § 30‑467 and its subsections for the details and exceptions, including the ADU impact fee thresholds (§ 30‑467; see the ADU subparts on setbacks, parking and fees) . Link to the local ADU entry here: ADUs. For how state ADU law interacts with local rules, consult state guidance (local ADU rules explicitly reference Government Code ADU provisions in § 30‑467) .
• Density bonus / No‑Net‑Loss program: Fontana implements density bonus mechanisms including a No Net Loss Density Bonus Bank; the density bonus rules and processing are in the Density Bonus division (see § 30‑968 and related sections) and the Code specifies how to calculate bonus units and that density bonus approvals do not waive compliance with base zone development standards (§ 30‑968–969) .
• SB 9 and parcel splitting: the retrieved materials in the supplied code do not include an explicit, standalone SB 9 implementation section in the excerpts provided here. The Code does include subdivision/zoning rules for lot creation and annexations (see § 30‑413 / § 30‑411), but a firm conclusion on local SB 9 procedures cannot be made from the retrieved excerpts alone — verify with Community Development for the City’s ministerial SB 9 process (Not found in retrieved materials; verify with the jurisdiction).
• Rent control / tenant protections: no municipal rent control regime or rent‑control chapter was identified in the retrieved Chapter 30 Zoning and Development Code excerpts. If you are searching for local rent or eviction controls, check other chapters of the Municipal Code or the City’s housing department; the zoning code does not itself establish rent control (Not found in retrieved materials; verify with the jurisdiction).
• State law cross‑references: Fontana’s ADU and housing sections explicitly reference the applicable Government Code and Health & Safety Code provisions (see § 30‑467 referencing state ADU statutes) . For state building and energy requirements, local permits must comply with the statewide code: see the California Building Standards Code (first‑mention link above).

Practical red flags and quick checklist for developers & residents

• Always confirm the zoning on the City’s official Zoning District Map (Table No. 30‑408 and § 30‑409 explain the map is on file at Community Development) § 30‑409 .
• Check overlays: a property’s overlay can change setbacks, uses, signage and review path (see overlay divisions such as § 30‑635–640 for the Auto Center and § 30‑648–663 for other overlays) .
• For housing projects: consult the Density Bonus / No Net Loss rules before assuming maximum density — density bonuses must still meet base zone development standards (§ 30‑968–969) .
• ADU applicants: follow § 30‑467; the Code lists unit‑type allowances, size/height/setback/parking exceptions, fee rules and permitting guidelines for ADUs and JADUs (§ 30‑467) .

Information gaps

• The files supplied give broad and deep coverage of Chapter 30 but do not include every cross‑reference (for example, a full, consolidated Article XI parking table printout was not present in the provided excerpts). Where specific parking counts, a complete SB 9 ministerial checklist, or the City’s current fee schedule are needed, those should be requested from the City’s Planning Division or the full printed table of Article XI (not all parking table pages were returned in the snippets above) (§ 30‑440; § 30‑496 point to Article XI for details) .

Source References

• Fontana Municipal Code — Chapter 30, ZONING AND DEVELOPMENT CODE (see purpose, definitions, district table and organizational headings at § 30‑1, § 30‑12, § 30‑408) § 30‑1; § 30‑12; § 30‑408
• Area Plan / Area Plan submittal requirements (Area plan text, pre‑application and submittal checklist) § 30‑50 – 30‑52
• Development Standards (Table No. 30‑613 and related residential/open‑space standards) § 30‑613; Table No. 30‑613
• Industrial (M‑district) standards (lot size, height, lot coverage, FAR) § 30‑535; Table No. 30‑536
• Valley Business Park Overlay (height, lot coverage, FAR, setbacks) § 30‑663
• Warehouse Distribution / Logistics Overlay (minimum lot size, height, FAR, lot coverage) § 30‑648 – 650
• Auto Center Overlay (Overlay intent, planning areas and requirements) § 30‑635 – 640
• ADUs / JADUs (local ADU ordinance and state cross‑references) § 30‑467
• Density bonus / No Net Loss program rules § 30‑968 – 970