Rural Vacant LandZoning Library
Zoning Library › Colorado › Loveland, CO

Loveland, CO zoning: where a drive-thru restaurant is allowed

Larimer County · 108 districts on file · last read 2026-11-17 · data.json

Is a drive-thru allowed in Loveland, CO?

A drive-thru restaurant is allowed by right (no conditional use permit, special exception or rezoning) in these zoning districts: B, E, MAC.

It needs a conditional or special use approval in: I.

It is not allowed in 9 districts: DR, DT, ER, PP, R1, R1e, R2, R3, R3e.

95 districts are not confirmed yet.

Drive-thru rules in plain words

The use table has no separate drive-through row; fast-food restaurants are a limited (administrative, with standards) use in B, MAC and E. In I they are allowed only on arterial/collector streets or sites already developed with a restaurant, otherwise by conditional use. Drive-in and drive-through facilities are not allowed in DT; residential, PP and DR do not allow them.

Code facts

Jurisdiction
City of Loveland Unified Development Code
Zoning code
Title 18, Unified Development Code (UDC)
Code last amended
Approved by City Council December 2018; effective January 1, 2019 (no later amendment date found)
Restaurant parking
Restaurant parking is the greatest of several ratios, including one space per three seats or one per 200 sf, plus a five-space minimum (Section 18.05.03.03.C, per Zoneomics excerpt).
Drive-thru stacking
Section 18.05.02.04 (per a Zoneomics excerpt of Chapter 18.05) requires stacking spaces for drive-through service; restaurants need five and coffee shops need eight.
Official code
lovgov.org
Official zoning map
mapserv.cityofloveland.org
Planning office
Current Planning Division, Development Center, City of Loveland 970-962-2523 lovgov.org

District standards

DistrictNameRestaurantGas stationCar washSection
BDeveloping BusinessBy rightNot confirmedNot confirmed18.02.03.04; 18.02.04.05(P) source
DRDeveloping ResourceNot allowedNot confirmedNot confirmed18.02.03.04; 18.02.04.05(P) source
DTDowntown (sit-down restaurant permitted; drive-through not allowed)Not allowedNot confirmedNot confirmed18.02.03.04; 18.02.04.05(P) source
EEmployment CenterBy rightNot confirmedNot confirmed18.02.03.04; 18.02.04.05(P) source
EREstate ResidentialNot allowedNot confirmedNot confirmed18.02.03.04; 18.02.04.05(P) source
IDeveloping IndustrialConditionalNot confirmedNot confirmed18.02.03.04; 18.02.04.05(P) source
MACMixed-Use Activity CenterBy rightNot confirmedNot confirmed18.02.03.04; 18.02.04.05(P) source
PPPublic ParkNot allowedNot confirmedNot confirmed18.02.03.04; 18.02.04.05(P) source
R1Developing Low-Density ResidentialNot allowedNot confirmedNot confirmed18.02.03.04; 18.02.04.05(P) source
R1eEstablished Low-Density ResidentialNot allowedNot confirmedNot confirmed18.02.03.04; 18.02.04.05(P) source
R2Developing Medium-Density ResidentialNot allowedNot confirmedNot confirmed18.02.03.04; 18.02.04.05(P) source
R3Developing High-Density ResidentialNot allowedNot confirmedNot confirmed18.02.03.04; 18.02.04.05(P) source
R3eEstablished High-Density ResidentialNot allowedNot confirmedNot confirmed18.02.03.04; 18.02.04.05(P) source

Overlays to watch

Second check against the source text: 2026-11-17 (Re-read Table 18.02.03.04 (column order ER, R1/R1e, R2, R3e, R3, DT, B, MAC, E, I, PP, DR), the L/R legend in 18.02.03.01(B) and 18.02.04.05(P)(1)-(3) on the Zoneomics copy; official enCodePlus was blocked by robots. B, MAC, E, I, DT, ER and PP/DR confirmed; quotes tightened, I status kept conditional because it is site dependent, profile gas/car wash columns set to unclear (not read), P-, -UD, -FF, -FW, FZO left unclear.).

Drive-thru restaurant rule by zoning district

