“Every ChatGPT conversation drinks a bottle of water.”
It is the single most famous statistic in the debate over AI’s environmental cost. The image is vivid, portable, and almost perfectly designed to go viral. It has shaped public and political conversation about AI infrastructure more than any other single number.
The concern behind it is legitimate. Data centers are being built at extraordinary speed, some of them in water-stressed regions, and much of the installed base was designed in an era when water efficiency was not a primary design constraint; communities have in several documented cases had genuine cause for grievance. But the public debate is now running on figures that range from outdated to wrong, and wrong on many levels. Some of the loudest claims overstate the problem by orders of magnitude. Others, including several the industry itself repeats, understate it.
Getting the numbers right matters most to the communities that host these facilities, because bad numbers produce bad siting decisions, misdirected scrutiny, and misplaced trust. Here are ten myths about AI and water, with the sources for each, concluded with honest caveats on where the corrections apply and where they do not.
Download the full paper by clicking below, or read on for a summary of the document.
Myth 1: “Every ChatGPT conversation drinks a bottle of water”
The claim traces to a single academic paper: Making AI Less “Thirsty” by Pengfei Li, Jianyi Yang, Mohammad A. Islam, and Shaolei Ren of UC Riverside, first posted in 2023 and later published in Communications of the ACM. Their figure was a calculated estimate built from public data, not a meter reading from inside a data center. A 2024 Washington Post analysis ensured the figure went viral.
Two things happened next that the viral version never caught up with. First, Ren himself has since indicated the GPT-4 estimate was likely far too high and that the real figure is closer to 15ml per prompt in total, of which around 5ml is on-site cooling water. Second, in August 2025 Google published the first large-scale measurement from a production environment, finding the median Gemini text prompt consumed 0.26ml of on-site water, or about five drops.
Credible per-prompt estimates still span more than a thousandfold depending on model, location, season, and, above all, what you choose to count. The honest answer to “how much water does a query use?” is a range, and the range is wide because disclosure is inconsistent.
Myth 2: “All data centers cool with water”
The differences between cooling technologies and their associated water consumption figures are not marginal. Google’s own facility-level disclosures for 2024, a useful example of the transparency this debate needs more of, show one Texas data center consuming about 10,000 gallons in a year, roughly two months of a single household’s use, while its largest water consumer, in Iowa, used around a billion gallons. Same company, same year, a difference of five orders of magnitude, determined almost entirely by cooling architecture and climate.
Although modern data center cooling designs often do not involve the evaporation of water, they are not representative of the whole installed base. Data centers have been around for decades, and the installed base is huge. In many countries, evaporative cooling remains widespread across the existing global fleet. When someone says, “data centers don’t really use water” or “data centers devour water,” the right response is to ask: which data centers? Built when and where? Cooled how? Both statements are true of some facilities and false of others.
Myth 3: “Water used by a data center is gone forever”
The single most conflated distinction in this debate is between withdrawal, meaning water taken from a source, discharge, meaning water used and then returned to a waterway or treatment facility, and consumption, meaning water lost to evaporation. The source of the withdrawal is also important to note. A facility that withdraws river water, runs it through heat exchangers, and returns it at a slightly higher temperature has a very different impact from one that draws from aquifers and evaporates the same volume into the sky. Many press accounts of data center water use quote withdrawal figures as if they were consumption, or vice versa, without noticing the difference.
The lesson is not that withdrawal does not count. It is that a report which does not tell you which figure it is quoting has not told you the full story.
Myth 4: “AI’s water footprint is mostly at the data center”
Here is a myth that cuts against the industry, and it deserves far more attention than it gets. The 2024 US Data Center Energy Usage Report from Lawrence Berkeley National Laboratory estimated that American data centers consumed about 17 billion gallons of water directly through cooling in 2023, and roughly 211 billion gallons indirectly, through the water consumed generating their electricity.
This means a data center that consumes zero water on-site, while drawing power from a water-hungry grid, may have simply moved its water demand upstream and out of sight.
The power generation figure comes with a multitude of caveats and is genuinely uncertain. However, for most facilities, electricity is where the majority of the water use is. Any assessment that stops at the facility fence is measuring the smaller number.
Myth 5: “Any water use is bad water use”
If Myth 4 establishes that electricity has a hidden water cost, this is its corollary: sometimes using water on-site is the environmentally responsible choice. Evaporative cooling exists because it is significantly more energy-efficient than mechanical alternatives in many climates.
Given the water-intensive and carbon-intensive nature of some forms of power generation, in a genuinely water-abundant region a facility that evaporates water on-site but burns meaningfully less electricity can have a lower total water and carbon footprint than a “water-free” neighbor pulling harder on the grid.
This argument applies only where water abundance is real and verified against local hydrology, meaning river flows, aquifer recharge, seasonal drought risk, and, of course, the effects of a changing climate on the watershed.
Myth 6: “Data centers are uniquely enormous water users”
In most countries, at the level of national accounting, data centers barely register. For the US, data centers’ direct annual consumption works out to about 0.3% of the US public water supply. For comparison, golf uses approximately thirty times more water than every American data center combined. Agriculture dwarfs both: the UN’s World Water Development Report puts farming at roughly 70% of global freshwater withdrawals.
However, national figures obscure local impact. Water is consumed from local watersheds, not from a national reservoir. A single facility drawing millions of gallons a day, arriving suddenly in one small municipality, can matter more locally than a thousand diffuse legacy uses spread across a continent. This is precisely why the concern exists despite the aggregate numbers. Data centers attract scrutiny not because they are large water users nationally but because they are new, concentrated, and visible, and those are rational things for a community to scrutinize.
Myth 7: “More compute always means more water”
The assumption that more AI means more heat, which in turn means more evaporation, runs into an engineering reality: extreme rack densities are exactly what evaporative systems were not designed for. The newest generation of AI facilities are increasingly built around closed-loop, direct-to-chip, and immersion cooling, precisely because the thermal loads demand it.
The important caveat: intensity is not volume. Efficiency per prompt can fall while total consumption rises if growth outruns the gains, the classic Jevons dynamic, and the projections say exactly that. LBNL expects US direct consumption to grow two-to-four-fold by 2028, even as new builds get more efficient. The fleet is expanding faster than it is improving. The myth worth busting is the automatic link between compute growth and water growth, not the possibility that sector totals rise. On current evidence, they will.
Myth 8: “Data centers take drinking water from communities”
Stated as a general rule about the industry, this is false; the majority of facilities operate without measurable effect on municipal supply. But this myth demands the most careful handling in the list, because in specific, documented cases community concerns have been well founded, and acknowledging that plainly is essential to the credibility of everything else in this piece.
The industry’s response has been substantive: new builds increasingly arrive with closed-loop designs, reclaimed-water agreements, and materially stronger disclosure commitments attached to their permits, and the largest operators have led much of that shift in design standards.
The word “increasingly” in the last paragraph is doing honest work, but it is a trend claim, not a guarantee, and it is exactly the kind of claim that should be verified permit by permit and site by site rather than taken on assurance.
Myth 9: “Water use is just the cost of progress, and nothing can be done”
Almost everything can be done, and much of it is already commercial rather than experimental. Closed-loop and chip-level cooling eliminate evaporative consumption for new builds. Reclaimed and non-potable water can replace drinking water at facilities that do use some form of evaporative cooling. Warmer coolant temperatures, enabled by the tolerances of modern chip families such as NVIDIA’s Rubin generation, recover the energy penalty of choosing dry cooling over wet. Water usage effectiveness (WUE) gives regulators and communities a metric to write into permits. And the three largest hyperscalers, Microsoft, Google, and Amazon, have all committed to being “water positive” by 2030, replenishing more than they consume.
One caveat has already been mentioned: global figures should not eclipse local impact. Replenishment commitments are global accounting, and restoring water to one basin does not refill the aquifer beside a specific facility.
Myth 10: “The numbers can be taken at face value”
Not yet, and this piece’s own sourcing shows why. Not every major operator publishes aggregate water figures. There is no mandatory water-disclosure requirement for data centers in the United States at federal level, and WUE reporting, where it exists, uses inconsistent boundaries that make operators difficult to compare.
Scrutiny of the numbers is therefore not cynicism; it is the rational posture until reporting is standardized, mandatory, and independently verifiable. That scrutiny should be applied symmetrically to the viral bottle-of-water figure as much as to the corporate five drops. Operators hold the meters, which is why leadership on disclosure sits naturally with them, and why the operators that proactively standardize ahead of legislative requirements will set the terms of trust.
The real questions to ask
The question that matters was never just “does AI use water?” The questions that matter are:
- What? Is the cooling methodology evaporative, air, or liquid?
- Which? Is the water potable or reclaimed, evaporated or returned / discharged?
- Where? An abundant watershed or a stressed one? What is the water intensity of the regional grid mix?
- How much?
- When? Including time of day, drought months or years, or just overall averages?
- Who checks? Anyone outside the company, or is data provided via report taken at face value?
On today’s evidence, AI data centers are a small national water user with a real and rising footprint, genuinely severe in a handful of badly sited legacy cases, and increasingly solvable by planning and engineering that already exist. What is not yet solved is the accounting. Standardized, facility-level, independently verifiable disclosure of withdrawals, discharge, and consumption, direct and indirect, would cost the industry relatively little and would do more to build trust with the communities hosting it than any single commitment. Until that exists, every number in this debate, including the reassuring ones, should be read as provisional: an estimate with a boundary, not a fact with an audit.
