Local zoning · Orinda

Orinda — Zoning

Q: What can I build on an R‑1 lot in Orinda?

Orinda does not use the label "R‑1" in the list of base districts; instead low‑density residential districts are designated RVL and RL and the exact permitted uses are shown in Schedule 17.3.3 (single‑family permitted in RVL and RL, accessory dwelling units are listed as permitted) § 17.3.3 . Verify the parcel's exact district on the Zoning Map § 17.1.7 .

Q: What are Orinda's setback requirements?

Setbacks are district‑specific and presented in the Chapter 17.4 schedules (for example Schedule 17.4.2(B) lists front, side and rear yard requirements such as 15 ft front and 10 ft side in many multifamily/residential columns). Use the schedule column that corresponds to your base district to read the exact numbers § 17.4.2 .

Q: Do I need design review in Orinda?

Possibly. The code requires design review for many exterior changes, new nonresidential buildings in specified districts, and new multifamily residential in certain districts (see Chapter 17.30 ). Projects in the ridgeline overlay or on severely sloped sites will often require special design review § 17.30.3–§ 17.30.7 .

Q: Are accessory dwelling units (ADUs) allowed in Orinda?

The local land‑use schedule lists Accessory dwelling unit as a permitted use in residential districts (Schedule 17.3.3 , see § 17.3.3 ). You must still meet Chapter 17 development standards and any applicable overlay rules; verify local ADU implementation with the city's ADU guidance § 17.3.3 .

Q: How does the Ridgeline (‑R) overlay affect my project?

The Ridgeline and Environmental Preservation Overlay limits default development to structures less than 500 sq ft and less than 18 ft in height unless the applicant obtains approval through the design review mechanisms; a visual analysis is required for R‑overlay applications § 17.5.4–§ 17.5.5 .

Q: What if my lot is split across two zoning districts?

A zoning district boundary can apply to portions of a lot; where a street, right‑of‑way, or map ambiguity exists the Planning Director may determine the boundary location. If your parcel is split, you must satisfy the standards applicable to each portion § 17.1.11 .

Q: When is a use permit required instead of a right‑of‑way use?

Use permits are required where a schedule entry shows a use as "U" or where additional use limitations are indicated in the district schedule (e.g., some ancillary uses and certain nonresidential uses in residential zones). See Schedule 17.3.3 and Chapter 17.31 for use permit rules § 17.3.3 , § 17.31 .

Q: Can the planned development (PD) district change base standards?

Yes. A PD district is established by ordinance and, through an approved PD plan, may modify base district controls; the PD plan must still be consistent with the general plan and the PD chapter spells out required PD submittals and minimum PD sizes § 17.12.1–§ 17.12.5 .

Q: Where are parking requirements found?

Parking requirements are set out in Chapter 17.16 and are referenced within the Chapter 17.4 development schedules; consult Chapter 17.16 for space counts and design standards § 17.16 , Schedule references in § 17.4.2 .

Q: How does the code treat nonconforming structures or uses?

Chapter 17.19 governs continuation, maintenance, and limits on enlarging or reestablishing nonconforming uses and structures; routine maintenance that does not alter the structure's appearance generally does not affect legal nonconforming status § 17.19.1–§ 17.19.3 .

Zoning under the Orinda local zoning and planning code, with the controlling citations.

Ask a question free See coverage

Last reviewed: July 2, 2026

Overview

Orinda's zoning code is adopted as Title 17 — ZONING and organizes the city into specific base districts and overlay districts, establishes the development standards that control setbacks, heights and lot coverage, and ties permitted uses to each district. The zoning map and district designators are the primary tools to determine what is allowed on a parcel; interpretive and discretionary review (for example design review) and overlay rules can change the baseline rules for a site. The code's purpose statements and mapping rules are in § 17.1.1–§ 17.1.8 and the Zoning Map rules are in § 17.1.7 .

Note: this page covers what Orinda's planning and zoning ordinance (Title 17) says about zoning — technical building code requirements under the California Building Standards Code are outside Title 17 and not summarized here. Verify parcel-specific limits with the city; where the ordinance text is silent I state "Not found in retrieved materials."

How the code is organized (quick anchors)

The zoning map and district designators: § 17.1.7, § 17.1.8 .
Residential use lists and accessory uses (including ADUs): § 17.3.3 (Schedule 17.3.3) .
Development standards (setbacks, heights, min densities): Chapter 17.4 and schedules such as 17.4.2(B) for multifamily standards .
Downtown districts and downtown-specific rules: Chapter 17.8 (e.g., § 17.8.4–17.8.5) .
Overlay districts (Ridgeline/Environmental and others): § 17.1.9 and Chapter 17.5 (R overlay) .
Design review policy and standards: Chapter 17.30 (including § 17.30.5 and § 17.30.7) .
Parking rules are in Chapter 17.16 (referenced from development tables) .