DistrictDrive-thru restaurantWhat the code saysSectionSourceRead on
B
Developing Business
By rightRestaurant, Fast Food: DT L4, B L, MAC L, E L, I L
Confirmed: 'L' = limited use, administrative review against use-specific standards (18.02.03.01(B)), so no conditional use permit. Standards in 18.02.04.05(P)(1): where adjoining residential lots, the order station is turned off at 10 PM, or 50 ft away and oriented away, or buffered with a Type C bufferyard with noise barrier. No separate drive-through row exists; the fast-food row is the one covering drive-through restaurants. Read on the Zoneomics copy, not the official copy.
18.02.03.04; 18.02.04.05(P)zoneomics.com2026-11-17
B-UD
Developing Business, UD suffix (undefined in code read)
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
DR
Developing Resource
Not allowedRestaurant, Fast Food row, Table 18.02.03.04: '-' (not allowed) in ER, R1/R1e, R2, R3e, R3, PP, DR
Both the Restaurant and Restaurant, Fast Food rows show '-' (not allowed) in this district. Column order confirmed: ER | R1/R1e | R2 | R3e | R3 | DT | B | MAC | E | I | PP | DR.
18.02.03.04zoneomics.com2026-11-17
DR-FF
Developing Resource, Flood Fringe sub-zone
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
DR-FW
Developing Resource, Floodway sub-zone
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
DT
Downtown
Not allowedDrive-in and drive-through facilities are not allowed.
Table 18.02.03.04 DT column: Restaurant R4 (permitted, review type varies with scale; applies to the neighborhood activity center of a complete neighborhood), Restaurant, Fast Food L4. But 18.02.04.05(P)(3) says drive-in and drive-through facilities are not allowed in DT, so a drive-through restaurant is prohibited.
18.02.04.05(P)(3)zoneomics.com2026-11-17
E
Employment Center
By rightRestaurant, Fast Food: DT L4, B L, MAC L, E L, I L
Confirmed: 'L' = limited use, administrative review against use-specific standards (18.02.03.01(B)), so no conditional use permit. Standards in 18.02.04.05(P)(1): where adjoining residential lots, the order station is turned off at 10 PM, or 50 ft away and oriented away, or buffered with a Type C bufferyard with noise barrier. No separate drive-through row exists; the fast-food row is the one covering drive-through restaurants. Read on the Zoneomics copy, not the official copy.
18.02.03.04; 18.02.04.05(P)zoneomics.com2026-11-17
ER
Estate Residential
Not allowedRestaurant, Fast Food row, Table 18.02.03.04: '-' (not allowed) in ER, R1/R1e, R2, R3e, R3, PP, DR
Both the Restaurant and Restaurant, Fast Food rows show '-' (not allowed) in this district. Column order confirmed: ER | R1/R1e | R2 | R3e | R3 | DT | B | MAC | E | I | PP | DR.
18.02.03.04zoneomics.com2026-11-17
FZO
Not defined in code text read
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
I
Developing Industrial
Conditionalalready developed with a restaurant use; or along an arterial or collector street, unless approved as a conditional use
Table cell for I is L (limited use). 18.02.04.05(P)(2) adds that fast food in I is allowed only on a property already developed with a restaurant, or along an arterial or collector street; otherwise it needs conditional use approval (18.14.03.01(B)(4)). So by-right on qualifying sites, conditional elsewhere; rated conditional as the conservative answer. (P)(1) order-station standards also apply.
18.02.04.05(P)(2)zoneomics.com2026-11-17
I-FF
Developing Industrial, Flood Fringe sub-zone
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
I-FW
Developing Industrial, Floodway sub-zone
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
MAC
Mixed-Use Activity Center
By rightRestaurant, Fast Food: DT L4, B L, MAC L, E L, I L
Confirmed: 'L' = limited use, administrative review against use-specific standards (18.02.03.01(B)), so no conditional use permit. Standards in 18.02.04.05(P)(1): where adjoining residential lots, the order station is turned off at 10 PM, or 50 ft away and oriented away, or buffered with a Type C bufferyard with noise barrier. No separate drive-through row exists; the fast-food row is the one covering drive-through restaurants. Read on the Zoneomics copy, not the official copy.
18.02.03.04; 18.02.04.05(P)zoneomics.com2026-11-17
P-2
Planned district sub-code P-2
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-3
Planned district sub-code P-3
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-4
Planned district sub-code P-4
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-6
Planned district sub-code P-6
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-7
Planned district sub-code P-7
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-8
Planned district sub-code P-8
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-9
Planned district sub-code P-9
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-10
Planned district sub-code P-10
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-11
Planned district sub-code P-11
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-12
Planned district sub-code P-12
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-13
Planned district sub-code P-13
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-14
Planned district sub-code P-14
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-15
Planned district sub-code P-15
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-16
Planned district sub-code P-16
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-18
Planned district sub-code P-18
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-20
Planned district sub-code P-20
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-22
Planned district sub-code P-22
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-25
Planned district sub-code P-25
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-26
Planned district sub-code P-26
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-27
Planned district sub-code P-27
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-30
Planned district sub-code P-30
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-33
Planned district sub-code P-33
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-34
Planned district sub-code P-34
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-35
Planned district sub-code P-35
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-36
Planned district sub-code P-36
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-37
Planned district sub-code P-37
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-38
Planned district sub-code P-38
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-40
Planned district sub-code P-40
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-42
Planned district sub-code P-42
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-43
Planned district sub-code P-43
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-44
Planned district sub-code P-44
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-45
Planned district sub-code P-45
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-49
Planned district sub-code P-49
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-50
Planned district sub-code P-50
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-51
Planned district sub-code P-51
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-54
Planned district sub-code P-54
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-55
Planned district sub-code P-55
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-56
Planned district sub-code P-56
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-57
Planned district sub-code P-57
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-58
Planned district sub-code P-58
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-59
Planned district sub-code P-59
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-60
Planned district sub-code P-60
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-61
Planned district sub-code P-61
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-62
Planned district sub-code P-62
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-64
Planned district sub-code P-64
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-65
Planned district sub-code P-65
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-66
Planned district sub-code P-66
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-67
Planned district sub-code P-67
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-68
Planned district sub-code P-68
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-69
Planned district sub-code P-69
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-70
Planned district sub-code P-70
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-72
Planned district sub-code P-72
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-73
Planned district sub-code P-73
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-74
Planned district sub-code P-74
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-75
Planned district sub-code P-75
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-78
Planned district sub-code P-78
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-80
Planned district sub-code P-80
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-81
Planned district sub-code P-81
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-85
Planned district sub-code P-85
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-86
Planned district sub-code P-86
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-87
Planned district sub-code P-87
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-89
Planned district sub-code P-89
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-90
Planned district sub-code P-90
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-91
Planned district sub-code P-91
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-92
Planned district sub-code P-92
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-93
Planned district sub-code P-93
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-95
Planned district sub-code P-95
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-96
Planned district sub-code P-96
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-97
Planned district sub-code P-97
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-98
Planned district sub-code P-98
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-99
Planned district sub-code P-99
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-100
Planned district sub-code P-100
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-101
Planned district sub-code P-101
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-102
Planned district sub-code P-102
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-103
Planned district sub-code P-103
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-104
Planned district sub-code P-104
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-105
Planned district sub-code P-105
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-106
Planned district sub-code P-106
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-107
Planned district sub-code P-107
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-108
Planned district sub-code P-108
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-109
Planned district sub-code P-109
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-110
Planned district sub-code P-110
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-111
Planned district sub-code P-111
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
P-112
Planned district sub-code P-112
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
PP
Public Park
Not allowedRestaurant, Fast Food row, Table 18.02.03.04: '-' (not allowed) in ER, R1/R1e, R2, R3e, R3, PP, DR
Both the Restaurant and Restaurant, Fast Food rows show '-' (not allowed) in this district. Column order confirmed: ER | R1/R1e | R2 | R3e | R3 | DT | B | MAC | E | I | PP | DR.
18.02.03.04zoneomics.com2026-11-17
R1
Developing Low-Density Residential
Not allowedRestaurant, Fast Food row, Table 18.02.03.04: '-' (not allowed) in ER, R1/R1e, R2, R3e, R3, PP, DR
Both the Restaurant and Restaurant, Fast Food rows show '-' (not allowed) in this district. Column order confirmed: ER | R1/R1e | R2 | R3e | R3 | DT | B | MAC | E | I | PP | DR.
18.02.03.04zoneomics.com2026-11-17
R1-FF
Developing Low-Density Residential, Flood Fringe sub-zone
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
R1-FW
Developing Low-Density Residential, Floodway sub-zone
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
R1-UD
Developing Low-Density Residential, UD suffix (undefined in code read)
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
R1e
Established Low-Density Residential
Not allowedRestaurant, Fast Food row, Table 18.02.03.04: '-' (not allowed) in ER, R1/R1e, R2, R3e, R3, PP, DR
Both the Restaurant and Restaurant, Fast Food rows show '-' (not allowed) in this district. Column order confirmed: ER | R1/R1e | R2 | R3e | R3 | DT | B | MAC | E | I | PP | DR.
18.02.03.04zoneomics.com2026-11-17
R2
Developing Medium-Density Residential
Not allowedRestaurant, Fast Food row, Table 18.02.03.04: '-' (not allowed) in ER, R1/R1e, R2, R3e, R3, PP, DR
Both the Restaurant and Restaurant, Fast Food rows show '-' (not allowed) in this district. Column order confirmed: ER | R1/R1e | R2 | R3e | R3 | DT | B | MAC | E | I | PP | DR.
18.02.03.04zoneomics.com2026-11-17
R2-UD
Developing Medium-Density Residential, UD suffix (undefined in code read)
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
R3
Developing High-Density Residential
Not allowedRestaurant, Fast Food row, Table 18.02.03.04: '-' (not allowed) in ER, R1/R1e, R2, R3e, R3, PP, DR
Both the Restaurant and Restaurant, Fast Food rows show '-' (not allowed) in this district. Column order confirmed: ER | R1/R1e | R2 | R3e | R3 | DT | B | MAC | E | I | PP | DR.
18.02.03.04zoneomics.com2026-11-17
R3-UD
Developing High-Density Residential, UD suffix (undefined in code read)
Not confirmedNot read closely enough to state a rule.zoneomics.com2026-11-17
R3e
Established High-Density Residential
Not allowedRestaurant, Fast Food row, Table 18.02.03.04: '-' (not allowed) in ER, R1/R1e, R2, R3e, R3, PP, DR
Both the Restaurant and Restaurant, Fast Food rows show '-' (not allowed) in this district. Column order confirmed: ER | R1/R1e | R2 | R3e | R3 | DT | B | MAC | E | I | PP | DR.
18.02.03.04zoneomics.com2026-11-17

