Skip to content
Get in touchFR
Updated in November 2026
Explained

How much water does a ChatGPT query use?

AI's electricity use is routinely quantified; its water use almost never is. A ChatGPT query evaporates only a few drops of water, and this article sets out the published figures for ChatGPT and Gemini, what each one counts and why the location of the data centre matters so much.

Guillaume Pakula
By Guillaume Pakula, co-founder of Celsius. Since 2020, he has helped 80+ organisations with their Bilan Carbone® and climate strategy.
June 2026
Updated November 2026 · 6 min
An AI query evaporates a few drops of water, not the "half a litre" often quoted: Google measured 0.26 mL for a Gemini query and Sam Altman cites ~0.3 mL for ChatGPT. Both figures count only cooling; Mistral's life cycle assessment (LCA), which covers the full life cycle, reaches 45 mL per response. The issue becomes serious at the scale of the infrastructure: worldwide data centre water consumption is projected to double by 2030, according to the International Energy Agency (IEA).
Key takeaways
  • 1A query uses a few drops of water: 0.26 mL measured for Gemini, ~0.3 mL cited for ChatGPT.
  • 2Published figures range from 0.26 to 519 mL because they do not count the same water.
  • 3"Half a litre per query" is a misleading shortcut, taken from studies that counted total water or whole sessions.
  • 4Location decides: the same query matters little in Sweden but a great deal in Arizona, where water is already scarce.

Searching Google for "ChatGPT water usage" quickly turns up a striking claim: each AI query supposedly "drinks" a bottle of water. The published figures are far lower. Servers are cooled with water, and the only 2 figures that AI providers have put forward for a single query come to a few drops: 0.26 mL measured by Google for Gemini and ~0.3 mL cited by Sam Altman for ChatGPT.

AI water use

How much water does an AI query use?

Choose a number of queries, from 1 to several billion: the water evaporated is shown on the matching object.

Number of queries, on a logarithmic scale: each tick multiplies by 1,000.

A single question put to an AI

0.26 mL of water, equivalent to 5 drops of water.

For ChatGPT, Sam Altman cites ~0.3 mL: the same order of magnitude, with no published methodology.

Sources: Google, arXiv 2508.15734; Sam Altman, blog, June 2025; Google, environmental report 2026; Celsius analysis.

These volumes cover only the cooling water evaporated on site; they exclude the water used to generate the servers' electricity and the manufacture of the hardware. Volume does not tell the whole story: the same query has a small footprint in Sweden and a large one in Arizona, where data centres draw on water basins that are already under strain.

This leaves open where the "half a litre" figure comes from, why published figures range from 0.26 to 519 mL, and at what scale AI's water use becomes a real issue. On the energy side, a query uses around 0.3 Wh; this article is about water, which is quantified far less often.

1How much water does a ChatGPT or Gemini query use?

Only one figure comes from a measurement in production: Google puts a median Gemini query (in French) at 0.26 mL of water, about 5 drops, in its August 2025 study. For ChatGPT there is no measurement: in a June 2025 blog post, Sam Altman cited ~0.3 mL for an average query, with no stated method or scope. The 2 figures converge. Google's counts only the data centre's cooling water, not the water used to generate its electricity; Altman's does not say what it counts.

  • A Gemini query: 0.26 mL, or 5 drops of water. This is the only figure that has been measured and published, by Google, and it leaves out the water tied to electricity.
  • A ChatGPT query: ~0.3 mL according to Sam Altman, one fifteenth of a teaspoon, taken from a statement on his blog rather than an audited measurement.
  • A teaspoon (5 mL): about twenty queries.
  • A glass of water (25 cl): around 1,000 queries.

This figure varies widely with the model and the task, as energy use does: the gap between models reaches a factor of 100. The "half a litre per query" that circulates is a genuine figure, but misquoted: a 2023 study counted 500 mL for 10 to 50 responses from GPT-3 (UC Riverside), not for a single one.

The same team then estimated ~519 mL for a 100-word email generated by GPT-4, a figure that counts total water, electricity included (Washington Post). Like the "10x" claim in the comparison with a Google search, the "half a litre" keeps circulating without the scope that gave it meaning.

AFP infographic: a data centre relies on a cooling system (air conditioning or cold water injection); 40% of its energy goes to preventing the servers from overheating
Reference diagram - AFP
40% of a data centre's energy goes to cooling the servers
AFP sources: McKinsey, J.P. Morgan, IEA, Dorsalys

A data centre depends on two flows: the electricity that powers the servers, and the water that removes their heat by evaporation. No "water per query" figure can be read without its scope.

2Why AI uses water, and when it becomes a problem

