Local zoning · Orange

Orange — Development Standards

Development Standards under the Orange local zoning and planning code, with the controlling citations.

Last reviewed: July 2, 2026

Overview

This page pulls together the City of Orange zoning development standards that control setbacks, height, lot coverage, density, and floor‑area ratio (FAR) under Title 17 (Zoning). It summarizes the most decision‑relevant rules for residential, mixed‑use, and small‑lot settings as mapped by the City and explains where to verify parcel‑specific outcomes. The primary controlling tables and rules are in § 17.14.070, § 17.14.060, and § 17.19.120 of the City code.

Note: this page interprets and synthesizes the ordinance text — consult the code and the Community Development Director for parcel‑specific determinations. For related procedural topics see the City’s zoning and planning menus: Orange Zoning, Orange Land Use, and Orange Overlay Districts. When projects trigger vehicle counts or spaces, consult Orange Parking. If your project involves ADUs, consult Orange ADUs. For design triggers, consult Orange Design Review. Construction compliance with the statewide code remains with the California Building Standards Code.


Key controlling rules (quick citations)

  • Residential development standards table: § 17.14.070.
  • SB9 / two‑unit standards in single‑family zones: § 17.14.060.
  • Mixed‑use zone development standards (OTMU/NMU/UMU): § 17.19.120.
  • Small lot subdivision rules (supplemental standards and Table 17.14.270): § 17.14.275 (and Table 17.14.270).
  • Variances and administrative adjustments for development standards: § 17.10.040 and § 17.10.050.

District‑by‑district breakdown (what a planner or applicant needs to know)

Each subsection below summarizes the district purpose, typical permitted uses (high level), the most decision‑relevant dimensional standards (minimum lot, setbacks, height, FAR/coverage where shown), and where the standard is stated in the code.

All tabular development standards for the residential districts are contained in Table 17.14.070 (§ 17.14.070) unless otherwise noted.

R‑1 family zones (R1‑5, R1‑6, R1‑7, R1‑8, R1‑10, R1‑12, R1‑15, R1‑20, R1‑40)

  • Purpose / uses: single‑family detached dwellings and accessory uses typical to R‑1 zones; accessory dwelling units follow City ADU rules and state law. See Table 17.14.070 for district specifics.
  • Typical dimensional standards (examples drawn from Table 17.14.070): minimum lot area varies by district (for example R1‑6 = 6,000 sf, R1‑8 = 8,000 sf, R1‑40 = 43,560 sf); front setback = 20 ft (standard; garage/driveway specifics differ) ; side = 5 ft; rear = 20 ft; maximum height = 32 ft / 2 stories in most R‑1 zones; FAR may be expressed as lot coverage or FAR per district as shown in Table 17.14.070. All values are from § 17.14.070.
  • Notes and special rules: R1‑5 has builder tract provisions allowing a 5,000 sf average lot under criteria and conditional use permits and special setback rules for garages and second stories — see the R1‑5 notes in § 17.14.070.

Practical tip: SB9 two‑unit projects in R‑1 must still meet the development standards in Table 17.14.070 and the SB9‑specific Table 17.14.060 (units created in R‑1 pursuant to SB9). See § 17.14.060 for the SB9 adjustments and permitted code waivers where standards preclude two 800 sf units.

R‑2 zones (R2‑6, R2‑7, R2‑8)

  • Purpose / uses: low‑density multi‑family / duplex development; two or more units allowed where lot area supports it. See Table 17.14.070.
  • Key standards: examples from Table 17.14.070 — R2‑6 minimum lot area = 6,000 sf, front setback = 15 ft, side setback = 5 ft, rear = 10 ft, max height = 32 ft / 2 stories, FAR = 0.70 (for some R‑2 subtypes). See § 17.14.070 for full table cells and footnotes.

R‑3 and R‑4 (medium‑density residential)

  • Purpose / uses: multifamily developments up to district density ranges (actual density yield depends on lot size and other standards). Permitted density is set by the General Plan map and the zoning table. See § 17.14.070 and Table 17.14.070 notes for density interpretations.
  • Key standards: Table 17.14.070 and the small‑lot subdivision Table 17.14.270 (if subdividing to small‑lot products). Typical heights for R‑3/R‑4 small‑lot subdivisions can be up to 35 ft / 3 stories per Table 17.14.270. See § 17.14.275 and Table 17.14.270.