"By right" means permitted with site plan and building permit review only. Overlay districts, planned developments (PD/PUD) and conditions attached to a past rezoning can change the answer for a single parcel.

Official zoning map layer

To find the district for a parcel, query the jurisdiction's own GIS zoning layer: https://mapserv.cityofloveland.org/arcgis/rest/services/layers/Zoning/MapServer/0 (district field: TYPE)

City of Loveland public ArcGIS MapServer, layer 0 'Zoning' (polygon). Zone code field is TYPE. A returnDistinctValues query returned 108 distinct values, all listed in districts[]. The 84 P-prefixed codes are planned (PUD-style) codes and are unclear. Suffixes -FF and -FW match the floodplain sub-zones FP-FF and FP-FW in Section 18.02.02.02. The -UD suffix and the FZO value are not defined in the code text read.

Sources

How to confirm before you buy

  1. Look up the parcel on the official zoning map to get its district and any overlay.
  2. Open the code section linked in the table and read the use table and the drive-thru standards.
  3. Call the planning office and ask whether a drive-thru restaurant needs anything beyond site plan review at that address.

Why this library exists

I'm Luke Smith. I find land for drive-thru brands like 7 Brew, Ellianos Coffee and Starbucks, sign the tenant, build the shop and sell it as a net lease property. Every deal starts with the same question: is the use allowed here without a rezoning? Getting that answer takes too long, so we read the codes (with AI research help), and I publish what we find with a link back to every source so you can check it yourself.

If you have a site that fits a drive-thru, or you want to learn how these deals are put together, join the free Reverse Deal Finder community on Skool, see cap rates and land prices by brand, or call 1-760-392-1525. Brokers welcome: I pay commissions.