ClimateLevel 6 of 6 territoryTerritory, level 6 of 6Used to calculate 1 entry, level 6Calculated with 2 entries, levels 1 and 3Database structure 
5Organisations
4Occupations and activities
3Uses
2Machine operations
1Calculation factorsMistral Vibe, 1 day
The responses of Vibe (formerly Le Chat, renamed in May 2026) over one day worldwide. Projet Celsius estimate.
- The calculation covers the responses of Le Chat in one day, data centre included.
- 100% of the calculation rests on database assumptions; it does not measure actual use.
- Out of scope: uses of Mistral AI models by businesses and developers, and model training.
Sentence to citeMistral Vibe, 1 day, Projet Celsius estimate: 210 kgCO2e per day, for 450 kWh of electricity, servers worldwide (458 gCO2e/kWh).
- Calculated with
- Used to calculate
Breakdown of emissions by item
The pathQuick question × 1,500,000Vibe, per day
210 kgCO2e in total: 450 kWh of electricity × 458 gCO2e/kWh (servers worldwide).
Inputs of the calculation
PUE of the data centre, Read 1,000 tokens, Write 1,000 tokens, Quick question
How the calculation is built
Counted as questions to a medium-sized model with a response of 400 tokens, that of the life cycle assessment of Mistral AI, which publishes only carbon and water. The vendor publishes no volume: 1.5 million responses per day is an assumption, based on its audience in France.
Comparison with other territories
Characteristics
| Unit | 1 day |
|---|---|
| Default location | world, 458 gCO2e/kWh (Ember 2025, life cycle); 11 other locations to choose from |
| Counted | the responses of Le Chat in one day, data centre included |
| Not counted | uses of Mistral AI models by businesses and developers, and model training |
| Status | estimated |
All the characteristics
| Identifier | IA-0517, projetcelsius.com/en/ai/database/IA-0517/ |
|---|---|
| Version | 0.1 of 2 November 2026 |
| Category | Territories, cities, territories, global services |
| 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
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 |
|---|---|---|---|---|---|
| Quick question | × 1,500,000 | 0.3 Wh | 450 kWh | 100 % | assumption |
Entries that use it (1)
Sources of the calculation
7 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.
Arcom · June 2026
Baromètre de l'audience des services d'intelligence artificielle, 1re édition ↗ (new tab)
Role and limits : Arcom
Author. Arcom, based on Médiamétrie Netratings
What the publication covers. unique visitors and time spent per AI service, France, 2023 to 2026
What it does not cover. query volumes
Reading by the database. A panel-based audience measurement, service by service
Vibe, per day → : Quick question →
Le Chat answers over one day, counted as a question to an average model with an answer of 400 tokens, that of the Mistral AI analysis, which publishes only carbon and water; assumed volume, Mistral AI does not publish it
Scope of the figure used. computation of the response, data centre
Limit. The quantity and the share entrusted to AI are database assumptions, not a measured footprint.
Energy and factors
The references of the selected values and of the entries used in this calculation.
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
Reference of the selected value
Scope of the figure used. GPT-4o, 500 tokens written, full scope
Limit. A public calculation, from the hardware and the assumed size of the model
Role and limits : Google
What the publication covers. chips, host, standby machines, data centre, on-site water
What it does not cover. manufacturing, training
Reading by the database. The only production measurement published by a provider
Reference of the selected value
Scope of the figure used. Median of a text prompt; chips, host, standby machines, data centre
Limit. The only production measurement published by a provider, not audited by a third party
Microsoft Research · 2026
Estimation de l'énergie des requêtes en production (Joule) ↗ (new tab)
Role and limits : Microsoft Research
Author. Microsoft Research, Oviedo et al.
What the publication covers. H100 nodes, production
Reading by the database. Calibrated on production
Reference of the selected value
Scope of the figure used. Median, 500 tokens read and 300 written, H100 nodes
Limit. Not a measurement, but calibrated on production; judges public estimates to be 4 to 20 times too high
OpenAI · June 2025
Role and limits : OpenAI
Author. Sam Altman, OpenAI
What the publication covers. an average query
What it does not cover. method, scope
Reading by the database. One sentence, no method
Reference of the selected value
Scope of the figure used. "An average query", with no published method
Limit. No published scope; consistent with Google
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
Quick question → : 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
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
Quick question : × 1,500,000
Le Chat answers over one day, counted as a question to an average model with an answer of 400 tokens, that of the Mistral AI analysis, which publishes only carbon and water; assumed volume, Mistral AI does not publish it
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 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).