Mixed‑use zones (OTMU‑15, OTMU‑15S, OTMU‑24, NMU‑24, UMU)

  • Purpose / uses: combination of residential and nonresidential (retail/office) uses with minimum/maximum densities and FAR ranges established per sub‑zone. See § 17.19.120 and Table 17.19.120.
  • Key dimensional standards from Table 17.19.120 (§ 17.19.120):
    • Lot area & width minimums vary (OTMU typical min 10,000 sf / 50 ft width; NMU/UMU often require 40,000 sf / 100 ft width for new lots).
    • Residential density ranges: OTMU = 6–15 du/ac (or 6–24 in some OTMU‑24); NMU‑24 = 16–24 du/ac; UMU = 30–60 du/ac.
    • Nonresidential FAR (examples): OTMU‑15 max 0.6, OTMU‑24 ranges 0.5–1.0, NMU‑24 1.0–1.5, UMU 1.5–3.0.
    • Setbacks: many mixed‑use streets are allowed 0 ft front/side setbacks to create pedestrian frontage; however minimums vary by street and specific historic/plaza areas — see § 17.19.120 notes. Maximum front/street‑side setbacks for UMU/NMU may be increased (up to 20 ft) when pedestrian amenities are provided (Director approval).
  • Practical note: mixed‑use setbacks and frontage rules include exceptions for specific plan areas (for example the Santa Fe Depot Specific Plan) — check the specific plan maps and § 17.19.130 for lot area/plan cross‑references.

Mobile Home Parks / M‑Zones and Industrial (brief)

  • The code provides separate lot coverage, spacing, and density limits for mobile home park zones (maximum 10 spaces per net acre and other spacing rules) and industrial uses; see Table notes and related sections in Title 17. The FAR definition and calculation rules apply across uses and are explained in the Table notes to § 17.14.070.

Small Lot Subdivisions (special development standards)

  • Small‑lot subdivisions have their own standards (Table 17.14.270) and supplemental regulations in § 17.14.275 including minimum frontage (25 ft), minimum depth (50 ft), perimeter setbacks (front/side/rear) and interior lot relief (no yards required between interior small lots). Maximum lot coverage for small lot units is 75% of approved small lot. See § 17.14.275 and Table 17.14.270.

Quick reference table — selected decision‑relevant standards

District (bold) Min Lot Area (typical) Min Front / Side / Rear set backs Max Height FAR / Lot Coverage Code Reference
R1‑6 6,000 sf Front 20 ft / Side 5 ft / Rear 20 ft 32 ft / 2 stories FAR 0.70 § 17.14.070
R1‑8 8,000 sf Front 20 ft / Side 5 ft / Rear 20 ft 32 ft / 2 stories FAR per table (see § 17.14.070) § 17.14.070
R1‑40 43,560 sf Front 20 ft / Side 5 ft / Rear 20 ft 32 ft / 2 stories 0.40 FAR § 17.14.070 (note)
R2‑6 6,000 sf Front 15 ft / Side 5 ft / Rear 10 ft 32 ft / 2 stories 0.70 FAR § 17.14.070
R‑3 / R‑4 (small lot) Per GP zoning Perimeter front/side/rear as table; interior lots often zero 35 ft / 3 stories (small lot subdivisions) Max coverage 75% (small lot) § 17.14.275 / Table 17.14.270
OTMU / NMU / UMU (mixed‑use) 10,000 — 40,000 sf min (varies) Often 0 ft frontage allowed; exceptions apply 32–45 ft depending on subzone Nonresidential FAR 0.6 to 3.0 (subzone dependent) § 17.19.120

(Values above are representative cells from Table 17.14.070 and Table 17.19.120 — review the tables for full district rows and footnotes.)


How FAR, lot coverage and accessory structures are treated

  • The ordinance defines FAR as building square footage divided by lot area, and states that building square footage includes all structures on the lot, including garages and accessory structures, unless otherwise provided. See the FAR note to Table 17.14.070 for the calculation rule. § 17.14.070 (note (o)).
  • The code also allows an alternative unit‑size limit in lieu of FAR in some residential contexts: maximum unit square footage tied to lot size (e.g., 1,200 sf maximum unit on lots ≥40,000 sf and smaller unit caps for smaller lots); see Table notes to § 17.14.070.
  • Existing legally established structures may keep existing FAR/coverage, but expansions must comply with Table 17.14.070 limits. See § 17.14.070 notes.

