I can accept that people disagree on details. What I can’t accept is the way a major energy drain ends up treated like background noise while other emissions sources get the loud, coordinated response.
I’m not concerned about abstract climate values here. I’m concerned about something measurable: modern AI workloads require large amounts of electricity and cooling. That electricity is still produced in real places by real infrastructure, and it carries real environmental costs. The contradiction is that the system that benefits from AI growth often refuses to treat that energy draw as a central, urgent climate issue.
And that refusal has consequences. It shapes what gets regulated, what gets subsidized, what gets publicly discussed, and what gets quietly normalized.
So yes—I take the side of the problem, not the side of the PR. I want the institutions to be pinned to the facts instead of letting them reposition the blame as “complexity,” “tradeoffs,” or “we’ll deal with it later.”
AI uses lots of energy
When people say “AI uses energy,” they usually picture a computer. In practice, most of the impact comes from data centers running and training models.
There are three layers I think about:
- Training energy and compute churn: Training involves large-scale computation performed for long periods. Besides, in many organizations, model development includes repeated experiments, retraining, and iteration. That increases total compute cycles.
- Inference energy at scale: Even after training, the model is used repeatedly. Millions of requests can translate into substantial continuous electricity demand.
- Cooling and facility overhead: Servers generate heat; cooling is not optional. But, it should be remarked that energy use isn’t only “GPU power”—it’s also ventilation, pumping, and facility operations.
If you combine these layers, you get a clear point: the climate outcome isn’t just about whether a model is “smart.” It’s about how much compute is performed, how often it runs, and how the electricity is generated and managed.
The environmental burden is being shifted away
Here’s the pattern that makes me angry (and I’ll say it plainly): the institutions that enable AI growth do not carry the same level of public accountability that they apply to other climate targets.
When governments and environmental campaigns prioritize certain sectors, the result is not neutrality—it’s a hierarchy of concern. That hierarchy has effects:
- It determines which policies are funded and which are postponed.
- It determines which industries face immediate operational constraints.
- It determines what “responsible transition” looks like for ordinary people.
And the hierarchy I see is skewed. AI’s energy demand is discussed, but it rarely becomes the kind of policy centerpiece that would force major changes in how AI is produced and deployed.
Why does the issue get treated as “too complicated” to regulate?
It’s not complicated to regulate the principles. It’s complicated to regulate the economic comfort.
It’s easier for institutions to push burdens onto the public in visible ways (ticketing, travel norms, car restrictions) than to impose equivalent discipline on AI expansion, where the costs are harder to communicate and where the beneficiaries are powerful.
Why does policy feel like it targets mobility while letting AI expand?Because the policy pipeline is built around easy narratives:
- “Stop driving fossil fuel cars” is concrete.
- “Reduce flying” is concrete.
- “Change compute behavior and energy sourcing” is abstract until it’s enforced with paperwork, standards, and monitoring.
Institutions choose battles they can win politically and narrate publicly. AI’s energy footprint doesn’t fit that storytelling machinery unless someone forces it to.
What institutions should do
If AI energy use is real—and I think it is—then the response can’t be vague ethics statements. It has to be operational.
What “real accountability” for AI energy should include
- Workload-level transparency: Require organizations to disclose energy-related metrics for major training runs and high-volume inference services.
- Grid coordination requirements: Data centers should be treated as major electricity customers with planning obligations and institutions should push for scheduling, flexibility, and demand management—especially during peak stress.
- Independent auditing: Self-reported “green” claims should be verified.
Right now, a lot of climate messaging pressures consumers and keeps procurement incentives for compute growth lightly constrained. That’s upside down.
For example, in Spain, on some routes, a train ticket from north to south can end up costing more than flying—while also taking longer.
When governments push “choose the greener option” style messages, the public doesn’t experience them as abstract goals. They experience them as inconvenience and higher prices. And if the greener option is reliably worse on cost and time, then what readers are being asked to do stops feeling like “the transition.” It starts feeling like punishment.
Meanwhile, AI’s energy consumption—the infrastructure side that quietly scales energy demand—rarely faces the same obvious, day-to-day friction from policy pressure.
That mismatch is the point: restrictions get imposed where they’re easiest to enforce on everyday life, not where the energy burden is hardest and fastest to actually curb.
Practical steps
I’m not asking you to become an energy auditor. I’m asking you to stop accepting climate narratives that dodge the central question: how much energy AI workloads actually consume, and what that means for emissions and ecosystems. If institutions won’t answer plainly, you can still detect the avoidance.
When you see any policy statement about “climate tech” or “responsible AI,” watch for these evasions:
- They talk about future promises (“net zero by 2030”) but not about present compute growth and electricity demand.
- A common dodge is: “We powered our training with renewable electricity.” That can be true in some cases and still be misleading in others, depending on timing, location, and matching.
- If you get no specifics, interpret that as an informational refusal.
- If governments focus on restricting cars or flights while AI energy demand is treated as secondary, that’s not a neutral prioritization—it’s a political choice.
Ask Questions
Even if specific numbers vary by source, the direction is hard to deny: training and large-scale inference require compute, and compute requires electricity and cooling. The debate often isn’t “does it use energy?”—it’s how transparently institutions describe the scale and growth.
Because detailed workload-level energy reporting threatens incentives. So the conversation drifts toward statements that sound responsible but don’t enable enforcement.
Because efficiency gains can be eaten up by growth. If the model becomes cheaper to run, it can be used more often, for more tasks, and by more users. Net energy impact depends on total demand, not only efficiency per operation.
Read and compare. When someone makes a claim, track whether it’s testable. Then apply pressure where it matters: demand disclosure standards, refuse to accept vague “clean power” language, and support policy that targets data center electricity demand and grid constraints—not just consumer behavior.