Analysis

We read all fifty-eight county codes in search of Zone 0. Here is what California's local wildfire law actually says.

Fact-checked August 23, 2026·Sources at the end of this article

Why we did this

Every week someone is told that "the county" already requires a noncombustible fence, or that Zone 0 is "already the law" where they live. There is no state list of local ember-resistant-zone rules, so the only way to answer those claims is to read each jurisdiction's adopted text. We had been doing that county by county for the places we cover in depth. On August 23, 2026 we finished the job at county level: every California county whose code could be reached by any tool we have, read from the codified text its own publisher serves, with the ordinance numbers and adoption dates recorded.

The result is a negative in shape but not in value. Knowing that a county's law says nothing about the first five feet is exactly what a homeowner being quoted for a "required" fence replacement needs, and it is what nobody else publishes, because "we checked and there is nothing" earns no headlines. The full jurisdiction-level detail lives on the register, in its "checked, and there is nothing to report" section. This page is the pattern.

Finding one: county wildfire law was written in the thirty-and-one-hundred-foot era

The dominant shape, across dozens of counties, is a defensible space or fire-safe ordinance built on Public Resources Code section 4291 and the state's fire safe regulations: clear flammable vegetation within thirty feet of a structure, reduce fuel out to one hundred feet, keep roads wide and hydrants marked. The adoption dates tell the story. Sierra County's ban on smoking in flammable vegetation began as Ordinance 124 in 1928 and is still on the books. Humboldt's fire prevention chapter is Ordinance 231 of 1946, written about burn permits and waste fires. Siskiyou's fire hazard regulations date to 1968. Calaveras's hazardous fire area chapter is from 1977. Trinity and Tehama adopted the same fire-safe model in 1991. Mono and Modoc adopted theirs in 2008. Shasta rewrote its chapter in 2019 and amended it in 2025, and it is still a thirty-and-one-hundred-foot regime.

There is a reason those codes read alike, and we found it in the state's own paperwork. The Board of Forestry's General Guidelines for Creating Defensible Space, adopted February 8, 2006 and still the guidance document posted on its website, defines "Fuel" and then says that "for the purposes of these guidelines, it does not include fences, decks, woodpiles, trash, etc." County after county copied that formula: Fresno's ordinance says fuel "does not include fences, decks, woodpiles, or trash," Alpine's chapter excludes the same four things, and Monterey's code excludes fences from its fire requirements outright. The idea that a fence is not fuel was not a local eccentricity. It was the state's own guidance, and local drafters followed it.

Nothing in that framework regulates what the first five feet is made of. When the statewide Zone 0 regulation takes effect, it will not be tightening county rules. It will be introducing a concept most county codes have never contained, into communities whose local law has told them for thirty-five years that compliance means cutting grass, not choosing materials.

Finding two: eight codes may change meaning on effective day, silently

Three jurisdictions incorporated the state's defensible space regulation, Title 14 Section 1299.03 and its neighbors, into their own codes by reference:

• Calaveras County, by a February 2017 ordinance, adopted Public Resources Code sections 4291 through 4299 and Title 14 sections 1299.01 through 1299.05 wholesale into its municipal code, county-wide.
• Contra Costa County and two of its fire districts (Contra Costa County Fire and Crockett-Carquinez Fire), by a 2023 ordinance, require defensible space "in accordance with" section 1299.03, with a documentation requirement at close of escrow attached.
• Morro Bay, by an ordinance adopted September 23, 2025, made section 1299.03 and the Board of Forestry's guidelines "the controlling standards" for its weed abatement chapter, citywide, across every hazard designation.

Four more counties point at the statutes instead of the regulation. Mono County wrote the model sentence in 2008, and its code stands current through a 2025 ordinance: property "shall be maintained in accordance with the defensible space requirements contained in Government Code Section 51182... and Public Resources Code Section 4291, as applicable." Inyo County copied it in 2020, in the same ordinance that designates every unincorporated acre of the county a Wildland-Urban Interface Fire Area and makes violations a public nuisance per se. Tehama County's fire hazard abatement chapter directs that firebreaks on rural and agricultural lands "shall be created and maintained in accordance [with] the Public Resources Code 4291 and Government Code 51182." The ember-resistant zone was later written into both of those statutes, to activate when the state's regulation takes effect. And Alpine County completes the set: its sentence, first spotted in a 2008 archive and carried on our watch list as a verify-first item, survived the chapter's 2018 rewrite and now reads, verified current through July 2026, that defensible space must be maintained in compliance with Public Resources Code section 4291 “as currently exists and as may be amended in the future,” the only county pointer whose dynamism is drafted rather than left to interpretation.

