What one ChatGPT question really costs

Every few weeks a striking number goes viral: a single ChatGPT question supposedly boils a bottle of water, or burns ten times the energy of a Google search. Then a rebuttal insists it is all a rounding error. Both cannot be true, so we did what we do for any AI system we build: chased every figure back to its primary source, checked the arithmetic, and added up the real cost of one query, from the electricity to the GPU to the water to the network. The short version is that a single question is remarkably cheap. The longer version, which is the honest one, is more interesting.

A note on method first, because this topic is full of confidently wrong numbers. Every figure below comes from a primary source: an official technical report, a peer-reviewed paper, or a government dataset, and each was checked against that source before it went in. Where two credible sources disagree, we give you both and explain the gap. We use these tools every day and we are not here to sell you a clean conscience, only the math.

The number everyone argues about

Start with electricity, the cost that stands in for all the others. Three independent estimates now land in the same small range. OpenAI's Sam Altman wrote in a June 2025 essay that the average ChatGPT query uses "about 0.34 watt-hours, about what an oven would use in a little over one second." Independent modeling by the research group Epoch AI put a typical GPT-4o query at "roughly 0.3 watt-hours." And Google, in an August 2025 technical report, measured the median Gemini text prompt at 0.24 watt-hours using a full-stack method that counts idle machines, cooling, and data-center overhead, not just the chip. Call it a quarter to a third of a watt-hour.

Now the famous scary figure. For two years the internet has repeated that a ChatGPT query burns 2.9 watt-hours, ten times a Google search. That number traces to a 2023 estimate by researcher Alex de Vries, popularized in the IEA's Electricity 2024 report. Epoch went back and checked its assumptions: it "assumed 4000 input tokens and 2000 output tokens per query," about 1,500 words, running on older A100 servers rated at 800 watts per GPU. It modeled an unusually long answer on last-generation hardware, and it came out roughly ten times too high. The honest reading is that the alarming number everyone quotes is a stale worst case, and the current typical case is about 0.3 watt-hours.

One caution on the lowest-effort figures. Altman's number is a blog assertion with no published methodology, and it leaves out the one-time cost of training the model. Google's 0.24 watt-hours is the sturdiest of the three because the company documented how it measured it and deliberately included the overhead most estimates skip. When a figure is convenient for the company publishing it, we lean on the one that shows its work. All three still sit in the same neighborhood, which is why the range is trustworthy even when a single decimal point is not.

The electricity bill for your question

Turn watt-hours into money. The average U.S. commercial electricity price in 2024 was 12.75 cents per kilowatt-hour, and the industrial rate 8.13 cents, per the Energy Information Administration. A third of a watt-hour at those prices costs somewhere between two and five thousandths of a single cent. Put the other way around, the raw electricity for a ChatGPT answer is so cheap that it takes a few hundred queries to add up to one penny. You could run a query every waking minute for a month and the power would cost you less than a cup of coffee.

Those per-query figures already fold in the overhead, which is worth understanding because it is where a lot of energy genuinely goes. Data centers report a number called PUE, power usage effectiveness, the ratio of total facility power to the power that actually reaches the chips. The industry average is about 1.5 to 1.56 according to the Uptime Institute, meaning roughly half again as much power for cooling and losses as for computing. The hyperscalers are far better: Google reports a fleet-wide PUE of 1.09. The good per-query numbers above come from the efficient end of that spectrum, which is where most large AI models actually run.

The hardware behind the answer

Electricity is the cost people fixate on, but it is not the biggest one. The expensive part is the machine. A single NVIDIA H100, the workhorse accelerator for this generation of models, has carried a street price of roughly 25,000 to 40,000 dollars and draws up to 700 watts. A full server of eight of them, an NVIDIA DGX, runs on the order of 400,000 dollars. That capital cost has to be spread across every query the machine ever serves.

Two things make that spreading dramatic. First, the hardware stays in service for years: Microsoft, like its peers, extended the assumed useful life of its servers to six years in a recent filing. Second, and more important, a serving GPU does not answer one question at a time. It batches many users' requests together and streams their tokens in parallel, so a single chip is producing answers for dozens of people at once. A 2026 measurement study found the effective hardware cost on one H100 ranges from about 0.21 dollars to 15.25 dollars per million output tokens depending purely on how busy it is. At a typical answer of a few hundred tokens, that is a fraction of a cent of amortized machine time, and it falls further the harder the hardware is used.

Even OpenAI's public API price, which bundles in the hardware, the research, the staff, and a profit margin on top of the electricity, works out to roughly 0.04 to 0.6 cents for a short answer, depending on the model. That is the whole all-in cost of a query as a paying customer sees it, and it is still well under a cent. Notice what that means: the electricity is a rounding error inside a number that is itself a fraction of a penny. The price of a query is dominated by everything except the power.

The hardware carries an environmental cost too, paid once when it is built rather than each time it runs. The manufacturing, or embodied, carbon of a high-end GPU is on the order of 150 to 165 kilograms of CO2 equivalent per chip. Spread across the billions of queries a GPU handles over six years, that also dissolves into fractions of a gram per question. The pattern repeats at every layer: a big fixed cost, divided by an enormous number of queries, becomes tiny per query.

The water and the cooling

Water is the other number that goes viral, and it is the one where honest sources genuinely disagree, so it is worth slowing down. The optimistic figures come from the model builders. Google's report puts the median Gemini prompt at 0.26 milliliters of water, about five drops. Altman's essay claims 0.000085 gallons, roughly a fifteenth of a teaspoon, per query. For scale, a teaspoon is 5 milliliters and a standard water bottle is 500, so a few drops per query is about one part in seventeen hundred of a single bottle.

