Wednesday, October 14, 2026News, analysis and data on AI infrastructure
Carbon Neutral Data Center

Your AI strategy has a carbon footprint. Here's how to measure and cut it.

The energy per AI query has fallen more than 30-fold in a year, and total AI emissions are still climbing. For CIOs and chief AI officers, the levers that matter most are model choice, workload design, and procurement.

The main aisle of racks in the Frontier exascale supercomputer at Oak Ridge National Laboratory
The Frontier supercomputer at Oak Ridge National Laboratory. Every AI query runs on hardware like this, and the energy it draws depends on how the query is designed. OLCF at ORNL / Flickr, CC BY 2.0

In August 2025, Google reported that the median text prompt to its Gemini apps used 0.24 watt-hours of electricity, about as much as running a television for nine seconds. Energy per prompt had fallen 33-fold in twelve months.

Then, in May 2026, Google said it was processing more than 3.2 quadrillion tokens a month, up from about 480 trillion a year earlier. Its 2026 environmental report showed electricity use up 37% and total emissions up 18%.

That is the situation every enterprise AI program now faces. Each unit of AI keeps getting cheaper in energy, while the number of units grows faster. For the executives setting AI strategy, a sustainability plan that looks only at the provider's efficiency will miss where the emissions actually come from: how many tokens your own workloads use.

How much energy does one query use?

Published estimates have converged for simple chat prompts, and diverge sharply for everything else.

EstimateWorkloadEnergy per queryNotes
Google (Aug 2025)Median Gemini text prompt0.24 WhIncludes idle capacity and cooling; market-based emissions of 0.03 gCO2e
Epoch AI (Feb 2025)Typical GPT-4o queryAbout 0.3 WhRises to about 2.5 Wh with 10,000 input tokens
OpenAI's Sam Altman (Jun 2025)Average ChatGPT query0.34 WhNo methodology published
Microsoft researchers in Joule (Aug 2026)Frontier models, median0.31 WhEarlier public estimates were 4 to 20 times too high
Microsoft researchers in Joule (Aug 2026)Reasoning, about 5,000 output tokens3.91 Wh13 times a standard query
Zeke Hausfather (Aug 2026)One agentic coding session150 to 1,200 WhOne heavy user's logs; central estimate about 600 Wh

The figures differ for three reasons, and anyone comparing them should know all three. Boundaries vary: some count only the active chips, others include idle servers and cooling. Emissions factors vary: Google's 0.03 grams is market-based, meaning it nets out clean energy purchases. MIT Technology Review noted it is about a third of what the local grid average would imply. And response lengths vary. Mistral's peer-reviewed lifecycle analysis of its Large 2 model, which includes training and hardware manufacturing, puts a 400-token response at 1.14 grams of CO2e, nearly 40 times Google's figure, largely because of these boundary choices.

The practical takeaway: a short chat prompt is a rounding error. A reasoning model, a long context window, or an agent is not.

Inference is now the footprint

Training a frontier model is a large, one-time cost. Serving it to millions of users is a continuous one. MIT Technology Review estimates that 80% to 90% of AI computing power now goes to inference. For an enterprise buyer this is good news, because inference is the part you control. You choose which model handles each task, how much context it sees, and how long it runs.

Reasoning and agents are the multipliers. Hugging Face's AI Energy Score found that turning on reasoning increased energy use about 30-fold on average, and 150 to 700 times for some models. It also found that 8 of 14 newer models used as much energy as their predecessors, or more. Newer models are not automatically more efficient, so procurement teams should test rather than assume.

Measuring it: where your AI emissions sit

For most enterprises, AI used through cloud APIs or software subscriptions falls under Scope 3, Category 1 (purchased goods and services). AI running on hardware you own or lease falls under Scope 2 for the electricity and Scope 3 for the equipment.

Three measurement approaches are in use, in order of accuracy:

  1. Provider-certified emissions. The best option, and mostly not yet available for AI services specifically.
  2. Token-based estimates. Multiply tokens from your API billing logs by published energy-per-token figures and a location-based grid factor for the region where the model runs. A June 2026 preprint by researcher Llopis puts the uncertainty at plus or minus 50%, which is adequate for decisions.
  3. Spend-based estimates. Generic emissions factors per dollar spent. The same preprint finds they overstate AI emissions 10 to 40 times. Use them only as a placeholder.

