Introduction

Data centers are becoming one of the most visible water stories in the United States. The rapid growth of cloud computing and artificial intelligence has increased demand for facilities that require reliable energy, land, cooling capacity, utility coordination, and, in some locations, substantial water. As those facilities move through local approval processes, communities are asking increasingly direct questions about water demand, infrastructure capacity, public costs, transparency, and long-term sustainability.

Those questions are reasonable. Water utilities are often managing aging infrastructure, deferred maintenance, changing demand patterns, ratepayer concerns, water quality requirements, and uncertainty around future growth. Municipal governments are trying to balance economic development with community expectations, infrastructure limits, environmental conditions, and public trust. Data center developers and operators are trying to secure sites, manage energy and water requirements, reduce permitting risk, meet corporate sustainability commitments, and respond to scrutiny from communities and regulators.

The emerging tension is often framed as a data center problem. In some locations, that framing is understandable. Large new water users can expose the limits of existing systems quickly, particularly where capacity is constrained, infrastructure investment has lagged, drought risk is increasing, or public confidence in growth decisions is low.

However, the broader issue is not only data center water use. Data center growth is revealing long-standing weaknesses in how communities plan for water demand, fund infrastructure, coordinate across watershed interests, and translate economic development into durable public and environmental outcomes.

This distinction matters because it changes the range of solutions available. If the problem is defined only as “data centers use water,” the likely responses are restrictions, disclosure requirements, moratoriums, project-by-project mitigation, or narrow offset expectations. These tools may be necessary in some circumstances, particularly when communities lack information or capacity to evaluate proposed projects. But they do not, by themselves, resolve the larger question of how water systems should adapt to changing demand, infrastructure needs, watershed conditions, and stakeholder expectations.

The larger opportunity is to recognize that large water users, utilities, municipalities, watershed organizations, conservation groups, agricultural interests, infrastructure investors, and communities all depend on the same water systems. Their priorities are not identical, and in some cases they may conflict. But they often share a long-term interest in reliable water supply, resilient infrastructure, functioning watersheds, transparent decision-making, and public confidence that growth is not being pursued at the expense of existing users or future conditions.

That shared interest is the basis for a different conversation. Rather than treating data center water demand only as a source of conflict, communities and large water users can use this moment to develop more integrated approaches to watershed sustainability, infrastructure investment, and project generation.

Why data centers are becoming a water story

Data centers have become highly visible because they concentrate several infrastructure pressures in one facility type. They require reliable energy, specialized cooling, site access, backup systems, utility coordination, and local land-use approvals. Depending on facility design, climate, cooling technology, and operational decisions, they may also require significant water withdrawals or rely on public water systems during periods when demand is already high.

The water issue is not only about annual volume. It is also about capacity, timing, transparency, and distribution of costs. A facility that uses water for cooling may create peak demand during hot periods when communities are already managing seasonal water stress, energy demand, or drought conditions. A 2026 analysis of data center water demand emphasized that peak water withdrawals can create public water system capacity constraints, particularly during the hottest days of the year.[1] Even where total system supply appears sufficient on paper, treatment capacity, distribution infrastructure, pressure zones, storage, water rights, wastewater capacity, or capital investment needs may create more localized constraints.

This is one reason public concern can escalate quickly. Community members may not object to digital infrastructure in principle, but they may object to approving large new users without clear information about water demand, utility impacts, ratepayer exposure, emergency conditions, or long-term planning. In many communities, the data center debate is less about technology than trust.

That trust is affected by the way projects are introduced. If a large facility appears in the public process after most site, design, utility, and incentive decisions have already been shaped, communities are left reacting to a project rather than participating in a broader discussion about water, growth, infrastructure, and benefit. Municipal staff may be asked to evaluate a project under existing rules that were not designed for this scale or type of demand. Utilities may have to answer capacity questions with incomplete or rapidly changing information. Developers may be asked to provide assurances that do not fully address public concerns because there is no shared framework for evaluating what should be disclosed, funded, monitored, or mitigated.

In this context, public scrutiny is not surprising. It is a response to uncertainty, and often to the absence of an institutional process that can translate a large new water demand into a credible plan for infrastructure, watershed resilience, and community benefit.

The rise of moratoriums, restrictions, and disclosure requirements

