US Liquid Cooling editorial · Reviewed · 3 min read
When someone says a data center is water-cooled, it is reasonable to picture water being used up all day. But that phrase can describe several different systems. Some circulate fluid repeatedly. Others deliberately evaporate water to reject heat.
To understand consumption, follow the heat beyond the server. The presence of liquid near a processor does not settle the question.
Circulating water is not the same as consuming it
A closed circuit moves fluid through equipment and back again. Its circulation rate tells you how much moves through the circuit over time; it is not automatically a measure of new water withdrawn from a local supply.
That distinction matters when reading a specification. A large flow rate can describe recirculation. It should not be presented as an equivalent volume of daily freshwater consumption.
Initial filling, service, leaks, and other losses are separate questions. Ask which of them a published water figure includes.
Follow the second half of the heat path
Heat transferred into a server coolant circuit still needs to leave that circuit. From there it may pass into a facility cooling system and eventually into outdoor air, an evaporative process, or a useful heat application.
Microsoft's June 2026 explanation distinguishes cooling towers, hybrid fluid coolers, air-cooled chillers, and closed-loop direct-to-chip designs. It describes its newer AI cooling design as recirculating water without evaporation for operational cooling. That is a statement about a particular design and boundary, not every facility using cold plates.
A closed server loop does not settle the building's total
When reviewing a proposal, ask the supplier to draw the complete heat path. Identify every place water can enter, leave, evaporate, or be discharged. This makes it possible to see what the phrase closed loop covers.
For example, ask whether an outer heat-rejection stage uses evaporative assistance during hot weather. Also ask whether the quoted figure covers cooling only, all on-site activities, or a wider assessment including electricity supply. Different boundaries can produce different answers without either number necessarily being wrong.
Questions worth asking about a zero-water claim
- Does the claim concern consumption, withdrawal, or evaporation?
- Which equipment and operating activities are included?
- Does it apply throughout the year or only under certain conditions?
- Are initial fill and maintenance losses reported separately?
- Is the number measured, modeled, or a design target?
Ask for an explanation in ordinary units and for the period being measured. A percentage reduction without a starting point is difficult to judge.
Compare the same amount of useful work
Suppose two proposed systems serve different computing loads or use different climate assumptions. Their annual water totals alone will not tell you which design performs better for your project.
Record the workload, time period, site conditions, and measurement boundary beside each figure. Keep cooling electricity in the comparison too. A proposal should explain its water and energy assumptions together rather than presenting one favorable number in isolation.
What readers should take away
Liquid cooling can operate with very low evaporative water demand, but the technology name is not a complete environmental assessment. The important evidence is the whole system diagram and a clearly defined set of measured or modeled figures.
If an article gives a water-use number, look for what it measures before sharing it. The difference between circulation and consumption is small in wording and enormous in meaning.
Sources & further reading
- Microsoft: Water intensity and cooling methods, June 24, 2026 ↗
- Vertiv: Liquid cooling deployment guide ↗
Explore the company directory → · All liquid-cooling guides →