Local zoning · Temecula

Temecula — Development Standards

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

Ask a question free See coverage

Last reviewed: July 2, 2026

Overview

This page distills the Temecula Development Code (Title 17) rules that control setbacks, height, lot coverage, density and FAR across Temecula’s zoning districts. It is a code-focused reference (not a building-code or permitting checklist) summarizing the district tables and overlay exceptions you must read first in the municipal code. See the city's general summary for orientation at Temecula zoning & planning overview and the city zoning index at Temecula Zoning.

How to read these rules (quick)

  • The numeric limits you will use most are in the development standards tables (for residential: Table 17.06.040; for commercial/industrial: Table 17.08.040A/B; for public/institutional: Table 17.12.040). See § 17.06.040 § 17.08.040A/B and § 17.12.040 for the controlling tables and notes .
  • Parking minimums and layout are in Chapter 17.24; consult the Temecula Parking page and § 17.24.040/050 for how required stalls and drive aisles interact with your design .
  • Multifamily objective design review rules and ministerial standards are in § 17.06.090; see Temecula Design Review for procedure and objective standards .
  • Overlays and PDOs frequently change baseline standards—check the specific Planned Development Overlay (PDO) or overlay district instead of assuming the base zone applies; see Temecula Overlay Districts and the PDO sections in Chapter 17.22 (examples cited below) .

District-by-district summary (key dimensions and where they apply)

Note: the municipal code identifies many residential districts (HR, RR, VL, L-1, L-2, LM, M, H, HR‑SM) and commercial/industrial districts (NC, CC, HT, SC, PO, BP, LI). The district tables in the code are authoritative—this summary pulls the most decision-relevant entries and points you to the controlling sections. All numeric limits below are drawn from the Development Code tables; see the cited § entries (and the table entries) for the full rule text.

Residential districts — Table 17.06.040 (summary)

  • Where the standard lives: § 17.06.040 .
  • Districts and intent:
    • HR (Hillside Residential) — very-low density hillside estate neighborhoods. Key limits: maximum height 35 ft, maximum lot coverage 10%; minimum lot areas and large front/side/rear setbacks apply (see table) (§ 17.06.040) .
    • RR (Rural Residential) and VL (Very Low Density) — large-lot single-family with low FAR and limited coverage; maximum height 35 ft and low lot coverage percentages in table (§ 17.06.040) .
    • L-1 / L-2 (Low Density) — single-family neighborhoods; L-1 minimum lot size 1 acre, L-2 minimum ½ acre; typical height 35 ft, lot coverage increases in L-2 (§ 17.06.040) .
    • LM (Low‑Medium) — single-family on smaller lots; minimum lot size 7,200 sq ft, density 3.0–6.9 du/ac, lot coverage ~35% (§ 17.06.040) .
    • M (Medium) — townhouses, duplexes, patio homes; minimum lot size 7,200 sq ft, density 7.0–12.9 du/ac, maximum height 40 ft in some cases (§ 17.06.040) .
    • H (High) — attached apartments/stacked units; density 13–20 du/ac, no minimum lot size, maximum height typically 50 ft (varies by context) (§ 17.06.040) .
    • HR‑SM (Hillside‑Santa Margarita) — constrained hillside standards; special hillside development standards apply (see § 17.06.080) and different setbacks/heights in the HR‑SM notes (§ 17.06.040 and § 17.06.080) .

Typical permitted uses: residential uses in Table 17.06.030 cross-reference each residential zone; consult § 17.06.030 and the Table for allowed P/C uses in each zone .

Commercial / Office / Industrial — Table 17.08.040A / 17.08.040B

  • Where the standard lives: § 17.08.040A/B and FAR incentive rules in § 17.08.050 .
  • Districts: NC (Neighborhood Commercial), CC (Community Commercial), HT (Highway Tourism), SC (Service Commercial), PO (Professional Office), BP (Business Park), LI (Light Industrial).
  • Key numbers you will encounter (see table): front-yard adjacency rules by street class (e.g., arterial/collector/local), maximum heights by district (35–75 ft depending on district), maximum percent lot coverage (ranges commonly 25%–50%), and target FAR values with higher maximums available by incentive and showing justifications (§ 17.08.040A/B; § 17.08.050) .
  • FAR increases: projects can request FAR increases under the incentive criteria in § 17.08.050; traffic and utility capacity review is required and the engineer/approval authority can deny increases that create unmitigable impacts (§ 17.08.050) .

Public/Institutional (PI)

  • Where the standard lives: § 17.12.040 (Table 17.12.040) — minimum lot size 7,000 sq ft, max lot coverage 35%, FAR 0.3, setbacks front 20 ft, interior side 5 ft, street side 15 ft, rear 15–20 ft, landscape minimums 25% (§ 17.12.040) .

