Estimator methodology

Version 2026.06 · updated 2026-06-12. Every number below is versioned in the open and carries a citation — when a provider publishes a new disclosure, one row changes.

The estimation chain

energy (Wh)     = (tokens / 1000) × Wh-per-1k-tokens(model class) × PUE
emissions (gCO₂e) = energy (kWh) × grid intensity of region (gCO₂/kWh)

Results are always shown as a range: the honest uncertainty on per-token energy is ±3–5×, so a single number would be false precision. When you enter queries instead of tokens, we assume 500 output tokens per query (a typical chat answer).

1 · Energy per token

Anchored on 2025 provider disclosures — Google's median Gemini text prompt (0.24 Wh / 0.03 gCO₂e, including idle machines, CPU/RAM and datacenter overhead), Epoch AI's ~0.3 Wh per average ChatGPT query, and Mistral's LCA (~1.14 gCO₂e per 400-token answer). You pick a model class, not an exact model:

ClassExamplesWh / 1k output tokens
LightHaiku, GPT-4o-mini, Gemini Flash0.120.25
StandardGPT-4o, Sonnet, Gemini Pro0.40.8
Frontier / reasoningOpus, o-series, extended thinking1.56

Frontier/reasoning models include hidden thinking tokens. The often quoted “3 Wh per query” figure predates provider disclosures and measured much less efficient 2023-era serving — we treat it as obsolete.

2 · Grid intensity

Your cloud region maps to a physical grid. We use location-based annual intensities (Ember) — the physical reality of the grid the datacenter draws from. Providers usually advertise market-based figures (renewable PPAs and certificates), which can show “0 g” on a coal-heavy grid; we note them but do not use them. A live ENTSO-E layer for EU regions is on the roadmap via our agents service.

RegionGridgCO₂/kWhCloud regions
Europe (Stockholm)Sweden (hydro + nuclear)25AWS eu-north-1 · Azure Sweden Central
Canada (Montréal)Canada — Québec (hydro)30AWS ca-central-1 · GCP northamerica-northeast1
Europe (Paris)France (nuclear)55AWS eu-west-3 · Azure France Central
Europe (London)United Kingdom220AWS eu-west-2 · Azure UK South
Europe (Amsterdam)Netherlands270Azure West Europe · GCP europe-west4
US West (Oregon)United States — Oregon285AWS us-west-2 · GCP us-west1
Europe (Ireland)Ireland290AWS eu-west-1 · Azure North Europe
US Central (Iowa)United States — Iowa340GCP us-central1 · Azure Central US
Europe (Frankfurt)Germany350AWS eu-central-1 · GCP europe-west3
US East (N. Virginia)United States — Virginia370AWS us-east-1 · Azure East US · GCP us-east4
Asia (Tokyo)Japan450AWS ap-northeast-1 · Azure Japan East
Asia (Singapore)Singapore470AWS ap-southeast-1 · GCP asia-southeast1
Australia (Sydney)Australia — NSW510AWS ap-southeast-2 · Azure Australia East
Asia (Mumbai)India630AWS ap-south-1 · GCP asia-south1

3 · Vendor factors

The vendor comparison applies a multiplier to the model-class baseline (managed, well-batched serving at hyperscale PUE ~1.1) and maps each vendor to the regions it actually serves from. These are honest estimates, not disclosures — except Google, the only provider that has published a per-prompt figure.

VendorFactorWhy
OpenAI×11.2Serves from Microsoft Azure, predominantly US — typically US East (Virginia).
Anthropic×11.2Serves from AWS and Google Cloud, US-heavy.
Google Gemini×0.81.1TPU serving on GCP; the only provider with a published per-prompt figure (0.24 Wh median).
Self-hosted (open weights)×24Own GPUs: lower batching and utilization than hyperscale serving, usually higher PUE.

4 · Overheads

Sources

Try it on your own workload — open the AI Footprint Estimator.

Research & Business plans · machine-readable export

Download methodology.json

Versioned constants, sources and grid intensities as JSON. Upgrade to Research to unlock.

Estimator methodology — CO2Radar