Is Google's Data Center Hoarding Water Resources?
Discover how Google's data centers are impacting our water resources and what that means for the environment and local communities.
When a city starts quietly rerouting its water policy, it’s worth asking who’s actually at the table. In one municipality where Google operates a sprawling data center campus, critics—including local environmentalists—are raising exactly that question. The allegation: city officials are engineering water access for one of the world’s most powerful corporations while the surrounding ecosystem and community pay the price.
This isn’t a hypothetical concern about the distant future. It’s happening now, and it reflects a tension that will define infrastructure development for the next decade.
Understanding Data Centers and Their Water Needs
Most people think of data centers as energy problems. The electricity demand is real and enormous—but water is the quieter crisis.
Large-scale data centers use water in two primary ways: cooling tower systems that evaporate water to regulate server temperatures, and in some cases, direct liquid cooling for high-density compute hardware. A single hyperscale facility can consume millions of gallons of water per day, with some estimates from the Lawrence Berkeley National Laboratory placing U.S. data center water consumption in the billions of gallons annually.
Google, Microsoft, and Meta have all published water usage effectiveness (WUE) metrics—a measure of how many liters of water are consumed per kilowatt-hour of IT load. Google's average WUE has hovered around 1.1 L/kWh in recent years, which is competitive by industry standards. But "efficient" is relative. When you’re running compute infrastructure at the scale Google operates, even a good WUE number translates into staggering absolute consumption.
The facilities don’t just need water—they need *reliable* water. That’s where municipal agreements, water rights negotiations, and infrastructure commitments enter the picture. And that’s where things get complicated.
The Environmental Impact of Increased Water Use
Redirecting significant water resources to serve industrial cooling doesn’t happen in a vacuum. Local watersheds, aquifer recharge rates, and downstream agricultural users all exist within a connected system. When one large actor increases its draw—especially in regions already stressed by drought or population growth—the effects ripple outward.
The ecological math is unforgiving: water diverted to cool servers is water that doesn’t flow through wetlands, doesn’t recharge groundwater, and doesn’t support the agricultural operations that communities often depend on.
For communities in arid or semi-arid regions—increasingly where data centers are being sited, attracted by cheaper land and power—this is particularly acute. The American Southwest is the most obvious example: a region already managing water scarcity across state lines, tribal water rights, and federal compacts is now absorbing the demands of a rapidly expanding digital infrastructure buildout.
The long-term sustainability concern isn’t just about one company’s one facility. It’s about the cumulative effect of dozens of hyperscale campuses concentrating in regions without the water budget to support them—and the policy frameworks that haven’t kept pace.
Case Study: Google's Data Center Expansion
Google’s data center in question sits at the center of a community dispute that illustrates exactly how these tensions play out on the ground. According to critics—including local environmentalists—city officials have been working to secure additional water resources in ways that appear to benefit Google’s campus operations directly.
The company’s data center footprint is not small. Google has invested billions in physical infrastructure across the U.S., and its facilities require the kind of long-term resource commitments that naturally entangle corporate interests with municipal planning decisions.
What makes this case instructive is the mechanism: it’s not Google openly lobbying for water rights—it’s a city appearing to restructure its water acquisition strategy in ways that align neatly with a major tenant’s operational needs.
That’s a subtler form of corporate capture, and it’s harder to challenge. When a company builds a campus that employs hundreds of people and generates significant tax revenue, local governments face real pressure to accommodate that partner’s infrastructure requirements. The political economy of economic development can quietly override environmental stewardship—not through corruption, but through the ordinary incentives of elected officials who want to keep a major employer happy.
Environmentalists who’ve raised objections aren’t opposing economic development categorically. Their argument is about process and prioritization: Who was consulted? What environmental review was conducted? And when water is finite, whose needs come last?
Shifts in Water Policy Due to Corporate Demands
The Google situation isn’t an isolated policy wrinkle—it’s a preview of a much larger governance challenge. As data center water use becomes a material issue for communities across the country, regulators are beginning to respond, though unevenly.
Some states have started requiring data center operators to disclose water consumption as part of permitting processes. Virginia, which hosts the largest concentration of data centers on the planet in its "Data Center Alley," has seen legislative efforts to increase transparency around both energy and water use. Nevada, another major data center hub, has similarly begun tightening its water-use scrutiny given the state’s ongoing drought conditions.
The regulatory gap, however, remains wide. There’s no federal standard for data center water disclosure, and most municipalities are negotiating these agreements without the technical expertise or legal leverage to push back effectively against sophisticated corporate counterparties.
What tends to happen in the absence of strong policy: cities compete against each other for data center investment by offering favorable terms—tax incentives, streamlined permitting, and infrastructure commitments including water access. The result is a race to the bottom on environmental conditions, with communities bearing the long-term costs of resource depletion while the economic benefits are captured largely by corporate shareholders.
The most effective policy interventions emerging from early-adopter jurisdictions share a common thread: mandatory water consumption reporting, enforceable efficiency standards as a condition of permitting, and genuine community input processes before major water agreements are finalized.
Community Activism Against Water Hoarding
Local communities aren’t passive in this story, and the most effective pushback has come from coalitions that combine environmental expertise with civic organizing.
In several jurisdictions facing similar dynamics—where a large tech employer’s water needs have collided with local resource constraints—community groups have successfully demanded environmental impact reviews, delayed permitting processes, and in some cases negotiated binding commitments on water recycling and efficiency standards from operators.
The playbook that works tends to involve a few consistent elements: early organizing before agreements are finalized (once a deal is signed, options narrow dramatically), data-driven advocacy that challenges corporate water metrics on technical grounds, and coalition-building that connects environmental groups with agricultural water users and municipal ratepayers who have overlapping interests.
The communities that have made the most progress are the ones that reframed the conversation—not as "anti-tech" but as pro-accountability. That framing matters. It’s harder for officials to dismiss when the people asking for transparency include farmers, small business owners, and local ratepayers alongside environmental advocates.
There’s also a growing movement to establish "water budgets" as part of zoning and land use frameworks—essentially requiring any large industrial user to demonstrate that its water consumption is sustainable within the local watershed before development approval. That kind of upstream policy tool changes the negotiating dynamic before it reaches the contentious stage.
The deeper issue here isn’t really about Google specifically—it’s about what happens when infrastructure at planetary scale meets governance designed for a different era. Data centers are essential. The digital economy runs on them, and the AI compute buildout underway will only increase demand. But "essential" doesn’t mean "unconditional."
The communities, regulators, and advocates who figure out how to set meaningful conditions on data center water use—while remaining genuinely open to responsible development—are the ones who will shape what this industry looks like in twenty years. The alternative is a slow accumulation of small decisions, each defensible in isolation, that collectively drain resources communities can’t replace.
Water, unlike compute capacity, doesn’t scale.
Explore more about responsible data center practices and community engagement on our marketplace.