Indio — Zoning

Last reviewed: July 2, 2026

Overview

This page summarizes how the City of Indio defines and applies zoning under the Title 17 Unified Development Code (the "Indio Development Code"). The Code establishes an Official Zoning Map and a set of base zones and overlay zones (Table 1.02.03-1) that control allowed uses, development standards, and review procedures. Find your parcel on the Official Zoning Map first, then use the zone-specific allowed-use tables and development standards cited below to determine what is permitted and what discretionary permits may be required (§ 1.02.01, § 1.02.02) .

Article 2 of the Code organizes the zones into groups (Residential Neighborhood, Mixed-Use, Non‑Residential, Public/Institutional, Specific Plans / Project Master Plans) and identifies overlays; the City applies zone text plus the Official Zoning Map maintained by Community Development as the controlling source of zoning for any parcel (see Table 1.02.03-1) .

District-by-district breakdown

Below each subsection names the zone symbol in bold, gives its stated purpose, typical permitted uses (summary), the key numeric standards shown in the Code where present (setbacks, height, density/FAR), and where that zone is governed in the Code. When numeric standards are not reproduced in the retrieved materials I note that and point to the controlling chapter.

Note: when the Code refers to an adopted Specific Plan or Project Master Plan, that plan controls in place of base-zone tables where it is in effect; see SP/PMP below and § 2.06.02 for the rule that Specific Plans govern where adopted .

DET-3 (Desert Estates Transition - 3)

• Purpose: Implements the General Plan Desert Estates place-type; transition residential zone for low-density desert estates. See Table 1.02.03-1 and Chapter 2.02 for use tables.
• Typical uses: large‑lot single‑family residential and accessory uses (see Chapter 2.02).
• Key standards: Specific numeric lot area, setbacks and height are set in Chapter 2.02 (Residential Zones). Not found in retrieved materials: exact numbers for DET-3; verify in Chapter 2.02.

SN-4 (Suburban Neighborhood - 4)

• Purpose: Implements lower-density suburban neighborhoods. See Table 1.02.03-1 and Chapter 2.02.
• Typical uses: single-family homes, accessory dwelling units (ADUs) per Chapter 4.02; neighborhood parks and allied uses. ADUs are allowed as accessory units in mixed-use tables and are governed by Chapter 4.02 as well.
• Key standards: Not found in retrieved materials: exact minimum lot size, setbacks, and height for SN‑4 (see Chapter 2.02). Verify with the Code.

SN-8 (Suburban Neighborhood - 8)

• Purpose: Similar to SN‑4 but higher allowable density within the Suburban Neighborhood place-type. See Table 1.02.03-1.
• Typical uses: single‑family and compatible accessory uses; ADUs allowed as accessory units (Chapter 4.02).
• Key standards: Specific numeric standards for SN‑8 are in Chapter 2.02 and are not shown in the retrieved snippets. Verify with the Code.

CN-14 (Connected Neighborhood - 14)

• Purpose: A mixed-use, walkable neighborhood scale intended to provide daily retail and services near housing; implements the Connected Neighborhood place-type. See Chapter 2.03 and Table 2.03.02-1.
• Typical permitted uses: neighborhood retail (small shops), service uses, small restaurants, some office, limited civic uses. Uses are listed in TABLE 2.03.02-1; permissions vary (P, AUP, CUP). See that table for the exact permit requirement for each use (e.g., General Retail ≤ 5,000 sf = P in many MU zones) .
• Key standards (mixed‑use middle housing table): Residential density minimum > 8.0 units/acre, maximum 14.0 units/acre; minimum front setback 10 ft; maximum height in CN middle‑housing is typically 40 ft / 3 stories (see TABLE 2.03.03‑1 and Figure references) .

CN-20 (Connected Neighborhood - 20)

• Purpose and uses: similar to CN‑14 but allows higher residential intensity and project scale; see Chapter 2.03 and TABLE 2.03.02‑1 for permitted uses. .

NC (Neighborhood Center)

