/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Google releases a study saying a median Gemini text prompt uses 0.26mm of water and produces ~0.03g of CO2; critics: omitting indirect water use is misleading

Google shared a study of Gemini's environmental impact, but it omits some key data. … Amid a fierce debate about the environmental toll …

The Verge Justine Calma

Context & Ripple Effects

Google’s per-prompt disclosure arrives against a longer-running question over data-center water use, including reporting on Google’s water consumption at US data centers. The disagreement is not over whether Gemini has a footprint, but over which parts of that footprint belong in a user-facing estimate.

Related coverage separately reported Google’s energy and emissions figures for a median Gemini app prompt, putting a per-prompt energy number alongside the emissions estimate. That makes system-boundary choices—especially direct versus indirect water use—the central issue in interpreting the company’s claims.

First-order effects

  • Google gains a concrete environmental metric for Gemini, but critics’ boundary objection limits how confidently users, journalists, and policymakers can treat the water figure as a full impact estimate.
  • The disclosure shifts immediate scrutiny to Google’s methodology: what infrastructure and upstream water use the calculation includes or excludes.

Second-order effects

  • AI providers publishing per-query environmental claims face pressure to disclose comparable assumptions, rather than relying on small-looking prompt-level figures that may not capture shared infrastructure impacts.
  • Enterprise buyers and sustainability teams may need to distinguish operational prompt metrics from broader lifecycle or supply-chain accounting when evaluating AI deployments.

Third-order effects

  • If providers continue to market AI efficiency through per-prompt metrics, environmental reporting is likely to move toward more explicit, standardized accounting boundaries for energy, emissions, and water.
  • The larger structural tension is that model-level efficiency claims can coexist with rising total infrastructure demand; transparent aggregate reporting will determine whether efficiency translates into lower overall impact.

The trend: Generative-AI environmental reporting is evolving from headline per-query estimates toward scrutiny of the accounting boundaries and total infrastructure footprint behind them.

Discussion

  • @justinhendrix Justin Hendrix on bluesky
    Google has just released a technical report detailing how much energy its Gemini apps use for each query, and estimates of water consumption and carbon emissions.... the median prompt...consumes 0.24 watt-hours of electricity, the equivalent of running a standard microwave for ab…
  • @caseycrownhart Casey Crownhart on bluesky
    We've finally got some hard numbers on AI's energy demand from a major tech company: Google says a median prompt to Gemini uses 0.24 watt-hours of electricity.  🧵 @technologyreview.com www.technologyreview.com/2025/08/21/ 1...
  • @shanumathew93 Shanu Mathew on x
    Per new paper, Google says a median Gemini text prompt uses ~0.24 Wh (9 seconds of TV), 0.26 mL water (~5 drops). ~58% of the energy is used toward the accelerator, 25% is the host CPU/DRAM, 10% is “idle” capacity kept ready for reliability, and 8% is datacenter overhead [image]
  • r/Bard r on reddit
    Google has possibly admitted to quantizing Gemini