← Back to Intel
Sustainability March 12, 2026

The Water-Power Tradeoff That Data Center Operators Keep Getting Wrong

A growing number of data center operators have started swapping water-cooled systems for air-cooled alternatives, claiming sustainability wins. The math tells a different story. Air cooling eliminates on-site water use, sure. But it doubles or triples electricity consumption, pushing the water burden upstream to power plants that need their own cooling loops to generate that extra juice. The problem doesn't vanish. It moves.

Colocation vacancy rates have cratered to 2.3%, down from 9.8% in 2020. The construction pipeline grew tenfold over the same period. Every new facility that comes online has to make a fundamental call on how it manages heat, and that decision ripples through local water tables and power grids for decades. A large data center drinks roughly what a town of 50,000 people does in a day. Regulators in multiple states have started blocking projects over that kind of draw.

The operators getting this right tend to match their cooling architecture to their actual scale. Hyperscalers running 100+ MW loads are exploring on-site power generation, including hydrogen fuel cells that produce water as a byproduct. Facilities in central Ohio are already piloting private microgrids built around this concept. Mid-tier and edge deployments, meanwhile, are finding that modern evaporative cooling towers can hit the efficiency marks without the electricity penalty. And micro data centers, anything from a large closet to a shipping container, remain firmly in air-cooling territory, where even the smallest cooling tower would be ten times more capacity than needed.

True sustainability means refusing to solve one problem by creating another. The operators who claim green credentials while tripling their grid draw are playing an accounting trick, not running an efficient facility.

_linkedin_partner_id = "8831074"; window._linkedin_data_partner_ids = window._linkedin_data_partner_ids || []; window._linkedin_data_partner_ids.push( _linkedin_partner_id);