Local zoning · Indio

Indio — Development Standards

Q: What can I build on a **DE‑1** (Estate Residential) lot in Indio?

You can build uses consistent with low‑density estate residential character; the Code caps density at 1 unit/acre , sets minimum lot size 40,000 sf , maximum lot coverage 30% , and primary building height 25 ft / 2 stories (or lower if otherwise specified). Confirm permitted accessory uses in the allowed‑uses table for the DE‑1 zone and check § 2.02.03 (Table 2.02.03‑1) for the numeric standards .

Q: What are Indio's standard front, side, and rear setbacks for mixed‑use projects?

Mixed‑use setbacks vary by subzone but typical values are front minimum ~10 ft (residential ground floor), front maximums (to encourage active frontage) of 15–25 ft depending on ground‑floor type, interior side minimums 0–10 ft (10 ft where abutting single‑family), and rear 10–20 ft when abutting single‑family. See § 2.03.03 (Tables 2.03.03‑1/2) for table‑by‑table specifics and Figure references for site setbacks .

Q: How does Indio measure building height and allow architectural features?

Heights are measured per the Code's measurement rules in § 3.01.03 . Many zones allow limited architectural projections (stair/elevator overruns, mechanical screens) to exceed primary height by a small amount — mixed‑use tables often list an architectural features allowance (e.g., buildings capped at 55 ft with features up to 60 ft ). Provide measured elevations following § 3.01.03 to avoid misinterpretation .

Q: Does lot coverage include carports, garages, and porches?

Yes — the Code defines lot coverage as the footprint of all principal and accessory structures, including garages, carports, covered patios, and roofed porches , with specific exclusions (unenclosed decks <4 ft, eaves ≤3 ft, open trellises). The lot coverage rules and illustrative figures are in § 3.01.05 .

Q: What does Indio require for ADU setbacks, height, and lot coverage?

Indio's ADU rules in § 4.02.03 require a minimum 4‑ft side and rear setback for new ADUs (with some conversion exceptions), set the typical detached ADU height at 18 ft , and generally exempt ADUs from the underlying zone's lot coverage calculations (attached garages/carports counted) — see § 4.02.03 for full limits and conversion rules .

Q: If my project abuts single‑family homes, are there transition rules?

Yes. The Code requires a 45‑degree diagonal transition plane measured from the abutting property line at grade to limit how close taller portions of a building can be to single‑family lots; there are also minimum offsets for windows and balconies and landscape buffer requirements in § 2.03.06(J) and related site sections .

Q: Can I use a Planned Development (PD) to change height/setback standards?

Yes. The Planned Development Overlay (PD) permits site‑specific standards in exchange for findings showing superior design or community benefit; PDs have procedural requirements, findings, and a typical minimum area of 10 acres (although the Council may allow smaller PDs) — see § 2.07.04 for findings, minimum area, and procedures .

Q: How do I calculate residential density for a mixed‑use development?

Density is units per gross acre of the mixed‑use project area; in mixed projects the Code counts publicly accessible private open space, public/private streets/pathways, dedicated public parkland, and required easements in lot area for density calculations — see § 3.01.06 (Density) and the mixed‑use density entries in § 2.03.03 .

Q: Are there special rules for properties in the Bermuda Dunes Airport Influence Area?

Yes. Some density/intensity criteria must be consistent with the Bermuda Dunes Airport Compatibility Plan; the mixed‑use table and use notes flag the airport influence as a constraint — projects in influence areas should coordinate with the Riverside County Airport Land Use Commission and Indio Planning Staff (notes in the Code) .

Q: Do parking structures count toward the parking‑frontage limit on primary streets?

Yes. In certain mixed‑use zones the Code limits parking frontage on a primary street (e.g., no more than 30% of primary street frontage devoted to parking) to preserve active frontages; see TABLE 2.03.03‑2 and the mixed‑use frontage rules in § 2.03.03 for the precise percentages and applicability .

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

Ask a question free See coverage

Last reviewed: July 2, 2026

Overview

This page summarizes what the City of Indio's Unified Development Code (Title 17) actually requires for development standards — setbacks, heights, lot coverage, density/FAR, and related site rules — organized by the city's zones. It synthesizes the Code (the "Indio Development Code") and points to the controlling table/section for each rule so you can verify or pull the ordinance text. The Code is organized by base zones plus overlays; start at the Official Zoning Map to find a property's zone before applying these standards (§ 1.01.01) .

