How much energy and water does artificial intelligence use: verified figures

How much energy and water does artificial intelligence use: verified figures

In short: A text query to an AI assistant can use anywhere from 0.24 Wh, the median Google measured for Gemini, to more than 29 Wh in the most power-hungry models of an academic study. The gap comes from what gets counted, which model is measured and what task is asked. Data centers worldwide used about 415 TWh in 2024, 1.5% of global electricity, and the International Energy Agency projects about 945 TWh in 2030. For water, figures range from 0.26 ml to 45 ml per query depending on the scope of the measurement.
Contents of this guide
  1. The key numbers at a glance
  2. Why the numbers differ
  3. Data center electricity
  4. What one query uses
  5. How much water: the three taps
  6. Model size and life cycle
  7. A concentrated problem
  8. What reduces the impact
  9. What is still unknown
  10. How to read a headline
  11. Myths and reality
  12. Frequently asked questions
  13. Sources

The key numbers at a glance

The table gathers the figures repeated most often, each with its source and year. A figure without those two details says nothing, because AI efficiency changes fast and each institution measures a different scope. The rest of the guide explains where each row comes from and why they cannot all be compared with each other.

MeasureFigureSource and year
Electricity used by all data centers worldwideAbout 415 TWh in 2024, 1.5% of global electricityIEA, Energy and AI, 2025
Projection for 2030 (base case)About 945 TWh, just under 3% of global electricityIEA, Energy and AI, 2025
US data centers176 TWh in 2023, about 4.4% of the country’s electricityLawrence Berkeley, via DOE, 2024
Median text query in Gemini0.24 Wh, 0.03 g of CO₂e and 0.26 ml of waterGoogle, 2025
400-token answer in Le Chat1.14 g of CO₂e and 45 ml of water, life-cycle basisMistral AI, 2025
Most intensive vs most efficient model, long queryOver 29 Wh, more than 65 times the most efficient figureJegham et al., 2025
Water withdrawn by AI worldwideBetween 4.2 and 6.6 billion m³ in 2027 (projection)Li et al., 2023
Where to start: read the row that matters most and jump to its section to see what it includes and leaves out.

Why the numbers on AI do not match

The numbers differ because each source counts different things: which equipment is included, which model and type of task is tested, and whether water is measured as withdrawn or consumed. Two figures can both be correct and still not be comparable with each other.

Google shows this with its own case. In the narrow approach, which measures only the AI accelerator in a highly utilized test on the most efficient data centers, the median Gemini query comes out at 0.10 Wh. In the full approach, it rises to 0.24 Wh. The difference lies in what gets added, according to Google’s technical paper.

Component of the median Gemini query (May 2025)Energy
Active AI accelerator0.14 Wh
Server processor and memory0.06 Wh
Idle machines, ready for demand spikes0.02 Wh
Data center overhead (cooling and power distribution)0.02 Wh
Total, full approach0.24 Wh

With the narrow rule, the same service would give 10,000 queries per kWh. With the full one, 4,167. Google leaves out external internet networking because it does not control it, and estimates that the data center’s internal networking weighs little in a text query. It also uses the median instead of the average, because a few very long queries or ones served by under-used models distort the average.

Before comparing two figures, four things need to be fixed:

  • What the measurement includes: the chip only, the whole server, the data center, or also the manufacturing of the equipment.
  • Which model and task: a short answer is not the same as a long text, and a reasoning model is not the same as a light one.
  • Who measures: the provider itself, a lab, or an academic study estimating from outside.
  • Which water is counted: the water withdrawn from a source or the water consumed.
Where to start: when two figures clash, check what equipment each one includes and which model it measures before deciding which one is right.

How much electricity data centers use

According to the International Energy Agency (IEA), data centers worldwide used about 415 TWh in 2024, 1.5% of global electricity, and would reach about 945 TWh in 2030, just under 3%. That amount is slightly more than Japan’s entire electricity consumption today.

These figures cover all data centers, not only AI ones. Consumption grows about 15% a year between 2024 and 2030, more than four times the pace of electricity use in all other sectors. Even so, the IEA clarifies that data center growth explains less than 10% of the rise in global electricity demand over that period, and that a 3% share remains limited in the global picture.

AI weighs on that growth. Accelerated servers, driven mainly by AI, would grow 30% a year in the base case, versus 9% for conventional servers. Accelerated servers explain almost half of the net increase in data center consumption; conventional ones, about 20%; other IT equipment, about 10%, and cooling and support infrastructure, about 20%.

