San Francisco Data Center Moratorium: 45 Days, Extendable to 22 Months

San Francisco has paused new data centers. On Tuesday, October 6, 2026, the Board of Supervisors unanimously approved a 45-day moratorium, according to the San Francisco Standard. The city that houses OpenAI and Anthropic now has a San Francisco data center moratorium on its books, and the pause can grow far longer than 45 days.

Aggregator headlines say the ban can stretch to "2 years". The local reporting says 22 months. That gap is small, but it is the kind of rounding error that spreads fast, so this post sticks to what the Standard and Mission Local actually printed. It also explains what the ordinance does, which sites it touches, and why it matters to people who build with AI. For the broader national picture, see our map of the AI data center backlash.

TL;DR: the San Francisco moratorium in one table

What did the Board of Supervisors actually vote on?

The measure is an urgent ordinance that imposes an interim zoning moratorium. In plain terms, it freezes the city's ability to approve new data centers for a fixed window while the Planning Department studies them. The Standard reports that the freeze would "pause city approvals of the facilities and task the Planning Department with studying their impacts and developing long-term controls."

Supervisor Shamann Walton, who authored it, described the aim this way: "During this period, we are looking at issues including energy, water, air quality, land use, and community impacts, while working toward stronger protections and meaningful community input, as well as a data center definition that is clear to everyone." Walton also told reporters, when he announced the plan, "We need to know what these impacts are. Until we know what that is, it needs to stop," as quoted by Mission Local.

The legislation defines a data center broadly. According to Mission Local, it covers any "facility, or part of a facility, that houses computing infrastructure, including graphics and central processing units, servers, storage devices, networking equipment, and associated power and cooling systems, for the primary purpose of processing, storing, or distributing electronic data." That wording is wide on purpose. It reaches GPU halls, but also small downtown server rooms that operate as colocation space.

Walton says the city's old rules are part of the problem. The data center provisions were written in 2001, long before AI-scale compute. A clear definition is one stated goal of the 45-day study.

Is it 45 days, 22 months or two years?

All three numbers circulate, and they describe different things.

• 45 days is the base term of the moratorium.
• 22 months is the maximum extension that the Standard and Mission Local both report.
• "2 years" is the headline rounding used by aggregators. 22 months is about 1.8 years.

The Mission Local article adds the mechanism. If the Planning Department finds a significant environmental impact, the moratorium can be extended up to 22 months, or the city can adopt permanent controls or restrictions instead. At the end of the 45 days, Planning presents its findings at a hearing. The Standard also says leaders will convene a progress hearing by November.

The Standard says plainly that it is "unclear whether city leaders would entertain" the longer extension. Mission Local reports that sources close to Walton's office hope the moratorium leads to a permanent ban. Those are two different readings of the same unknown, and you should hold both.

When does it take effect?

Here the early reports disagree. Mission Local wrote that the measure "will take effect immediately." The Standard first said the same, then added a correction: the moratorium takes effect in 10 days if Mayor Daniel Lurie does not return it earlier, and he could veto it.

We could not read the Board of Supervisors file itself during this write-up, so we cannot settle the point. The practical advice is simple. If a project depends on San Francisco permits, check the legislative file and the Planning Department directly before you rely on either date.

Which sites does the pause touch?

The city does not have many data centers, and that matters for how to read the story. The Standard cites market intelligence firm Data Center Map to say District 10 holds two of the six data center sites in San Francisco. Mission Local names the specifics:

• NOVVA, 400 Paul Ave. in Bayview. A 7.6-acre data center that was slated to grow from 9 to 36 megawatts by 2028. The moratorium pauses that expansion.
• 1215 Michigan St. in Dogpatch. Permits have been filed for a 160,000 square foot data center. No construction has started. The Standard adds that in August a lobbyist for a private equity firm met two of Mayor Lurie's policy chiefs about permits for a waterfront Dogpatch plot, and the site there is 1.6 acres.

Both are in Walton's district. Bayview-Hunters Point already carries a heavy pollution load from decades of truck traffic and a since-shuttered PG&E power plant, as Mission Local describes it. That history shapes the politics. Community voices at the committee hearing, including the executive director of the Marie Harrison Community Foundation, argued for health outcomes first.

What will Planning study?

The study list reads like the standard checklist of the national backlash: energy, water, air quality, land use and community impacts. These match the arguments in our explainer on the real environmental impact of AI data centers, where the water and power numbers vary a lot by cooling design and region.