Note: this page stays strictly within the Development Standards portion of the Code (zoning/development form). For vehicle spaces and dimensional layout see the city's parking standards; for design review processes see design review; for overlay rules see overlay districts; and for ADU-specific rules see ADUs. For building-code technical compliance consult the California Building Standards Code.

How the Code measures things (short primer)

Measurements use the shortest distance between objects and rounds fractions as prescribed in the Code; see § 3.01.02 (Measuring Distances) and § 3.01.01 (Rounding) for rules that affect setbacks, lot area calculations, and height measurement .
Lot coverage and FAR definitions and diagrams are in § 3.01.05 (FAR / Lot Coverage) and density rules are in § 3.01.06 (Density) — use those when calculating buildable footprint or units/acre for projects and mixed-use developments .
Citywide site rules (block size, connectivity, neighborhood transition planes, landscape buffers) apply in addition to zone tables; see Chapter 3.02 for standards that apply across zones (§ 3.02.01–.02) .

District-by-district breakdown (what matters at first review)

Below are the principal zone groups and the decision-relevant standards pulled from the Code tables. For each zone I list the purpose (as the Code frames it), typical uses (as allowed by the zone family), key dimensional standards you will be asked to comply with, and where that zone typically applies in the city.

Note: the Code presents full allowed-use tables and more detailed subrules inside Article 2; this summary highlights the development standards (setbacks/height/lot coverage/density/FAR) you will need for entitlement-level review.

Residential Neighborhood Zones (key base zones)

Purpose & typical uses: low- to moderate-density housing forms; single-family, small-lot detached, some multi-family types where allowed. Consult the allowed uses table for specific permitted uses in each residential zone (§ 2.02.03) .

Districts and key rules (from TABLE 2.02.03-1 / § 2.02.03):

DE-1 — Estate/large lots. Maximum density 1.0 unit/acre, minimum lot size 40,000 sf, maximum lot coverage 30%, maximum height 25 ft / 2 stories (primary building) — see § 2.02.03 and Table 2.02.03-1 .
DET-3 — Detached small-lot single-family. Maximum density 3.0 units/acre, minimum lot size 10,000 sf, maximum lot coverage 40%, max height 25 ft / 2 stories — see § 2.02.03 and Table 2.02.03-1 .
SN-4 and SN-8 — Suburban neighborhood types (4 & 8 units/acre). Maximum lot coverage 50% (SN‑4) and 60% (SN‑8); max heights 30 ft (varies by zone) — see § 2.02.03 and Table 2.02.03-1 .
MH — Manufactured/mobile home park zones. Rules address space counts (e.g., 10 spaces/gross acre) and lot coverage allowances specific to mobile home developments — refer to Table 2.02.03-1 (§ 2.02.03) .

Where it applies: established neighborhoods and new subdivisions where General Plan place-types call for detached housing; confirm by checking the Official Zoning Map (§ 1.02.01–.03) .

Mixed-Use Zones (middle-housing and urban mixed-use)

Purpose & typical uses: combine residential above/behind commercial or mixed residential types to meet infill and corridor-intensification goals. See the mixed-use tables for permitted densities and FAR limits (§ 2.03.03) .

Districts and key rules (from TABLE 2.03.03-1/2 / § 2.03.03):

CN‑14, CN‑20, NC (Mixed‑use middle housing types). Typical metrics: minimum densities >8–14 units/acre, maximum densities 14–20 units/acre (varies by subzone). Non-residential maximum FAR 0.25–0.5 depending on subzone. Setbacks: front minimums generally 10 ft, front maximums for residential ground floor 25 ft (varies), interior side sometimes 0 ft except 10 ft where abutting single‑family — see § 2.03.03 and Table 2.03.03-1 .
MUN and MT (Urban mixed-use / transit-oriented). Non-residential maximum FAR 0.5 (MUN) to 1.0 (MT); height up to 55 ft/4 stories (typical) with architectural features allowed up to 60 ft in limited cases; setbacks and parking frontage limits (e.g., maximum 30% parking frontage on primary streets) are applied to encourage active frontages — see § 2.03.03 and Table 2.03.03-2 .

Special mixed‑use rules: neighborhood transition planes (45‑degree plane to protect adjacent single‑family areas), window/balcony offset requirements, and hours/operation performance standards for non‑residential uses inside mixed‑use developments are in Chapter 2.03.06 and Chapter 3.04 (Performance Standards) — verify when designing a mixed project .

Where it applies: main corridors, downtown fringe, transit- and corridor-focused sites. For downtown-specific ground-floor rules check the Downtown Indio Specific Plan referenced by the Code (§ 2.03.03 notes) .

Public / Institutional Zones