• Purpose: Small neighborhood centers for more concentrated commercial/residential mix. See Chapter 2.03 and TABLE 2.03.02‑1.
• Typical uses: retail, small service businesses, civic uses, limited residential (sometimes upper floors). Many uses are permitted with AUP/CUP depending on size; consult TABLE 2.03.02‑1 for per‑use permit types.
• Key standards: Mixed‑use tables show a maximum residential density often 20 units/acre and setbacks such as minimum front 10 ft and rear 15 ft depending on adjacency to single‑family zones (see TABLE 2.03.03‑1). .

MUN (Mixed‑Use Neighborhood)

• Purpose: Higher-intensity mixed‑use neighborhood center supporting multi‑story residential and non‑residential uses. See Chapter 2.03, TABLE 2.03.03‑2.
• Typical uses: Multifamily residential, ground-floor retail and restaurants, offices, community uses. Many uses are permitted (P) or allowed by AUP/CUP; see TABLE 2.03.02‑1 for details.
• Key standards (TABLE 2.03.03‑2): Residential density minimum 20.0 units/acre; maximum 40.0 units/acre; Non‑residential FAR 0.5; Maximum height up to 55 ft / 4 stories with architectural features up to 60 ft (see TABLE 2.03.03‑2) .

MT (Midtown)

• Purpose: Implements the Midtown place-type for an active, higher‑intensity corridor (notably the Highway 111 corridor near Indio Grand Marketplace) to support mixed‑use, multi‑story buildings and public gathering spaces. See Chapter 2.03 (Midtown) and TABLE 2.03.03‑2.
• Typical uses: vertical/horizontal mixed use, multi‑story residential up to 40 units/acre to 40+ per the table; community-serving commercial and entertainment uses. Permitting varies by use and size (see TABLE 2.03.02‑1).
• Key standards: Minimum residential density 20.0 units/acre; Maximum 40.0 units/acre; Maximum height 55 ft / 4 stories (see TABLE 2.03.03‑2); strict parking frontage limits (max 30% of primary street frontage devoted to parking) to encourage urban frontage. .

DT (Downtown)

• Purpose: Downtown core; the Code defers to the Indio Downtown Specific Plan for detailed regulations. See Chapter 2.03 note referencing the Downtown Specific Plan.
• Typical uses and standards: See the Downtown Indio Specific Plan; the base zone is listed in Table 1.02.03‑1 but detailed ground‑floor use rules and frontage requirements live in the Specific Plan (not fully reproduced in the retrieved snippets). Not found in retrieved materials: full downtown numeric standards — consult the Downtown Specific Plan and Community Development.

RC (Regional Commercial)

• Purpose: Large-scale commercial and regional retail centers. See Chapter 2.04 and TABLE 2.04.03‑1.
• Typical uses: regional shopping, big‑box retail, commercial services; some uses (e.g., superstores > 50,000 sf) trigger a CUP per table notes. See TABLE 2.04.03‑1 and TABLE 2.03.02‑1 notes.
• Key standards (TABLE 2.04.03‑1): Minimum lot size 40,000 sf; Maximum FAR 1.0; Maximum height 55 ft/3 stories (see TABLE 2.04.03‑1).

IL (Light Industrial)

• Purpose: Workplace and employment district for light industrial/manufacturing and compatible services. See Chapter 2.04 and TABLE 2.04.03‑1.
• Typical uses: light manufacturing, warehousing, distribution, business services (use permissions in TABLE 2.04.).
• Key standards: Minimum lot size 10,000 sf; Maximum FAR 1.0; Maximum height 55 ft / 3 stories; setbacks commonly 10 ft front (see TABLE 2.04.03‑1).

IH (Heavy Industrial)

• Purpose: Heavy industrial/resource recovery uses where appropriate. See Chapter 2.04 and TABLE 2.04.03‑1.
• Typical uses: heavy manufacturing, resource recovery operations (some uses may be prohibited in other zones). See the Prohibited Uses list and Chapter 4 use regs.
• Key standards: Minimum lot size 20,000 sf; Maximum FAR 1.0; Maximum height 55 ft / 3 stories with 45‑degree transition to adjacent residential zones (TABLE 2.04.03‑1).

