A data center that switches from water-based cooling to air-based cooling can report a large drop in onsite water use. That drop is real. What's rarely reported is where the water demand went — because it didn't disappear, it moved upstream, past the fence line, to somewhere the facility's water report doesn't reach.
The tradeoff is physics, not a design choice
Cooling a data center is fundamentally a trade between water and electricity:
Water-based cooling (evaporative cooling towers) uses less electricity, more water — water evaporates and carries heat away directly.
Air-based cooling uses more electricity, less water — mechanical refrigeration replaces evaporation with power-hungry compressors.
Switch from one to the other and you haven't eliminated a resource cost. You've traded which resource you're consuming, and where.
Where the "eliminated" water actually goes
Air cooling's extra electricity has to be generated somewhere, and most generation methods use water: thermoelectric power plants (coal, gas, nuclear) use water for their own cooling; even accounting for hydropower's evaporative losses, generating electricity has a water footprint. So a facility that reports "we cut onsite water use by switching to air cooling" is often reporting a real local win while quietly increasing the indirect water footprint embedded in the extra electricity it now draws.
Studies estimating full-chain water intensity of electricity generation regularly find the indirect water footprint of the power used to run a data center exceeds the facility's onsite water use — by multiples, not percentages — once you account for the water consumed generating that electricity upstream. The number depends heavily on the grid mix (thermoelectric-heavy grids carry a much bigger indirect water footprint than wind or solar-heavy ones) and the local water source (freshwater withdrawal versus a coastal or reused-water source changes the stakes entirely).
Why "moving the tradeoff" isn't neutral
This wouldn't be a big deal if water stress were geographically uniform. It isn't. 62% of Texas's AI data center capacity sits in high water-stress zones — regions where water is already a contested resource for agriculture, municipal use, or drought management. A facility can cut its own reported water use while increasing draw on a grid whose generation mix pulls water from a stressed source hundreds of miles away, and both changes can be true at once, reported separately, by different parties, with no line connecting them.
The community absorbing the onsite water reduction gets a genuine local win. The community whose grid now serves more electricity demand doesn't see it show up as an AI data center's problem — it shows up as "the grid," a boundary that conveniently ends the accounting.
The point isn't that cooling should stop being efficient
Air cooling isn't wrong. Efficiency gains onsite are real and worth having. The problem is reporting one side of a two-sided tradeoff as if it were a net reduction, when the honest description is a resource shift whose full footprint depends on where the extra electrons came from.
That's the boundary CarbonLayer's water accounting is built to close: tracking water at the generation source behind the electricity, not just the meter at the cooling tower, so "water positive" claims can't hide a shifted cost outside the reporting boundary.