The higher, scarier estimates come from a peer-reviewed study out of UC Riverside, "Making AI Less Thirsty," which estimates that GPT-style models consume a 500-milliliter bottle of water for every 10 to 50 medium responses. Why the gap? Scope. The five-drops figure counts only the water evaporated in the data center's own cooling towers. The bottle-per-few-answers figure also counts the water consumed off-site at the power plants generating the electricity. Both are legitimate, because they answer different questions. The researchers are careful to separate on-site cooling water from off-site generation water, and so are we: your single query directly evaporates a few drops on-site, and is indirectly responsible for a little more upstream.

The reason cooling uses water at all is simple physics: those 700-watt chips throw off heat, and evaporating water is a cheap, effective way to carry it away, the same trick as sweating. That also explains why location matters so much, a point we return to below, because evaporating a few drops is trivial in Ohio and genuinely contentious in a drought-stricken desert.

The network barely registers

What about sending the question and answer across the internet? This is the easiest cost to dismiss. Text is tiny: your prompt and its reply are a few kilobytes, not the megabytes of a photo or the gigabytes of a video. And moving data has become remarkably efficient. The peer-reviewed benchmark for fixed-line internet transmission was about 0.06 kilowatt-hours per gigabyte in 2015, and that intensity has roughly halved every two years since. Multiply a few kilobytes by even a generous transmission figure and the network energy for a query comes out under 2.5 percent of the compute energy, usually well under 1 percent. The wire is a rounding error on a rounding error.

Putting a third of a watt-hour in perspective

Numbers this small only mean something next to familiar ones. So: one ChatGPT query, at about 0.3 watt-hours, is roughly the same as a single Google web search, which Google itself pegged at 0.3 watt-hours back in 2009. It is, in Altman's own comparison, a couple of minutes of a high-efficiency LED bulb. Boiling one mug of water takes about 23 watt-hours, roughly 75 queries' worth. Streaming an hour of video uses about 77 watt-hours, so one query is about 14 seconds of Netflix. And driving a single mile burns around 1.5 kilowatt-hours of fuel energy, about five thousand queries, and emits 400 grams of CO2, against roughly 0.03 grams for a Gemini prompt. If you drove to a coffee shop to think about your question instead of asking the AI, the drive cost thousands of times more.

So why do the scary numbers exist?

If a single query is this cheap, where do the alarming headlines come from? Two honest places. The first is aggregation. Multiply a tiny number by billions of queries a day and it stops being tiny. Global data centers used about 415 terawatt-hours in 2024, around 1.5 percent of the world's electricity, and the IEA expects that to more than double to roughly 945 terawatt-hours by 2030. In the United States, data centers already drew about 176 terawatt-hours, 4.4 percent of the national total, in 2023, and Lawrence Berkeley National Laboratory projects that could reach between 6.7 and 12 percent by 2028. That growth is real, and not all of it is AI, but AI is the fastest-rising slice.

The second honest place is concentration. The problem with data centers is rarely the global average, it is the local spike. The IEA warns that strained grids put about 20 percent of planned data-center projects at risk of delay, that new transmission lines take four to eight years to build, and that the sector's emissions could climb from 180 million tonnes of CO2 to as much as 300 to 500 million by 2035. Water follows the same logic: a few drops per query is nothing until a hundred thousand servers evaporate it in a county that is already rationing. Training a single large model can directly evaporate hundreds of thousands of liters of freshwater. The per-query cost is trivial, the geographic concentration of millions of queries is not.

It is also worth being clear about which phase dominates over a model's life. A model is trained once, at real expense, and then answers questions billions of times, so the serving, the inference, is where most of its lifetime energy eventually goes. When Google accounted for its own machine-learning energy, inference was the larger share, not training. That is precisely why the per-query number matters, and why the industry's frantic work on efficiency lands where it counts.

And that efficiency is moving fast. In the same report, Google found that the energy behind its median text prompt fell 33-fold, and its carbon footprint 44-fold, in a single year, while the answers got better. Underneath that, the compute needed to reach a given level of language-model quality has been halving roughly every eight months, faster than Moore's law, according to Epoch AI. The honest caveat is that efficiency has not lowered total demand, because usage is growing faster than efficiency, which is why the aggregate figures keep climbing even as each query gets cheaper. Both things are true at once.

The honest bottom line

So, is asking an AI a question bad for the planet? Per question, no, and it is not close. Your query costs about a quarter to a third of a watt-hour, a few thousandths of a cent of electricity, a handful of drops of water directly, and a sliver of a very expensive but very heavily shared machine. It is comparable to a web search, cheaper than the lightbulb over your desk, and thousands of times less than the drive to work. The genuinely large and rising costs live at the level of the whole industry: in where and how fast we build data centers, in the strain on particular grids and particular watersheds, and in the one-time expense of training. Those are real problems and they deserve serious attention. They are simply not an argument against your individual question.

This is the same thing we tell clients about AI generally, and it is why we wrote separately about when automation is actually worth it and why a person still has to own the output. The useful question is almost never whether AI is too expensive to use, because at the level of a single task it plainly is not. The useful questions are whether the task is worth doing at all, whether the answer is correct, and whether the thing gets built responsibly. If you want a partner who reasons about AI from the actual numbers rather than the headlines, that is how we work, and you can tell us what you are trying to build.

Sources

External sources are provided for verification. NavoTech is not affiliated with and does not endorse the organizations cited.

Written by the team at NavoTech Digital Solutions. Have a project or counter-example? Get in touch.