In the United States, Lawrence Berkeley National Laboratory estimated that consumption rose from 58 TWh in 2014 to 176 TWh in 2023, about 4.4% of the country’s electricity, and projects between 325 and 580 TWh in 2028. The Department of Energy summarizes that data center load tripled in a decade and could double or triple again by 2028.

IEA scenario for 2035What it assumesData center consumption
Base caseGrowth following server shipment projectionsAbout 945 TWh already in 2030
Lift-OffStronger AI adoption than in the base caseOver 1,700 TWh, about 4.4% of global demand, 45% above the base case
High EfficiencyMore progress in software, hardware and infrastructure efficiencyAbout 970 TWh, with savings of more than 15%
HeadwindsSlower AI adoption than expectedLevels off at about 700 TWh, under 2%
Key fact: the IEA projects that data center consumption will more than double between 2024 and 2030, to about 945 TWh, according to its release on AI and electricity.
Where to start: read the IEA figure together with its year and scope, and compare the scenarios before citing a single projection.

What one query to an AI assistant uses

It depends on who measures it. Google measured 0.24 Wh for the median Gemini text query, and an academic study comparing 30 models found that the most intensive ones exceed 29 Wh per long query, more than 65 times what the most efficient use. The gap mixes models, text lengths and measurement rules.

SourceWhat it measuresEnergyWaterCO₂e
Google, August 2025Median text query in Gemini Apps, full measurement in production0.24 Wh0.26 ml0.03 g
Mistral AI, July 2025400-token answer in Le Chat, life-cycle analysis, excluding user devicesNot detailed in the announcement45 ml1.14 g
Jegham et al., 2025Long query across 30 commercial models, estimated from outsideOver 29 Wh in the most intensive onesNot detailed in the abstractNot detailed in the abstract

The study by Jegham and colleagues does not measure inside data centers: it estimates from public performance data and company-specific environmental factors. It analyzes 30 models from OpenAI, Anthropic, Meta and DeepSeek with three query sizes. The table shows three OpenAI models and the extremes for the long query.

ModelShort query (100 input tokens, 300 output)Long query (10,000 input, 1,500 output)
GPT-4.1 nano0.207 Wh0.827 Wh
GPT-4.1 mini0.450 Wh2.122 Wh
GPT-4.10.871 Wh4.833 Wh
LLaMA-3.1-8B (most efficient on the long query)Not shown here0.443 Wh
DeepSeek-R1 (reasoning model)Not shown here29.075 Wh

Two lessons come out of that table. The first is that model size matters: within the LLaMA family, consumption rises from 0.443 Wh at 8 billion parameters to 25.202 Wh at 405 billion. The second is that reasoning models use much more, and DeepSeek-R1 consumes about 65 times what the most efficient model does.

Google adds that the energy of its median query fell 33 times and its total carbon footprint 44 times in 12 months, comparing May 2024 with May 2025. In that same paper, Google cites a June 2025 post by OpenAI’s chief executive, Sam Altman, that gave 0.34 Wh and about 0.3 ml of water for an average ChatGPT query. It is a statement on a blog, with no published methodology, so it cannot be checked against the others.

Key fact: a short 0.42 Wh query, multiplied by 700 million daily queries, equals the yearly electricity use of about 35,000 US homes, according to Jegham et al..
Where to start: treat the Google and Mistral figures as each provider’s own measurements, and the Jegham figure as an outside estimate.

How much water AI uses: the three taps

AI’s water comes from three taps: the water that cools the data center, the water used by the plants that generate its electricity, and the water spent manufacturing the servers. That is why per-query figures range from 0.26 ml at Google to 45 ml at Mistral, which also counts the life cycle. They measure different scopes.

Li and colleagues describe that split into three scopes: on-site water for cooling (scope 1), off-site water for electricity generation (scope 2) and supply-chain water for server manufacturing (scope 3). Someone who counts only the first tap gets a smaller figure than someone who adds all three.

Two concepts also need telling apart. Withdrawal is water taken from the ground or from a surface source. Consumption is withdrawal minus what is returned: what evaporates or stops being available. According to the same study, in cooling towers about 80% of what is withdrawn evaporates. Google, in its paper, explains that it considers consumption the best measure of its effect on local water, and that on average it consumes 80% of what it withdraws.

The amount that evaporates per kWh of server energy varies with the climate. Li and colleagues put it between 1 and 9 liters per kWh: 1 liter per kWh in Google’s annual average and 9 in a large commercial data center in Arizona during summer. For 2023 and 2024, Google reports 1.15 liters per kWh on its water usage indicator.

