Local zoning · Azusa

Azusa — Parking

Q: Can I put required parking on a different site?

Yes — the code allows designated off‑site parking up to 300 feet away if a recordable covenant or easement acceptable to the city attorney is recorded; a copy must be on file before a certificate of occupancy is issued. § 88.36.120

Parking under the Azusa local zoning and planning code, with the controlling citations.

Ask a question free See coverage

Last reviewed: July 3, 2026

Overview

This page explains how off‑street parking, loading, and bicycle/motorcycle parking are regulated under Azusa’s Development Code (commonly codified as the city’s zoning regulations). It synthesizes where parking counts come from, how parking must be designed and located, how reductions/alternatives are handled (TOD/mixed‑use/variances), and special rules for disabled, bicycle, motorcycle, driveway and off‑site parking. Off‑street parking is handled in Chapter 88.36 of the Development Code; district placement and exceptions are in the Article 2 neighborhood/district chapters. Parking is required for new uses and must meet both the Chapter 88.36 standards and the applicable district/site standards in Article 2. § 88.36.020 .

(Note: this page links into Azusa’s internal guidance pages where topics appear naturally: the first mention of parking links to the city zoning page, setbacks/design details link to Development Standards, and other related topics are linked below.)

How the Azusa code organizes parking rules (quick map)

Off‑street parking required for new uses and for expansions: § 88.36.020 .
Count/ratios set by a parking table (Table 3‑7) and special tables (e.g., loading Table 3‑10): § 88.36.050, § 88.36.110 .
Design/placement/dimensions in § 88.36.090 (plus surfacing, curbing, lighting, stall size): § 88.36.090, § 88.36.080 .
Bicycle & motorcycle parking rules in § 88.36.070; accessible parking must follow Title 24/ADA guidance and counts per § 88.36.060 .
Off‑site parking allowed under conditions (maximum 300 ft, recorded covenant): § 88.36.120 .
Reductions/alternatives (shared parking, TOD, variances) are authorized in § 88.36.080 and related mixed‑use/TOD rules: § 88.36.080 .

(First internal links: the first mention of parking above links to the city zoning overview: Azusa Zoning. Later references link to other internal pages as noted below.)

District‑by‑district (how parking interacts with each Azusa district / corridor)

Note on reading these subsections: the Development Code separates parking COUNT rules (Article 3 / Chapter 88.36) from PARKING PLACEMENT rules (Article 2 — the neighborhood/district/corridor chapters). Where a district has special placement or relief, that is called out below. Always satisfy both the district standards and Chapter 88.36. See the city’s district summaries at Azusa Land Use and the specific development rules at Azusa Development Standards.

CAZ — Azusa Avenue Corridor

Purpose: Corridor‑oriented commercial/residential frontage along Azusa Avenue; emphasis on pedestrian orientation and limited visible surface parking. (District rules in Article 2 apply.) See § 88.24.010 for building placement standards that affect where parking may go; parking itself must comply with Chapter 88.36. § 88.36.090.A .
Typical uses: general retail, restaurants, mixed‑use residential over commerce (permitted uses shown in Table 2‑3). Parking for mixed‑use projects may use shared parking provisions under § 88.36.080. § 88.36.080 .
Key practical note: expect parking to be sited to the rear or side of lots where the corridor standard requires street‑facing active uses; verify front setback and frontage type in the CAZ district chapter. § 88.36.090.A .

CSG — San Gabriel Avenue Corridor

Purpose: Similar corridor rules to CAZ with pedestrian emphasis; parking placement follows the corridor’s building placement rules. See Article 2 corridor table and Chapter 88.36 for counts and design standards. § 88.36.090.A .
Typical uses: neighborhood retail, services, small‑scale mixed use (see Table 2‑3). Parking for uses that front the street is often expected to be internalized or behind structures; verify the corridor’s specific frontage and setback requirements in the district chapter. (Verify with the jurisdiction.)

CSA — South Azusa Avenue Corridor

Purpose & uses: corridor‑scale retail/residential; parking placement per district; counts per Chapter 88.36. § 88.36.010, § 88.36.090 .
Practical: mixed use projects can use shared parking reductions under § 88.36.080 if they meet mixed‑use criteria in § 88.42.120. § 88.36.080 .

