Where the water goes
Three common approaches to cooling treat water very differently:
- Evaporative cooling at the building level consumes water. It is the more energy-efficient option.
- Air-cooled chillers reject heat outside the building without consuming water. They use more energy, so they suit places where water is scarce.
- Liquid cooling at the server is a closed loop. The coolant does not evaporate, so its effect on water consumption is negligible.
The trade-off with energy
Avoiding evaporative cooling saves water but raises energy use, which shows up as a higher PUE. That is why water and energy have to be looked at together. A design that cuts water but quietly adds power demand has only moved the problem.
Measuring it: WUE
Water usage effectiveness, or WUE, is the water used for cooling divided by the energy used by the IT equipment, measured in cubic metres per megawatt-hour. As one operator's example, Equinix reported 0.95 m³/MWh across its portfolio in 2024 and 1.55 m³/MWh in its evaporative-cooled data centres.
WUE has limits. Operators report it in different ways, and it treats every kind of water the same, whether it is drinking water or treated wastewater.
Other ways to reduce demand
- Assess each site. Look at local water stress and water planning before choosing a cooling design.
- Use reclaimed water. Treated wastewater can serve non-potable uses such as evaporative cooling, where it is available at the right standard.
- Consider desalination with care. It can be a source near the coast, but it uses energy, produces brine and affects the coastal environment.
How we think about it
We treat water, energy and the local community as one question. That means choosing cooling that fits each site's water situation, preferring low-water designs where supply is tight, and looking at water use alongside power, not after it.