Purpose & typical uses: parks, schools, civic buildings, utilities. Development intensity is determined case‑by‑case for PI; OS (Open Space) typically has very low FAR (0.01) and density limits (e.g., single-family at 1 unit per 20 acres permitted in OS under special rules) — see TABLE 2.05.03-1 and § 2.05.03 .

Planned Development (PD) Overlay (flexible site-specific standards)

Purpose: allows projects to deviate from base-zone numeric standards where a site‑specific PD Permit/Plan provides an improved design or community benefit. The PD Overlay becomes the effective zoning inside its boundaries once adopted; PDs typically require a PD Permit, specific findings and public hearings, and have a minimum area typically 10 acres (City Council may approve smaller) — see § 2.07.04 (Planned Development Overlay (PD)) and PD procedures in Chapter 6.05.01 .

How to use PD: if standards appear constraining, a PD may be the route for site-specific deviations (but PDs have findings and public process requirements — see § 2.07.04 for findings and expiration/extension rules) .

A quick decision table — most-decision-relevant numeric standards

Topic	Representative values in common zones	Code reference
Residential max density (units/acre) — SN‑8, SN‑4, DET‑3, DE‑1	SN‑8: 8; SN‑4: 4; DET‑3: 3; DE‑1: 1	§ 2.02.03 (Table 2.02.03-1)
Mixed‑use non‑residential FAR — MUN, MT	MUN: 0.5; MT: 1.0	§ 2.03.03 (Table 2.03.03-2)
Mixed‑use max height	55 ft / 4 stories (typical; architectural features up to 60 ft)	§ 2.03.03 (Table 2.03.03-2); see § 3.01.03 for measuring heights
Residential lot coverage (examples)	DE‑1: 30%; DET‑3: 40%; SN‑4: 50%; SN‑8: 60%	§ 2.02.03 (Table 2.02.03-1)
Setbacks (mixed/use examples)	Front min 10 ft (residential ground floor); Interior side 0–10 ft depending on adjacency; Rear 10–20 ft abutting single family	§ 2.03.03 (Table 2.03.03-1)
ADU side/rear setbacks	Minimum 4 ft side and rear for new ADUs; attached/detached ADU height caps 18 ft typical; ADUs exempt from lot coverage calculations	§ 4.02.03 (ADU Development Standards)
Lot coverage calculation rules	Footprint of all structures counts; exclusions include unenclosed decks <4 ft, eaves up to 3 ft, open trellises; see diagrams	§ 3.01.05 (Lot Coverage rules & figures)

Practical guidance / synthesis (what to do first)

Always begin by confirming the property's Official Zoning Map designation (§ 1.02.01–.03) — zone selection determines which table controls (residential, mixed-use, commercial/industrial, or overlays) .
Use the zone's development table (e.g., TABLE 2.02.03‑1 for residential, TABLE 2.03.03‑1/2 for mixed‑use) to capture numeric limits (density/FAR/coverage/setbacks/height) and then apply Chapter 3.02 citywide site standards (landscaping, minimum spacing, neighborhood transitions) for compatibility issues .
When converting or adding an ADU, rely on § 4.02.03; ADUs have statewide overlays of law but the Indio Code identifies local thresholds (e.g., 4 ft side/rear minimum for new ADUs and 18 ft detached ADU height cap) — ADUs are also exempt from lot coverage in many cases (§ 4.02.03) .
For projects near single‑family neighborhoods, check neighborhood transition rules (diagonal 45° plane, window offsets, balcony offsets) in Article 2 design standards and § 2.03.06(J) to avoid surprises during review .
If an applicant needs broader deviations from numeric limits and can show superior design or public benefit, consider a Planned Development (PD) Overlay — PDs require findings, public hearings, and often a minimum area (typical minimum 10 acres) (§ 2.07.04) .

Checklist (what an applicant must satisfy before permits/clearances)

