3.6× less energy than Kimi.
Kimi Environmental Impact
China's popular long-context AI assistant
The figures below are for one quick question. A longer chat with follow-ups uses about 0.88 Wh, and an hour or two of agent work about 25.0 Wh.
One query, in context
Energy, carbon and water for a single use. Quick single question (one exchange)
83% of a Google search.
About 1.1× a Google search and 6% of 10 m by car.
About 18× a drop of water and 18% of a teaspoon of water.
- Where it runsMoonshot AI Cloud (China)
- Grid carbon intensity525 g CO₂/kWh · 33% renewable
- Compared with a Google searchabout the same as a search (0.3 Wh)
- Water~1,087 queries to fill 1 litre
Where Kimi sits
#72 of 199 by energy per query. Lighter than 64% of all models. Lit dots are the same kind of model; click any dot to open it.
Want something lighter?
1.7× less energy than Kimi.
4.2× less energy than Kimi.
What a month of use adds up to
Pick how much you use it. Based on one quick use at a time, five days a week.
- Energy
- 27.1 Wh
- Carbon
- 14.1 g
- Water
- 100 mL
A month of 5 chats a day, 5 days a week. The energy is about 2.3× a phone charge and 25% of a kettle boil.
Work out your own →- Energy
- 108.3 Wh
- Carbon
- 56.3 g
- Water
- 398 mL
A month of 20 chats a day, 5 days a week. The energy is about 9.0× a phone charge and 98% of a kettle boil.
Work out your own →- Energy
- 541.3 Wh
- Carbon
- 281.4 g
- Water
- 1.99 L
A month of 100 chats a day, 5 days a week. The energy is about 4.9× a kettle boil and 7% of a UK home's day.
Work out your own →How does Kimi compare?
Next to similar models. Bars use a log scale, so each step is a big jump.
Detailed breakdown
Energy
We estimate Kimi at ~0.25 Wh for a quick single question. CLEER benchmarked the later Kimi K2.6 directly at ~0.30 Wh; the original Kimi was a smaller model, so we place it slightly below. This is our extrapolation, not a CLEER figure or a measurement. It replaces our earlier ~1.2 Wh estimate, which was built on 2025 benchmark figures for older hardware.
Power source & carbon
Runs on Chinese data centre infrastructure, subject to China's coal-heavy grid.
Water use
At ~0.92 mL per quick question, derived from the energy estimate at the ~3.7 L/kWh water factor we apply to this model's infrastructure. Water scales directly with energy, so longer chats, reasoning and agentic sessions use proportionally more.
About Kimi
Kimi is a text and chat model from Moonshot AI, released in March 18, 2024. China's popular long-context AI assistant. Each query uses 0.25 Wh of energy and produces 0.13 g of CO₂. That's roughly comparable to a traditional Google search.
These figures are estimates derived from hardware specifications and API benchmarks — Moonshot AI has not published official energy data for Kimi. Actual consumption may vary significantly depending on batching, quantisation, and infrastructure optimisations that we cannot observe from outside.
The Moonshot AI Kimi family
One chart per tier, on a shared time axis. Hover a dot for details; click to open that version.
What does your Kimi usage cost the planet?
Use the calculator to estimate your personal footprint based on how often you use Kimi.
Frequently asked questions
How much energy does Kimi use per query?
Each Kimi query consumes approximately 0.25 Wh of energy. This is about the same as a traditional Google search (~0.3 Wh).
What is Kimi's carbon footprint?
Based on the carbon intensity of Moonshot AI Cloud (China), each query produces approximately 0.13 g of CO2. The grid in this region has a carbon intensity of 525 g CO2/kWh with 33% renewable energy.
How much water does Kimi use?
Each query consumes approximately 0.92 mL of water, primarily used for cooling the data centers that process the request.
How does Kimi compare to a Google search?
A Kimi query uses about the same as a Google search in terms of energy. A Google search uses approximately 0.3 Wh, while Kimi uses 0.25 Wh.
Technical details
- Architecture
- Dense Transformer (long-context optimised)
- Context window
- 2,000,000 tokens
- Release date
- 2024-03-18
- Open source
- No
- Training data cutoff
- 2024-06