Three practical questions will decide whether the study leads to extension or permanent rules.

1. Where does the power come from, and what does a 36-megawatt site do to local load? Cities with their own utility planning care about peak demand.
2. How much water does cooling use? Liquid-cooled designs change the answer, and so does whether the site uses potable or reclaimed water.
3. What counts as a data center? A clear definition decides whether a small colocation room downtown is in scope or a GPU hall is.

None of those has a published answer yet. That is the point of a moratorium: the city buys time to write the rules.

Is this a city of AI companies saying no to AI?

It can look that way, but the reporting does not support the strong version. The Standard notes that a data center in San Francisco is not where frontier labs train models. No lab is reported to be building a hyperscale campus inside the city. The hit is to the small number of local facilities and the proposals in the pipeline.

The framing that does hold up is political. The Standard calls the vote a sign that the data centers powering AI, "and the accompanying public outcry," are something city leaders cannot ignore. All three front-runners to replace Walton, who terms out in January 2027, support a moratorium, according to both outlets. Mission Local lists them as Theo Ellington, J.R. Eppler and Dion-Jay Brookter, and says Brookter was first to propose a permanent ban before the others joined in at a candidate forum. So the policy has a political tailwind beyond a single supervisor.

The Bay Area is moving as a bloc

San Francisco is not alone. The Standard reports that the Oakland City Council approved its own data center moratorium on the same Tuesday. It adds that Oakley, Richmond and Gilroy already have moratoriums and that Hayward is considering one.

Zoom out and you get a pattern we have covered before. New York's governor backed a statewide pause on hyperscale permits, as we explained in Hochul and AOC back New York's data center moratorium. Virginia has moved on cost recovery in the other direction, as we described in Virginia's data center power tax. The tool differs by place, but the question is the same: who pays for the power, water and land that AI compute uses?

What this means for people who build with AI

For most builders, nothing changes this week. You rent compute from a cloud region, and none of the large cloud regions sits inside San Francisco. The consequences are indirect, and they are worth naming.

Siting pressure moves outward. Companies that wanted local, low-latency compute near their San Francisco teams will look at Oakland, the Peninsula or the Central Valley. Oakland and several neighbours now have their own pauses, so the easy alternatives are shrinking. Expect more compute to land in states with abundant power and fewer local vetoes.

Permitting risk is now a line item. A year ago a developer priced land, power and chips. Today they price the chance of a moratorium. That feeds into the cost of capacity, and in time into the price of tokens. We covered that chain in Virginia's data center power tax and the memory-side pressures in RAM prices and local AI builds.

On-device and desk-side compute gets more attractive. If shared data center capacity gets harder to site, running models on your own hardware looks better. That does not make local AI cheap, as the memory market shows, but it is one more reason to compare options such as the DGX Spark local LLM setup.

Policy literacy is a skill. If you run AI infrastructure at a startup, learn your city and county rules. Zoning, interim controls and definitions of "data center" now decide whether a server room is legal. Our workshops cover practical AI operations for teams that need to plan around this.

What to watch next

• The mayor's action. Does Lurie let the ordinance take effect, return it or veto it?
• The 45-day hearing. Planning will present findings on energy, water, air quality and land use.
• The November progress hearing. The Standard says leaders will meet by then.
• Extension vote. Whether the board moves to 22 months or to permanent controls.
• The January 2027 board change. Walton terms out, and the three front-runners to replace him back a moratorium.
• Bay Area contagion. Whether Hayward and other cities follow Oakland.

What we could not confirm

We read the Standard and Mission Local reports in full. We could not open the official Board of Supervisors legislation file or the city's own announcement page, so ordinance wording, the exact effective date and the vote record come from press reporting. A HuggingNews summary, which prompted this post, adds that the moratorium directly affects OpenAI and Anthropic. We found no reporting that names either company as having a planned San Francisco data center, so we have not repeated that claim. A short Hacker News thread on the story also exists, with only a handful of comments, one of which says few companies were trying to build data centers in San Francisco in the first place. That matches the reporting that the affected pipeline is small.

Details on the ordinance, its effective date and extension terms were accurate as of October 9, 2026, and may change after the mayor's action and the Planning Department's findings.

Related reading

• The AI data center backlash, mapped
• Hochul and AOC back New York's data center moratorium
• The real environmental impact of AI data centers
• Virginia's data center power tax and AI pricing
• RAM prices and local AI builds
• NVIDIA DGX Spark: the best setup for local LLMs
• Source reporting: San Francisco Standard and Mission Local