Practical note: accessory garages and other accessory structures count toward the lot’s FAR cap unless a specific exception applies; verify the applicable note in § 17.14.070.


Setbacks, projections, and special exceptions

  • Projecting elements (eaves, awnings, lattice) can encroach into setback areas subject to specific minimum clearances and limitations described in the Table notes and accessory structure sections; check the Table 17.14.070 notes (for residential) and overlay/specific plan exceptions. See § 17.14.070 and supporting notes.
  • Mixed‑use zones frequently permit 0 ft front setbacks to encourage pedestrian orientation; however, exceptions exist where a block is partially residential or within historic/plaza areas — consult § 17.19.120 notes.
  • The code identifies specific exceptions where building height may exceed allowed maximum if the building remains at a safe horizontal distance from a single‑family boundary (a measured formula is in the mixed‑use notes). See the height exceptions in § 17.19.120 notes.

Checklist (what an applicant must satisfy before permits)

  • Confirm zoning district on the City zoning map and the district‑specific row in Table 17.14.070 or Table 17.19.120. (§ 17.14.070 / § 17.19.120)
  • Confirm minimum lot area, lot frontage, and minimum lot depth for new lots or subdivisions (Table 17.19.120 / § 17.19.130 / Table 17.14.270).
  • Verify front, side and rear yard setbacks and any overlay or specific‑plan exceptions (e.g., Santa Fe Depot); check Table notes. (§ 17.19.120 notes; § 17.14.070 notes)
  • Calculate FAR and include all building area including garages/accessories per Table notes; check alternative unit‑size caps if applicable. (§ 17.14.070 notes)
  • Confirm height limits (stories and feet) and whether a discretionary approval is required for exceedance. (§ 17.14.070 / § 17.19.120 notes)
  • Check parking requirements in Chapter 17.34 and overlay‑specific parking rules (see Orange Parking). (§ 17.19.150; Chapter 17.34)
  • Confirm if design review is required and plan for any required design review. (See Title 17 review procedures.)
  • If pursuing variances or administrative adjustments for setbacks/coverage/height, document special circumstances and use § 17.10.040 / § 17.10.050 process.

Risks & Ambiguities

Issue Why it matters What to verify
FAR includes accessory buildings A garage or ADU can push a project over FAR limits Verify FAR calculation basis in Table notes to § 17.14.070 and confirm whether accessory area is counted for your lot.
Multiple overlapping overlays / specific plans Overlays (Neighborhood Preservation, Parking, Specific Plans) change yard, height, or frontage rules Check whether your parcel lies inside NP Overlay, Parking Overlay, or a specific plan (e.g., Santa Fe Depot) and apply overlay § requirements. See § 17.28.080 (NP) and § 17.19.120 notes.
SB9 unit waivers / code conflicts SB9 projects may trigger waivers and special rules but still must meet public‑safety and other standards Use § 17.14.060 for SB9 unit development standards and confirm allowable waivers; “if standards physically preclude” language applies.
Mixed‑use setback exceptions (0 ft vs residential continuity) Block frontage partly residential can dictate larger setbacks to be compatible Confirm block frontage context and the front setback rule footnote in § 17.19.120.
Small lot subdivision interior yards = none Interior lots in a recorded small‑lot subdivision have no yard requirement between interior lot lines — can create fire/safety and privacy issues Confirm small lot map requirements and design review findings required by § 17.14.275 and Table 17.14.270.
Height vs adjacent single‑family rule Height may exceed allowed maximum only if set-back formula is met — ambiguous in irregular parcels Confirm the “one‑quarter of horizontal distance” height exception language in § 17.19.120 notes and verify with the Community Development Director.

Plain‑English summary

Orange’s zoning tables set fixed minimum lot sizes, front/side/rear setbacks, and maximum heights for each district (residential values mostly in Table 17.14.070; mixed‑use in Table 17.19.120). FAR is calculated as building area divided by lot area and generally counts garages and accessory buildings; small‑lot subdivisions and SB9 units have separate tables and limited waivers. Always confirm overlay or specific‑plan rules that can override or modify the table numbers. (§ 17.14.070; § 17.19.120; § 17.14.060).