And an eighth belongs to a fire district that wrote its intent down. Kensington Fire Protection District, in Contra Costa County, adopted Ordinance 2025-01 on July 16, 2025, effective thirty-five days later, and its duty section outdoes every other entry in this list: any person who owns or maintains a building “shall maintain such building or structure in conformance with the vegetation maintenance standards established by the applicable defensible space and home hardening requirements of Public Resources Code Section 4291, Government Code Section 51182, 14 CCR Sections 1299.01-1299.05 and any other state regulations adopted pursuant to” either statute, “as each is amended from time to time.” Statutes, regulation, future amendments and express dynamism, all in one sentence, and the ordinance's own recitals say the district “seeks to align local regulations with state law by adopting defensible space and home hardening measures that include Zone Zero standards.” It attaches a point-of-sale inspection and certificate regime to the duty. For this ordinance, the dynamic-versus-frozen question is about as close to answered as this class of drafting gets, because the drafters answered it. The county page has the details.

Today none of these eight codes requires an ember-resistant zone, because the sections and statutes they point at do not require one yet. But the state's Zone 0 package will write its requirements into exactly the places these codes point. On the day the state text takes effect, the local law of all eight may begin requiring Zone 0 through their own municipal codes, in Morro Bay's case reaching parcels the state rule's own Local Responsibility Area trigger would never touch, and in the statute-pointing counties mirroring the state duty with county enforcement behind it. Whether each incorporation is dynamic or frozen at the text as it stood is a legal question the ordinances do not answer, and we do not answer it either. We track all eight on our effective-date checklist, and we may be the only ones tracking them at all. We are, however, no longer alone in reading the question this way: when the city of San Luis Obispo adopted the 2025 Wildland-Urban Interface Code, its staff report, prepared by a deputy city attorney, reasoned that because the WUI code "references and requires compliance with Section 1299.03," adopting it means the city "will also adopt, by reference, the Zone 0 requirements as issued by the state (including any future amendments)." That is one city's lawyer, not a court, and it concerns the model code's own machinery rather than these eight hand-written pointers, which is exactly the class our membership test excludes because the question is unsettled. But it is the first official analysis we have seen answer it, and it answers yes. The county page quotes it.

The pointer is pre-printed in the state's model code, at section 604.3

A staff report is a description of a document, so we went and read the document. The sentence that deputy city attorney is describing is section 604.3 of the 2025 California Wildland-Urban Interface Code, which the 2025 cycle published as a standalone code at Part 7 of Title 24. The section is titled "Requirements," and it is three lines long. Hazardous vegetation and fuels around all buildings and structures, it says, "shall be maintained in accordance with the following laws and regulations," and then it lists four: Public Resources Code section 4291; California Government Code section 51182; Title 19 section 3.07; and "California Code of Regulations, Title 14, Division 1.5, Chapter 7, Subchapter 3, Article 3, Section 1299.03."

That last one is the section the Board of Forestry's Zone 0 package is being written into. Which means the thing we spent this survey hunting for, one jurisdiction at a time, in ordinances drafted by local attorneys, is also sitting pre-printed in the model code that California cities adopt by the dozen every code cycle. The eight codes in Finding Two are the ones whose own drafters wrote the pointer by hand. Section 604.3 hands the same pointer to everyone who adopts the state model, without anyone at the local level having to intend it.

The section just above it decides who owes the duty, and it is worth reading too, because its reach is not what people assume. Section 604.2 applies the fuel-management requirement to buildings and structures on three kinds of land: all unincorporated land in a State Responsibility Area; land a city or local agency has designated Very High; and, third, "land designated in a city or local agency ordinance as a wildland-urban interface (WUI) area." That third trigger is not a state hazard map at all. It is whatever the city itself drew.

