{"id":39733,"date":"2025-09-03T00:23:07","date_gmt":"2025-09-03T00:23:07","guid":{"rendered":"https:\/\/www.europesays.com\/ie\/39733\/"},"modified":"2025-09-03T00:23:07","modified_gmt":"2025-09-03T00:23:07","slug":"how-much-water-do-your-ai-chats-consume-do-the-math-commentary","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ie\/39733\/","title":{"rendered":"How much water do your AI chats consume? Do the math (commentary)"},"content":{"rendered":"

Artificial intelligence systems are thirsty, consuming as much as 500 milliliters of water<\/a> \u2013 a single-serving water bottle<\/a> \u2013 for each short conversation<\/a> a user has with the GPT-3 version of OpenAI\u2019s ChatGPT system. They use roughly the same amount of water to draft a 100-word email<\/a> message.<\/p>\n

That figure includes the water used to cool the data center\u2019s servers<\/a> and the water consumed at the power plants generating the electricity to run them.<\/p>\n

But the study that calculated those estimates also pointed out that AI systems\u2019 water usage can vary widely, depending on where and when<\/a> the computer answering the query is running.<\/p>\n

To me, as an academic librarian and professor of education<\/a>, understanding AI is not just about knowing how to write prompts. It also involves understanding the infrastructure, the trade-offs, and the civic choices that surround AI<\/a>.<\/p>\n

Many people assume AI is inherently harmful<\/a>, especially given headlines calling out its vast energy and water footprint<\/a>. Those effects are real, but they\u2019re only part of the story.<\/p>\n

When people move from seeing AI as simply a resource drain to understanding its actual footprint, where the effects come from, how they vary, and what can be done to reduce them, they are far better equipped to make choices that balance innovation with sustainability.<\/p>\n

2 hidden streams<\/p>\n

Behind every AI query are two streams of water use<\/a>.<\/p>\n

The first is on-site cooling<\/a> of servers that generate enormous amounts of heat. This often uses evaporative cooling towers \u2014 giant misters that spray water over hot pipes or open basins. The evaporation carries away heat, but that water is removed from the local water supply, such as a river, a reservoir or an aquifer. Other cooling systems may use less water but more electricity<\/a>.<\/p>\n

The second stream is used by the power plants generating the electricity to power the data center<\/a>. Coal, gas and nuclear plants use large volumes of water for steam cycles and cooling<\/a>.<\/p>\n

Hydropower also uses up significant amounts of water, which evaporates from reservoirs<\/a>. Concentrated solar plants, which run more like traditional steam power stations, can be water-intensive<\/a> if they rely on wet cooling.<\/p>\n

By contrast, wind turbines and solar panels use almost no water<\/a> once built, aside from occasional cleaning.<\/p>\n

Climate and timing matter<\/p>\n

Water use shifts dramatically with location. A data center in cool, humid Ireland can often rely on outside air or chillers and run for months with minimal water use<\/a>. By contrast, a data center in Arizona in July may depend heavily on evaporative cooling<\/a>. Hot, dry air makes that method highly effective, but it also consumes large volumes of water, since evaporation is the mechanism that removes heat.<\/p>\n

Timing matters too. A University of Massachusetts Amherst study found that a data center might use only half as much water in winter as in summer<\/a>. And at midday during a heat wave, cooling systems work overtime. At night, demand is lower.<\/p>\n

Newer approaches offer promising alternatives. For instance, immersion cooling<\/a> submerges servers in fluids that don\u2019t conduct electricity, such as synthetic oils, reducing water evaporation almost entirely.<\/p>\n

And a new design from Microsoft claims to use zero water for cooling<\/a>, by circulating a special liquid through sealed pipes directly across computer chips. The liquid absorbs heat and then releases it through a closed-loop system without needing any evaporation. The data centers would still use some potable water for restrooms and other staff facilities, but cooling itself would no longer draw from local water supplies.<\/p>\n

These solutions are not yet mainstream, however, mainly because of cost, maintenance complexity and the difficulty of converting existing data centers to new systems. Most operators rely on evaporative systems.<\/p>\n

A simple skill you can use<\/p>\n

The type of AI model being queried matters, too. That\u2019s because of the different levels of complexity and the hardware and amount of processor power<\/a> they require. Some models may use far more resources than others. For example, one study found that certain models can consume over 70 times more energy and water<\/a> than ultra\u2011efficient ones.<\/p>\n

You can estimate AI\u2019s water footprint yourself in just three steps, with no advanced math required.<\/p>\n

Step 1<\/b> \u2013 Look for credible research or official disclosures. Independent analyses estimate that a medium-length GPT-5 response, which is about 150 to 200 words of output, or roughly 200 to 300 tokens, uses about 19.3 watt-hours<\/a>. A response of similar length from GPT-4o uses about 1.75 watt-hours<\/a>.<\/p>\n

Step 2<\/b> \u2013 Use a practical estimate for the amount of water per unit of electricity, combining the usage for cooling and for power.<\/p>\n

Independent researchers<\/a> and industry<\/a> reports<\/a> suggest that a reasonable range today is about 1.3 to 2.0 milliliters per watt-hour. The lower end reflects efficient facilities that use modern cooling and cleaner grids. The higher end represents more typical sites.<\/p>\n

Step 3<\/b> \u2013 Now it\u2019s time to put the pieces together. Take the energy number you found in Step 1 and multiply it by the water factor from Step 2. That gives you the water footprint of a single AI response.<\/p>\n

Here\u2019s the one-line formula you\u2019ll need:<\/p>\n

Energy per prompt (watt-hours) \u00d7 Water factor (milliliters per watt-hour) = Water per prompt (in milliliters)<\/p>\n

For a medium-length query to GPT-5, that calculation should use the figures of 19.3 watt-hours and 2 milliliters per watt-hour. 19.3 x 2 = 39 milliliters of water per response.<\/p>\n

For a medium-length query to GPT-4o, the calculation is 1.75 watt-hours x 2 milliliters per watt-hour = 3.5 milliliters of water per response.<\/p>\n

If you assume the data centers are more efficient, and use 1.3 milliliters per watt-hour, the numbers drop: about 25 milliliters for GPT-5 and 2.3 milliliters for GPT-4o.<\/p>\n

A recent Google technical report said a median text prompt to its Gemini system uses just 0.24 watt-hours of electricity and about 0.26 milliliters of water<\/a> \u2013 roughly the volume of five drops. However, the report does not say how long that prompt is, so it can\u2019t be compared directly with GPT water usage.<\/p>\n

Those different estimates \u2013 ranging from 0.26 milliliters to 39 milliliters \u2013 demonstrate how much the effects of efficiency, AI model and power-generation infrastructure all matter.<\/p>\n

Comparisons can add context<\/p>\n

To truly understand how much water these queries use, it can be helpful to compare them to other familiar water uses.<\/p>\n

When multiplied by millions, AI queries\u2019 water use adds up. OpenAI reports about 2.5 billion prompts per day<\/a>. That figure includes queries to its GPT-4o, GPT-4 Turbo, GPT-3.5 and GPT-5 systems, with no public breakdown of how many queries are issued to each particular model.<\/p>\n

Using independent estimates and Google\u2019s official reporting gives a sense of the possible range:<\/p>\n