Throughout this page I link to the Orinda reference pages you’ll commonly need: the development standards, parking, design review, overlay districts, ADUs, the state building-code, and nonconforming uses for further process context.

District-by-district breakdown

Below I cover each base zoning district the code lists. For each I summarize the ordinance purpose, typical permitted uses, key dimensional controls that the text calls out, and where the district is applied (as described in the code). Every requirement below is grounded to the municipal code by the cited §.

Note on reading the code: the code uses schedules (for example Schedule 17.3.3 and Schedule 17.4.2) to present permitted uses and dimensional standards; when a schedule is referenced I show that schedule's controlling § below. See § 17.1.8 for the list of base districts .

RVL — Residential Very Low Density

Purpose: preserve very low-density, semi-rural neighborhoods and limit new subdivision and scale of homes per the general plan (see Chapter 17.1). See residential floor‑area controls in Chapter 17.6 for how home size is calculated. § 17.1.2, § 17.6.1–17.6.2 .
Typical permitted uses: single‑family residential is the baseline use; accessory uses such as garages, ADUs (Accessory dwelling units) are listed as permitted in Schedule 17.3.3 (Accessory dwelling unit = permitted in RVL) § 17.3.3 .
Key dimensional standards (examples from the development schedules): typical maximum height and setbacks for low‑density residential are reflected in the Chapter 17.4 tables (see Schedule 17.4.2 and related RM/RH tables for comparative numbers) — e.g., a common maximum building height around 27 ft and story limits are used for lower-density residential prototypes (see § 17.4.2 and related RM/RH tables) .
Where it applies: broadly across single‑family neighborhoods designated for very low densities; check the Zoning Map to confirm parcel designation § 17.1.7 .

RL — Residential Low Density

Purpose and uses: permits single‑family residential and limited ancillary uses; ADUs are permitted (Schedule 17.3.3) § 17.3.3 .
Dimensional standards: side/rear/front yard rules and height caps appear in Chapter 17.4 schedules; common measured front setbacks referenced in Schedule 17.4.2(B) are 15 ft front yard in many multifamily/residential contexts and 10 ft side yards for similar district entries (see the schedule for the exact column that maps to RL) § 17.4.2 .
Where it applies: established low‑density residential neighborhoods; confirm on the Zoning Map § 17.1.7 .

RM — Residential Medium Density

Purpose and uses: allows multifamily housing types and accessory uses (Schedule 17.3.3 lists multifamily as allowed with limitations) and includes special overlays like -SH (Senior Housing) and -HD (High Density) that modify density and yard standards § 17.3.3, § 17.1.9, Schedule 17.4.2(B) .
Dimensional highlights: the multifamily schedule (Schedule 17.4.2(B)) shows front yard 15 ft, side yard 10 ft, rear yard 10 ft, and typical maximum building height around 27 ft for RM prototypes; overlays may reduce front yard or alter density caps (see § 17.4.2(B)) .
Where: near corridors and transition neighborhoods where medium-density housing is contemplated; check Zoning Map and overlay listings § 17.1.7–§ 17.1.9 .

RH — Residential High Density

Purpose and uses: allows higher-density housing forms (multifamily) consistent with stated densities; additional subtypes in the code (for example RH‑25 and RH‑40) set differing maximum densities (see Schedule 17.4.2(B)) § 17.4.2 .
Dimensional highlights: maximum densities expressed as units/acre in the schedule (examples: 25 or 40 du/acre variants), maximum building heights indicated in the multifamily schedule (for some RH variants heights of 36 ft or 50 ft are referenced) § 17.4.2(B) .
Where: areas planned for higher-density residential growth; check the Zoning Map and any referenced enabling ordinance numbers § 17.1.7–§ 17.1.8 .

DC, DCOR, DG, DO — Downtown districts (Downtown Commercial, Downtown Core, Downtown General, Downtown Office)