Water figureWhat it isSource
0.26 ml per median queryWater consumed in serving Gemini, excluding manufacturingGoogle, 2025
45 ml per 400-token answerWater consumed, on a life-cycle basisMistral AI, 2025
About 700,000 litersWater directly evaporated when training GPT-3 in Microsoft data centers in the USLi et al.
About 5.4 million litersTotal water consumed training GPT-3, adding scopes 1 and 2Li et al.
10 to 50 answers per 500 ml bottleWhat GPT-3 consumes in medium-length answers, depending on when and where it runsLi et al.
4.2 to 6.6 billion m³ in 2027Water withdrawn by global AI demand (projection), scopes 1 and 2Li et al.
0.38 to 0.60 billion m³ in 2027Part of that projection that would be consumed by evaporationLi et al.

The authors compare the withdrawal projection with the water that 4 to 6 Denmarks or half the United Kingdom withdraw in a year. It is a comparison of withdrawal and not of consumption, and it should be read that way. Its source is a 2023 study updated in 2025, and the 2027 projections depend on assumptions about AI electricity use.

Where to start: check which water scope the figure refers to, whether it is withdrawn or consumed, and whether it covers one query, one training run or a full year.

Model size and life cycle

Mistral calculated the life cycle of its Mistral Large 2 model up to January 2025, after 18 months of use: 20.4 kt of CO₂e and 281,000 m³ of water consumed. It also found that impact grows almost in proportion to size: a model ten times larger produces an impact one order of magnitude higher for the same amount of text.

The company ran the analysis with the consultancy Carbone 4 and the French ecological transition agency ADEME, and Resilio and Hubblo reviewed it. Mistral presents it as the first complete life-cycle analysis of an AI model. It measures three categories: greenhouse gas emissions, water use and resource depletion, and the last one gives 660 kg of antimony equivalent for Large 2.

With those results, the company proposes three indicators to inform the public: the absolute impact of training a model, the marginal impact of each answer, and the ratio between the total impact of answers and that of the whole life cycle. The first two, it says, could be mandatory reporting. The third shows whether the cost of training is spread across many answers or wasted.

The Jegham study points the same way: within one family, consumption soars with the number of parameters. Hence the practical value of choosing the right model for each use, instead of the largest by default.

Where to start: for simple tasks, try a smaller model first; impact rises with size.

A problem concentrated in a few places

The United States and China will account for nearly 80% of the growth in data center consumption through 2030, according to the IEA: about 240 TWh more in the United States, 130% above 2024, and about 175 TWh more in China, 170% more. The United States already had the highest consumption per person in 2024, about 540 kWh.

The IEA notes that, unlike electric vehicles, data centers tend to cluster in specific locations, which can make connecting them to the grid harder. A national or global average does not show the pressure felt by the grids and water sources in those areas. Southeast Asia is another example: its demand would more than double by 2030, partly because of the regional hub in Singapore and southern Malaysia.

The type of facility also counts. According to the IEA, cooling accounts for about 7% of total consumption in efficient hyperscale data centers and more than 30% in less efficient enterprise ones. Two facilities with the same servers can have different footprints because of how they are cooled.

Where to start: when reading a global percentage, look for the figure for the region where data centers are concentrated.

What reduces the impact

The sources consulted point to four measurable levers: choosing a smaller model, improving software and hardware efficiency, deciding where and when the load runs, and publishing comparable metrics. None is enough alone, and the IEA warns that demand growth can outpace the improvements.

  • The right model: according to Mistral, impact rises almost in proportion to model size, and in Jegham the LLaMA family goes from 0.443 Wh to 25.202 Wh between 8 and 405 billion parameters.
  • Efficiency: Google attributes its 33-fold cut in energy and 44-fold cut in carbon in a year to software improvements and clean energy procurement, according to the summary of its technical paper. In the IEA’s High Efficiency scenario, the same digital service is covered with more than 15% in savings.
  • Place and time: Li and colleagues show that water use varies in space and time, and that choosing when and where to train a large model can noticeably cut its water footprint.
  • Transparency: Mistral and Google publish their methodology and argue for more transparency in the sector, so models can be compared and purchase decisions can be informed.

The paradox that Jegham and colleagues point out limits the effect of efficiency: as AI gets cheaper and faster, mass adoption drives resource use disproportionately. The improvement per query can be offset if the number of queries grows faster.

Where to start: ask the AI provider for the methodology and scope of its figures, and choose the smallest model that does the job.

What is still unknown