A few drops per query are not a problem in themselves. The difficulty lies in the cooling mechanism, through which water is lost to evaporation, and above all in where your queries are processed.

Server room in a data centre, with air-conditioned aisles
Closed loops, adiabatic cooling, immersion: how data centres are trying to reduce their dependence on water. Report in French by La Croix.

Data centres use water to cool their servers

What matters is the difference between water withdrawn and water consumed. A data centre withdraws water, returns part of it to the environment and evaporates the rest: Google states that 80% of the water withdrawn by its sites is consumed, and therefore lost to the local basin. There is also a hidden water cost: the water used to generate the electricity that powers the servers. In some countries this indirect water use outweighs cooling, and it is precisely this water that Google's 0.26 mL leaves out.

Everything depends on where your queries are processed

Location decides almost everything. A data centre in Sweden is cooled with cold air for much of the year, whereas a site in Arizona or the Persian Gulf depends far more on evaporation, in regions that are already short of water. With the same model and the same query, the footprint differs completely from one site to another, and you do not choose which site handles yours. Location matters in the same way for carbon: electricity in Sweden emits about 10 times less CO2 per kWh than the average in the United States.

Geography

Water footprint of a query by data centre region

Tap a region to see its cooling method and the pressure on water.

Arizona, Texas, Virginia · Wet cooling towers

Documented local water stress. Growing public opposition.

Qualitative levels: the physical mechanism is known, precise figures by region are not published.

The local water basin and cooling matter more than the model. Users do not choose where their query is processed.

WUE (Water Usage Effectiveness) principle and data centre geography. No provider publishes a figure by region to date (checked June 2026).

3Which AI water figures can you trust, and how to read them

Only 3 AI providers have published a figure, and each counts something different. Google publishes a measurement made in production: 0.26 mL, cooling only. OpenAI relies on a statement by its chief executive in a blog post, with no method given. Mistral has published a full life cycle assessment (LCA) with Carbone 4 and ADEME (the French Agency for Ecological Transition): 45 mL per response of 400 tokens (tokens are the word fragments a model processes), server manufacturing included. Anthropic and Microsoft publish no figure per query. For Claude, our estimates for Fable 5.2 and Opus 5.5 start from the electricity and water indicators of its hosting providers.

Compare boundaries

5 orders of magnitude for water consumed by AI queries

None of these figures is wrong: they do not count the same things. Click to read the boundaries and sources.

What the figure counts: Cooling water evaporated on site, measured in production across Google's AI fleet. This is the most reliable figure on the market.

What it excludes: Water used to generate electricity and manufacture servers.

≈ 5 drops of water · Google study, August 2025 (arXiv 2508.15734)

Google, arXiv 2508.15734; S. Altman, blog, June 2025; UC Riverside, arXiv 2304.03271; Mistral AI × Carbone 4 × ADEME, July 2025; Washington Post × UC Riverside, September 2024.

Why published figures per query range from 0.26 to 519 mL

Set side by side, the published figures run from 0.26 to 519 mL, a factor of 2,000. None of them is wrong: the first counts the cooling water of a median query, the last the total water of a long output from GPT-4, the largest model in service at the time. In between, the standard academic estimate puts a GPT-3 response at 10 to 50 mL of total water, and the Mistral LCA puts a response from Le Chat, Mistral's chatbot, at 45 mL. So before quoting a water figure, you need to know what it counts.

Mistral AI infographic: 1.14 gCO2e, 0.05 L of water and 0.2 mg antimony equivalent for a 400-token page generated by Mistral Large 2
Mistral Large 2 LCA (Mistral AI × Carbone 4 × ADEME, July 2025). A response of 400 tokens: 1.14 gCO2e and 45 mL of water, full life cycle, server manufacturing included. See the Mistral Large 2 LCA.

3 checks before quoting an AI water figure

  • Check the scope: cooling only, electricity included or full life cycle. The gap between these scopes ranges from a factor of 10 to a factor of 100.
  • Be wary of fleet averages: an average indicator pools sites in Finland and Arizona, and so describes no real site.
  • Distinguish water withdrawn from water consumed: Amazon Web Services (AWS) publishes 0.12 L/kWh of water withdrawn in 2025 (0.15 in 2024) and Google 1.15 L/kWh of water consumed (in French), so the 2 indicators cannot be compared like for like.

In practice, this means reasoning in orders of magnitude rather than in measurements. For an organisation, water is not handled in a Bilan Carbone® (the French carbon accounting method), which looks only at carbon, but in a multi-criteria LCA, with the range and the uncertainty stated openly. On the carbon side, AI use fits into Scope 3 of your carbon footprint.

Published figures for AI's water use vary by a factor of 2,000 without any of them being wrong, because they do not count the same water.

