---
title: "Including AI in your carbon footprint:\nmethod, Scopes and reduction levers"
description: "Cloud AI is Scope 3 Category 1, self-hosted AI is Scope 2. This guide covers what AI weighs in a carbon footprint, a 4-step calculation and ways to reduce it."
canonical: https://projetcelsius.com/en/blog/ai-emissions-carbon-accounting-scope-3/
author: "Guillaume Pakula"
datePublished: 2026-06-08
dateModified: 2026-06-11
language: en
translationOf: https://projetcelsius.com/blog/ia-bilan-carbone-scope-3/
---

# Including AI in your carbon footprint: method, Scopes and reduction levers

**Author**: Guillaume Pakula
**Published**: 2026-06-08
**Updated**: 2026-06-11
**Section**: Practical guide
**Canonical URL**: https://projetcelsius.com/en/blog/ai-emissions-carbon-accounting-scope-3/
**French original**: https://projetcelsius.com/blog/ia-bilan-carbone-scope-3/
**Source**: Projet Celsius (https://projetcelsius.com/en/), a climate strategy consultancy of engineers and PhDs based in Paris and Marseille.

> AI has to be counted in your **Bilan Carbone®** (the French carbon accounting method, whose logic is identical under the GHG Protocol), under **[Scope 3](https://projetcelsius.com/en/blog/scope-3-emissions-guide/)**, as a purchased service. Your teams' internal use generally weighs **less than 1%** of a services company's footprint, whereas **AI built into a company's products** can become a significant emission source.

## Key takeaways

- **3 uses to count**: AI your teams use, AI inside your software, AI built into your product.
- **Cloud AI is Scope 3 Category 1**: a purchased service, not your electricity. Only self-hosted AI is Scope 2.
- **4 steps to a defensible figure**: inventory the uses, choose factors, calculate a range and document it.
- **Reduction starts with the right model**: matching it to the task cuts energy use by a factor of 10 to 50.

You are building your organisation's Bilan Carbone® (the French carbon accounting method) and have reached digital uses, where one line gives you pause: **AI**. It takes the form of ChatGPT, Copilot or the "smart" features that appear in every tool. The CSR (corporate social responsibility) manager then wonders whether it is significant, whether it has to be counted and how to count it without perfect data.

**Yes, it has to be included**, under **Scope 3** in almost every case. The stakes depend on **where AI is used in your organisation**: by your teams, inside your software or at the core of your product. The overview above gives the orders of magnitude, and the following sections set out the method step by step. For absolute consumption figures, [the energy used by a ChatGPT query](https://projetcelsius.com/en/blog/chatgpt-query-energy-consumption/) gives the 2026 values.

## Do you need to include AI in your Bilan Carbone®?

Yes, and at several levels, because AI does not appear in a single place in your activity. These **3 uses** differ in both weight and accounting treatment, and telling them apart from the start saves you from looking in the wrong place.

- **Internal use** is your teams' daily use of ChatGPT, Copilot or Gemini. It is generally **marginal** (less than 1% of the footprint), but it still has to be documented.
- **AI included in your software** covers the AI features already built into the tools you use every day (Copilot in Microsoft 365, your CRM, your "AI-enhanced" SaaS products), invisible on invoices. It is the classic blind spot when mapping your uses.
- **AI in your products** is the AI you build into a service you sell. Inference (running a trained model to answer a query) then runs each time a customer uses it, and this emission source can become **heavy**. It stays in your Scope 2 if the AI runs on your own servers, or in Scope 3 Category 1 if it runs on a cloud you buy.

This last case is the most underestimated. For a software publisher that builds AI into its offer (an app, a platform, a data product), AI stops being an anecdotal item and should be managed as an emission source in its own right. Even where internal use is marginal, it should be documented. It **doubles every year** in many organisations. The [macro trajectory is rising](https://projetcelsius.com/en/blog/chatgpt-carbon-footprint/) as well (data centres are projected to go from **~1.5% to ~3% of global electricity** between 2024 and 2030, according to the International Energy Agency (IEA)). If the Corporate Sustainability Reporting Directive (CSRD) [applies to you](https://projetcelsius.com/en/blog/esrs-e1-ghg-inventory-after-omnibus/), ESRS E1 (one of the European Sustainability Reporting Standards) also expects a **complete Scope 3 inventory**.

## What is AI's impact, and where does it belong: Scope 2 or Scope 3?

There are 2 separate questions, to be taken in order: **how much AI weighs**, then **where it is classified**. The second is the one that trips up the most carbon footprint assessments.

> **What is Scope 3 Category 1?** A carbon footprint sorts emissions into **3 scopes**: Scope 1 (your direct combustion), Scope 2 (energy you purchase and consume on site, visible on your meters) and Scope 3 (everything else in the value chain). Category 1 of Scope 3 covers **purchased goods and services**, which is where an AI subscription falls, like your accounting software or your hosting provider.

### Weight: a small item for internal use

For internal use, AI generally weighs **less than 1%** of the Bilan Carbone® of a services company. For 200 employees, this comes to roughly **a few hundred kilograms to a few tonnes of CO2e per year**, depending on how intensively it is used and which models are switched on (move the sliders of the calculator at the start of the article). That is a real share but a minor one: the **manufacturing of workstations** alone accounts for around 80 kgCO2e per employee per year, often **25 to 100 times** that employee's AI use. Digital emissions are ranked [by orders of magnitude](https://projetcelsius.com/en/blog/company-carbon-footprint-main-emission-sources/), and in that ranking [equipment weighs far more than cloud services](https://projetcelsius.com/en/blog/corporate-digital-carbon-footprint/). The exception remains **AI built into your products**, which can weigh much more.

### Classification: a purchased service, so Scope 3 Category 1

This is where many carbon footprints go wrong. AI used through a cloud service (ChatGPT, Copilot, Azure AI, Gemini) falls under **Scope 3 Category 1** as defined by the [GHG Protocol](https://ghgprotocol.org/corporate-value-chain-scope-3-standard), not under Scope 2. This is because you are buying a **service**, not the electricity consumed in your supplier's data centres. The reasoning is exactly the same as for your cloud hosting or your SaaS products. There are **2 special cases** worth keeping in mind:

- **Self-hosted AI** on your own servers (an in-house Llama or Mistral) means the electricity goes through your meter, so it falls under **Scope 2**. This is still a minority case in 2026.
- For **AI built into a product you sell**, inference served from your own servers stays in **Scope 2**, and inference served from a cloud you buy (API, hosting provider) in **Scope 3 Category 1**. Only the energy consumed by your customers' devices falls under **Category 11** (use of sold products).
- **Everything else (ChatGPT Team, Microsoft 365 Copilot, the AI in your CRM, an OpenAI API)** falls under Scope 3 Category 1, like your other purchases of digital services.

Scope 3 is [not mandatory for every organisation](https://projetcelsius.com/en/blog/is-scope-3-reporting-mandatory/), and a footprint limited to **Scopes 1 and 2** will never show AI. That is precisely [what makes a complete Scope 3 valuable](https://projetcelsius.com/en/blog/scope-3-emissions-guide/): it picks up **growing emission sources** before they come as a surprise.

## How do you calculate AI emissions, and with which tools?

AI providers disclose little about their consumption and do so poorly: only Google has published [an official measurement per query](https://arxiv.org/abs/2508.15734) (**0.24 Wh** [median for Gemini (in French)](https://projetcelsius.com/ia/chiffres/electricite-requete-gemini/)) and only Mistral a full life cycle assessment of a model. But a Bilan Carbone® works from **documented orders of magnitude**, not measurements to the nearest tenth, and the V9 version of the method, in force since January 2025, specifically asks for **uncertainties to be assessed item by item**. **4 steps** are enough to produce a defensible figure, and our [AI carbon footprint calculator](https://projetcelsius.com/en/tools/ai-carbon-footprint-calculator/) gives a first order of magnitude by model and by volume. To go further with a provider, our article on [measuring and managing AI in your company](https://projetcelsius.com/en/blog/measure-ai-footprint-in-your-company/) compares the options.

### A worked example

Take a services company with **200 employees**, average use (25 queries per day per person) and common models: 200 × 25 × 220 working days ≈ **1.1 million queries per year**. At ~0.3 Wh per query, that comes to ≈ **330 kWh**, or **≈ 0.15 tCO2e** with [the global electricity mix (in French)](https://projetcelsius.com/ia/chiffres/intensite-electricite-monde/), and 11 times lower if the data centres run in France. Compared with a services-sector footprint that runs to [hundreds of tonnes for 100 employees](https://projetcelsius.com/en/blog/first-carbon-footprint-ten-common-pitfalls/), this stays **below 0.1% of the total**. The same calculation for heavy generative use (reasoning models, long prompts, **~3 Wh per query** on average) raises the item tenfold without changing its place in the ranking.

### Where to find the right figures

- **Energy per query** varies by a factor of more than 100 depending on the model. You use a range tied to a specific model, never a generic "AI" average, and [the ChatGPT, Claude and Gemini comparison](https://projetcelsius.com/en/blog/chatgpt-vs-claude-vs-gemini-environmental-impact/) gives the 2026 values.
- **The electricity mix** of the region where the data centres are located comes to ~41 gCO2e/kWh in France, against ~458 g as a global average (Ember, an energy think tank, 2025, life cycle). The gap is a factor of 11 for the same watt-hour.
- **Volumes** are read from logs and API invoices where they exist; otherwise you use a transparent proxy (active users × estimated average use).
- **Official factors** come from the [Base Empreinte®](https://base-empreinte.ademe.fr/) database of ADEME (the French Agency for Ecological Transition), with more than 60,000 emission factors, for everything that surrounds AI: equipment, cloud and network.

For this emission source, the calculation [can perfectly well be done in-house](https://projetcelsius.com/en/blog/do-your-own-bilan-carbone-cost/), and the difficulty lies in **data collection** (tracking down the AI included in your software, questioning suppliers) and **traceability**. An auditor accepts a stated margin of uncertainty but penalises a **figure plucked out of thin air** or an overlooked emission source. The water footprint follows the same logic of ranges: [a query consumes about 0.26 mL of water](https://projetcelsius.com/en/blog/ai-water-footprint/), and the real issue is where the data centres are located.

> **The question to put to your suppliers** A sentence to include in your procurement questionnaire: "Can you provide the emissions (gCO2e) associated with our consumption of your AI service over the period or, failing that, the average energy per query and the location of the data centres that serve us?" Few suppliers answer yet, but once the question has been asked and dated it already counts as evidence of due diligence, and responses improve from year to year.

## What habits should you adopt to reduce the impact of AI?

Once AI is in the footprint, the levers for reducing it are **simple and inexpensive** and fall under a **usage policy**, with no investment required.

### The reference framework: frugal AI

In July 2024, France published the **world's first framework** on the subject, the **general framework for frugal AI** ([AFNOR SPEC 2314](https://ecoresponsable.numerique.gouv.fr/actualites/afnor-spec-iafrugale/) (in French), from AFNOR, France's national standards body), with **31 best-practice sheets**. It defines frugal AI by 3 conditions: the need to use AI rather than a simpler solution has been **demonstrated**, practices of restraint are applied, and uses have been questioned against planetary boundaries. Frugality therefore starts before any technical measure, with common sense. For digital services, the [RGESN](https://ecoresponsable.numerique.gouv.fr/publications/referentiel-general-ecoconception/) (in French), the French general framework for the eco-design of digital services published in 2024 by Arcep (the French electronic communications regulator), Arcom (the French audiovisual and digital regulator) and ADEME, complements it with its **78 eco-design criteria**, which cover AI tools.

### The action that counts most: match the model to the task

A **smaller model** is enough to summarise, classify or draft, and uses **10 to 50 times less energy** than a large one; reasoning models should be kept for problems that warrant them. The other habits follow: **concise prompts** (energy follows the volume of tokens, the units of text a model reads and writes, especially in the output) and **volume monitoring** with an energy or carbon budget for each use case. A final habit concerns the **data requested from suppliers**: low-carbon data centre regions and emission factors by service. None of them costs a penny, and all fit into a [broader reduction approach](https://projetcelsius.com/en/blog/how-to-reduce-company-carbon-footprint/) in which AI remains a small lever among large ones.

The opposite reflex would be to ban the tool. But taken individually, [an AI query uses as much energy as a Google search](https://projetcelsius.com/en/blog/chatgpt-vs-google-search-energy/), around **0.3 Wh**, and banning a worthwhile use to save a few tens of kilograms of CO2e per year would be a poor trade-off. Restraint comes down to the **choice of model and the volume**.

> Matching the model to the task is the first lever for reducing the footprint of AI, ahead of any technical measure and without investment.

## Pitfalls to avoid: misclassification, hidden AI, a single factor and false precision

**4 blind spots** come up on almost every engagement, and a verifier will spot them at first glance.

- **Putting everything in Scope 2.** This is classification error No. 1: it distorts the structure of the footprint and its [comparability between methods](https://projetcelsius.com/en/blog/bilan-carbone-vs-ghg-protocol/). Start from the distinction between a purchased service and electricity consumed, not from intuition.
- **Forgetting the AI included in your software.** M365 Copilot and the AI features of SaaS products appear on no dedicated invoice. Track them down as soon as you map your purchases by asking: "does this licence include active AI, and for how many people?"
- **Applying a single "AI" factor.** Between a light model and a reasoning model, the gap exceeds a factor of 100, so an average factor for "AI" in general does not stand up to scrutiny.
- **Aiming for false precision.** A figure to the nearest tenth on an emission source below 1% of the footprint is a waste of time, and a documented range is worth more than an invented decimal.

At Projet Celsius, we consider the fourth pitfall the most widespread. Teams spend days chasing the decimal of an AI emission source worth **0.05% of the footprint**, while **purchases, which often weigh 60% of it**, are left waiting. AI should be documented properly, and attention then moves to the sources that count.

## Key takeaways

- The **3 uses to tell apart** are internal use by teams (marginal), AI included in your software (the blind spot) and AI built into your products (potentially heavy, in Scope 2 or Scope 3 Category 1 depending on hosting).
- **Cloud AI use falls under Scope 3 Category 1, not Scope 2**, because you are buying a service. Only self-hosted AI moves to Scope 2.
- **The method comes down to 4 steps**, which are to inventory the uses, choose factors by model, calculate a range and document the assumptions.
- **The orders of magnitude are set out**, with ~0.3 Wh per typical query and less than 1% of a services company's footprint. A workstation often weighs 25 to 100 times more than the same employee's AI use.
- **Reduction starts before any technical measure**, by matching the model to the task (10 to 50 times less energy), writing concise prompts, monitoring volumes and engaging suppliers. This is the logic of frugal AI.

Classifying AI correctly, quantifying it and reducing it costs little when it is done in time, and the approach fits within the general framework of a [first Bilan Carbone®](https://projetcelsius.com/en/blog/bilan-carbone-method-explained/): **boundary, emission sources, method**. To budget for a complete carbon footprint, [the 2026 price ranges in France](https://projetcelsius.com/en/blog/bilan-carbone-cost-france/) give a benchmark, and for the rest of digital, [mapping a company's digital carbon footprint](https://projetcelsius.com/en/blog/corporate-digital-carbon-footprint/) is the right starting point.

## Frequently asked questions

## Frequently asked questions

### Is AI Scope 2 or Scope 3 in a carbon footprint?

AI used through a cloud service (ChatGPT, Copilot, Azure AI, Gemini) falls under Scope 3 Category 1, because you are buying a service, not the data centre's electricity. The only exception is self-hosted AI on your own servers, which goes under Scope 2. For AI built into a product you sell, inference stays in your Scope 2 if it runs on your own servers, or in Scope 3 Category 1 if it runs on a cloud you buy; only the energy of your customers' devices falls under Category 11 (use of sold products).

### How much does AI weigh in an SME's carbon footprint?

For internal use, AI generally weighs less than 1% of the footprint: from a few kilograms of CO2e per year for a small organisation to a few tonnes for 200 employees with intensive generative use. That is marginal but real, and it should be documented. If your company builds AI into a product or service it sells, however, use by your customers can make it a much heavier emission source.

### Where do you find emission factors for AI tools?

Suppliers publish little at service level: only Google has published an official measurement (0.24 Wh per median Gemini query). You combine an energy-per-query figure from independent benchmarks, tied to a specific model, with the electricity mix of the data centres' region, and use ADEME's Base Empreinte® for the factors surrounding AI (equipment, cloud). A proxy factor that is dated, sourced and given with its uncertainty stands up to scrutiny.

### How do you reduce the carbon footprint of AI in your company?

The first habit is to question the need (the most frugal query is the one you never run). The second is to match the model to the task: a smaller model is enough for most uses and needs 10 to 50 times less energy than a large one. Add concise prompts, volume monitoring with a budget for each use case, and requests to your suppliers for data and for low-carbon regions. This is the logic of the general framework for frugal AI (AFNOR SPEC 2314).

### Does the CSRD require companies to report AI emissions explicitly?

No ESRS standard addresses AI directly: it falls under Scope 3 within ESRS E1, and its materiality is assessed case by case. For most organisations in 2026, AI is not a material emission source in the strict sense. Directive (EU) 2026/470 has refocused the CSRD on companies with more than 1,000 employees and more than €450 million in turnover. If you fall within the scope of the CSRD, you may ask your suppliers for these data, within the limit of the value chain cap, which protects those with 1,000 employees or fewer. In every case, the trajectory of use is a reason to scope the issue now.

### Do we need to count Microsoft 365 Copilot in our carbon footprint?

Yes, under Scope 3 Category 1, like the rest of your Microsoft subscription. The emissions are generally negligible per employee, but they should be documented: number of licences, estimated intensity of use and a per-query factor for an equivalent model. If Microsoft ever publishes an official factor per licence, it will take precedence over your estimate.

## Sources

**Sources**: [GHG Protocol, Corporate Value Chain (Scope 3) Standard](https://ghgprotocol.org/corporate-value-chain-scope-3-standard); [ADEME, Base Empreinte® (more than 60,000 emission factors)](https://base-empreinte.ademe.fr/); [General framework for frugal AI, AFNOR SPEC 2314 (MiNumEco, the French interministerial mission for eco-responsible digital technology, July 2024)](https://ecoresponsable.numerique.gouv.fr/actualites/afnor-spec-iafrugale/); [RGESN 2024, Arcep-Arcom-ADEME](https://ecoresponsable.numerique.gouv.fr/publications/referentiel-general-ecoconception/); [Google, Measuring the environmental impact of delivering AI at Google Scale, arXiv 2508.15734](https://arxiv.org/abs/2508.15734) (Gemini median: 0.24 Wh, 0.26 mL of water); [Epoch AI, How much energy does ChatGPT use?](https://epoch.ai/gradient-updates/how-much-energy-does-chatgpt-use); [Ember, Global Electricity Review 2026](https://ember-energy.org/latest-insights/global-electricity-review-2026/) and [Our World in Data based on Ember](https://ourworldindata.org/grapher/carbon-intensity-electricity) (carbon intensity of electricity in 2025, life cycle: 458 gCO2e/kWh worldwide, 41 in France); [IEA, Energy and AI](https://www.iea.org/reports/energy-and-ai); [Bilan Carbone® V9 method, Association pour la transition Bas Carbone](https://www.bilancarbone-methode.com/), the French low-carbon transition association. Energy-per-query figures other than Google's are orders of magnitude drawn from independent benchmarks, which should be dated and documented in the carbon footprint. The ecoresponsable.numerique.gouv.fr pages are in French.