Across the country, local and state governments are considering or adopting new approaches to data center oversight. These include temporary moratoriums, zoning changes, water-use disclosure requirements, limits on cooling technologies, rate structures for large users, community benefit expectations, and additional review of energy and water infrastructure impacts. MultiState’s 2026 legislative guide notes that data center policy activity is increasingly focused on energy, water, zoning, tax issues, water-use disclosure, and local construction pauses.[2]

These tools are emerging because existing approval processes often do not fully account for the cumulative and cross-sector nature of data center development. A land-use process may evaluate zoning compatibility but not water system resilience. A utility review may evaluate service capacity but not broader watershed conditions. An economic development process may evaluate jobs, tax revenue, and redevelopment potential but not long-term infrastructure cost allocation or stakeholder trust. A sustainability commitment may address corporate reporting but not local project generation or governance.

Moratoriums and restrictions are often criticized as anti-growth. In practice, they may also be a signal that communities do not yet have the planning framework needed to evaluate growth confidently. A pause can create space for better rules, clearer information, and more transparent decision-making. However, a pause is not a strategy. Disclosure is not implementation. Restrictions can reduce risk, but they do not necessarily create the infrastructure, watershed investments, or collaboration needed to improve long-term conditions.

The same is true of narrow mitigation or offset approaches. If a data center project is treated as an isolated demand to be offset by an isolated water project, the response may satisfy a narrow requirement without improving the underlying system. A project may be funded because it is available, visible, or easy to count, rather than because it is the right intervention for the watershed, utility, community, or long-term resilience need.

This is where the data center conversation begins to resemble broader challenges in conservation and watershed management. Projects often originate from compliance requirements, funding availability, permitting needs, operational demands, or public pressure. These drivers are important because they create action. But if they operate without an integrated framework, they tend to generate individual projects with narrow scopes rather than coordinated portfolios that can serve multiple outcomes.

St. Louis as an emerging example

St. Louis offers an early example of how a community can begin moving beyond a simple yes-or-no response to data center development. The city has not presented itself as having solved the issue, and the approach will need to be evaluated over time. Still, the emerging framework is notable because it recognizes that data center approval is not only a land-use decision. It is also a water, energy, infrastructure, transparency, and community benefit decision.

In February 2026, the City of St. Louis Planning & Urban Design Agency published a proposed framework for data center zoning regulations intended to establish clearer rules regarding where and under what conditions data centers could be allowed. The stated goals included predictable standards, size-based regulation, industrial siting, energy- and water-efficient design, transparency, and community input.[3] In April 2026, the City approved a data center permit with conditions including use of closed-loop and air-cooled systems, large-load or data center-specific water rates, a hydraulic model study, protection of existing customers, wastewater compliance, energy performance, waste heat reporting, noise controls, battery storage, and community benefits.[4]

The specific conditions matter less than the broader governance signal. St. Louis appears to be asking a more complete set of questions: What would this facility require from public systems? How should large users contribute to infrastructure costs? How can water impacts be evaluated before they affect existing customers? What design standards should be expected? What information should be reported? How can community benefits be defined in terms that are specific enough to enforce?

This is not the same as a watershed-scale strategy, but it points toward the kind of institutional coordination that watershed-scale strategy requires. It recognizes that the public interest is not served by approving growth without conditions, but also not necessarily served by rejecting growth without asking whether new investment can be structured to improve shared systems.

For many communities, that may be the more useful lesson. Data center growth does not have to be evaluated only as a threat or an economic development opportunity. It can also be evaluated as a forcing mechanism that reveals whether a community has the planning, utility, infrastructure, and watershed partnerships needed to manage large new demands in a way that produces broader public value.

The emerging water stewardship marketplace

The response to data center water demand is not beginning from zero. Large technology companies, water stewardship organizations, state-level partnership platforms, utilities, and conservation groups have already begun developing tools that connect corporate water goals to project implementation.

Google’s current water strategy illustrates the direction of travel. The company states that it aims to replenish more freshwater than it consumes, on average, across its data centers and offices by 2030, evaluates local water sources through a science-based watershed health framework, looks for alternatives such as air cooling or recycled water in locations with high water risk, and reports annual water use for each data center location and each replenishment project it has supported.[5] These commitments indicate that major data center operators increasingly understand water as a local operating, community, and sustainability issue rather than only a facility efficiency issue.

