The hidden wastewater problem of AI data centers: what cooling-tower blowdown actually is

What blowdown is, in plain English

Many data centers reject heat by circulating water through cooling systems. In systems that rely on evaporative cooling, some of that water evaporates into the air. The water that evaporates is relatively pure. What stays behind is a more concentrated mix of whatever was dissolved in the water to begin with, plus whatever treatment chemicals were added to keep the system operating safely.

That remaining concentrated water must be discharged, treated, or reused. The intentional removal of that concentrated water is called blowdown.

Think of boiling salty water in a pot. As steam leaves, the salts do not. The remaining water gets more concentrated. Cooling systems face a similar concentration problem, just in an industrial setting and with tighter operational controls.

Why blowdown matters

The basic engineering goal of blowdown is reasonable: prevent minerals, salts, corrosion, scale, and biological growth from damaging the cooling system. The water-quality question begins when that concentrated stream leaves the cooling system.

A February 2026 TNFD case study says data centers can affect water quality when wastewater from evaporative cooling is mismanaged and notes that this stream can contain high concentrations of salts, heavy metals, and other pollutants.

That does not automatically mean a data center is violating permits or dumping toxic water into a river. It means the quality of the discharge matters, the treatment approach matters, and the local receiving system matters. A small, well-managed discharge going to a system designed to handle it is one thing. Multiple facilities in one basin, all producing concentrated discharges and relying on the same wastewater infrastructure, is another.

What can be in blowdown?

The answer depends on source water, chemistry, treatment program, and how many cycles of concentration the operator is running. In broad terms, blowdown can contain:

• Elevated total dissolved solids (TDS)
• Salts and hardness minerals
• Treatment residuals such as chlorine-related compounds or biocides
• Corrosion inhibitors
• Altered pH
• Metals that accumulate through system contact and concentration

This is why water reuse and cooling-water literature spends so much time on scaling, corrosion, microbial control, and pretreatment.

Why AI may make this more visible

AI workloads increase heat density. More heat generally means more cooling demand. The Environmental and Energy Study Institute notes that data-center water use closely parallels energy use and that larger data centers can consume very large quantities of water when water-based cooling is used.

The more AI pushes operators toward higher-density compute, the more closely communities will examine what kind of cooling system is being used, whether the site uses potable or reclaimed water, how much blowdown is generated, where that blowdown goes, and whether local wastewater plants have the capacity to handle it.

Recycled water helps — but it does not erase the quality question

A common response from the industry is to use more recycled or reclaimed water instead of drinking water. That is often a good idea. Amazon says AWS is expanding recycled-water use from 24 to more than 120 U.S. locations and expects the shift to preserve over 530 million gallons of drinking water annually.

But recycled water does not eliminate water-quality management. It changes it. Reclaimed water may already carry a different chemistry than potable water. That can increase the need for pretreatment, corrosion control, scaling control, or more advanced monitoring before the water enters a cooling loop.

Why local wastewater systems matter

A frequent blind spot in data-center debates is the role of the local wastewater utility. Cooling-tower blowdown is not simply a private on-site issue if it is discharged to a municipal treatment plant or another shared system.

A 2026 PLOS Water paper on datacenter-driven water insecurity argues that local governments and utilities do not always readily provide water-use data tied to data-center operations and calls for public records to be requested and shared so communities can evaluate the tradeoffs.

If a region is adding multiple high-density data centers, a useful public checklist includes:

• Total expected discharge volumes
• Expected TDS and chemistry ranges
• Pretreatment requirements
• Discharge destination
• Whether reclaimed water is part of the system
• Whether the receiving utility has evaluated cumulative load

What communities should ask

If a data-center project is being proposed nearby, these are the right water-quality questions:

1. 1Will the site use evaporative cooling, closed-loop cooling, or mainly air cooling?
2. 2Will it use potable water, reclaimed water, or both?
3. 3What chemicals are used to manage scaling, corrosion, and microbial growth?
4. 4How much blowdown will be produced under average and peak conditions?
5. 5Where will that blowdown go?
6. 6What pretreatment is required before discharge or reuse?
7. 7What public monitoring and reporting will be available?

What this means for households

Most households do not need to become cooling-system experts. But understanding blowdown helps people ask better questions when they hear claims that a facility is 'water efficient' or 'using recycled water.' Those claims may be true — and still leave unanswered questions about wastewater management.

• Know your utility
• Read your local reports
• Understand which contaminants already matter in your area
• Watch how major industrial water users in your basin are permitted and monitored

A stronger local water system is not only about what comes out of your tap. It is also about what enters your watershed, your wastewater system, and your source waters upstream.