Cost and footprint calculator
Describe your model mix, the impact shows up as you type.
No context estimated: only output tokens are counted.
CO₂e / month
9.5 kg
Cost / month
€87
Energy / month
25.3 kWh
Water / month
150 L
2% for cooling, the rest to generate the electricity
Tokens processed on this profile
Cache read0 · 0%
Cache write0 · 0%
Input0 · 0%
Output10,000,000 · 100%
This profile only counts output. The other profiles estimate the context and cache processed around those output tokens.
That is about 67 km in a combustion car and 3 showers for this monthly volume.
“Output only” profile: only output tokens are counted. In agentic use, context and cache make up most of the volume: pick a profile to estimate them. The dashboard measures this ratio on your organisation's volumes, pulled every day.
These numbers are estimates, at the providers' list prices. If they look really wrong to you, write to gaetan@tokenclimate.com.
Free calculator, built on public sources, each cited and versioned in the methodology. The field moves fast: a factor can be out of date within months. For a real measurement on your own data, per team, there is the dashboard: see the demo.
40 models covered. Every energy factor is sourced and versioned: a published estimate for the model where one exists, otherwise a documented extrapolation, with the confidence level shown on each model sheet. Per-model detail: all models (French).
Here, an estimate. To measure it on your real usage: see the demo.
Frequently asked questions
What exactly does the calculator count?
The four token classes billed by providers: input, cache write, cache read and output. The scope is that of the TokenClimate methodology: third-party datacenter, inference only, location-based by default. Every energy factor is sourced and versioned, and the full methodology is public.
Why aren't output tokens enough?
Because in agentic use they are only a small part of what the machine processes. On the coding agent profile, about 91% of the tokens processed are cache reads. A cache read costs about 0.08 times the energy of an input token (see the methodology's cache energy section): little per token, but the volume makes it a significant term of the total.
Where do the usage profile ratios come from?
Each profile is a sourced, versioned set of reference volumes, shown on screen with its assumption. The chat profile relies on the median of a conversational production trace (Splitwise, ISCA 2024). The coding agent profile is copied from the aggregates TraceLab measured on 2,676 real Claude Code sessions, 37 developers from a single lab. The real ratio varies from one organisation to another: the dashboard measures it on your real data.
I don't know my token volume, what now?
Nobody knows it by heart, which is what the simplified mode is for. It asks three questions, what you delegate to the tool, how many people use it and how often, then derives a monthly volume you can correct in the field. Tokens per session (96,900,000 / 2,676, TraceLab) and per exchange (150, Splitwise) come from published sources; the cadence is not guessed, you enter it. To place yourself, the methodology publishes the one TraceLab measured: 1.9 session per developer per week, or 8.0 per month. The result is a ballpark figure rounded to two significant digits, not a measurement.
Can a scenario be shared or cited?
Yes. The URL encodes the model mix, the volume and the usage profile, nothing else. The figures are recomputed on every open with the current version of the methodology, server-side for emails. A cited scenario therefore stays verifiable and recomputable.