Overview
| res_sf | letter-code with density-intensity suffix (RA = residential agriculture; RS = single-family residential; RD = residential duplex) |
|---|---|
| res_mf | letter-code with Roman-numeral intensity (RM-I < RM-II < RM-III, low to high density) |
| com | letter-code (CR = retail commercial, CG = general commercial, CB = central business, CO = commercial office, etc.) |
| mu | letter-code with Roman-numeral intensity (MU-I/MU-II/MU-III) |
| ind | letter-code (IP = industrial park, IG = general industrial, IC = industrial commercial) |
| spec | letter-code (PE public/educational, PS public service, PA public amusement) |
Salem UDC uses Euclidean zoning with named residential/commercial/industrial/mixed-use families. Numeric suffixes in RM-I/II/III indicate intensity tier, not lot-size or density numerics directly. Use classifications live in Chapter 400; per-zone dimensional standards in Chapters 511–551. Overlay zones (Floodplain, Historic Contribution, West Salem, South Waterfront Mixed-Use, etc.) apply as map-based overlays on top of base zones.
- Municode SPA blocker — primary dimensional standards not retrievable. Salem's authoritative UDC is hosted on library.municode.com, which renders as a JavaScript SPA and returns an empty HTML shell to scripted fetches. Per the one-attempt blocker rule, dimensional standards inside Chapters 511–551 (min lot sf, height, setbacks, FAR, density, parking ratios, lot coverage) could not be verified from primary source during this research run. Chapter roster, chapter titles, and UDC effective date of 2022-12-28 were confirmed via Google search snippets of municode-indexed section headings. This record should be updated via a manual browser-based retrieval pass or by obtaining a PDF copy of each UDC chapter from Salem Planning Division (planning@cityofsalem.net, 503-588-6213).
- UDC uses zone-family letter codes rather than lot-size-encoded. Unlike Portland (lot-size-encoded R5/R7/R10) or typical Texas cities (lot-size numeric suffixes), Salem uses named letter-code families with Roman-numeral intensity tiers for MF and MU zones (RM-I < RM-II < RM-III; MU-I < MU-II < MU-III). RA/RS/RD for residential families, CR/CG/CB for commercial tiers, IP/IG/IC for industrial. This is closer to historical Oregon mid-size-city convention than to the newer lot-size-encoded model. Consequence: district code alone does not convey density or lot size — must reference Chapter 110 zone-family listings or the specific chapter dimensional table.
- Salem CFA compliance embedded in base zones, not separate overlay. Per the Salem CFA Study (oregon.gov/lcd/CL/Documents/SalemCFAStudy.pdf), Salem elected NOT to create a new CFA/Walkable Mixed-Use Area overlay zoning district. Instead Salem is meeting OAR 660-012 CFEC requirements by upgrading existing CB, MU-II, and MU-III zone standards to meet state minimums (15 du/ac, 50 ft min height, no parking minimums) within mapped CFA areas. This means CFEC preemption applies as field-level overrides on MU/CB zones rather than via a distinct overlay code. Developers must check CFA map + base zone, not look for a separate 'CFA' code.
+ 4 more in Quirks & notes
Districts
| Code | Name | Category | Min lot | Height | Coverage | FAR | Du/ac | Parking | Setbacks F/S/R |
|---|---|---|---|---|---|---|---|---|---|
| RA | Residential Agriculture | res_sf | —[1] | — | — | — | — | — | — / — / — |
| RS | Single-Family Residential | res_sf | —[2] | — | — | — | — | — | — / — / — |
| RD | Residential Duplex | res_sf | —[3] | — | — | — | — | — | — / — / — |
| RM-I | Multiple Family Residential — Low Density | res_mf | —[4] | — | — | — | — | — | — / — / — |
| RM-II | Multiple Family Residential — Medium Density | res_mf | —[5] | — | — | — | — | — | — / — / — |
| RM-III | Multiple Family Residential — High Density | res_mf | —[6] | — | — | — | — | — | — / — / — |
| CR | Retail Commercial | com | —[7] | — | — | — | — | — | — / — / — |
| CG | General Commercial | com | —[8] | — | — | — | — | — | — / — / — |
| CB | Central Business (Downtown) | com | —[9] | — | — | — | — | 0 | — / — / — |
| MU-II | Mixed Use — Medium Intensity | mu | —[10] | — | — | — | — | — | — / — / — |
| MU-III | Mixed Use — High Intensity | mu | —[11] | — | — | — | — | — | — / — / — |
| IP | Industrial Park | ind | —[12] | — | — | — | — | — | — / — / — |
| IG | General Industrial | ind | —[13] | — | — | — | — | — | — / — / — |
| IC | Industrial Commercial | ind | —[14] | — | — | — | — | — | — / — / — |
Confidence: confirmed partial under review not found
Overlays
State preemptions
Adopted building codes
2024 codes eff. April 2026
Click a code label to open its state-by-state adoption atlas.
Amendment history
| Date | Kind | Citation |
|---|---|---|
| Council Action Nov 28, 2022 adopting UDC amendment | ||
| UDC amendment effective Dec 28, 2022 | ||
Quirks & notes
- Municode SPA blocker — primary dimensional standards not retrievable. Salem's authoritative UDC is hosted on library.municode.com, which renders as a JavaScript SPA and returns an empty HTML shell to scripted fetches. Per the one-attempt blocker rule, dimensional standards inside Chapters 511–551 (min lot sf, height, setbacks, FAR, density, parking ratios, lot coverage) could not be verified from primary source during this research run. Chapter roster, chapter titles, and UDC effective date of 2022-12-28 were confirmed via Google search snippets of municode-indexed section headings. This record should be updated via a manual browser-based retrieval pass or by obtaining a PDF copy of each UDC chapter from Salem Planning Division (planning@cityofsalem.net, 503-588-6213).
- UDC uses zone-family letter codes rather than lot-size-encoded. Unlike Portland (lot-size-encoded R5/R7/R10) or typical Texas cities (lot-size numeric suffixes), Salem uses named letter-code families with Roman-numeral intensity tiers for MF and MU zones (RM-I < RM-II < RM-III; MU-I < MU-II < MU-III). RA/RS/RD for residential families, CR/CG/CB for commercial tiers, IP/IG/IC for industrial. This is closer to historical Oregon mid-size-city convention than to the newer lot-size-encoded model. Consequence: district code alone does not convey density or lot size — must reference Chapter 110 zone-family listings or the specific chapter dimensional table.
- Salem CFA compliance embedded in base zones, not separate overlay. Per the Salem CFA Study (oregon.gov/lcd/CL/Documents/SalemCFAStudy.pdf), Salem elected NOT to create a new CFA/Walkable Mixed-Use Area overlay zoning district. Instead Salem is meeting OAR 660-012 CFEC requirements by upgrading existing CB, MU-II, and MU-III zone standards to meet state minimums (15 du/ac, 50 ft min height, no parking minimums) within mapped CFA areas. This means CFEC preemption applies as field-level overrides on MU/CB zones rather than via a distinct overlay code. Developers must check CFA map + base zone, not look for a separate 'CFA' code.
- Dual-county jurisdiction — Marion + Polk. Salem sits on the Willamette River boundary between Marion County (east bank, majority of city) and Polk County (West Salem, west bank). UGB is jointly administered. County-population aggregate (Marion 353k + Polk 90k) exceeds 400k but zoning authority is city-level within UGB. West Salem has historically had area-specific plan provisions (see West Salem Neighborhood Plan references).
- McNary Field airport ownership and FAA Part 77 exposure. Salem owns McNary Field (Salem Municipal Airport, SLE). FAA Part 77 imaginary surfaces extend over much of south and southeast Salem. Any structure proposed within Part 77 notice surfaces must file FAA Form 7460-1 regardless of local UDC airport overlay. Salem UDC likely has a local airport overlay chapter but it was not confirmed in this retrieval pass.
- Floodplain ESA-compliance ordinance beyond NFIP baseline. Salem has adopted a Floodplain Mitigation Assessment requirement above the federal NFIP baseline — new development in SFHA must demonstrate no net loss of flood storage, water quality, and riparian vegetation (Endangered Species Act compliance for salmonid habitat). This is more stringent than standard FEMA minimums and can materially affect feasible development footprint in Willamette River floodplain parcels.
- HB 2001 fourplex tier fully adopted via 2022-12-28 UDC amendment. Salem's UDC amendment effective 2022-12-28 (Council Action 2022-11-28) implements HB 2001 fourplex tier — duplex/triplex/fourplex/townhome/cottage cluster allowed by-right in all zones permitting single-family dwellings (RA/RS/RD/RM-I). Salem ~183k population puts it squarely in the fourplex tier. Two-family (duplex) is also explicitly allowed on any lot ≥4,000 sf in RS, RA, RD, and RM-I per Chapter 400 use provisions (confirmed via search snippet).
Formulas
Definitions
- height
- Grade to highest point of structure (per SRC UDC Chapter 110 / Chapter 800 general standards).
- lot_coverage
- Building footprint / lot area.
- far
- Gross floor area / lot area.
- du_ac
- Dwelling units per net acre (Salem standard; confirmation of net vs. gross deferred — SRC §110 definitions not directly captured).
- setback_front
- Front property line to nearest building face.
- setback_side
- Side property line to nearest building face.
- setback_rear
- Rear property line to nearest building face.
- parking
- Spaces per dwelling unit unless noted; waived near frequent transit per state preemption.
Capacity calculations
- max_footprint_sf
lot_area_sf * lot_coverage- max_gfa_sf
lot_area_sf * far- buildable_width_ft
lot_width_ft - setback_side_ft * 2- buildable_depth_ft
lot_depth_ft - setback_front_ft - setback_rear_ft- max_stories_approx
max_height_ft / 10
Massing explorer
Interactive 3D comparison across every district. Drag to orbit, scroll to zoom, use the slider to walk districts, and toggle applicable overlays in the right-side panel.
| District | Category | Height | FAR | Coverage | Setbacks | Parking | Density | Min lot | Overlays |
|---|
Sources & references
library.municode.com hosts the authoritative UDC but returns empty HTML shell to scripted fetches (JS-rendered SPA). Per one-attempt blocker rule, one WebFetch attempt was made and failed as expected. City-hosted landing (cityofsalem.net/government/laws-rules/salem-revised-code) also returned HTTP 403 to scripted fetches. Chapter roster, section labels, and UDC effective date confirmed via Google search snippets of municode-indexed section headings (Chapters 110, 205, 230, 400, 511, 513, 514, 522, 523, 535, 551, 601, 700, 800, 808, 809, 900). Dimensional standards inside each chapter body could not be directly verified; all dimensional fields below carry status=partial with paired what_is_confirmed / what_is_missing.
Retrieval failure: municode_js_spa
- https://www.cityofsalem.net/government/laws-rules/salem-revised-code
- https://www.cityofsalem.net/business/land-use-zoning
- https://www.cityofsalem.net/business/land-use-zoning/find-your-property-zone-map
- https://www.oregon.gov/lcd/CL/Documents/SalemCFAStudy.pdf
- https://www.oregon.gov/lcd/CL/Documents/Salem_report.pdf
- [1] SRC UDC Chapter 110
- [2] SRC UDC Chapter 511 — CH511INFARE
- [3] SRC UDC Chapter 110 residential-zone family
- [4] SRC UDC Chapter 513
- [5] SRC UDC Chapter 514
- [6] SRC UDC Chapter 515
- [7] SRC UDC Chapter 522
- [8] SRC UDC Chapter 523
- [9] SRC UDC CB chapter
- [10] SRC UDC Chapter 534 (inferred by numbering between MU-I at 533 and MU-III at 535)
- [11] SRC UDC Chapter 535 — CH535XEUI
- [12] SRC UDC IP chapter
- [13] SRC UDC IG chapter
- [14] SRC UDC Chapter 551 — CH551NDCO
Research status
Publication gates
| primary url present | passed | source.primary_url = https://library.municode.com/or/salem/codes/code_of_ordinances (authoritative municode index for Salem SRC/UDC Title X — Unified Development Code; not an aggregator). Secondary URLs include cityofsalem.net code landing page and Oregon DLCD Salem CFA/Minor Reports — all HTTPS, all authoritative. |
|---|---|---|
| no aggregator cited | passed | Record scan finds no references to zoneomics, steadily, siteplanguide, siteplancreator, propwire, zonara, or unzoned anywhere in the record body. All citations point to SRC UDC chapter numbers (Chapter 110, 230, 400, 511, 513, 514, 522, 523, 525, 533–535, 551, 601, 808, 809), Oregon DLCD documents (oregon.gov/lcd CFA Study + Salem Minor Report), Census Bureau PEP, FAA Part 77 / 14 CFR Part 77, NFIP federal standard, ORS statute citations (197.290, 197.296, 197.312, 197.524, 197.727, 197.758), OAR 660-012 / 660-046 administrative rules, and the Oregon state preemptions overlay file. Wayback Machine cited only as retrieval mechanism. |
| confidence tags full form | passed | Every confirmed value carries chapter-section citation form (e.g. 'SRC UDC Chapter 601' for floodplain, 'SRC UDC Chapter 230' for historic, 'OAR 660-012-0440' for parking-minimum elimination, 'ORS 197.758' for HB 2001). Confirmed-with-citation slots include: code_dates (Council Action 2022-11-28; effective 2022-12-28), federal_overlay_refs FEMA-SFHA (citation: SRC UDC Chapter 601), Floodplain Mitigation Assessment param (citation: Salem Floodplain Development Permits page + ESA-compliance ordinance), Historic Design Review (citation: SRC UDC Chapter 230), Riparian Buffer Protection (citation: SRC UDC Chapter 808), CFA Parking-Minimums-Waived (citation: OAR 660-012-0440), CFA Mixed-Use Frontage (citation: OAR 660-012-0320), Part 77 Imaginary Surface (citation: 14 CFR Part 77), and all 7 state-preemption entries (each citing ORS section + DLCD overlay file). Partial values carry paired what_is_confirmed/what_is_missing companion structure with retrieval_failure_reason=municode_js_spa — explicit demotion rather than fabrication. |
| overlays have parameters trigger confidence | passed | 10 overlay entries populated. 7 are real overlays (FP, HC, RP, CFA-MU, DT, WS, AP-SLE) each carrying: name, code, type (floodplain / historic / environmental / tod / downtown / corridor / airport), ordinance_ref (SRC UDC chapter or federal Part 77), geographic_trigger (specific Salem geography — Willamette/Pringle/Mill/Claggett/Battle creek corridors for FP/RP; Court-Chemeketa, Gaiety Hill-Bush's Pasture Park, North Downtown, Grant, SCAN historic districts for HC; Downtown core / Lancaster Drive / Mission/Commercial/Portland Rd for CFA-MU; downtown Salem bounded by Mission/Marion/Front/12th for DT; West Salem + South Waterfront Mixed-Use for WS; McNary Field SLE approach surfaces for AP-SLE), non-empty parameters[] (each ≥1 entry, with at least one confirmed parameter per overlay), interaction_with_base prose, confidence (overlay-level status with citation to chapter or §), and citation field. 3 slots are explicit not_found / not_applicable (TOD absorbed into CFA-MU per OR statewide CFEC; Affordable-Housing absorbed into SB 8 / state HB 2001 framework per ORS 197.309 inclusionary preemption; Military N/A — no military airfield in Salem). Each not_found entry carries search_performed prose explaining why no separate overlay exists. All overlays now carry source_jurisdiction='salem-or' to prevent FM-3 cross-contamination. |
| preempt section city specific | passed | state_preemptions_applicable[] contains 7 OR per-law entries, each with city-specific qualifying_condition_checked referencing primary Salem inputs: HB 2001 fourplex tier (Salem pop ~183,000 / 2023 PEP — clears 25,000 fourplex threshold by 7.3×; non-Portland-Metro stand-alone Willamette Valley city; trigger evaluated TRUE; local implementation effective 2022-12-28 via UDC amendment); ADU By-Right ORS 197.312 (Salem inside its UGB; res_sf base zones RS/RA/RD/RM-I match parcel predicate); HB 2003 HPS (Salem pop >> 10,000 HPS threshold; HPS adoption extends 2024–2025 per DLCD Salem Minor Report); SB 1537/CFEC (Salem one of 8 large non-Metro cities ≥25k subject to OAR 660-012-0310 CFA mandate; embedded compliance via existing CB/MU-II/MU-III zones rather than discrete overlay per Salem CFA Study); HB 3414 (Salem pop >> 10,000 ministerial-adjustment threshold); SB 8 (parcel-level trigger — religious/nonprofit-owned land statewide; Salem density-floor = RM-III); Goal 10 + Goal 14 UGB (jointly administered with Marion + Polk counties; always-on trigger). Each entry carries effect prose naming Salem-specific affected districts (RA/RS/RD/RM-I for HB 2001; CB/MU base zones for CFEC; RM-III as SB 8 floor). Not link-stubs — each is city-specific arithmetic + Salem implementation status. |
Data quality
- Dimensional standards (min lot sf, height, setbacks, FAR, density, parking, coverage) for all 15 districts not retrieved from primary source — municode SPA blocker
- Overlay parameter detail (specific freeboard ft, buffer widths, design review thresholds) not retrieved
- Airport overlay UDC chapter number not confirmed
- UDC post-2022 supplement effective date not confirmed
- Full Chapter 400 use tables (permitted vs. conditional uses per zone) not retrieved
Known issues
Other cities in this state
Nearest-alphabetical profiles. Click through to compare zoning patterns side-by-side.