4How much water does AI use per day and per year, at scale?

As an order of magnitude for a company, take 100 people who send 25 queries a day over 220 working days: that adds up to 550,000 queries a year. At 0.26 mL per query, this comes to 143 litres of water over the year, the equivalent of a bathtub, or 1.4 litres per person. Even at the widest LCA scope (45 mL), the total reaches ~25 m³: real, but marginal in the footprint of a services company, where equipment far outweighs online services.

The change of scale comes from the infrastructure. In 2021, an average Google data centre evaporated around 1.7 million litres a day, two thirds of an Olympic pool. In 2025, Google consumed 41 billion litres of water across its data centres and offices, 34% more than in 2024 and more than double the 2021 level. Worldwide, the International Energy Agency (IEA) puts water consumption linked to data centres at ~560 billion litres in 2023: 2 thirds to produce the energy they use, a quarter to cool them on site and the rest to manufacture chips. It projects 1,200 billion litres in 2030, 2.1 times as much within 7 years. The IEA attributes this increase to the rise of AI, which accounts for 5 to 15% of data centre electricity today and could account for 35 to 50% in 2030. The report from United Nations University (UNU-INWEH, the United Nations University Institute for Water, Environment and Health, June 2026) gives much higher volumes: 4,500 billion litres as early as 2025, enough to meet the water needs of more than 600 million people in sub-Saharan Africa, and 9,300 billion litres in 2030, equal to the annual needs of the region's 1.3 billion inhabitants. For 2030, the UN projection is nearly 8 times the IEA's, a sign of how uncertain these volumes are.

Le Parisien map of planned future data centre sites in France, by region and by size in hectares
Geography - Élysée (French presidency), February 2025
Where the next French queries will land
Le Parisien map