Planned Development Overlays (PDOs) and other overlays

  • PDOs are codified in Chapter 17.22. Many PDOs modify the base development standards (examples below). Always check the PDO text for site-specific setback, FAR, height and lot coverage changes (examples: PDO‑2 Table 17.22.118 in § 17.22.118; PDO‑13 Arbor Vista § 17.22.262; PDO‑14/16 examples have their own development tables) .
    • Example: PDO‑2 (Table 17.22.118) lists variable front yards, zero or variable interior side yards, max height 35 ft, max lot coverage 50% for certain residential product types — see § 17.22.118 for the PDO‑2 table and notes .
    • Example: PDO‑13 (Arbor Vista) sets a maximum building height 35 ft to ridge, minimum front setback 10 ft, and maximum lot coverage and open-space rules specific to the PDO (see § 17.22.262) .

Accessory structures, ADUs and SB9 rules

  • Accessory structures placements and heights are controlled in the applicable district tables and Chapter 17.06 supplemental sections; accessory structure maximum height is often 12 ft (see table notes) and accessory setbacks often 5 ft or as specified in Table 17.06.050(A) (§ 17.06.050, Table 17.06.050(A)) .
  • Accessory Dwelling Units must follow Chapter 17.23 and state ADU law; the local code cross‑references ADU rules and the ADU chapter for detailed dimensional standards — see Temecula ADUs and Chapter 17.23 for local implementation (local ADU rules and state constraints are both relevant) .
  • SB9 two‑unit developments are specifically regulated under § 17.06.120 (SB9 Two‑unit development). They must meet the front‑yard setbacks in the parcel’s zoning district (Table 17.06.040), but have minimum 4 ft interior side and rear yard setbacks for the units and specific accessory structure rules (e.g., accessory structures must meet Table 17.06.050(A) and maintain 6 ft separation from other structures) (§ 17.06.120 and related subsections) .

Design/landscape/visibility rules that matter to development standards

  • Landscaping minimums and water‑efficient standards are enforced in Chapter 17.32 and are referenced as required in the district tables; see Temecula Landscaping and Screening and § 17.32 for plan contents and water budget requirements .
  • Objective design review: multifamily and mixed‑use projects must comply with Temecula Objective Design Standards (§ 17.06.090) and may be eligible for ministerial review where state law applies .

Decision-relevant quick table

What you need to check first Typical City limit or rule you will use Code Reference
Residential setbacks, heights, lot coverage by zone See Table 17.06.040 (district-by-district limits) — e.g., H: density 13–20 du/ac, max height often 50 ft; LM/M: min lot 7,200 sq ft; max lot coverage ranges 25–35% § 17.06.040
Commercial/office heights, lot coverage, FAR Target FARs and maximums by district; max heights 35–75 ft depending on district; lot coverage 25–50% § 17.08.040A/B; § 17.08.050
Public/Institutional min lot, setbacks, FAR Min lot 7,000 sq ft, FAR 0.3, front 20 ft, interior side 5 ft § 17.12.040
SB9 two‑unit minimum side/rear setbacks Units: 4 ft interior side and rear minimum; accessory structure separation 6 ft § 17.06.120 and Table references (§ 17.06.040/17.06.050)
FAR increases / intensity bonuses Allowed with justification; must follow the criteria in § 17.08.050 and meet traffic/utility analysis requirements § 17.08.050
Parking counts, layout & stall dimensions See Chapter 17.24 and parking facility layout rules (drive aisles, tandem allowed in some cases) — consult Temecula Parking § 17.24.040 / § 17.24.050 references in code

Checklist (what an applicant must satisfy to match Temecula development standards)

  • Determine the exact zoning designation for the parcel and read Table 17.06.040 or the applicable Table in § 17.08/17.12 for that district (§ 17.06.040; § 17.08.040A/B; § 17.12.040) .
  • Confirm permitted uses in Table 17.06.030 or the matching land‑use table for the district (residential/commercial) (§ 17.06.030) .
  • Verify setbacks (front/corner/interior/rear), accessory structure setbacks, and maximum percent lot coverage in the district table and in Table 17.06.050 where accessory setbacks are listed (§ 17.06.040; § 17.06.050) .
  • Calculate FAR and lot coverage against the table target and the maximums (commercial projects that want extra FAR must prepare FAR‑justification materials and a traffic analysis per § 17.08.050) (§ 17.08.050) .
  • Confirm parking counts and layout comply with Chapter 17.24, and verify if SB9 or transit proximity modifies parking requirements (see § 17.06.120 for SB9 exemptions) (§ 17.24.040/050; § 17.06.120) .
  • Check overlays/PDOs that apply to the parcel (Chapter 17.22) and read the PDO text — overlay rules supersede base‑zone tables where they differ (see Temecula Overlay Districts and the PDO chapter) (§ 17.22.*) .
  • Determine whether the project triggers objective design review (§ 17.06.090) and prepare the objective standards package if required (see Temecula Design Review) (§ 17.06.090) .
  • For ADUs, follow Chapter 17.23 and state ADU law—local rules cannot conflict with state ADU minimum allowances (see Temecula ADUs and California ADU law) (§ 17.23; Gov. Code cross‑refs cited in the ADU chapter) .

