Code Assistant

Cursor Environmental Impact

StandardEstimated

AI-native code editor — most popular AI coding tool

Architecture
Multi-model (GPT-4, Claude, custom)
Provider
Anysphere
1.2 Wh
Energy per query
0.50 g
CO₂ per query
5 mL
Water per query
4x more than
vs Google search

Energy per query

1.2 Wh

4x more than a Google search (0.3 Wh)

CO2 per query

0.50 g

US East (Virginia) grid (450 gCO₂/kWh)

Water per query

5 mL

~222 queries to fill 1 litre

Processing location

Multi-cloud (Azure, AWS)

Provider

Anysphere

Category

Code Assistant

Grid carbon intensity

450 g CO2/kWh (25% renewable)

How does Cursor compare?

Ranked #65 of 152 models by energy per query

0 Wh0.4 Wh0.8 Wh1.2 Wh1.6 WhCodestralAmazon QDeveloperCursorGitHub CopilotGoogle search (0.3 Wh)

Detailed Breakdown

Energy Consumption

Cursor is the most popular AI coding tool, using a mix of models (GPT-4, Claude, custom fine-tunes) depending on the task. A typical code edit or chat turn consumes ~1.2 Wh, though Tab autocomplete uses lighter models (~0.1 Wh). Heavy users may trigger 100+ queries per hour, making Cursor one of the highest-volume AI use cases per user.

Power Source & Carbon

Cursor routes queries to multiple model providers (OpenAI, Anthropic, custom), inheriting the carbon profile of each. Infrastructure spans Azure and AWS.

Water Usage

At ~4.5 mL per code edit. The aggregate water impact is significant given the frequency of use — a developer using Cursor for 8 hours may trigger hundreds of model calls.

About Cursor

Cursor is a code assistant model from Anysphere, released in March 12, 2024. AI-native code editor — most popular AI coding tool. Each query uses 1.2 Wh of energy and produces 0.50 g of CO₂. That's about 4.0x what a Google search consumes.

These figures are estimates derived from hardware specifications and API benchmarks — Anysphere has not published official energy data for Cursor. Actual consumption may vary significantly depending on batching, quantisation, and infrastructure optimisations that we cannot observe from outside.

Cursor in Context

120 MWh
estimated daily

At global scale

With an estimated 10M+ daily users averaging 10 queries each, Cursor consumes roughly 120 MWh of electricity per day — enough to power 4000 homes.

10.9 kWh
per year

Your yearly Cursor footprint

At 25 queries per day, your annual Cursor usage consumes 10.9 kWh — roughly what a fridge uses in a month. That produces 4.6 kg of CO₂.

What does your Cursor usage cost the planet?

Use our calculator to estimate your personal environmental footprint based on how often you use Cursor.

Calculate My Compute

Frequently Asked Questions

How much energy does Cursor use per query?

Each Cursor query consumes approximately 1.2 Wh of energy. This is 4x more than a traditional Google search (~0.3 Wh).

What is Cursor's carbon footprint?

Based on the carbon intensity of Multi-cloud (Azure, AWS), each query produces approximately 0.50 g of CO2. The grid in this region has a carbon intensity of 450 g CO2/kWh with 25% renewable energy.

How much water does Cursor use?

Each query consumes approximately 5 mL of water, primarily used for cooling the data centers that process the request.

How does Cursor compare to a Google search?

A Cursor query uses 4x more than a Google search in terms of energy. A Google search uses approximately 0.3 Wh, while Cursor uses 1.2 Wh.

Technical Details

Architecture

Multi-model (GPT-4, Claude, custom)

Release date

2024-03-12

Open source

No