Around thirty sites announced by 2030, concentrated along the Île-de-France to Hauts-de-France axis (close to the transatlantic cables and to the Marseille interconnection hub), with a second belt in Grand Est, Auvergne-Rhône-Alpes and the Marseille region. The choice depends less on available water than on the connection to the grid operated by RTE (France's electricity transmission operator) and on industrial land. The useful question to put to an AI provider is therefore no longer "how much water per query?" but "where do your data centres run, and how are they cooled?". The local basin determines the real water pressure, not the global average.

Volumes of this size matter little in Scandinavia and a great deal in Arizona or Texas, where conflicts over water use are documented. The French think tank The Shift Project (October 2025) points to competing uses of water around the sites and recommends setting a ceiling trajectory for data centre electricity, listing the sites and their consumption and bringing the sector into France's national low-carbon strategy.

Operators respond in 2 ways. Air cooling (dry cooling) exchanges heat directly with the atmosphere, with no evaporation. It can be used anywhere, at the cost of lower thermal efficiency and higher electricity costs, and it is becoming viable as modern servers tolerate higher operating temperatures. Google says it chooses the cooling method site by site, according to the water and carbon-free electricity available locally. Immersion cooling submerges the servers in a dielectric fluid.

At Projet Celsius, we therefore think the useful question to put to an AI provider concerns its sites rather than water per query: "where do your data centres run, and how are they cooled?"

5Key takeaways

  • A query uses a few drops of water: 0.26 mL measured by Google for Gemini and ~0.3 mL cited by Sam Altman for ChatGPT, with no published scope. Google's figure counts only cooling.
  • The "half a litre per query" figure is a misleading shortcut: the 500 mL was for 10 to 50 GPT-3 responses, and the ~519 mL for a GPT-4 email counts total water.
  • From 0.26 mL (cooling) to 45 mL (Mistral's full LCA), each published figure is accurate within its own scope, and that scope must be checked before any comparison.
  • Geography decides: the same query has a small footprint in Sweden and a large one in Arizona, and the real issue is the concentration of data centres in basins that are already under strain.
  • For a company, the water used by digital services is assessed in a multi-criteria LCA, because the Bilan Carbone® counts only carbon.

Water completes the picture left by energy figures. This aspect is best read alongside the energy comparison of AI models and the carbon footprint of AI at organisation level, then carried into an LCA as soon as your analysis of digital services needs to be taken seriously.

Further resources

Frequently asked questions

or: guillaume@projetcelsius.com

More articles to read

View all →
French environmental cost label for clothing: what changed on 1 October 2026
Regulation

French environmental cost label for clothing: what changed on 1 October 2026

6 min read
What is the French textile eco-score?
Who displays it, and has it become mandatory?
Regulation

What is the French textile eco-score? Who displays it, and has it become mandatory?

12 min read
Removable batteries and battery passports: who is affected in 2027?
Regulation

Removable batteries and battery passports: who is affected in 2027?

14 min read

A senior consultant reads every message

Tell us where you stand and what is pressing, and we will reply within 24 working hours with a first view on how to proceed.

Write to a consultant →
Our toolkit

A full range of free assessment tools

Cost estimator, obligation and eligibility checkers, footprint calculator.

Estimate costs and impacts
Ref. 2026·BC·0184REPORT · FINANCIAL YEAR 2026Bilan Carbone®complete 1·2·3Presentation to the Executive Committee · 2027 action planCONTENTS01Executive summaryp. 402Scope and methodologyp. 1203Emissions by scopep. 24042027 action planp. 5605Methodological appendicesp. 78VOLUME84 pages · ConfidentialSTANDARDISO 14064 · GHG ProtocolQUOTATION · BC.2026.0184Issued 05·05·2026 · Valid for 30 daysCelsius consultancy · Paris 3rd arrondissementINDICATIVE COST ESTIMATEYour companyMid-sized company · 180 employees · CSRD 2027SERVICEBilan Carbone®Scope 1·2·3 · 13 weeksBPIFRANCE FUNDING · - 60%INDICATIVE RANGE EXCL. VAT€16,800to €22,400PROJECT DETAILS01 · SCOPING3 weeks~€4,20002 · MODELLING8 weeks~€9,80003 · PRESENTATION2 weeks~€4,800Indicative estimate · Refined after scopingSIRET 891 234 567 00012

Bilan Carbone® cost estimator

Your price range in 1 minute, based on 2026 market rates and public funding.

1 minStart
Estimate costs and impacts
AI FOOTPRINT · MONTHLY USEYOUR TOTAL FOOTPRINT4.2 kgCO₂eq for 1,000 typical prompts · May 2026MODEL COMPARISON · 1,000 TYPICAL PROMPTSGPT-4oOpenAI6.8 kgClaude OpusAnthropic2.1 kgGemini ProGoogle4.5 kgMistral LargeMistral AI · FR1.6 kg

AI carbon footprint calculator

The climate impact of your AI queries, by model and task. Ecologits methodology.

3 minStart
Check an obligation
DIAGDÉCARBON'ACTIONACCELERATE THETRANSFORMATIONOF YOUR COMPANYIN ENERGY ANDTHE ENVIRONMENTOFFICIAL SCHEME · BPIFRANCE × ADEMECHECKER · ELIGIBILITYELIGIBLEYou meet the 3 Diag Décarbon'Action criteria.YOUR FUNDING€10,000 excl. VAT€6,000excl. VATAmount payable by you after the Bpifrance subsidyFUNDING BREAKDOWNBPIFRANCE 40%YOU 60%€4,000€6,000SCHEME SUBSIDISED BY

Diag Décarbon'Action eligibility

Check in 30 seconds whether your business is eligible for Bpifrance funding covering 40% of a Bilan Carbone® assessment.

30 secStart
Check an obligation
FRENCH REPUBLICMinistry for the Ecological TransitionLEGAL REQUIREMENTGreenhouse GasEmissions AssessmentArticle L. 229-25 of the French Environmental CodeDecree 2022-982 · published 1 July 2022FREQUENCY · 4 YEARSFILING · ADEMECHECKER · BEGES REQUIREMENTREQUIRED720 employees · BEGES requirementPOTENTIAL PENALTY€50,000maximum fine for failing to complete itart. L. 229-25OFFICIAL REFERENCE

BEGES checker

Does the BEGES requirement apply to you? An immediate answer, with the deadline and penalty.

30 secStart
Check an obligation
9:42SCANSCANNING DPP...DPP IDENTIFIEDOrganic cotton T-shirtSKU TX-CB-220 · Batch L-26-04781ESPR COMPLIANT42 DATA POINTS · 5 SECTIONSORIGINIndia · GOTSOrganic cottonFOOTPRINT5.2 kg CO₂eqLCA ISO 14040RECYCLABILITY85%Cotton recycling schemeREPAIRABILITY7.5 / 10Accessible partsEND OF LIFETextile recycling scheme (TLC) · Bordeaux/FRRefashion-approved recovery operatorEU · ESPR 2024/178112.05.2026

DPP checker

Is your product covered by the Digital Product Passport?

1 minStart
Check an obligation
COSTENVIRONMENTAL386POINTS257PER 100 GOfficial methodEcobalyse, v7.0.0CHECKER · ENVIRONMENTAL LABELLINGELIGIBLETextiles · voluntary labellingENVIRONMENTAL COST386 ptsT-shirt 150 g · 257 pts per 100 gExample: Ministry for the Ecological Transition FAQ

Textile environmental labelling 2026

Voluntary labelling, but third parties can publish it from October 2026: where do you stand?

1 minStart