DEV Community

guillermo llopis
guillermo llopis

Posted on Originally published at somaai.earth AI-assisted

The same AI query can emit 12 times more carbon depending on the cloud region

Two choices you already make as a developer, the region and the model size, move the estimate more than anything else.

I am CTO of SOMA AI, which publishes the dataset used here.

When we built our emission factors for AI inference, I expected the model to be the whole story. It is not. The place where the model runs matters almost as much, and it is a setting most teams pick once, by latency or habit, and never revisit.

Here is what the numbers say. All of them are estimates from the SOMA AI Emission Factors (CC BY 4.0, DOI 10.5281/zenodo.20443585), for one mid-size AI exchange of 1,210 tokens. They are location-based grid averages, not renewable contracts.

One exchange, 12 times apart

Across the 143 AWS, Azure and Google Cloud regions in the dataset, the lowest estimate is on the Quebec grid, where the dataset maps AWS ca-central-1. It comes to 0.008 g CO₂e. The highest is Bahrain, at 0.095 g. That is about 12 times more for identical work.

Closer to home, the spread inside the EU is about 7.4 times. Sweden is lowest at 0.009 g and Poland highest at 0.070 g. The EU-27 average is 0.029 g and the world-average grid gives 0.053 g. Spain sits at 0.022 g, rank 12 of 27.

Why does the grid change the number so much? Because electricity is most of the footprint on a fossil-heavy grid and a small part on a clean one. On the world-average grid, electricity is 90% of the estimate for one exchange. The rest is server hardware, the data-centre building and the amortised training of the model. That remainder is about 0.006 g wherever the query runs, which is why even the cleanest grid does not reach zero.

One detail matters to platform teams. A query is served where the data centre is, not where the user sits. So the factor to use is the region in your cloud usage export, not your office's country.

Model size multiplies everything

Region is half of the picture. The other half is the model class. This table shows the estimated g CO₂e for the same 1,210-token exchange on three grids.

Model class Quebec (Canada) World average Bahrain
Class A, small 0.002 0.016 0.028
Class B, mid 0.008 0.053 0.095
Class C, frontier 0.033 0.201 0.355

Compare the corners and you find the uncomfortable result. A frontier model on the cleanest grid (0.033 g) can emit more than a small model on the dirtiest one (0.028 g). So looking only at the region, or only at the model, can send you in the wrong direction.

What a dev or platform team can do

There are three practical moves, and none needs a research project.

  1. Know the region. Cloud platforms state it in the usage export next to the token counts. If you cannot say where your AI calls are served from, that is the gap to close before anything else.
  2. Where you can choose, choose with both variables in mind. The region is the largest lever after the model class, with no change to the work. Whether latency, data residency and price allow a cleaner region is your call, but now you can put a number on the trade.
  3. Right-size the model. If a small model does the job for a routing, classification or summarisation step, the class A row above is the reason to use it.

If you also have to report this, report the location-based figure. A market-based one beside it makes sense only if the provider documents its renewable contracts for that region.

Limits worth stating

These are annual 2023 averages, mostly Ember yearly data on a lifecycle basis, with US subregions from EPA eGRID 2023. A country's average is not the mix of a specific data centre, which may sit on a cleaner or dirtier part of the grid or buy renewable electricity. The modelled range of the models inside a class, around the class value, is −41% to +48% for class A, −39% to +24% for class B and −67% to +55% for class C. Water is not part of this comparison.

We also know of one error in this dataset version. Azure canadaeast and Google Cloud northamerica-northeast1, both in Quebec, are mapped to the Canada-wide average rather than the Quebec grid. They will be corrected in the next version. The method paper, arXiv 2606.10660, is under peer review, and corrections go into the next dataset version.

Try it on your own usage

The full ranking of 209 countries and every mapped cloud region is on the source page, and the free calculator applies the region for you. Full table and method are at the original page, and you can run your own numbers in the free calculator.

Disclosure: I am CTO of SOMA AI, which publishes the dataset used here.

Top comments (0)