CAH — Arrow Highway Corridor

Purpose & uses: auto‑oriented corridor features exist here; district chapters set building placement and allowable driveway widths which influence where parking can be located (see § 88.36.100 on driveways/site access). § 88.36.100 .
Practical: expect specific driveway and curb cut limits; see § 88.36.100 (driveway counts, widths, clearance). § 88.36.100 .

CFB — Foothill Boulevard Corridor

Purpose & uses: similar to other corridors but consult Table 2‑5 and corridor chapter for exact parking placement and frontage rules. Parking counts remain under Chapter 88.36; placement and landscaping references are handled in Article 2 and Chapter 88.34 (landscaping of parking). § 88.36.090, § 88.34.050 .

DE — Edgewood District

Purpose: residential neighborhood district with its own Article 2 site planning rules; parking for single‑family dwellings tied to driveway/garage rules (one driveway for a single‑family unless minor use permit) and guest parking rules for certain developments. § 88.36.100 .
Typical uses: single‑family and low‑rise residential; parking expectations emphasize private on‑site garages/driveways and limits on visible carports.

DW / DWL — West End Industrial / West End Light Industrial

Purpose: industrial districts where on‑site parking and loading are critical; loading spaces required per Table 3‑10 and location/screening standards in § 88.36.110. § 88.36.110 .
Practical: loading must not be in required setbacks and should be screened from streets and residential uses; confirm truck delivery hours when adjacent to residential per the district overlay rules. § 88.36.110 .

TOD Specific Plan / Park‑Once District

Purpose: the TOD Specific Plan contains its own parking rules for areas around transit; projects in the TOD are explicitly directed to follow the Specific Plan’s parking table or alternatives rather than the general Chapter 88.36 counts. § 88.36.050.B .
Practical: projects may participate in a city "park once" program and use shared/alternative parking strategies (see § 88.36.080 and the TOD Specific Plan). § 88.36.080 .

Overlays (example: Downtown North II — Target Overlay / DNT)

Purpose: overlays can modify building placement and parking expectations. The DNT overlay sets zero front/side setbacks and refers projects back to base district development standards while calling out parking design expectations (e.g., parking stall sizes, landscaping exemptions for structured parking). The overlay cites Chapter 88.36 for parking and notes specific stall size and structured parking facade requirements. § 88.27.60, § 88.36.080 .
Practical: always check overlay language (e.g., DNT) because it can override or refine where parking is allowed and what design treatments are required.

Key rules & decision‑relevant standards (quick reference table)