RR (Resource Recovery)

• Purpose: Zones for waste/resource recovery uses; see Chapter 2.04 and Table 1.02.03‑1.
• Typical uses and standards: Specific uses and standards are set in Chapter 2.04 and the Prohibited Uses list; consult TABLE 2.04.03‑1 for development standards. Not all numeric RR standards are reproduced in the retrieved snippets. Verify with Chapter 2.04.

PI (Public and Institutional)

• Purpose: Public and institutional uses (schools, government buildings, community facilities). See Chapter 2.05 and TABLE 2.05.03‑1.
• Typical uses: civic, educational, emergency services and parks where appropriate; uses reviewed case‑by‑case for intensity.
• Key standards (TABLE 2.05.03‑1): Maximum height 45 ft / 3 stories (primary building), FAR/intensity often evaluated on a case‑by‑case basis; OS (Parks/Open Space) has a maximum density of 0.05 units/acre for limited residential uses in open space zones.

OS (Parks and Open Space)

• Purpose: Parks, natural open space, and low‑intensity recreation. See Chapter 2.05 and TABLE 2.05.03‑1.
• Typical uses: parks, trails, habitat management consistent with CVMSHCP where applicable; density and building intensity are minimal (see table).

SP/PMP (Specific Plans / Project Master Plans)

• Purpose: Areas governed by an adopted Specific Plan or Project Master Plan. Where adopted, the specific plan document governs all use and development within its boundaries (§ 2.06.02).
• Typical uses and standards: Governed entirely by the adopted plan; where silent, base Code provisions apply. Verify relevant Specific Plan documents with Community Development.

Overlay zones (summary)

• The Code uses overlays to add or modify regulations within a base zone. Overlays listed in Table 1.02.03‑1 include R‑OS (Resource Management and Open Space), FD (Festival District), ES (Emergency Shelter Overlay), and -PD (Planned Development Overlay). Overlays apply where the Official Zoning Map shows them and supplement or supersede base rules when conflict exists (§ 1.02.02, § 2.07.01) .

R‑OS (Resource Management and Open Space Overlay)

• Purpose: Protect open space and CVMSHCP‑designated resource areas; allowed uses and standards largely defer to the underlying base zone plus any CVMSHCP requirements (§ 2.07.03) .

PD (Planned Development Overlay)

• Purpose: Provides site‑specific flexibility; once adopted the PD becomes the effective zoning for its area. Minimum PD area is 10 acres unless the City Council finds otherwise; PD procedures and required findings are in § 2.07.04 and Chapter 6.05.01 (Planned Developments). PD allows uses consistent with the base zone but development regulations are established by the approved PD plan; where silent, base zone standards apply. See § 2.07.04 for required findings and § 6.05.01 for PD procedures.

FD (Festival District) and ES (Emergency Shelter Overlay)

• Purpose and rules: The Festival District and Emergency Shelter Overlay are defined overlay zones listed in Table 1.02.03‑1; see Chapter 2.07 for their purpose and applicability. Specific provisions (for example, Major Music Festival regulations) reference prior Municode chapters and adopted ordinances (Municode Chapter 159 and Ordinance No. 1765 for MMF). Verify event‑specific procedures with Community Development.

Quick reference table — decision‑relevant zones and standards

(For full per‑use permit types see the allowed‑uses tables, e.g., TABLE 2.03.02‑1 for mixed use; ADUs are permitted as accessory units — see Chapter 4.02) .

How to use this information (practical guidance)

