Reno starts rewriting data center rules after council vote

Reno City Council has started a code-change process for data centers, with water, power, noise and infrastructure questions still ahead.


Reno City Council has started the process of rewriting how the city regulates data centers, but it has not adopted final new standards yet.

At its April 22, 2026 meeting, the council voted to initiate a Title 18 text amendment related to data center regulations, according to the City of Reno’s meeting highlights. In plain terms, that means the city is opening a formal review of its zoning code so staff, officials and the public can work through possible changes before any final rules come back for approval.

The distinction matters for residents and developers. A text amendment launch is the beginning of a rulemaking process, not the end of one. It does not, by itself, settle where data centers should be allowed, what operating standards should apply, or how the city should handle pending and future applications.

Why the issue is moving now

The City of Reno says it has already reviewed four data center projects. That local pipeline helps explain why council members are now looking at whether the existing zoning code is specific enough for a land use that can carry large utility and infrastructure demands.

City materials show data centers were already on Reno’s policy agenda before the April 22 action. The city’s memo on policy and ordinance changes related to data centers framed the issue as a Title 18 question, meaning the debate is centered on the city’s land-use and development rules rather than a one-off project decision.

Local reporting from KOLO and This Is Reno described concerns raised around the council discussion, including water use, power demand, noise, infrastructure impacts and whether Reno’s current code gives the city enough clarity when reviewing large-scale data center proposals.

What residents should take from the vote

For nearby neighborhoods, the practical question is how future rules may address impacts that are often hard to evaluate project by project: backup power equipment, cooling systems, utility capacity, traffic during construction, noise standards and the cumulative effect of multiple facilities in the same region.

For local business owners and development applicants, the vote signals that Reno may move toward more specific standards. But until final language is drafted, reviewed and adopted, the details remain unsettled.

The city has also indicated that next steps include public review and regional coordination. That regional piece is important because utility systems, water planning, energy demand and infrastructure networks do not stop at Reno’s city limits, even when the zoning decision is a city action.

The moratorium question is still separate

Councilmember Devon Reese had called for a moratorium on new data center approvals before the April 22 meeting, according to KOLO. That proposal is part of the broader policy debate, but the available city action from April 22 was to initiate the Title 18 amendment process.

Residents should not read the April 22 vote as proof that Reno has enacted a moratorium or adopted final data center regulations. If a pause on approvals comes back for formal consideration, that would be a separate policy action that would need to be tracked on its own terms.

What to watch next

The next meaningful steps are the public review process, any staff-drafted code language, regional coordination updates and future council or planning hearings where standards could be debated in detail.

For renters, homeowners, commuters and employers, the issue is not only whether data centers locate in Reno. It is how the city measures and manages their effects on utilities, public infrastructure, nearby properties and long-term growth planning.

The April 22 vote put that question into Reno’s formal zoning-code pipeline. The decisions that determine the actual rules are still ahead.

Sources

Local Tips & Viewpoints

Your email address will not be published. Required fields are marked *