Purpose: create and manage the downtown commercial core with tailored rules for retail, office, and mixed uses; the downtown chapters define interior commercial “Type I/II/III” spaces and limit office uses in prime storefront areas to preserve retail character § 17.8.4–§ 17.8.5 .
Typical permitted uses: retail and office as allowed in Chapter 17.8; multifamily residential can be permitted with a use permit if density limits are respected (see § 17.8.4) .
Key dimensional/operational rules: downtown maps and Type I/II/III space definitions affect where uses can occur; signage and Type‑specific limitations are in Chapter 17.18 and Chapter 17.8 respectively § 17.8.5, § 17.18.17 .
Where: the Village and adjacent downtown streets as defined on the Zoning Map and downtown maps embedded in Chapter 17.8 § 17.1.7, § 17.8.5 .

OS — Open Space

Purpose: preserve lands where limited development is allowed, conserve environmental resources; see Chapter 17.11 for OS rules § 17.11.1–§ 17.11.4 .
Permitted uses: parks, limited horticulture, crop production, limited animal husbandry and certain public/semi‑public uses with use permits; the OS schedule (Schedule 17.11.3) indicates which uses are permitted, limited, or require a use permit § 17.11.3 .
Dimensional/development limits: restricts further subdivision and limits residences to one single‑family unit on parcels legally created before certain dates; development standards for homes reference the RVL rules § 17.11.2–§ 17.11.4 .
Where: city open‑space parcels, ridgelines, and areas mapped as environmental preservation on the Zoning Map § 17.1.7 .

PD — Planned Development

Purpose: allow flexible comprehensive development of large parcels where a PD plan replaces portions of base standards and creates a unified plan; PD requires a PD plan and is indicated on the map as PD with an ordinance number § 17.12.1–§ 17.12.5 .
Uses and standards: no new uses other than existing ones are permitted in PD unless in accord with an approved PD plan; minimum PD sizes and the requirement to conform to general plan density are specified in § 17.12.3–§ 17.12.4 .
Where: specific large sites with an adopted PD overlay shown on the Zoning Map § 17.12.2 .

PR — Parks & Recreation

Purpose and uses: public parks and recreation facilities; special rules appear in the PR district chapter and the land‑use schedules (see § 17.1.8 for the district list; PR chapter specifics in Title 17 schedules) .

PS — Public, Semi‑public & Utility

Purpose and uses: government, institutional, major and minor utilities, public facilities; uses are controlled by Chapter entries and use permit rules (refer to Schedule entries and Chapter 17.8/17.11 for related use controls) .

SP — Specific Plan District

Purpose: to implement a site‑specific specific plan; SP is shown on the Zoning Map as SP plus the ordinance number and no use other than existing uses is permitted except as allowed by an adopted specific plan § 17.13.1–§ 17.13.5 .
Key rules: SPs carry their own development regs and may modify base standards; minimum SP area is generally 10 acres unless the City Council finds otherwise § 17.13.4 .

Quick reference: Most decision‑relevant standards (selected)

District	Typical primary uses	Representative min setbacks / height (decision‑relevant)	Code Reference
RVL	Single‑family residential; ADUs allowed	Front yard commonly measured per district; typical max height prototype ~27 ft; see RVL rules and residential floor area rules	§ 17.3.3, § 17.6.2, Schedule 17.4.2
RL	Single‑family residential; limited ancillary uses	Front ~15 ft (district columns vary); side ~10 ft; heights per 17.4 schedules	Schedule 17.4.2(B), § 17.3.3
RM	Multifamily allowed; ADUs allowed	Multifamily standards: front 15 ft, side 10 ft, rear 10 ft, max height ~27 ft (overlays may change)	Schedule 17.4.2(B), § 17.3.3
RH	Higher‑density multifamily	Max density expressed in du/acre (RH‑25, RH‑40 variants); heights 36 ft or 50 ft for some RH variants per schedule	Schedule 17.4.2(B)
DC / DCOR / DG / DO	Retail, offices, mixed uses; downtown rules	Downtown space types (I/II/III) control where offices/retail allowed; multifamily allowed with use permit at limited densities § 17.8.4–17.8.5	§ 17.8.4–§ 17.8.5
OS	Parks, limited agriculture, utilities	Limits on subdivision and residential units; many uses require a use permit	§ 17.11.2–§ 17.11.4

For full numeric and parcel‑level standards (lot area, combined side yard formulas, building plane lines, FAR/aggregate heights), consult the specific schedule columns in Chapter 17.4 and the residential floor area rules in Chapter 17.6 § 17.4.2, § 17.6.2 .

How overlays change the baseline