Organizations such as Bonneville Environmental Foundation have also helped create mechanisms for companies to support verified water projects, including water restoration certificates and broader business water stewardship portfolios. BEF describes Water Restoration Certificates as supporting verified, high-quality water projects that balance a water footprint gallon-for-gallon, and its Business for Water Stewardship program points to corporate replenishment and restoration portfolios across multiple basins.[6][7] These tools have been important in helping companies move from generalized commitments toward funded implementation.

State-level platforms also show how partnership infrastructure can help organize conservation and water interests. The Texas Partnership for Forests and Water, for example, is described by Texas A&M Forest Service as a statewide collaboration across the forest, water, corporate, and conservation sectors, with focus areas that include watershed assessment, land conservation and stewardship, strategic partnerships, source water protection, resiliency initiatives, and corporate sustainability goals.[8]

These examples are important because they show that the field is moving. Companies are making more specific commitments. Intermediaries are helping match corporate demand with water projects. State and regional platforms are creating partnership tables. Municipalities are beginning to ask harder questions about infrastructure capacity, disclosure, and public benefit.

However, these developments do not eliminate the need for watershed strategy. In some ways, they make it more important.

A company with a replenishment commitment still needs a way to determine which investments are most relevant to its operating geography and stakeholder context. A project-matching platform still needs a broader framework to evaluate whether available projects add up to a durable watershed program. A state partnership still needs funding logic, governance, project development capacity, and measurement approaches to move from aligned interest to implementation. A municipality still needs to understand how large new water users fit into infrastructure planning, community priorities, and long-term watershed conditions.

The emerging water stewardship marketplace has created more ways for companies to fund projects. The next challenge is creating the watershed strategy that determines which projects should be generated, how they should be sequenced, and how they can serve utilities, communities, companies, and ecosystems at the same time.

Why traditional responses are incomplete

Many of the available responses to data center water concerns are necessary but incomplete.

Water-use disclosure can improve transparency, but disclosure does not identify which infrastructure or watershed investments are needed. Moratoriums can create time for policy development, but they do not build a project pipeline. Water offsets may provide a measurable response to consumption, but they can become disconnected from local watershed function if they are not developed within a broader geographic and hydrologic strategy. Compliance-driven projects can satisfy specific obligations, but they may miss opportunities to address multiple outcomes if the broader framework is developed too late. Utility infrastructure investments can improve system capacity, but they may not address source-water protection, watershed storage, land use, floodplain function, or community concerns unless those considerations are intentionally integrated.

The issue is not that these tools are wrong. Each has a role. The problem is that they are often applied independently, after a specific project or controversy has already defined the decision frame.

When that happens, stakeholders are forced into transactional positions. A developer seeks approval. A utility evaluates service. A municipality negotiates conditions. Community members raise concerns. Conservation organizations may be asked to identify projects. Engineers assess capacity. Regulators evaluate compliance. Each actor is operating within its role, but the process may still fail to generate an integrated strategy.

This is the same project-generation problem that appears across watershed conservation and resilience work. The right projects are often not waiting in a complete and ready-to-fund pipeline. They need to be generated through a process that integrates watershed conditions, infrastructure needs, funding pathways, stakeholder interests, implementation capacity, and measurable outcomes. Without that process, the available options tend to reflect whatever is easiest to permit, fund, count, or explain in the moment.

Data center growth makes this problem more visible because the scale and timing of demand can be difficult for communities to absorb. But the underlying issue is much broader. Many communities are already trying to manage growth, aging infrastructure, water quality concerns, flood risk, land use change, agricultural demands, and ecosystem degradation through fragmented tools and funding sources. Data centers are not creating the fragmentation. They are revealing it.

The opportunity for unlikely partnerships

The emerging water conflict around data centers creates an opportunity for partnerships that might not have formed otherwise.

Large water users need reliable systems, predictable approvals, community trust, and credible sustainability outcomes. Utilities need capital, demand forecasting, infrastructure planning, rate structures, and protection for existing customers. Municipalities need economic development that does not undermine public confidence or create unfunded infrastructure burdens. Watershed organizations and conservation groups need mechanisms to move from planning and project identification to implementation. Agricultural interests need water reliability, soil and drainage solutions, and practical incentives. Infrastructure investors need durable project structures, revenue logic, and risk clarity. Communities need transparency, affordability, resilience, and confidence that growth will not reduce their own access to water or environmental quality.