• Step 1 — Locate the parcel on the City's Official Zoning Map; the Map is the controlling geographic application of the zones (§ 1.02.01, § 1.02.02) .
• Step 2 — Read the allowed‑uses table for the base zone (Article 2) to see if your proposed use is P, AUP, CUP, A, or X (not permitted) — e.g., consult TABLE 2.03.02‑1 for mixed‑use zones (P/AUP/CUP/X) .
• Step 3 — Pull the zone's development standards (setbacks, height, lot size, FAR, parking) from the applicable development standards table (Article 2 and Article 3). For parking requirements consult the City’s parking chapter and apply the minimums in Chapter 3.03 (link below). See TABLE 2.03.03‑1/2 for mixed‑use dimensional controls and parking frontage limits. .
• Step 4 — Check overlays and Specific Plans that may modify the base zone (overlays listed in Table 1.02.03‑1 and Chapter 2.07) and verify Bermuda Dunes Airport compatibility if within that influence area. Overlays may impose additional requirements or allow special uses (e.g., Major Music Festival rules referencing prior ordinances). .
• Step 5 — For any discretionary entitlement (CUP, PD, AUP) follow the permit procedures in Article 6; PDs require City Council adoption and a PD Permit/Plan per § 2.07.04 and § 6.05.01. .

Inline links you will find useful while following these steps: see the City’s pages for Indio zoning & planning overview, Indio Land Use, Indio Development Standards, Indio Parking, Indio Design Review, Indio Overlay Districts, and Indio ADUs. Where work will trigger building permits, consult the California Building Standards Code for construction standards (Title 24) — but note this page covers zoning only.

Checklist

• Locate the parcel on the Official Zoning Map and record the base zone and any overlay designations (§ 1.02.01, § 1.02.02)
• Confirm whether the proposed use is Permitted (P), Accessory (A), AUP, CUP, or Not Permitted (X) in the zone table (see TABLE 2.03.02‑1 for mixed‑use examples)
• Pull the zone’s numeric standards (lot size, setbacks, height, density/FAR) from the applicable development standards table (e.g., TABLE 2.03.03‑1/2, TABLE 2.04.03‑1, TABLE 2.05.03‑1)
• Apply parking minimums per Chapter 3.03 and confirm whether shared parking, on‑street credits, or reductions apply (see Chapter 3.03)
• Check overlays (R‑OS, PD, FD, ES, MMF, etc.) and Specific Plan boundaries — if inside a Specific Plan, the Specific Plan governs (§ 2.06.02)
• Determine whether a discretionary permit (CUP, PD Permit, AUP) is required and prepare findings/justification per Article 6 and the PD findings in § 2.07.04 (if PD)
• For ADUs follow Chapter 4.02 (ADU rules referenced in the allowed‑uses tables) and state ADU law where relevant; confirm parking and development standards that interact with ADUs.

Risks & Ambiguities

Plain-English Summary

Indio’s zoning is implemented through an Official Zoning Map and a set of base zones (residential, mixed‑use, commercial/industrial, public/institutional) plus overlays and Specific Plans; the Code’s allowed‑use tables tell you whether a use is permitted or needs a permit, and the development standards tables state setbacks, height, density/FAR, and parking rules — always start by finding the parcel on the Official Zoning Map and then read the specific tables cited in Article 2 and the development standards tables in Article 3 to confirm what you can build or operate (§ 1.02.01, § 1.02.02) .

Source References

• Title 17, Unified Development Code (Indio Development Code), Title/Cover and purpose: § 1.01.01 and Purpose §§ 1.01.02–1.01.04.
• Official Zoning Map and relationship to zones: § 1.02.01, § 1.02.02, and Table 1.02.03‑1 (Base Zones and Overlay Zones) (lists DET‑3, SN‑4, SN‑8, CN‑14, CN‑20, MUN, NC, MT, DT, RC, IL, IH, RR, PI, OS, SP/PMP, R‑OS, FD, ES, PD).
• Mixed‑Use zones allowed uses and development standards: § 2.03.02 (TABLE 2.03.02‑1 Allowed Uses), § 2.03.03 (TABLE 2.03.03‑1/2 Development Standards) (includes CN‑14, CN‑20, NC, MUN, MT, DT references)
• Non‑residential development standards: § 2.04.03 (TABLE 2.04.03‑1 for RC, IL, IH)
• Public/Institutional development standards: § 2.05.03 (TABLE 2.05.03‑1 for PI, OS)
• Overlay zones: Chapter 2.07 (including § 2.07.01 general overlay policy, § 2.07.03 R‑OS, and § 2.07.04 PD overlay rules and findings)
• Planned Developments (PD) procedures and findings: § 2.07.04 and Chapter 6.05.01 (procedures referenced) — PD minimum area 10 acres, PD Permit processed as map amendment and PD Permit per § 6.05.01 (see PD text).
• How to use and cross‑references (how tables work, permitted/conditional definitions): § 1.03.01 (How to use this Code), § 2.01.04 (Allowed Uses and Permit Requirements) and related allowed uses explanation.
• Nonconforming uses and repair/reconstruction rules: Chapter 6.07 (nonconforming provisions).