The cloud providers' carbon dashboards help, but with limits:

  • AWS: launched a Sustainability console in March 2026 with location-based data and Scope 3 hardware emissions.
  • Microsoft Azure: the Emissions Impact Dashboard allocates emissions by usage within each region, and its coverage of AI services such as Copilot is unclear.
  • Google Cloud: Carbon Footprint reports by project, product, and region, and is not third-party assured.
  • All three providers: allocate emissions by spend or usage rather than measuring them, lag by months, and do not show emissions per model or per token.
  • Direct model providers: third-party model APIs and AI features inside SaaS tools are generally not covered at all.

Standards are catching up. The Green Software Foundation ratified its Software Carbon Intensity specification for AI in December 2025, with separate scores for providers and consumers and functional units such as tokens and inferences. Under the EU AI Act, providers of general-purpose AI models must document known or estimated energy consumption from August 2025, with enforcement powers active since August 2026. That documentation goes to regulators, not to customers, so buyers should ask for it directly.

The levers, ranked by impact

LeverTypical reductionEvidence
Route tasks to the smallest capable model15 to 50 times for well-defined tasksUNESCO and UCL, 2025
Make reasoning opt-in, not default5 times or moreJoule, 2026
Use distilled models for high-volume tasks5 to 10 timesJoule, 2026
Batch requests and use modern serving softwareUp to 12.5 times per requestHugging Face
Keep serving software current15% to 41% per tokenML.ENERGY, 2026
Shorten outputsAbout 54% when output length is halvedUNESCO and UCL, 2025
Choose cleaner regionsUp to 13 times between best and worst cloud regionsLlopis, 2026
Shift flexible jobs in timeUp to 80% for short jobs with a six-hour windowDodge et al., 2022
Newer hardware2.8 to 3.4 times throughput per GPUJoule, 2026

Stacked together, the Joule authors estimate 8 to 20 times reductions are within reach. Two cautions apply. Quantization, running models at lower numerical precision, is often assumed to save energy, but Hugging Face researchers found it can increase energy use during text generation on some hardware, so measure before you rely on it. And prompt caching is priced at a fraction of fresh input on most APIs (Anthropic bills cache reads at 10% of the base input price), but its actual energy saving has not been independently measured.

A 90-day plan for AI strategy leaders

Month one: get a baseline.

  1. Pull token counts by application, model, and region from API billing logs and cloud usage exports.
  2. Build a token-based estimate using location-based grid factors, and record the uncertainty.
  3. Identify the five workloads that account for most tokens. They are usually agents, document processing pipelines, and anything with long context.

Month two: change the defaults.

  1. Set a routing policy: small or distilled models by default, frontier models by exception, reasoning only when the task requires it.
  2. Cap context and output length in production prompts, and cache shared context.
  3. Move batch and offline jobs to lower-carbon regions and hours where data residency allows.

Month three: put it in contracts.

  1. Add AI sustainability questions to every RFP: energy per token for the models you will use, location-based emissions for the serving region, hourly carbon-free energy share, and whether the provider reports under the Software Carbon Intensity for AI specification.
  2. Report AI emissions as a line in your Scope 3 inventory, with the method stated.
  3. Set an absolute budget, not just an intensity target. Efficiency gains that are absorbed by growth do not reduce emissions.

The strategic point

For most companies, AI emissions are still small compared with the rest of their footprint. The same preprint estimated a 200-person firm's AI use at under one tonne of CO2e a year. That will not last. Agentic workloads can use hundreds of times the energy of a chat prompt, and enterprises are scaling them now.

The companies that build measurement and routing discipline while the numbers are small will be ready for disclosure rules, will keep their inference bills in check, and will be able to back their climate claims with evidence. Good carbon practice here is also good cost control: every token you do not need is energy and money you do not spend.

Sources

Keep reading