UsesLevel 3 of 6 useUse, level 3 of 6Used to calculate 1 entry, level 4Calculated with 4 entries, levels 1 and 3Database structure 
6Territories
5Organisations
4Occupations and activities
2Machine operations
1Calculation factorsReview a contract of 20 pages
Read a 20-page contract and summarise its risks, ask 3 follow-up questions, rephrase the clauses to review. Projet Celsius estimate.
- "Summarise 30 pages" accounts for 58% of emissions in this scenario.
- 100% of the calculation rests on database assumptions; it does not measure actual use.
- Out of scope: server manufacturing, model training, the network and the user's device.
Sentence to citeReview a 20-page contract, Projet Celsius estimate: 2.7 gCO2e per contract, for 5.8 Wh of electricity, servers worldwide (458 gCO2e/kWh).
- Calculated with
- Used to calculate
Breakdown of emissions by item
2.7 gCO2e in total: 5.8 Wh of electricity × 458 gCO2e/kWh (servers worldwide).
Inputs of the calculation
PUE of the data centre, Read 1,000 tokens, Write, with reasoning, Re-read from cache
How the calculation is built
Made up of simple tasks; the contract is re-read from the cache for the follow-up questions.
Comparison with the other uses
↓ The heaviest use in the topic, "Deep research": 45 gCO2e, 17 times more
Emissions of one use, linear scale, 7 of the 21 uses in the topic. For calculated values, servers worldwide.
Characteristics
| Unit | 1 contract |
|---|---|
| Default location | world, 458 gCO2e/kWh (Ember 2025, life cycle); 11 other locations to choose from |
| Counted | the model reading and writing tokens, and data centre cooling |
| Not counted | server manufacturing, model training, the network and the user's device |
| Status | estimated |
All the characteristics
| Identifier | IA-0222, projetcelsius.com/en/ai/database/IA-0222/ |
|---|---|
| Version | 0.1 of 2 November 2026 |
| Category | Uses, a request to AI |
| Choice of the selected value | database calculation from the entries this one is made of, at the quantities of the unit |
| Sources | calculation of the database |
| Licence | CC BY 4.0 |
Usage parameters
Advanced settings
Result for the chosen case
For a carbon footprint
| Item | purchases of services (GHG Protocol scope 3, category 1); regulatory BEGES, category 4 |
|---|---|
| Quantity | 1 contract |
| Factor | 2.7 gCO2e per contract, IA-0222 version 0.1, according to the grid at the location (location-based), servers worldwide |
| Total | 2.7 gCO2e · not counted: server manufacturing, model training, the network and the user's device |
Breakdown by item
Quantity, unit value, contribution and nature of the data for each item
| Item | Quantity | Unit value | Contribution | Share | Nature of the data |
|---|---|---|---|---|---|
| Summarise 30 pages (20 pages) | × 1 | 3.4 Wh | 3.4 Wh | 58 % | assumption |
| Conversation of 10 exchanges (20 pages) | × 1 | 1.8 Wh | 1.8 Wh | 31 % | assumption |
| Proofread a page | × 1 | 0.6 Wh | 0.6 Wh | 10 % | assumption |
Entries that use it (1)
Sources of the calculation
4 publications, for this entry and those used to calculate it, with the chosen parameters.
The result is calculated by Projet Celsius. The sources below support its uses, its factors and its conversion; they do not all measure this total.
Uses and assumptions
These publications shed light on AI tasks and uses. They do not measure the carbon footprint of the case calculated.
Epoch AI · February 2025
Role and limits : Epoch AI
What the publication covers. the calculation from the hardware and the assumed size of the model
What it does not cover. actual measurements
Reading by the database. A public, transparent calculation
Conversation of 10 exchanges → : Re-read from cache →
The context re-read from cache at each turn: the previous exchanges, and the document already in the conversation if there is one
Scope of the figure used. server, convention C4
Limit. The quantity and the share entrusted to AI are database assumptions, not a measured footprint.
Projet Celsius · November 2026
Tokens per word, per line of code and per cell, measured with 7 public tokenisers
Role and limits : Projet Celsius
What the publication covers. 479,888 words from 196 blog articles and their English translation, code from the site and the Python library, a table of measurements; tokenisers of GPT-4o, GPT-4, Llama 3, Gemini (via Gemma 3), Mistral, DeepSeek and Qwen
What it does not cover. the Claude tokeniser, not public
Reading by the database. A measurement on technical texts, figures included; to be repeated if publishers change their tokeniser
Projet Celsius measurement, repeated on request with the public tokenisers
Summarise 30 pages → : Read 1,000 tokens →
Length convention: one page
Scope of the figure used. A report page, headings and paragraphs included: between the 1,500-character sheet (250 words) and a full A4 page in single spacing (about 550 words, at 6.1 characters per word measured on our articles)
Limit. This publication supports the quantity of text or content processed, not its carbon footprint.
Summarise 30 pages → : Write, with reasoning →
Length convention: one page
Scope of the figure used. A report page, headings and paragraphs included: between the 1,500-character sheet (250 words) and a full A4 page in single spacing (about 550 words, at 6.1 characters per word measured on our articles)
Limit. This publication supports the quantity of text or content processed, not its carbon footprint.
Conversation of 10 exchanges → : Re-read from cache →
Length convention: one page
Scope of the figure used. A report page, headings and paragraphs included: between the 1,500-character sheet (250 words) and a full A4 page in single spacing (about 550 words, at 6.1 characters per word measured on our articles)
Limit. This publication supports the quantity of text or content processed, not its carbon footprint.
Proofread a page → : Read 1,000 tokens →
Length convention: one page
Scope of the figure used. A report page, headings and paragraphs included: between the 1,500-character sheet (250 words) and a full A4 page in single spacing (about 550 words, at 6.1 characters per word measured on our articles)
Limit. This publication supports the quantity of text or content processed, not its carbon footprint.
Proofread a page → : Write, with reasoning →
Length convention: one page
Scope of the figure used. A report page, headings and paragraphs included: between the 1,500-character sheet (250 words) and a full A4 page in single spacing (about 550 words, at 6.1 characters per word measured on our articles)
Limit. This publication supports the quantity of text or content processed, not its carbon footprint.
Energy and factors
The references of the selected values and of the entries used in this calculation.
Watershed · Aug. 2026
Estimating GHG Emissions from AI Use: Framework for Corporate-Level Measurement ↗ (new tab)
Role and limits : Watershed
Author. Bistline, Ulissi, Davis, Glidden, Joyce, Li, Mohsenin and Suh (Watershed)
What the publication covers. factors per 1,000 tokens read and written at the server before PUE (host and standby machines included), PUE separate (1.10 for a large operator, 1.56 for an unknown operator)
What it does not cover. clean measurements, the model and the hardware
Reading by the database. Default factors proposed for review (public data as of June 2026); for a large operator, taken from Google's measurement published in 2025 (Elsworth et al.), which already contains the data centre overhead; constant per token, they underestimate long contexts and agents according to the authors
Reference for the variant "Medium model, Watershed default factor"
Scope of the figure used. Default factor for 1,000 tokens read, medium model, large operator, at the server before PUE (Watershed table 2, public data as of June 2026)
Limit. A default value that Watershed derives from Google's measurement (0.24 Wh for the median text query of the Gemini app), with about 500 tokens per query and a written token costing 3 times a read token; Watershed does not give the split between read and written tokens. The 0.24 Wh already include the overhead of Google's data centre (0.02 Wh, 8%): with 375 tokens read and 125 written, the simplest reading, the factor contains it, and the PUE of 1.10 applied afterwards counts it a second time (about 9%). Values proposed for review, final at the next version of the framework
Reference for the variant "Medium model, Watershed default factor"
Scope of the figure used. Default factor for 1,000 tokens written, medium model, large operator, at the server before PUE (Watershed table 2, public data as of June 2026)
Limit. 3 times the reading factor, based on the ratio between writing and reading selected by Watershed (Patel et al., Splitwise, 2024). Same derivation and same caveat as for reading: Google's 0.24 Wh already include about 8% of data centre. Values proposed for review, final at the next version of the framework
Summarise 30 pages → : Data centre PUE →
The data centre, convention C3
Scope of the figure used. building cooling and losses
Limit. This figure covers part of the calculation; it does not measure the whole entry.
Reference of the selected value
Scope of the figure used. Default factor for a large operator, from the server to the data centre; 1.56 for an unknown operator
Limit. A default value, not a measurement
Conversation of 10 exchanges → : Data centre PUE →
The data centre, convention C3
Scope of the figure used. building cooling and losses
Limit. This figure covers part of the calculation; it does not measure the whole entry.
Proofread a page → : Data centre PUE →
The data centre, convention C3
Scope of the figure used. building cooling and losses
Limit. This figure covers part of the calculation; it does not measure the whole entry.
Conversion into carbon
The source of the electricity factor of the selected location.
Worldwide: 458 gCO2e/kWh, life cycle.
Role and limits : Ember
Author. Ember, Our World in Data
What the publication covers. electricity generation over the life cycle, by country
What it does not cover. guarantees of origin
Reading by the database. The same source for all countries
Conversion of electricity into carbon: worldwide
Scope of the figure used. the production of electricity over the life cycle, including power plant construction and fuels
Limit. An average for the chosen country, not the electricity contract or the data centre of a specific service.
Nature of the data
Published readings, conventions, assumptions
- Projet Celsius assumptions 100 %
Calculation assumptions
Quantities, nature and source of each assumption
Summarise 30 pages : counted 1 times
Read the contract of 20 pages and summarise its risks on one page
Conversation of 10 exchanges : counted 1 times
The 3 follow-up questions, the contract re-read from cache
Proofread a page : counted 1 times
Reword the clauses to be reviewed, one page
Methodology conventions
With their alternatives
| The standard query | A query counts 100 tokens read and 400 written |
|---|---|
| The data centre | Server electricity is multiplied by 1.10 for the data centre |
| The cache | A token re-read from the cache costs 10% of a token read |
| The default location | Without other information, the servers are in the world, at the world average electricity |
| Electricity, location-based, on a life cycle basis | The kilowatt-hour is that of the servers' country, on a life cycle basis, from a single source for all countries |
| Two significant figures | A calculated value is rounded to two significant figures, a published value is reproduced with the precision of its source; the calculation keeps full precision |
| The formula | the sum of what makes up the entry, then CO2e: electricity (Wh) multiplied by the carbon intensity of the server location (gCO2e/kWh), divided by 1,000 |
| Calculate a case without an entry | The formula, the default values and a step-by-step example |
History
Entry in version 0.1 of 2 November 2026, in the database in version 0.4
- 2 November 2026Version 0.1 of the entry, as of the date of its current value.
- 31 October 2026Creation of the database, in its first version (0.1).