Identify the property’s zoning on the Official Zoning Map (§ 1.02.01–.03) .
Confirm the applicable zone development table (e.g., TABLE 2.02.03‑1 or TABLE 2.03.03‑2) and note height, setbacks, lot coverage, density/FAR limits (§ 2.02.03; § 2.03.03) .
Apply citywide measurement rules (height, lot area, coverage, density/FAR) from CHAPTER 3.01 when preparing plans (§ 3.01.02–.06) .
Demonstrate compliance with Chapter 3.02 site standards (landscaping, screening, separation, visibility) and provide a landscape plan per the Code; see landscaping and screening for related requirements (§ 3.02.09) .
Check parking requirements (Chapter 3.03) and include required parking in plans — see the city's parking page and Chapter 3.03 for stall counts and layout (§ 3.03.x) .
If proposing ADUs, follow § 4.02.03 ADU development standards (setbacks, height, exemptions to lot coverage) and note state ADU law interactions; see ADUs (§ 4.02.03) .
For deviation requests, examine Planned Development (PD) Overlay process (§ 2.07.04) and the required findings — PD approval path requires public notice and findings of public benefit .
Submit plans with measurements showing how all distances, FAR, and lot coverage were calculated according to the Code's measurement rules (§ 3.01.01–.06) .
Verify whether any overlays (e.g., R‑OS, PD, Major Music Festival, Bermuda Dunes airport influence) apply; overlays can change allowed intensities or trigger other compatibility rules — see overlay districts (§ 2.07.x) .

Risks & Ambiguities

Issue	Why it matters	What to verify
FAR vs lot coverage interpretation	Different calculations affect allowable building area vs. footprint; an error can mean a rejected plan.	Check § 3.01.05 (FAR rules and figure) and the zone table’s stated FAR or lot coverage limit; provide calculation sheets showing which items are excluded (eaves, open decks) .
Height measurement and architectural features	Architectural elements may be allowed above the primary height but counted differently; mis-reading leads to non‑compliance.	Confirm how heights are measured in § 3.01.03 and which features can exceed the primary cap (see mixed‑use tables noting architectural features and the measuring-height section) .
Neighborhood transition requirements (45° plane)	Impacts where upper floors can be placed near single‑family lots; costly redesign if missed.	Apply § 2.03.06(J) neighborhood transition plane early in massing studies and document window/balcony offsets .
Planned Development (PD) scope & findings	PD can grant flexibility but requires findings and public hearings; false expectations waste time.	If seeking deviations, review § 2.07.04 PD findings, minimum area, and procedure; plan for public hearing timelines and conditions .
ADU local vs state rules	State ADU laws limit some local controls (setbacks, lot coverage rules) — conflicts may invalidate local limits.	Use § 4.02.03 for local ADU standards and verify that local limitations don't conflict with state ADU law; where the Code is silent, state rules may control — verify with Planning staff .
Airport influence areas (Bermuda Dunes ALUC)	Airport overlays can limit density/intensity and trigger additional compatibility findings.	If site is in the Bermuda Dunes Airport Influence Area, coordinate with Riverside County Airport Land Use Commission and check notes in mixed‑use tables (§ 2.03.03 notes) .

Information Gaps (what the retrieved materials did not confirm)

Full, consolidated commercial zone development tables for all commercial/industrial zones (C‑1, C‑2, I‑L, I‑H, etc.) are not visible in the retrieved snippets. The Code indicates commercial/industrial zones exist, but specific numeric development tables for each commercial base zone were not found in the materials I reviewed. Verify with the Official Zoning Map and the full Article 2 tables. Not found in retrieved materials. .
Specific downtown (Downtown Indio Specific Plan) ground-floor exceptions and ground-floor use mandates are referenced but the Specific Plan text was not included in the materials. Verify Downtown Indio Specific Plan for downtown specifics. Not found in retrieved materials. .
Precise section cross‑references for every commercial subzone’s setbacks (where they exist) were not searchable in the excerpts; consult the full Code or Planning staff for parcel‑specific rulings. Verify with the jurisdiction.

Plain-English Summary

Indio's Unified Development Code (Title 17) provides clear numeric limits for each zone: densities (units/acre), lot coverage (%), heights (ft/stories), set‑backs (front/side/rear) and FAR for mixed‑use areas. Start by confirming your property's zone on the Official Zoning Map, read that zone’s development table (residential tables such as TABLE 2.02.03‑1 or mixed‑use TABLE 2.03.03‑1/2), then apply citywide rules on measurement, landscaping, and neighborhood transitions; ADUs have their own development standards in § 4.02.03 and PD overlays allow site‑specific alternatives if you meet the findings (§ 2.07.04) .

Source References

Title 17, Unified Development Code — Title and purpose: § 1.01.01 and § 1.01.02 .
Residential development standards: § 2.02.03 (Table 2.02.03‑1) — Development Regulations (Residential Zones) .
Mixed‑Use development standards: § 2.03.03 (Tables 2.03.03‑1 and 2.03.03‑2) — Mixed‑Use Zones (CN‑14, CN‑20, NC, MUN, MT) .
ADU Development Standards: § 4.02.03 (ADU rules: setbacks, heights, lot coverage exemptions) .
Measuring distances, FAR, density rules: § 3.01.02, § 3.01.05 (FAR and lot coverage), § 3.01.06 (Density) .
Citywide site standards and neighborhood transitions: Chapter 3.02 (Site Design) and § 2.03.06 (Neighborhood Transitions) .
Planned Development Overlay: § 2.07.04 (Planned Development (PD) Overlay; findings, minimum area, procedure) and PD procedures in Chapter 6.05.01 .
Use tables and permitted‑use notes (airport influence, special limits): permitted uses tables and notes in Article 2 and Table 1.02.03‑1; see § 1.02.03 and the use tables excerpted in Article 2 .

