
We help UK businesses understand the real footprint of the models, servers and people behind their AI — and shows where to cut emissions without losing pace.
Pick the LLMs your team relies on, tell us about your infrastructure, and we'll model the annual energy and emissions — and what to do about them.
Per-query energy figures are modelled, not measured — frontier vendors don't publish verified Wh/query. Results are advisory and rounded. See methodology, sources & ranges → v1.2 · reviewed 2026-06-06
A curated ranking of major LLMs by reported watt-hours per query. Choose smaller models for everyday tasks; reserve frontier reasoning for problems that deserve it.
Small, efficient. Runs on TPU v5e — among the lowest reported energy per query.
Lightweight Claude tier, good for high-volume tasks.
Distilled model, suitable for most everyday tasks.
Energy depends on your grid; great on renewable-powered infra.
Efficient European-hosted option.
Larger reasoning model — use selectively.
Mid-tier Claude, balanced quality/energy.
Multimodal flagship; meaningfully more energy than 4o-mini.
Heavy self-hosted footprint unless run on green energy.
Top-tier reasoning. Reserve for high-value tasks only.
Deep-reasoning runs can use 10–30× a standard query.
A working guide to which tasks justify the carbon of a model call, which should stay manual, and which need a careful hand.
High productivity gain, tiny model is sufficient. Tier-A models only.
Saves hours of human attention; energy per summary is negligible vs. the time saved.
Use a small model for completion; reserve large models for architecture questions.
Route first-line responses through a Tier-A model with human escalation.
Image generation is ~100× more energy than text. Use only when the image earns its place.
Highest energy class. Record once or use static assets instead.
Reasoning loops can use 10–30× a standard query. Save for genuinely complex problems.
If you know the source, go direct. AI search is convenient but wasteful as a habit.
Powerful, but each step compounds energy. Cap step count and prefer smaller agents.
Training is energy-intensive up-front but pays back if it lets you use a smaller model.
Mature, efficient, high human value.
Worth it for first drafts; don't regenerate 20 versions.
We give your team the data and defaults to make those choices — every day, in every workflow.
Run your score