Analysis · ESG reports · Bloomberg · Ceres · LBNL · EESI

The water problem: what cooling AI actually costs the ground it sits on

Power gets the headlines and the lawsuits. But the resource that quietly decides where a data center can actually be built — and where the buildout runs into a wall it can't buy its way past — is water.

A Gridlas analysis · built from public data · figures 2021–2026, primary sources cited throughout

Our first two analyses were about electricity — the interconnection queue and the workarounds operators use to get power fast. Water is the other meter, and it behaves differently. A cluster that can't get grid power can burn gas on-site or sign a nuclear PPA. A cluster that runs a region's aquifer or river dry has no equivalent escape hatch. Cooling is where AI touches the ground most directly, it is increasingly landing in the driest places in the country, and it is the constraint least amenable to a clever deal. Here is what the public record shows.

1. Cooling is a water decision, not just a power one

Most large data centers reject heat by evaporating water in cooling towers — trading water for electricity, because evaporative cooling is far more energy-efficient than refrigeration. The metric is Water Usage Effectiveness (WUE), liters of water per kWh of IT load. The industry average sits around 1.8 L/kWh; best-in-class evaporative designs reach 0.3–0.7; and sealed closed-loop liquid or air cooling use almost no water on-site at all.

0 0.5 1 1.5 2 Evaporative cooling towers · industry avg Industry-average evaporative cooling: about 1.8 L/kWh ~1.8 L/kWh Efficient evaporative best-in-class (e.g. NREL) Best-in-class evaporative cooling: roughly 0.3–0.7 L/kWh ~0.5 L/kWh Closed-loop liquid sealed, recirculated Closed-loop liquid cooling: near-zero on-site water (WUE ~0) ~0 on-site Air-cooled no evaporation Air-cooled: virtually zero on-site water — but higher energy use ~0 on-site
Water intensity by cooling approach (WUE, liters per kWh of IT load). Evaporative cooling trades water for energy efficiency; closed-loop and air cooling use near-zero water on-site. Sources: industry WUE benchmarks (Introl, EESI); NREL; Microsoft (closed-loop).
The "zero-water" catch — Air and closed-loop cooling don't erase the water; they move it upstream. A drier cooling design usually needs more electricity, and thermoelectric power generation is itself water-intensive — the indirect water footprint from a data center's electricity is estimated at roughly 10× its direct cooling use. "Zero-water cooling" means the water is spent at the power plant instead of the campus.

That trade-off is why the number that matters isn't just how much a facility draws, but where the draw lands — because the same gallons mean very different things in Virginia and in Arizona.

2. The direct number is big — and the real number is bigger

The hyperscalers do report direct water use, and it is climbing fast. Google's data centers consumed 6.4 billion gallons in 2023 — up about 50% from 2021 — with roughly 95% of that going to cooling. Microsoft used 1.7 billion gallons, up 34% in a single year; Meta reported about 0.81 billion. The largest individual campuses can draw several million gallons a day, on the order of a town of tens of thousands of people.

0 2 4 6 Google 2023 · up ~50% since 2021 Google 2023: 6.4 billion gallons direct water, ~95% for data-center cooling 6.4 B gal Microsoft 2023 · +34% vs 2022 Microsoft 2023: 1.7 billion gallons, up 34% from 2022 1.7 B gal Meta 2023 Meta 2023: 813 million gallons (~0.81 billion), ~95% data centers 0.81 B gal
Reported direct data-center water consumption, 2023 (billions of gallons). Direct cooling only — the indirect footprint from electricity is far larger, and disclosure is voluntary and inconsistent. Sources: Google, Microsoft & Meta environmental/sustainability reports; Civil Beat / Fast Company on reporting gaps.
6.4 B gal
Google's 2023 direct water — up ~50% since 2021
~10×
indirect (power-generation) water vs direct cooling
~2/3
of new U.S. data centers sit in high-water-stress areas (Bloomberg)

And these are the companies that disclose. Multiple investigations — Honolulu Civil Beat, Fast Company, the Global Investigative Journalism Network — have found that most operators reveal little or nothing about site-level water use, so the public totals almost certainly understate the real draw.

3. The compute is landing where the water isn't

The siting data is the uncomfortable part. A 2025 Bloomberg analysis found that about two-thirds of new U.S. data centers built or in development since 2022 sit in places already under high water stress — and just five states account for 72% of them. Two of those five, Arizona and Texas, are among the most drought-exposed in the country.

0 20 40 60 Virginia Virginia: 67 new data centers in high-water-stress areas 67 Arizona Arizona: 26 new data centers in high-water-stress areas 26 Texas Texas: 26 new data centers in high-water-stress areas 26 Illinois Illinois: 23 new data centers in high-water-stress areas 23 California California: 17 new data centers in high-water-stress areas 17
New U.S. data centers in high-water-stress areas since 2022, top five states (counts of facilities, not size). These five are ~72% of the national total. Source: Bloomberg analysis using WRI Aqueduct water-stress data, through Q1 2025.

The flashpoints follow the map. In Memphis, xAI's cooling draws on the Memphis Sand aquifer, the city's drinking-water source. In Phoenix and across the Southwest, campuses compete with cities for Colorado River water. A single proposed Utah campus was reported to need up to ~16 billion gallons a year — more than double Google's entire global 2023 direct use — though such headline figures are contested and often reflect worst-case permitting estimates. The pattern is consistent even where the numbers are fuzzy: the cheapest land and fastest power sit in exactly the basins with the least water to spare.

Power can be trucked in — as gas, as a nuclear contract, as a new line. Water can't. It's local, it's political, and once a basin is stressed there's no PPA that refills it.

4. Why water, not power, may decide the map

Put the three Gridlas analyses together and a hierarchy of constraints emerges. The grid queue is slow, but it has exits — the whole point of powering around the queue is that a determined operator can generate its own electricity. Water has far fewer exits. The efficient fixes — closed-loop and air cooling, recycled and non-potable supply — are real and spreading (Microsoft now ships chip-level closed-loop designs), but they cost capex, energy, or both, and they don't help a project already permitted for evaporative cooling in a drought.

So water is likely to become the harder gate. It won't stop the buildout, but it will increasingly decide its geography — pushing new campuses toward the Midwest and the Pacific Northwest, toward recycled-water deals, and away from the sunbelt basins that cheap power and fast permitting made attractive in the first place. The map of AI, in the end, may be drawn less by where the electrons are than by where the water is.

The buildout has proven it can find power almost anywhere. Whether it can find water — in the places it actually wants to build — is the constraint still without a workaround.

The full picture, mapped. The Gridlas report puts demand, the interconnection queue, and five regional deep-dives onto the grid — with high-res maps and the underlying dataset (CSV/GeoJSON), built entirely from public data.

Get the report →
On the numbers — Company water figures are self-reported direct consumption for the stated year and cover cooling plus humidification; the far larger indirect footprint from electricity generation is excluded. WUE benchmarks are typical ranges, not a single facility. The Bloomberg siting analysis counts facilities in high-stress watersheds (WRI Aqueduct), not their size or actual withdrawals. Headline single-project figures (e.g. the ~16-billion-gallon Utah number) are contested permitting estimates — treat them as worst-case, not confirmed draw.
Sources: See also the grid-bottleneck analysis, powering around the queue, and the full methodology & sources.
This is the third Gridlas analysis, alongside the grid bottleneck and powering around the queue. The visual analysis maps demand over the U.S. grid, and the regional pages break it down market by market.

Gridlas · independent & unaffiliated · built from public data.