These interests do not automatically align. In many places, they may begin in tension. But they are not unrelated. They all depend, in different ways, on water systems that are reliable, resilient, and well managed.

A better approach would use large water demand as an entry point into a broader watershed implementation strategy. Rather than asking only how a data center can reduce or offset its own water use, stakeholders could ask what investments are needed to improve the water system on which all users depend. Some of those investments may be traditional utility infrastructure. Some may involve source-water protection, aquifer recharge, floodplain restoration, agricultural water efficiency, stormwater retrofits, wetland restoration, water reuse, wastewater improvements, or land conservation. Some may involve governance, monitoring, modeling, data transparency, or project development capacity.

The important point is not that every data center should fund every type of watershed project. That would be unfocused and unrealistic. The point is that communities and large water users need a framework for determining which investments are relevant, feasible, and beneficial in a specific place.

That framework should be developed before individual projects are selected. Otherwise, stakeholders risk defaulting to whatever projects are most visible, easiest to count, or already sitting on someone’s shelf. Those projects may be useful, but they may not represent the best opportunity to improve watershed sustainability, infrastructure resilience, or stakeholder alignment.

What an integrated watershed approach needs to account for

An integrated watershed approach should begin with the system, not the project.

This does not mean every community needs a lengthy planning process before acting. In many cases, water infrastructure, regulatory, or development decisions are time-sensitive. However, even rapid decision-making benefits from a clearer understanding of the conditions that control outcomes.

At a minimum, large water demand should be evaluated in relation to watershed conditions and risks, including water supply sources, seasonal demand patterns, drought exposure, water quality conditions, infrastructure constraints, wastewater capacity, ecological conditions, land use trends, community vulnerabilities, and existing planning efforts. The purpose is not to produce an academic watershed assessment. It is to understand the pathways and constraints that determine whether proposed investments will actually improve system resilience.

It should also account for the relationship between infrastructure, conservation, and resilience needs. In some places, the limiting factor may be treatment or distribution capacity. In others, it may be source-water protection, stormwater management, aquifer stress, flood exposure, wastewater limitations, degraded natural storage, or land use change. The most relevant response may be a utility investment, a conservation investment, a reuse strategy, a governance change, or some combination of approaches. The response should follow from the system conditions rather than from the category of funding or project type that happens to be available.

Stakeholder interests also need to be clarified early enough to influence the opportunity set. Utilities, municipal governments, watershed organizations, conservation groups, agricultural interests, community representatives, companies, agencies, and funders may each understand different parts of the system. Bringing those perspectives together only after projects have been selected limits the value of engagement. Bringing them together earlier can reveal where interests overlap, where tradeoffs need to be managed, and where a project could be shaped to serve more than its initiating purpose.

A mature approach also distinguishes between implementation opportunities that are ready now, opportunities that require development, and longer-term investments that may be important but not immediately actionable. This distinction is critical because watershed programs often fail when near-term funding pressure is applied to projects that are not yet ready, or when longer-term opportunities are ignored because they cannot be easily packaged within a current approval or budget cycle.

Funding and investment pathways should be considered in relation to these differences. Large water users may be one source of capital, but they should not be treated as the only mechanism. Public funding, utility investment, state and federal programs, philanthropy, infrastructure finance, mitigation funding, and private capital may each have a role. The important question is not only who can pay, but what each source of funding is suited to support and how those investments can be aligned without distorting the purpose of the work.

Finally, measurement should be tied to the purpose of the investment. Some outcomes may be quantified directly, such as water savings, storage, treatment capacity, or load reductions. Others may be modeled, monitored over time, or described qualitatively where direct quantification would overstate certainty. Credibility depends on being clear about what is measured, what is inferred, and what is expected to improve over time.

These considerations do not amount to a complete method. They are the categories of judgment that are too often handled separately. The work of applying them depends on the specific watershed, infrastructure system, institutional context, funding environment, stakeholder landscape, and implementation capacity in front of the decision-makers.

The emerging role of large water users

Large water users are becoming watershed stakeholders whether they intend to or not.

This is particularly true for data centers because their water and energy requirements are highly visible and because public concern can emerge quickly when communities perceive that local resources are being committed without adequate transparency or benefit. Even companies with relatively efficient cooling systems may face scrutiny if communities do not understand how water demand, infrastructure capacity, and public costs are being managed.