Sources

Retrieved passages

Indio Zoning Code (Chapter 154) High relevance
Indio Zoning Code (Chapter 154) High relevance
Indio Zoning Code (Chapter 3.03) High relevance
CBC § 66314 (§ 66314) High relevance
Indio Zoning Code (Chapter 4.04) High relevance
Indio Zoning Code (Section is) High relevance
CFC § 4.02.03 (§ 4.02.03.) High relevance
Indio Zoning Code High relevance
Indio Zoning Code (§ 3.01.06.) High relevance
Indio Zoning Code (Chapter 154) High relevance
Indio Zoning Code Medium relevance
Indio Zoning Code (§ 2.07.03.) Medium relevance
Indio Zoning Code (Chapter 3.03) Medium relevance
Indio Zoning Code (section is) Medium relevance

Cited sections

Official Indio code library

Frequently asked questions

What can I build on a **DE‑1** (Estate Residential) lot in Indio?

You can build uses consistent with low‑density estate residential character; the Code caps density at 1 unit/acre, sets minimum lot size 40,000 sf, maximum lot coverage 30%, and primary building height 25 ft / 2 stories (or lower if otherwise specified). Confirm permitted accessory uses in the allowed‑uses table for the DE‑1 zone and check § 2.02.03 (Table 2.02.03‑1) for the numeric standards .

What are Indio's standard front, side, and rear setbacks for mixed‑use projects?

Mixed‑use setbacks vary by subzone but typical values are front minimum ~10 ft (residential ground floor), front maximums (to encourage active frontage) of 15–25 ft depending on ground‑floor type, interior side minimums 0–10 ft (10 ft where abutting single‑family), and rear 10–20 ft when abutting single‑family. See § 2.03.03 (Tables 2.03.03‑1/2) for table‑by‑table specifics and Figure references for site setbacks .

How does Indio measure building height and allow architectural features?

Heights are measured per the Code's measurement rules in § 3.01.03. Many zones allow limited architectural projections (stair/elevator overruns, mechanical screens) to exceed primary height by a small amount — mixed‑use tables often list an architectural features allowance (e.g., buildings capped at 55 ft with features up to 60 ft). Provide measured elevations following § 3.01.03 to avoid misinterpretation .

Does lot coverage include carports, garages, and porches?

Yes — the Code defines lot coverage as the footprint of all principal and accessory structures, including garages, carports, covered patios, and roofed porches, with specific exclusions (unenclosed decks <4 ft, eaves ≤3 ft, open trellises). The lot coverage rules and illustrative figures are in § 3.01.05 .

What does Indio require for ADU setbacks, height, and lot coverage?

Indio's ADU rules in § 4.02.03 require a minimum 4‑ft side and rear setback for new ADUs (with some conversion exceptions), set the typical detached ADU height at 18 ft, and generally exempt ADUs from the underlying zone's lot coverage calculations (attached garages/carports counted) — see § 4.02.03 for full limits and conversion rules .

If my project abuts single‑family homes, are there transition rules?

Yes. The Code requires a 45‑degree diagonal transition plane measured from the abutting property line at grade to limit how close taller portions of a building can be to single‑family lots; there are also minimum offsets for windows and balconies and landscape buffer requirements in § 2.03.06(J) and related site sections .

Can I use a Planned Development (PD) to change height/setback standards?

Yes. The Planned Development Overlay (PD) permits site‑specific standards in exchange for findings showing superior design or community benefit; PDs have procedural requirements, findings, and a typical minimum area of 10 acres (although the Council may allow smaller PDs) — see § 2.07.04 for findings, minimum area, and procedures .

How do I calculate residential density for a mixed‑use development?

Density is units per gross acre of the mixed‑use project area; in mixed projects the Code counts publicly accessible private open space, public/private streets/pathways, dedicated public parkland, and required easements in lot area for density calculations — see § 3.01.06 (Density) and the mixed‑use density entries in § 2.03.03 .

Are there special rules for properties in the Bermuda Dunes Airport Influence Area?