The code recognizes multiple overlay zoning districts including the -R Ridgeline and Environmental Preservation Overlay, -SH (Senior Housing), and -HD (High Density) § 17.1.9 .
The -R overlay imposes very strict scale limits by default: development in the R overlay is limited to less than 500 sq ft and less than 18 ft in height unless approved through design review routes (special design review), and applications must include a visual analysis § 17.5.4–§ 17.5.5 .
Overlays display on the Zoning Map and, where an overlay conflicts with base district standards, the overlay rules govern § 17.1.7 .

Design review and discretionary checks

Many exterior changes, new nonresidential buildings in downtown/other base districts, and new multifamily buildings require design review; the ordinance sets basic standards (siting/neighborhood context, design, privacy/views, landscaping) that decisionmakers must find are satisfied § 17.30.3, § 17.30.5 .
Special design review applies for severely sloped development footprints and for lots in the R overlay (height/mass and ridgeline protection standards) § 17.30.7 .
Design review findings are discretionary; projects that exceed overlay numeric caps often must proceed through design review (or seek variances) § 17.5.4, § 17.30.5 .

Checklist — what an applicant must satisfy (practical)

Determine parcel's base zoning and any overlay(s) on the Zoning Map and note any ordinance numbers tied to the designation § 17.1.7–§ 17.1.8 .
Confirm whether the proposed use is permitted by right, is limited, or requires a use permit per Schedule 17.3.3 or the applicable district schedule § 17.3.3 .
Confirm applicable development standards (setbacks, building height, lot coverage, floor‑area controls) in Chapter 17.4 and Chapter 17.6 for residential floor area calculations § 17.4.2, § 17.6.2 .
Check overlay restrictions (for example the -R overlay limits and submittal requirements) § 17.1.9, § 17.5.4–§ 17.5.5 .
Confirm whether the project triggers design review (Chapter 17.30) and prepare required visual analyses, neighborhood context studies, and landscape plans § 17.30.3–§ 17.30.7 .
Calculate parking requirements per Chapter 17.16 and include parking plans with the application § 17.16 (parking referenced in development tables) .
Confirm nonconforming status or legal pre‑existing approvals if applicable (Chapter 17.19) and whether a variance or exception is needed (Chapter 17.33) § 17.19, § 17.33 .
If proposing an accessory dwelling unit, verify local ADU rules in Schedule 17.3.3 and state ADU law as applicable (see Orinda ADU guidance and California ADU law) § 17.3.3 .

Risks & Ambiguities

Issue	Why it matters	What to verify
Parcel partly inside an overlay or split by district boundary	District boundary can apply to parts of lots and change allowable uses/standards for different portions of the same parcel § 17.1.11	Verify mapped boundary on the official Zoning Map and ask Planning Director to resolve uncertainty § 17.1.11 .
Ridgeline / R‑overlay visual interpretation	R‑overlay has strict numeric caps (e.g., < 500 sq ft, < 18 ft) but also allows exceptions via special design review; visual impacts are discretionary § 17.5.4, § 17.30.7	Expect a required visual analysis and discretionary findings; verify whether your lot is exempted under § 17.5.6 for certain North Orinda subdivisions .
Design review findings are discretionary	Even if numeric standards are met, design review must show compatibility with neighborhood context and ridgeline/hillside guidelines § 17.30.5	Provide context drawings, massing studies and landscape screening to support findings; verify whether project is routed to Planning Commission or Zoning Administrator § 17.30.3 .
Nonconforming uses/structures	Pre‑existing uses may limit or permit continuation or modification; improper assumptions can cause permit denial § 17.19.1–§ 17.19.3	Confirm legal nonconforming status, limits on expansion, and whether a use permit or other relief is required § 17.19 .
Downtown Type I/II/III classification	Where the commercial space sits (Type I vs Type II) affects whether retail or office uses are allowed and whether office must amortize in certain prime spaces § 17.8.5	Verify building face/street segment against the downtown Space Utilization Map in Chapter 17.8 and confirm Type classification § 17.8.5 .

Plain‑English summary

Orinda’s Title 17 assigns each parcel a base district and possibly overlays; the base district (for example RL, RM, DC) tells you the kinds of uses allowed and the Chapter 17.4 schedules tell you the setbacks, heights and density you must meet, while overlays like the -R Ridgeline overlay can impose much stricter limits and require visual analyses and special design review § 17.1.7–§ 17.1.9, § 17.4.2, § 17.5.4–§ 17.5.5 .

Source References