A proactive approach can reduce these risks. It can improve community trust by engaging stakeholders before decisions feel predetermined. It can reduce permitting and approval risk by identifying infrastructure and watershed concerns early. It can improve water security by supporting the systems that facilities depend on. It can help companies move from generalized sustainability commitments to place-based strategies that are more credible because they are tied to actual watershed conditions and implementation pathways.

However, proactive engagement has to be substantive. Communities are unlikely to be reassured by broad claims of water stewardship if they do not see how the company’s actions relate to local needs, utility capacity, watershed conditions, and public benefit. Similarly, conservation organizations and watershed groups are unlikely to be effective partners if they are brought in only after a company needs a project to fund.

The opportunity is to engage earlier and more strategically. Large water users can help support the planning, project development, and implementation capacity that many watershed efforts lack. They can participate in shared frameworks that identify priority actions before project scopes are fixed. They can help fund projects that improve system resilience while also supporting their own water reliability, risk management, and sustainability objectives. They can also help create demand for better measurement, governance, and transparency.

This does not require presenting watershed investment as charity. It should be understood as part of a broader approach to water system resilience, infrastructure performance, community trust, and long-term operational risk management.

From water conflict to watershed stewardship

Data centers may be the first highly visible manifestation of a larger trend. As water demand grows, infrastructure ages, climate variability increases, and communities become more attentive to resource allocation, large water users of many kinds will face similar questions. Who benefits from growth? Who pays for infrastructure? How are existing users protected? What information is disclosed? How are watershed impacts understood? What investments are needed to make the system more resilient for everyone?

These questions cannot be answered well through isolated projects alone. They require a more deliberate process for connecting water planning, infrastructure investment, watershed management, and stakeholder coordination.

For data center developers and operators, the implication is that water strategy cannot stop at facility efficiency. Efficiency matters, but it is only one part of a larger relationship with the water systems and communities that support operations. For utilities and municipalities, the implication is that large new water users should be evaluated not only as demand, but also as potential participants in the long-term investment needed to maintain and improve shared systems. For watershed and conservation organizations, the implication is that technical priorities need to be translated into implementation opportunities that can engage new partners without losing ecological integrity. For funders and infrastructure investors, the implication is that watershed sustainability increasingly requires project portfolios with clear governance, funding logic, and delivery capacity.

The opportunity is not to avoid conflict by avoiding growth, or to approve growth by minimizing concerns. The opportunity is to use the pressure created by growth to build better mechanisms for planning, funding, and implementing watershed-scale solutions.

The communities and companies that recognize this shift early will be better positioned to support economic development, improve resilience, protect public trust, and sustain water resources over the long term. The work begins by changing the sequence: not selecting projects first and searching for value afterward, but developing the watershed strategy early enough that the right projects can be generated, shaped, funded, and delivered.

References

[1] Han, Y., Li, P., Wierman, A., & Ren, S. (2026). Small Bottle, Big Pipe: Quantifying and Addressing the Impact of Data Centers on Public Water Systems. arXiv. https://arxiv.org/abs/2603.02705

[2] MultiState. (2026). State Data Center Policy 101: 2026 Legislative Guide. https://www.multistate.us/resources/state-data-center-policy-101

[3] City of St. Louis. (2026, February 5). City of St. Louis Shares Report on Data Center Regulations, Community Invited to Public Hearing. https://www.stlouis-mo.gov/government/departments/mayor/news/data-center-regulations-report.cfm

[4] City of St. Louis. (2026, April 21). City of St. Louis Approves Permit for Data Center Project, Announces Significant Conditions and Community Benefit Framework. https://www.stlouis-mo.gov/government/departments/mayor/news/data-center-permit-approved.cfm

[5] Google Data Centers. (2026). Advancing responsible water use at our data centers. https://datacenters.google/water/

[6] Bonneville Environmental Foundation. (2020). Water Restoration Certificates. https://www.b-e-f.org/programs/water-restoration-certificates/

[7] Bonneville Environmental Foundation. (2020). Business for Water Stewardship. https://www.b-e-f.org/programs/business-for-water-stewardship/

[8] Texas A&M Forest Service. (2026). Texas Partnership for Forests & Water. https://tfsweb.tamu.edu/forest-land/texas-forests/ecosystem-services/forest-and-water-relationship/texas-partnership-for-forests-and-water/