# How do I pick a cloud region with low carbon?

> Choose a lower-carbon cloud region for AI work: compare grid carbon intensity and carbon-free energy by region, then weigh latency, data rules and cost.

Source: https://greenai.guide/how-do-i/pick-a-low-carbon-cloud-region/  
Updated: 2026-11-19

## In short

Compare regions on grid carbon intensity and the share of carbon-free energy, using your provider's published region data or a source such as Electricity Maps, then weigh latency, data-residency rules and cost. Batch work such as training, fine-tuning and overnight processing is the easiest to move; user-facing inference usually needs to stay close to users.

## Steps

1. List which workloads can run anywhere, starting with training, fine-tuning and batch jobs.
2. Compare candidate regions on grid carbon intensity and carbon-free energy share.
3. Check data-residency, latency and cost constraints for each candidate.
4. Allow for the energy and cost of moving data to the new region.
5. Re-check the choice yearly, as grids and provider data change.

**Region choice can change the carbon of the same job several times over, for no change in code.** The electricity
behind a kilowatt-hour differs widely between grids.

## Where do I find region data?

- **Google Cloud** publishes, for each region, the hourly average share of carbon-free energy and the grid carbon
  intensity in gCO₂e/kWh. Its console marks regions "Low CO2" where carbon-free energy is at least 75% or, where
  that isn't available, grid intensity is at most 200 gCO₂e/kWh.
- **Electricity Maps** gives real-time, forecast and historical carbon intensity for more than 350 zones, useful for
  any provider.
- Other providers' sustainability pages and carbon dashboards; see [your cloud provider's carbon data](/how-do-i/find-my-cloud-providers-carbon-data/).

## Which workloads should move?

The Green Software Foundation's pattern for AI workloads suggests running training, fine-tuning and batch work in
low-carbon regions where latency is less critical. Microsoft's Azure Well-Architected guidance advises weighing
carbon intensity, latency and resilience together when choosing regions.

## Common mistakes

- **Moving latency-sensitive inference far from users,** which can hurt experience and add network traffic.
- **Ignoring data movement.** Copying large datasets between regions has its own cost.
- **Relying on certificates.** A provider buying renewable certificates doesn't make a high-carbon grid low-carbon;
  see [checking whether your AI runs on renewable energy](/how-do-i/check-whether-my-ai-runs-on-renewable-energy/).
- **Treating region choice as a substitute for efficiency.** It cuts carbon, not energy.

More in [hosting and data centres](/practice/hosting-and-data-centres/).

## Sources

- [Carbon free energy for Google Cloud regions](https://cloud.google.com/sustainability/region-carbon), Google Cloud (2025)
- [Electricity Maps data](https://www.electricitymaps.com/data), Electricity Maps (2026)
- [Use carbon-aware scheduling and region selection for AI workloads](https://github.com/Green-Software-Foundation/patterns/blob/main/docs/operations/carbon-aware-ai-scheduling.md), Green Software Foundation, Green Software Patterns (2025)
- [Reliability recommendations for sustainable workloads on Azure](https://learn.microsoft.com/en-us/azure/well-architected/sustainability/sustainability-reliability-recommendations), Microsoft Azure Well-Architected Framework (2026)
