One City's Dark-Sky Ordinance Shouldn't Stop at the City Line

Drive from Palo Alto into Mountain View, or from Menlo Park into East Palo Alto, and nothing about the sky tells you where one city's jurisdiction ends and the next one begins. Light doesn't respect municipal boundaries. A floodlight glaring across a property line in one city washes out the same stretch of sky as a floodlight two blocks away in the next city over — and the birds, insects, and nocturnal animals moving through that sky have no idea they've crossed into a jurisdiction with different rules, or none at all.

That's the quiet problem with how the Bay Area currently handles light pollution: it doesn't. A handful of cities have adopted real standards. Most haven't. The result is a patchwork where the strength of your night sky, and the safety of the wildlife that depends on darkness, is basically a function of which city drew your parcel's boundary line. For a region that treats itself as a single ecological and economic unit in almost every other respect — transit, housing, water, air quality — lighting has been a strange holdout.

Palo Alto just gave the rest of the region a reason to close that gap.

What Palo Alto actually did

In February 2026, Palo Alto's updated outdoor lighting standards (Palo Alto Municipal Code §18.40.250, adopted via Ordinance 5692) took effect, and they're unusually thorough as these things go. Rather than a vague requirement to “minimize glare,” the ordinance sets specific, enforceable numbers:

• Shielding. Outdoor fixtures must be fully shielded — built and aimed so light goes down, not sideways or up — and light trespass onto a neighboring property is capped at 0.1 foot-candle measured at the property line. That's a genuinely low bar for spillover, not a symbolic one.
• Color temperature. All outdoor light sources are capped at 2,700 Kelvin, the warm end of the spectrum. This matters more than it sounds: cooler, bluer light (the kind LEDs default to unless someone specifies otherwise) scatters more in the atmosphere, contributes disproportionately to sky glow, and is more disruptive to nocturnal wildlife and human circadian rhythms than warm light at the same brightness.
• Curfews. Most outdoor lighting has to be off, or motion-sensor-only, by 11 p.m. — or two hours after a business closes, whichever is later. Lights on motion sensors have to extinguish again within five minutes of no activity.
• Lumen caps for residential lighting. In low-density residential districts, fully shielded fixtures are capped at 1,260 lumens each; unshielded fixtures at just 420 lumens. That's a meaningful constraint on the trend toward ever-brighter porch and security lighting.

Just as notably, Palo Alto didn't stop at lighting. The same chapter of its zoning code (§18.40.280) sets bird-friendly glazing standards for new buildings — requirements that glass be patterned, screened, or otherwise treated so birds can perceive it as a solid surface rather than open sky or reflected habitat. The two ordinances sit side by side and reference each other, because they're solving the same problem from two directions: buildings that don't blind wildlife with light, and buildings that don't look like open air to a bird flying past.

Why “canonical” is the right word

None of this is exotic. Dark-sky lighting standards — shielding, color temperature limits, curfews — have existed in model form for years, from the International Dark-Sky Association's model lighting ordinance to various state and county versions. Palo Alto didn't invent this playbook; it adapted an existing one, tuned it to local zoning categories, and got it through council. That's exactly what makes it useful as a template rather than a one-off.

The case for a canonical ordinance — one shared reference standard that Bay Area cities adopt with only minor local tailoring — comes down to three practical problems a city-by-city approach creates:

Compliance friction for anyone who builds across city lines. Developers, electrical contractors, and lighting designers who work in multiple Bay Area cities currently have to track a different (or nonexistent) lighting code for each one. A shared standard doesn't just protect the sky — it lowers the cost of doing the right thing, because “the right thing” becomes the same answer everywhere.

A missing baseline for cities without planning capacity to write their own. Palo Alto has a planning department that can research color-temperature science, draft precise definitions for “fully shielded,” and defend the ordinance through a public process. Smaller cities and towns in the region often don't have that bandwidth, and in practice that means lighting standards just don't get written at all — not because the city disagrees, but because nobody has the hours. A ready-made, already-litigated-and-adopted ordinance removes that barrier almost entirely; a council can adopt language that's already been vetted rather than starting from a blank page.

Enforcement and spillover don't stop at a boundary. Light trespass and sky glow are inherently regional effects. A single city's dark-sky ordinance measurably improves that city's night sky, but the benefit is diluted by every unlit-code neighbor nearby. Real improvement — the kind that actually restores dark sky and reduces bird strikes at a landscape scale — requires enough contiguous jurisdictions adopting comparable standards that the effect compounds instead of leaking out at every border.

What a shared standard would need to get right

A regional model ordinance doesn't mean identical language everywhere — zoning categories, building stock, and existing lighting infrastructure vary city to city, and any city adapting Palo Alto's ordinance will need to map its own district names onto Palo Alto's residential/commercial/mixed-use distinctions. But the core numeric thresholds — the 2,700K color-temperature cap, the fully-shielded requirement, a light-trespass limit in the neighborhood of 0.1 foot-candle, and a defined curfew — are exactly the kind of details that don't need to be reinvented locally. Those are the parts worth standardizing region-wide, with room left for each city to set its own compliance timeline and enforcement mechanism for existing, nonconforming fixtures.

What you can do

If you live in a Bay Area city that hasn't updated its outdoor lighting code, the fastest path isn't waiting for your city's planning department to independently rediscover dark-sky science — it's pointing them to a jurisdiction that already did the work. Palo Alto's ordinance (PAMC §18.40.250) is public, it's already survived a council adoption process, and it's specific enough that a planner could adapt it in an afternoon rather than a year.

That's a reasonable ask to bring to a city council meeting or a planning commission comment period: not “please study light pollution,” but “please adopt language modeled on what Palo Alto just passed.” We've put a full model ordinance together based on Palo Alto's language — you can find it in our Bay Area Model Outdoor Lighting Ordinance project. The night sky over the Bay Area is one contiguous thing. It's time our ordinances started treating it that way.