Risks & Ambiguities

Issue Why it matters What to verify
Overlay / PDO differences PDOs often change setbacks, height, FAR and coverage; relying on base zone will produce errors Check the parcel’s overlay/PDO text in Chapter 17.22 and the PDO table that applies (e.g., § 17.22.118 for PDO‑2)
FAR target vs. maximum and incentive Tables list a target FAR and a higher maximum via incentive; approval requires justifications and traffic/utility review If you plan to exceed target FAR, prepare FAR justification and traffic analysis per § 17.08.050; verify utility capacity with city/engineer
SB9 technical exclusions SB9 entitlements have state-imposed exceptions (e.g., historic, farmland, high fire severity, tenant-occupied) that may block ministerial approval If using SB9, confirm exclusions and procedural requirements in § 17.06.120; check fire severity maps and historic inventories
Variable side yard/zero‑lot line arrangements Some districts (LM/M/H) permit variable interior side yard arrangements; measurement conventions and “sum of setbacks” rules can be confusing Review the notes in Table 17.06.040 and the accompanying explanatory notes in § 17.06.040 and § 17.06.050 before preparing building envelopes
Accessory vs. Primary building coverage counting Local tables and accessory structure rules define whether accessory building area counts towards lot coverage and separation rules Confirm accessory structure limits (height, setback, separation) in Table 17.06.050(A) and the district table notes (§ 17.06.050; § 17.06.040)
Landscape and water‑efficiency requirements Landscape coverage is often a minimum in the district tables and subject to Chapter 17.32 water-budget rules Include a water‑efficient landscape plan that follows Chapter 17.32 when you submit—plans must include water budgets per § 17.32

Plain-English Summary

Temecula’s development standards live in zone‑specific tables: pick your zone, apply the table (setbacks, height, lot coverage, FAR, minimum lot size), then check for overlays or PDO text that override those numbers. SB9 and ADU state rules add exceptions and minimums; parking and landscape chapters impose additional site controls. Always check the precise table row and the PDO text for the parcel — those are the controlling numbers in the municipal code (see § 17.06.040; § 17.08.040A/B; § 17.12.040) .

Source References

  • Temecula Development Code — Chapter and table references:
    • § 17.06.040 (Table 17.06.040, Development Standards — Residential Districts)
    • § 17.06.030 (Residential uses table cross‑reference)
    • § 17.06.120 (SB9 Two‑unit development)
    • § 17.08.040A / 17.08.040B (Table 17.08.040A/B — Commercial/Office/Industrial development standards)
    • § 17.08.050 (FAR increase incentive criteria)
    • § 17.12.040 (Development Standards — Public/Institutional; Table 17.12.040)
    • Chapter 17.22 (Planned Development Overlays — example tables: § 17.22.118, § 17.22.262, § 17.22.296)
    • § 17.06.090 (Objective design standards — multifamily/mixed‑use)
    • Chapter 17.23 (Accessory Dwelling Units) and related ADU notes in the code (see Chapter references in the files)
    • Chapter 17.24 (Parking — layout and dimensions referenced in many development standards)
    • Chapter 17.32 (Landscape and water efficient landscape design requirements)

Sources

Retrieved passages

  • Temecula Zoning Code (section that) High relevance
  • Temecula Zoning Code (Title 17.) High relevance
  • Temecula Zoning Code (§ 3) High relevance
  • CBC § 66314 (§ 66314) High relevance
  • CFC § 2 (§ 2) High relevance
  • Temecula Zoning Code (§ 2) High relevance
  • Temecula Zoning Code (§ 2) High relevance
  • Temecula Zoning Code (Title 18) High relevance
  • Temecula Zoning Code High relevance
  • Temecula Zoning Code (§ 2) High relevance
  • Temecula Zoning Code (§ 2) High relevance
  • Temecula Zoning Code (§ 17.22.310.) High relevance
  • Temecula Zoning Code High relevance
  • Temecula Zoning Code (§ 3) High relevance
  • Temecula Zoning Code High relevance
  • Temecula Zoning Code (section shall) High relevance
  • Temecula Zoning Code (title is) High relevance
  • Temecula Zoning Code (Title 18) High relevance
  • Temecula Zoning Code High relevance

