At least 138 Ohio municipalities and townships have paused data-center development, turning local zoning decisions into a statewide test of how communities manage rapid infrastructure growth.
Ohio’s data-center debate has moved from individual project hearings to a statewide pattern of local pauses. Ohio Capital Journal reporting by Siddarth Sivaraman found that at least 138 municipalities and townships had active data-center moratoriums as of September 17, 2026. Because some small communities do not post ordinances or meeting records online, the total may be higher.
That number matters because data centers bring potential investment, construction work, and tax revenue, while also requiring communities to make difficult decisions about land use, electricity infrastructure, water, noise, and public oversight. For local governments, the central question is not simply whether Ohio should host data centers. It is whether local governments can set clear rules quickly enough to protect residents and give responsible developers a predictable path forward.
A data-center moratorium temporarily stops new construction or development approvals while a local government studies its options. It gives a city, village, or township time to collect information, consult planners, hear from residents, and decide whether its existing zoning code can handle a large electricity user.
That differs from a permanent ban. According to the Ohio Capital Journal, a ban often requires a more involved zoning process, while a temporary moratorium can be adopted more quickly. For households and property owners, the difference matters: a pause can create time for public review, while a ban can permanently limit how land may be used.
Ohio data-center moratoriums and bans. Ohio Capital Journal.
Local governments are not all reaching the same conclusion. Some communities have used pauses to write new rules and permit projects under those rules. Others have moved toward prohibiting data centers entirely. In the Logan-Union-Champaign region, for example, the regional planning commission reviewed 28 similar zoning amendments from April through September that would define data centers without listing them as an allowed use, effectively prohibiting them. A planning-commission staff report shows how a zoning code can produce that result.
That distinction leads to the next question: why are so many Ohio communities seeking time to decide?
Rapid, large-scale data-center development is the immediate driver. Major companies, including Amazon, Meta, and Google, have expanded activity in Ohio, according to the Ohio Capital Journal. Communities must weigh the economic opportunity against questions about where facilities will be built, who will supply the power, and who will pay for any supporting infrastructure.
Operating and planned data centers in Ohio, Via Meteorologist Ryan Wichman
A Bowling Green State University poll found that 78% of Ohioans supported a temporary moratorium until communities could gather more information. Its results also showed that 75% opposed data-center construction in their own community and 63% opposed it elsewhere in Ohio. Those results do not dictate a policy outcome, but they explain why local officials face pressure to show their work before approving large projects.
Server racks in a data center. via Brett Sayles.
Policy stakes run in both directions. A long or unclear pause can cause a developer to choose another state, reducing potential investment. But communities that approve projects without defined standards can face disputes over local services, property impacts, and infrastructure costs later. Ohio Capital Journal reporting also identifies lawsuits in Urbana, Lordstown, and Commercial Point involving developers that challenged local actions after moratoriums were adopted.
A pause therefore has value only if a community uses it to replace uncertainty with enforceable rules.
A moratorium gives local governments a chance to decide what they will require from a proposed facility. Common tools include zoning districts, setbacks, building-height limits, noise standards, traffic plans, water reporting, and emergency-generator rules.
Findlay provides one example. The city is considering a data-center ordinance that would require third-party technical reports at the developer’s expense and impose a case-by-case cap on electrical demand, according to the Ohio Capital Journal. Those requirements would shift some of the cost of evaluating a complex proposal away from local taxpayers and toward the company seeking approval.
Zoning map used for data center planning. Source: Data Center Knowledge
Communities can also ask developers to show how new substations, generation, or other electrical infrastructure will be financed. Local-hiring commitments, public data dashboards, and advance notice before emergency generators operate can give residents more information about a project’s local effects. These tools do not guarantee that every concern disappears, but they create measurable responsibilities instead of relying on broad promises.
Massillon illustrates another path. The city lifted its moratorium early after adopting new data-center zoning regulations. Jerome Township’s earlier moratorium also expired after the township adopted land-use restrictions. These examples show that a pause can lead to rules rather than a permanent prohibition.
Once communities decide whether regulation can address their concerns, voters and lawmakers will determine whether those local choices remain in place.
Ohio Capital Journal reports that voters in four cities with active moratoriums will decide in November whether to make bans permanent. Other townships are coordinating with regional planning commissions to create shared regulations or zoning prohibitions.
Ohio ballot initiative covering local data center bans. Source: WKYC Channel 3
State and federal policy could also shape these decisions, but local zoning remains the immediate point of contact for most residents. Ohio lawmakers have debated data-center regulation and tax incentives, while federal policymakers continue to discuss power, permitting, and consumer-cost issues. Those broader debates may affect projects over time, but they do not remove the need for local governments to define clear land-use standards.
Ohio’s experience shows that a moratorium is not a policy answer by itself. It is a deadline. Communities can use that period to adopt transparent standards, assign infrastructure costs clearly, and provide residents with meaningful information. If they do not, more temporary pauses may become permanent bans.
At least 138 Ohio communities have paused data-center development because they are trying to answer practical questions before approving major projects. Residents want to know how development could affect nearby land, local services, and household costs. Developers need to know whether a community has a predictable process and workable standards.
What happens during each pause will determine the lasting outcome. Clear zoning, transparent infrastructure commitments, and enforceable local safeguards can give communities more control without making every data-center proposal an all-or-nothing fight.