One qualification, and this one is ours rather than the deputy city attorney's. Section 604.3's duty runs on "hazardous vegetation and fuels." The Board of Forestry's own guidance document, the one the statute requires it to update before Zone 0 can reach new construction, defines fuel in terms that exclude fences. So even on the reading that 604.3 carries Zone 0 into local law automatically, the two halves of Zone 0 do not travel equally well through it: the mulch, litter and dead-plant half is squarely vegetation and fuel, and the fence half is the part the state's own definitions have never comfortably held. That is the same seam that runs through the state's model inspection guide, where fuel removal is what an inspector checks and fences sit under "Suggestions and Education."

We are not adding these adoptions to the register, and 604.3 is the clearest statement of why. The register lists rules in force. A pointer at a section that does not yet require an ember-resistant zone is not a rule in force, and if we counted pointers we would be publishing a list of nearly every city in California that has run a code cycle, which would tell a homeowner nothing about their own address. What 604.3 does change is the size of the question. Finding Two says eight codes may change meaning silently. On the deputy city attorney's logic, the real number is eight plus every 2025 Wildland-Urban Interface Code adopter in the state, and nobody, including us, has counted those.

We also applied the same test to every other surveyed county and excluded five near-misses by name on the register: a restatement, an applicability declaration, or a reference that describes a statute rather than deferring to it does not flip, and we would rather under-count than pad the list.

Finding three: cities are widening where fuel rules reach, not what they require

In the 2025 code-adoption cycle, three cities amended the same section of the California Wildland-Urban Interface Code, section 604.2, which says where hazardous vegetation and fuel management applies. Santa Monica did it in October 2025. Monte Sereno and San Jose did it in November 2025, extending the duty to Moderate hazard zones and city-designated interface areas, well past the state rule's own coverage. None of the three added anything about the first five feet or fence materials.

The consequence arrives later. The statewide Zone 0 text, once effective, will apply on top of local designations that these cities have quietly broadened. A San Jose or Monte Sereno homeowner in a Moderate zone, reading only the state regulation, would conclude the rule does not reach them. Their own city code may say otherwise. This is the kind of interaction nobody's coverage explains, which is why we track it.

Finding four: outside the register, the five-foot idea appears three times, in three different legal modes

Lassen County's fire hazards chapter, built on the modern fire-safe model, allows a new structure that cannot meet the required thirty-foot setback to substitute alternatives providing the same practical effect, including "noncombustible block walls or fences" and "five feet of noncombustible material horizontally around the structure." That is the ember-resistant zone concept, present in a county code as an optional trade for a setback nobody could meet, years before the state made any of it mandatory. The only other place the five feet appears outside the register is San Bernardino County's development code: section 82.13.050(j) of its Fire Safety Overlay chapter has required a five-foot noncombustible separation where wood or vinyl fencing meets a structure since 2007, binding at plan check for new construction in the overlay, and Yucca Valley copied it. Lassen remains the only place the idea appears as a bargaining chip rather than a requirement. And Amador County, alone among the fifty-eight county codes, wrote the words “Zone 0” into an ordinance: its 2022 defensible-space chapter draws the zone at five feet around every structure, attached decks included, and makes it the chapter's only recommendation while the thirty-foot and hundred-foot zones are enforceable duties, a choice the county re-adopted verbatim in March 2026, five months before the state made the same five feet mandatory. A plan-check mandate in San Bernardino, a bargaining chip in Lassen, a named recommendation in Amador: three modes of the same five feet, and none of them reaches an existing home the way the state's rule will. In fifty-eight county codes, those three are the closest thing to Zone 0 we found outside the thirty-five jurisdictions that actually adopted one.

All fifty-eight counties, in one table

This is the survey's result, county by county. The middle column answers only one question, whether some jurisdiction in that county has an ember-resistant-zone rule in force today, and every “yes” traces to a row on the register, read from its own adopted text. The right column is what the county's local law actually is, which for forty-six counties is the more useful answer, because it tells you what a fire official there can require of you now. Counties whose codes point at the state's defensible space law are flagged in place: those are the ones whose meaning may change on filing day.

Thirteen counties contain at least one jurisdiction with a rule in force; forty-five contain none. That is a fact about California as of August 23, 2026, not about how hard we looked: every county's operative text has now been read, and each county page carries its own dates, citations and the gaps we could not close.