There are four big gaps: no common standard exists to measure model impact, few companies publish their own measurements, outside estimates depend on assumptions, and the per-query figure changes almost every quarter. Any number in this guide should be read with its date.

  • No standard: Mistral acknowledges that its study is a first approximation because there are no public standards or impact factors for language models.
  • Own measurement: Google and Mistral measure their own systems. Google cites no outside audit of its figures, and two consultancies, Resilio and Hubblo, reviewed Mistral’s analysis.
  • Outside estimates: Jegham calculates from public performance data and company factors, not from measurements in the data center.
  • Projections: the IEA presents four scenarios for 2035 ranging from about 700 TWh to more than 1,700 TWh, and the range itself shows how much uncertainty there is.
  • Missing figures from other providers: this guide did not find a published measurement with methodology for ChatGPT, Claude or other assistants comparable to Google’s.
Where to start: always cite the year and provider of each figure, and reject those that do not say how they were measured.

How to read a headline about AI consumption

A headline about AI consumption reads well with five checks: what was measured, who measured it, which year it is from, which unit it uses and whether it refers to water withdrawn or consumed. If one is missing, the figure cannot yet be compared with another.

  1. Identify the scope: chip, server, data center or full life cycle.
  2. See who measures: the provider, a lab or an outside study.
  3. Check the date: Google reports a 33-fold improvement in one year, so a 2023 or 2024 figure may be outdated.
  4. Check the unit: Wh per query, TWh per year, ml per answer or m³ per year cannot be compared without converting them.
  5. Tell the water apart: withdrawn or consumed, and which scope.

A simple example: 0.24 Wh and 29 Wh do not contradict each other. One is the median text query in Gemini and the other is a long query on a reasoning model, estimated from outside.

Where to start: open the headline’s original source and look for the method table before repeating the figure.

Myths and reality

  • Myth: an AI query always uses the same amount. Reality: it ranges from 0.24 Wh to more than 29 Wh depending on the model, the length and how it is measured.
  • Myth: AI already uses a huge share of the world’s electricity. Reality: all data centers together were 1.5% in 2024 and the IEA projects just under 3% in 2030.
  • Myth: Google and Mistral give contradictory water figures. Reality: 0.26 ml and 45 ml correspond to different scopes, and the second includes the life cycle.
  • Myth: all the water used is lost. Reality: withdrawal and consumption are different, and in cooling towers about 80% of what is withdrawn evaporates.
  • Myth: efficiency has already solved the problem. Reality: Google cut the energy of its median query 33 times in a year, but the IEA projects data center consumption will double by 2030.
  • Myth: the impact is even across the planet. Reality: the United States and China account for nearly 80% of the growth through 2030, according to the IEA.
Frequently asked questions

How much energy does a ChatGPT or Gemini query use?

For Gemini, Google measured 0.24 Wh for the median text query. For ChatGPT, Google cites a statement by Sam Altman of 0.34 Wh per average query, with no published methodology. Outside studies give wider ranges, from under 1 Wh to more than 29 Wh depending on the model.

Is it true that AI uses a lot of water?

It depends on the scope. Google reports 0.26 ml per median query and Mistral 45 ml for a 400-token answer. Worldwide, Li and colleagues project between 4.2 and 6.6 billion cubic meters of water withdrawn in 2027, and between 0.38 and 0.60 billion consumed.

What share of the world’s electricity does AI use?

The sources consulted do not give an AI-only percentage. The IEA says all data centers used 1.5% of global electricity in 2024 and would be just under 3% in 2030, and that accelerated servers explain almost half of the increase.

Is it costlier to train a model or to use it?

The sources consulted do not allow a general ratio. Mistral measured the life cycle of Large 2 after 18 months of use and proposes reporting the impact of training and the impact of each answer separately, precisely because the ratio changes with the model and its use.

Do efficiency gains solve the problem?

They help a lot, but they are not enough on their own. Google achieved a 33-fold cut in the energy of its median query in a year, and even so the IEA projects data center consumption to more than double by 2030.

What can a company do to reduce its footprint when using AI?

It can choose the smallest model that does the job, since impact rises with size, and ask its provider for figures with a full methodology. Mistral proposes reporting the impact of training the model and of each answer.

Why do the figures change so much between one study and another?

Because they measure different scopes: some count only the chip and others the whole data center or the life cycle. The model, the query length and the year change too. Efficiency improves fast, and a figure from two years ago can be well out of date.

Related articles

Sources

Checked on November 5, 2026.

Radar answers

Ask about this article

Type your question and we will show you the answer inside this article or in other Radar Panamá publications.

Was this article useful?
By Daniela Bohórquez

Daniela Bohórquez is a writer at Radar Panamá. she writes about travel, tourism and business, with special attention to reviews of destinations, hotels and services. She lives between Panama, Italy and New York, which gives her a comparative view of how business is done in each market.