Topic	Rule / Standard (plain English)	Code Reference
Off‑street parking required for new uses	Every new use/structure or change/expansion must provide off‑street parking before occupancy.	§ 88.36.020
How many spaces (count)	Use the land‑use parking schedule (Table 3‑7). Fractions round up; downtown/TOD may use other tables.	§ 88.36.050
Parking location / placement	Required parking must be located per Article 2 district/corridor placement rules (rear/side emphasis in many corridors).	§ 88.36.090.A
Design & surfacing	Parking must be paved/all‑weather surface (2" asphaltic concrete or city‑approved alternative), striped, curbed/wheel stops, landscaped per Chapter 88.34.	§ 88.36.090.I, § 88.36.080.J
Stall size / layout	Standard stall size used in Azusa is 9 ft x 18 ft (see development standards); structured parking must be wrapped/treated on street level.	§ 88.36.080 (stall size note)
Accessible parking	Must comply with Title 24 / Federal ADA; accessible stalls count toward totals.	§ 88.36.060 and California Building Standards Code
Bicycle parking	Multi‑family and nonresidential: minimum 1 bike space per 20 auto spaces up to 100 (min 2); device, size and placement standards stated in code.	§ 88.36.070
Motorcycles	1 motorcycle space per 50 auto spaces (min dims 4 ft x 7 ft).	§ 88.36.070.B
Loading	Nonresidential uses must provide loading per Table 3‑10; location, screening, and hours limits apply.	§ 88.36.110 (Table 3‑10)
Off‑site parking	Allowed up to 300 ft away with recordable covenant/easement; certificate of occupancy withheld until recorded.	§ 88.36.120
Reductions / alternatives	Shared parking, variance, senior housing reductions, and mixed‑use/TOD reductions available per code; review authority discretion applies.	§ 88.36.080

Practical guidance and comparisons

If you are designing a retail or mixed‑use project in a corridor (for example CAZ or CSG), count your required spaces from Table 3‑7 (Chapter 88.36) but expect the district frontage rules to require parking to be behind or wrapped by active uses — the corridor requirements will override placement and may encourage shared parking or TOD alternatives. § 88.36.050, § 88.36.090.A .
For projects near the Gold Line TOD or inside the TOD Specific Plan, the Specific Plan parking table may apply instead of Table 3‑7 — always check the Specific Plan first. § 88.36.050.B .
Bicycle parking is a separate requirement: even if you obtain a shared‑parking reduction for autos, you still must provide the bicycle racks/spaces called for in § 88.36.070 and install them close to primary entrances. § 88.36.070 .
Accessible parking and disabled stalls are governed by the California Building Standards Code / Title 24; Azusa’s code defers to those standards for counts and dimensions and counts those stalls toward the Chapter 88.36 totals. § 88.36.060 .

(First natural mentions of several related topics linked above: Azusa Zoning, Azusa Development Standards, Azusa Design Review, Azusa Overlay Districts, Azusa ADUs, California Building Standards Code.)

Checklist (what an applicant must satisfy before occupancy)

Provide the number of off‑street parking spaces required by Table 3‑7 (round fractional spaces up) or follow TOD/Special Plan table if applicable. § 88.36.050
Install required bicycle parking devices and motorcycle spaces where applicable. § 88.36.070
Design parking areas to meet surfacing, striping, curbing/wheel‑stop, lighting and landscaping standards in § 88.36.090 / 88.36.080 and Chapter 88.34. § 88.36.090, § 88.36.080
Provide required accessible parking stalls per the California Building Standards Code / Title 24; ensure counts are included in totals. § 88.36.060
Locate parking per the applicable district/corridor Article 2 placement rules (rear/side preference in many corridors); coordinate with planning staff for frontage expectations. § 88.36.090.A
If using off‑site parking, secure and record a covenant/easement acceptable to the city attorney; submit attested copy before occupancy. § 88.36.120
If requesting parking reductions (shared parking, variance, senior housing, mixed‑use/TOD), prepare quantitative justification and apply through the review authority. § 88.36.080
Ensure loading areas meet the loading schedule and siting/screening rules (Table 3‑10 / § 88.36.110). § 88.36.110

Risks & Ambiguities

Issue	Why it matters	What to verify
Exact per‑use rates in Table 3‑7 are not fully reproduced here	You cannot finalize parking counts without the full Table 3‑7 entries.	Obtain Table 3‑7 from the Development Code or planning staff and cite the exact line item for your use. § 88.36.050
TOD Specific Plan overrides	Projects in the TOD may use Specific Plan standards instead of Chapter 88.36 counts.	Confirm whether the project is inside the TOD Specific Plan and which parking table applies. § 88.36.050.B
Off‑site parking covenant details	The code requires a covenant/easement but precise form/term conditions are case‑by‑case	Confirm city attorney requirements and the 300 ft maximum measurement point. § 88.36.120
District frontage exceptions (corridor vs. industrial)	Article 2 district rules can restrict visible/frontage parking even when you meet counts.	Check the applicable district chapter (e.g., 88.24.x for corridors, 88.22.x for neighborhoods) for placement rules. § 88.36.090.A
Accessible parking details	Azusa defers to Title 24 / ADA; local stall counts are not specified beyond deferral.	Use Title 24 for stall size and count; confirm stall count inclusion with plan reviewer. § 88.36.060

Plain‑English summary

If you build or change a use in Azusa you must provide off‑street parking and loading that meet the city’s count tables and Chapter 88.36 design rules; where to place that parking (rear, side, wrapped by buildings) is dictated by the district/corridor rules in Article 2 and any applicable overlay/TOD plan — talk to planning staff early to confirm which table and placement rules apply. § 88.36.020, § 88.36.090

Source References

Azusa Development Code — Chapter 88.36 (Parking and Loading), including § 88.36.010, § 88.36.020, § 88.36.030, § 88.36.050, § 88.36.060, § 88.36.070, § 88.36.080, § 88.36.090, § 88.36.100, § 88.36.110, § 88.36.120. See the Development Code extract for these sections. § 88.36.020, § 88.36.050, § 88.36.090, § 88.36.070, § 88.36.110
District / corridor chapters and overlays referenced in Article 2 (e.g., corridor tables and the Downtown North II—Target overlay) for parking placement and special standards — see the district tables and DNT overlay language. § 88.24.010, § 88.27.60
Landscaping and parking area landscape requirements: Chapter 88.34 (references to landscape requirements for parking). § 88.34.050
Development Code excerpts and tables referenced in the analysis above (Table 3‑7 and Table 3‑10 [loading]). § 88.36.050, § 88.36.110

Sources

Retrieved passages

Azusa Zoning Code (Article 2) High relevance
Azusa Zoning Code (Title 23) High relevance
Azusa Zoning Code (section shall) High relevance
Azusa Zoning Code (Article 2.) High relevance
Azusa Zoning Code (Section 88.36.090.I) Medium relevance
Azusa Zoning Code (Section 88.36.050) Medium relevance
Azusa Zoning Code (§ 1B) Medium relevance
Azusa Zoning Code (Section 88.34.050.D) Medium relevance

Cited sections

Official Azusa code library

Frequently asked questions

What parking counts apply to a new retail store in Azusa?

Azusa requires you to use the off‑street parking schedule (Table 3‑7) in Chapter 88.36 to compute required spaces; fractional spaces are rounded up and downtown/TOD projects may follow a different table in the Specific Plan. § 88.36.050

Where can parking be placed on a commercial lot in the CAZ corridor?

Placement is governed by the CAZ corridor (Article 2) building placement/frontage rules and Chapter 88.36 design rules; many corridor standards expect parking to be to the rear or side and active uses on the street. Confirm the CAZ frontage requirements in § 88.24.010 and parking placement rules in § 88.36.090.A. § 88.36.090.A, § 88.24.010

Do multi‑family projects need bicycle parking in Azusa?

Yes — multi‑family projects must provide bicycle parking: at least one bicycle space per 20 motor vehicle spaces up to 100 (minimum two spaces), with specific device, size and clearance requirements. § 88.36.070

Can I put required parking on a different site?

Yes — the code allows designated off‑site parking up to 300 feet away if a recordable covenant or easement acceptable to the city attorney is recorded; a copy must be on file before a certificate of occupancy is issued. § 88.36.120

How are accessible (disabled) parking stalls handled?

Accessible parking must comply with the California Building Standards Code / Title 24 and federal accessibility guidelines; those stalls count toward the Chapter 88.36 totals. § 88.36.060

Are there parking reductions or shared parking options?

Yes — the review authority may allow shared on‑site parking reductions, variances, senior housing reductions, and mixed‑use/TOD reductions where justified; shared arrangements normally require recorded covenants. § 88.36.080

What are the loading requirements for a new warehouse or large retail store?

Nonresidential buildings must provide loading spaces per the loading schedule (Table 3‑10) and loading areas must be located away from required setbacks, screened and sited to avoid facing public streets. § 88.36.110

Does Azusa specify stall dimensions and surfacing?

Yes — standard stall dimensions used in development standards include 9 ft x 18 ft stalls (the code references standard stall size and structured parking design), surfacing must be durable/all‑weather (2" asphaltic concrete or City‑approved alternative), and striping/curbing/landscape rules apply. § 88.36.080, § 88.36.090.I

If my project is in the TOD Specific Plan, which parking rules do I use?

If the project is located within the TOD Specific Plan, the Specific Plan parking requirements apply (see the Specific Plan) rather than the regular Table 3‑7; verify with planning staff and the Specific Plan. § 88.36.050.B

Are tandem parking stalls allowed for residential projects?

Tandem parking is allowed but limited: for multi‑family projects a maximum percentage may be authorized (check the applicable subsection in the code and minor use permit rules); for single‑family some tandem parking is allowed subject to limits. Verify the exact allowable percentage and permit route with the review authority. § 88.36.080.E (tandem rules)

Ask about any Azusa property

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

Start Free Trial