What we could not read, and how it finally got read

The survey's last five counties, Alpine, Amador, Glenn, Sacramento and Solano, sat for weeks behind publishers whose bot-detection refused every fetch we knew, and no archive held their current text. On August 23, 2026 all five were read from current sources, and the manner of it is worth a paragraph because it says something about how public these public laws are. Alpine and Solano were read from their publisher's live pages once we could render them, banners current to July and April 2026. Amador turned out to have moved publishers entirely, and its current code, dated April 2026, held a defensible-space chapter no archive had ever captured, the one with Zone 0 in it. Glenn's supposedly current publisher hosts nothing at all; the county publishes its own code as PDFs on its own website, and we read those. Sacramento's code, dated May 2026, sits with a publisher its own county counsel page points to, while the address most code tools try for it hosts nothing and the most common search result is the city's code wearing the county's name. Every verdict above now rests on current text. What remains unread is the layer below the counties: city codes, fire district ordinances, and Glenn's development code beyond its adoption ordinance, and each county page names its own gaps plainly.

Two counties came off this list at the last minute, and the way is worth recording. Mariposa's and Del Norte's publisher gates its section text behind a login, but leaves its print endpoint open, so we read both counties' operative fire chapters from the publisher's own live pages: Del Norte's 1991 fire-safe model, re-enacted in 2016, with section names identical to neighboring Humboldt's; and Mariposa's 1980 mandatory brush-clearing ordinance, an ongoing countywide duty of the thirty-and-one-hundred-foot shape, alongside a September 2025 adoption of the state's wildland-urban interface code, unamended. Nothing in either county touches the first five feet or fence materials, and both are surveyed from current text, not archives.

Three counties came off this list the day we published it. Humboldt's, Sierra's and Colusa's publishers all block direct access, but a public web archive turned out to hold their pages in depth, dated by the publishers' own banners: Humboldt through an October 2025 ordinance, Sierra through a December 2023 one, Colusa's fire chapter as served in March 2024. We read the operative fire chapters from the archived pages, found nothing about the first five feet in any of the three, and found the two oldest fire laws in the survey, from 1946 and 1928, plus Colusa's signature rule: a three-foot firebreak around grain fields, written for rice country. The handful of sections with no archived copy are named on the register rather than guessed at. All three count as surveyed as of their archived codification dates, and their entries say exactly that.

Every surveyed county now has its own page, linked from the homepage's county list, with the finding, the citations, the inspection numbers, and a "claims we could not verify" section naming what we did not read.

The same honesty applies below county level. California has hundreds of cities and fire protection districts with independent ordinance authority, and no survey of counties covers them. Where we read city and district codes, the register's county entries say so, and where we could not, they say that instead.

What this means for you

• If someone says your county already requires a noncombustible fence, ask for the section number. In fifty-eight counties we found no such requirement outside the register's thirty-five jurisdictions. The claim is checkable in minutes, and we have usually already checked it.
• If you live in Calaveras, Contra Costa Fire's territory, Morro Bay, Mono, Inyo or Tehama, your local code is wired to the state's defensible space law. When the state's Zone 0 text takes effect, ask your fire authority how your jurisdiction reads its own incorporation. Our status tracker will flag the day that question becomes live.
• If you live in San Jose, Monte Sereno or Santa Monica, your city has broadened where fuel-management duties apply. The state rule's arrival will mean more there than its own text suggests.
• Everywhere else, the thirty-and-one-hundred-foot duties are the law today. Cut the grass, clear the roof, keep the hundred feet. The five-foot materials rules arrive with the state regulation, on the timeline our timeline page tracks, and nothing about that timeline requires buying anything today.

Method, so you can check us

Every county was read from the codified text served by its own code publisher, through the publisher's public pages or data services, current through the codification date each publisher states. Where a county self-publishes its code as documents, we read the county's posted files. Where an ordinance existed only as an image scan, we read it page by page from the images and say so. Where a publisher blocks direct access but a public web archive holds its pages, we read the archived pages, record the codification date they state, and mark the finding as dated rather than current. Findings are recorded with ordinance numbers and adoption dates in our fact base, and the register's negative entries carry the same citations. If you find a county provision we missed, we publish corrections on the page where the error appeared, dated.