Cited sections

Frequently asked questions

What can I build on an R-1 lot in Temecula?

R‑1 permitted uses and dimensional limits are given in the residential use and standards tables: check Table 17.06.030 for allowed uses and Table 17.06.040 for setbacks, height and lot coverage applicable to the residential zone assigned to the parcel (§ 17.06.030; § 17.06.040) . Verify the parcel’s exact zone code on the zoning map and any overlay/PDO that modifies those numbers (verify with the jurisdiction).

What are Temecula setback requirements?

Setbacks are zone‑specific and listed in the district tables (for residential, Table 17.06.040; for commercial, Table 17.08.040A/B; for PI, Table 17.12.040) — read the table row for your zone for front, corner side, interior side, and rear setbacks; accessory setbacks are in Table 17.06.050(A) (§ 17.06.040; § 17.06.050; § 17.08.040A/B; § 17.12.040) .

How high can I build in Temecula?

Maximum heights depend on the zone: many residential districts are 35 ft to 50 ft; commercial districts range 35–75 ft in the tables. See the height column in Table 17.06.040 or Table 17.08.040A/B for the controlling limit and check any PDO/overlay for a site‑specific height limit (§ 17.06.040; § 17.08.040A/B; Chapter 17.22) .

How do FAR and lot coverage work in Temecula?

Each district table lists a target FAR and a maximum lot coverage; commercial projects can request FAR increases only under the incentive criteria in § 17.08.050, which requires specific justifications and traffic/utility review (§ 17.08.050; Table 17.08.040A/B) . Verify whether your site is in a PDO that sets different FAR/coverage.

Do I need design review in Temecula?

Multifamily or mixed‑use projects and many discretionary projects must meet the Temecula Objective Design Standards; see § 17.06.090 for when objective standards apply. Some smaller or ministerial projects are reviewed ministerially; consult Temecula Design Review and § 17.06.090 for the specifics (§ 17.06.090) .

What special rules apply to SB9 two‑unit developments?

SB9 two‑unit developments are regulated in § 17.06.120. They must be on residentially zoned parcels that permit single‑family development; building height cannot exceed the underlying zone limit; interior side and rear setbacks for SB9 units are 4 ft minimum and accessory structure rules apply (accessories follow Table 17.06.050(A) and must keep 6 ft clear from other structures) (§ 17.06.120; Table 17.06.050(A)) .

Can I place an ADU within front setback areas?

ADU rules are in Chapter 17.23, but state ADU law prohibits local rules that effectively prevent at least an 800 sq ft ADU with 4‑ft side/rear setbacks from being built in compliance with other local standards. The local ADU chapter and state ADU rules interact—check Chapter 17.23 and the cited state provisions (verify with the jurisdiction for parcel specifics) (§ 17.23; Gov. Code cross‑refs summarized in code) .

Where are parking rules defined and can SB9 change parking needs?

Parking counts, layout and stall dimensions are in Chapter 17.24 (see Temecula Parking). SB9 has modified parking provisions: SB9 two‑unit drives require one off‑street space per unit but may be exempt from additional parking if within 1/2 mile of a high‑quality transit corridor or major transit stop (see § 17.06.120) (§ 17.24.*; § 17.06.120) .

What do PDOs change about the base zone?

A PDO (Chapter 17.22) can change setbacks, lot sizes, height, FAR, coverage and open‑space requirements compared to the base zone. Always read the PDO text for the parcel (e.g., PDO‑2 Table 17.22.118 or PDO‑13 Arbor Vista § 17.22.262) — the PDO table is controlling where it applies (§ 17.22.*; § 17.22.118; § 17.22.262) .

Who decides FAR bonuses or deviations?

FAR increases via the commercial/office incentive program are considered by the approval authority under § 17.08.050 and require traffic and other technical analyses; the city engineer or planning authority can deny increases that create unmitigable impacts (§ 17.08.050) . ---

More in Temecula code

Ask about any Temecula property

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

Start Free Trial

More Temecula zoning topics

Temecula Zoning

Temecula Land Use

Temecula Parking

Temecula Design Review

Temecula Overlay Districts

Temecula Historic Preservation

Temecula Signage

Temecula Nonconforming Uses

Temecula Variances and Exceptions

Temecula Landscaping and Screening

Temecula overview