Title 17 — Planning & Zoning Code: purpose, scope and Zoning Map rules § 17.1.1–§ 17.1.8 .
Residential districts and the RVL/RL/RM/RH Schedule: § 17.3.3 (Schedule 17.3.3) .
Development standards and multifamily schedule (setbacks, heights, densities): Chapter 17.4, Schedule 17.4.2(B) .
Ridgeline and Environmental Preservation Overlay: Chapter 17.5, specifically § 17.5.4–§ 17.5.6 .
Planned Development district rules: Chapter 17.12 § 17.12.1–§ 17.12.5 .
Downtown district use rules and Type I/II/III commercial space: § 17.8.4–§ 17.8.5 (Downtown Commercial) .
Design review standards and special design review (hillside/ridge): Chapter 17.30, including § 17.30.5 and § 17.30.7 .
Nonconforming uses and structures: Chapter 17.19 § 17.19.1–§ 17.19.3 .
Residential floor‑area controls (how allowed home size is determined): Chapter 17.6, including § 17.6.1–§ 17.6.2 .
Development tables and cross references (parking, open space minima): Schedule excerpts and cross references in Chapter 17.4 tables; see Schedule 17.4.2 and related tables § 17.4.2 .

Sources

Retrieved passages

Orinda Zoning Code (§ 2) High relevance
Orinda Zoning Code (§ 2) High relevance
Orinda Zoning Code (§ 33) High relevance
Orinda Zoning Code (§ 2) High relevance
Orinda Zoning Code (Title 17) High relevance
Orinda Zoning Code (§ 2) Medium relevance
Orinda Zoning Code (§ 2) Medium relevance
Orinda Zoning Code (§ 33) Medium relevance

Cited sections

Official Orinda code library

Frequently asked questions

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

Orinda does not use the label "R‑1" in the list of base districts; instead low‑density residential districts are designated RVL and RL and the exact permitted uses are shown in Schedule 17.3.3 (single‑family permitted in RVL and RL, accessory dwelling units are listed as permitted) § 17.3.3 . Verify the parcel's exact district on the Zoning Map § 17.1.7 .

What are Orinda's setback requirements?

Setbacks are district‑specific and presented in the Chapter 17.4 schedules (for example Schedule 17.4.2(B) lists front, side and rear yard requirements such as 15 ft front and 10 ft side in many multifamily/residential columns). Use the schedule column that corresponds to your base district to read the exact numbers § 17.4.2 .

Do I need design review in Orinda?

Possibly. The code requires design review for many exterior changes, new nonresidential buildings in specified districts, and new multifamily residential in certain districts (see Chapter 17.30). Projects in the ridgeline overlay or on severely sloped sites will often require special design review § 17.30.3–§ 17.30.7 .

Are accessory dwelling units (ADUs) allowed in Orinda?

The local land‑use schedule lists Accessory dwelling unit as a permitted use in residential districts (Schedule 17.3.3, see § 17.3.3). You must still meet Chapter 17 development standards and any applicable overlay rules; verify local ADU implementation with the city's ADU guidance § 17.3.3 .

How does the Ridgeline (‑R) overlay affect my project?

The Ridgeline and Environmental Preservation Overlay limits default development to structures less than 500 sq ft and less than 18 ft in height unless the applicant obtains approval through the design review mechanisms; a visual analysis is required for R‑overlay applications § 17.5.4–§ 17.5.5 .

What if my lot is split across two zoning districts?

A zoning district boundary can apply to portions of a lot; where a street, right‑of‑way, or map ambiguity exists the Planning Director may determine the boundary location. If your parcel is split, you must satisfy the standards applicable to each portion § 17.1.11 .

When is a use permit required instead of a right‑of‑way use?

Use permits are required where a schedule entry shows a use as "U" or where additional use limitations are indicated in the district schedule (e.g., some ancillary uses and certain nonresidential uses in residential zones). See Schedule 17.3.3 and Chapter 17.31 for use permit rules § 17.3.3, § 17.31 .

Can the planned development (PD) district change base standards?

Yes. A PD district is established by ordinance and, through an approved PD plan, may modify base district controls; the PD plan must still be consistent with the general plan and the PD chapter spells out required PD submittals and minimum PD sizes § 17.12.1–§ 17.12.5 .

Where are parking requirements found?

Parking requirements are set out in Chapter 17.16 and are referenced within the Chapter 17.4 development schedules; consult Chapter 17.16 for space counts and design standards § 17.16, Schedule references in § 17.4.2 .

How does the code treat nonconforming structures or uses?

Chapter 17.19 governs continuation, maintenance, and limits on enlarging or reestablishing nonconforming uses and structures; routine maintenance that does not alter the structure's appearance generally does not affect legal nonconforming status § 17.19.1–§ 17.19.3 .

Ask about any Orinda property

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

Start Free Trial