Retrieved passages

• Indio Zoning Code (Chapter 154) High relevance show source text
• Indio Zoning Code (§ 2.07.03.) High relevance show source text
• Indio Zoning Code High relevance show source text
• Indio Zoning Code (Chapter 3.03) Medium relevance show source text
• Indio Zoning Code (§ 1.01.10.) Medium relevance show source text
• Indio Zoning Code (Chapter 3.03) Medium relevance show source text
• Indio Zoning Code (Article 2) Medium relevance show source text
• Indio Zoning Code (Section establishes) Medium relevance show source text
• Indio Zoning Code (Chapter 154) High relevance show source text
• Indio Zoning Code (§ 1.01.07.) Medium relevance show source text
• Indio Zoning Code (§ 2.03.03.) Medium relevance show source text
• Indio Zoning Code (Chapter 154) Medium relevance show source text
• Indio Zoning Code Medium relevance show source text
• Indio Zoning Code (§ 2.03.02.) Medium relevance show source text

Cited sections

• Title 17, Unified Development Code (Indio Development Code), Title/Cover and purpose: **§ 1.01.01** and Purpose §§ **1.01.02–1.01.04**. (Title 17)
• Official Zoning Map and relationship to zones: **§ 1.02.01**, **§ 1.02.02**, and **Table 1.02.03‑1 (Base Zones and Overlay Zones)** (lists **DET‑3, SN‑4, SN‑8, CN‑14, CN‑20, MUN, NC, MT, DT, RC, IL, IH, RR, PI, OS, SP/PMP, R‑OS, FD, ES, PD**). fileciteturn0file4 (§ 1.02.01)
• Mixed‑Use zones allowed uses and development standards: **§ 2.03.02** (TABLE **2.03.02‑1** Allowed Uses), **§ 2.03.03** (TABLE **2.03.03‑1/2** Development Standards) (includes **CN‑14, CN‑20, NC, MUN, MT, DT** references) fileciteturn1file7 (§ 2.03.02)
• Non‑residential development standards: **§ 2.04.03** (TABLE **2.04.03‑1** for **RC, IL, IH**) (§ 2.04.03)
• Public/Institutional development standards: **§ 2.05.03** (TABLE **2.05.03‑1** for **PI, OS**) (§ 2.05.03)
• Overlay zones: Chapter **2.07** (including **§ 2.07.01** general overlay policy, **§ 2.07.03** R‑OS, and **§ 2.07.04** PD overlay rules and findings) fileciteturn1file14 (§ 2.07.01)
• Planned Developments (PD) procedures and findings: **§ 2.07.04** and Chapter **6.05.01** (procedures referenced) — PD minimum area **10 acres**, PD Permit processed as map amendment and PD Permit per **§ 6.05.01** (see PD text). fileciteturn0file1 (§ 2.07.04)
• How to use and cross‑references (how tables work, permitted/conditional definitions): **§ 1.03.01** (How to use this Code), **§ 2.01.04** (Allowed Uses and Permit Requirements) and related allowed uses explanation. fileciteturn0file4 (§ 1.03.01)
• Nonconforming uses and repair/reconstruction rules: Chapter **6.07** (nonconforming provisions).
• Indio_ZoningCode.md

• Official Indio code library