Source References

  • Orange Municipal Code, Title 17 — § 17.14.070 (Residential development standards / Table 17.14.070).
  • Orange Municipal Code, Title 17 — § 17.14.060 (Units created in R‑1 pursuant to SB9).
  • Orange Municipal Code, Title 17 — § 17.19.120 (Development standards for mixed‑use zones / Table 17.19.120).
  • Orange Municipal Code, Title 17 — § 17.14.275 and Table 17.14.270 (Small lot subdivision supplemental standards).
  • Orange Municipal Code, Title 17 — § 17.19.130 (Lot area requirements / specific plan cross‑references).
  • Orange Municipal Code, Title 17 — § 17.10.040 (Variance rules) and § 17.10.050 (administrative adjustments).
  • Parking, landscaping, and other cross‑references in Title 17: see § 17.19.150 (off‑street parking reference) and Chapter 17.34 for parking standards.

Sources

Frequently asked questions

What can I build on an R‑1 lot in Orange?

You may build single‑family housing and accessory uses allowed in the R‑1 subzone mapped for your parcel; dimensional limits (minimum lot area, front/side/rear setbacks, and max height = 32 ft / 2 stories) and usable open‑space requirements are in Table 17.14.07017.14.070) and the SB9 table if you propose two units.

What are Orange setback requirements?

Setbacks depend on the zone row in Table 17.14.070 for residential districts (for example 20 ft front, 5 ft side, 20 ft rear in many single‑family zones). Mixed‑use districts can allow 0 ft front setbacks per § 17.19.120 notes; overlay or specific plan rules can change these. Always read the table row and its footnotes.

How is FAR calculated in Orange and does a garage count?

FAR = building square footage divided by lot area and the code states that the building square footage generally includes all structures on the lot, including garages and accessory structures, unless a specific exception applies in the table notes. See the FAR notes to § 17.14.070.

Do I need design review for a residential or small‑lot project?

Design review requirements depend on your project type and whether it sits in a special overlay/small lot program; small lot subdivisions require Design Review Committee review per § 17.14.275 and design review is triggered by many multifamily or infill applications. See Orange Design Review and § 17.14.275.

Can I exceed height limits for a mixed‑use project near single‑family neighborhoods?

There is a measured exception in the mixed‑use notes allowing some exceedance where the building does not exceed one‑quarter of the horizontal distance to the nearest single‑family boundary; review the height exception language in § 17.19.120 notes and verify on a site‑by‑site basis.

What are the rules for SB9 two‑unit development in R‑1 zones?

SB9 units in R‑1 zones must comply with Table 17.14.060 and Title 17 development standards; the code provides limited waivers (e.g., reduced setback) if strict application of the standards physically precludes two units of at least 800 sf. See § 17.14.060 for requirements and allowable Director waivers.

How do mixed‑use FAR and density ranges work (NMU / UMU)?

Mixed‑use zones publish minimum/maximum residential densities in units per acre and separate nonresidential FAR ranges (e.g., NMU‑24 nonresidential FAR 1.0–1.5; UMU 1.5–3.0). Density minimums can be required and lot breakup rules apply; see § 17.19.120 and the table footnotes.

Where do I check parking requirements for a proposed development?

Off‑street parking standards are in Chapter 17.34 and mixed‑use tables refer you to § 17.19.150; check Chapter 17.34 for spaces per use and overlay‑specific parking rules. See Orange Parking.

If my lot is nonconforming after a plan update, can I still expand?

Properties made nonconforming by the General Plan update have rules in § 17.38.065 that allow nonconforming uses and developments to remain and to expand if the expansion complies with the listed conditions — verify whether your parcel appears on the City’s "made non‑conforming" map.

Are there special rules for small‑lot subdivisions about yards and coverage?

Yes. Small‑lot subdivisions have Table 17.14.270 and § 17.14.275 supplemental rules: interior lots may have no required yards between interior lines, perimeter lots have specified minimums, and maximum coverage for approved small lot is 75%. See § 17.14.275. ---

More in Orange code

Ask about any Orange property

Get a cited, plain-English answer on Orange zoning, setbacks, FAR, ADUs and permits — for any address.

Start Free Trial

More Orange zoning topics