Live row values

Calculator activity reference

ActivityUnitStatusCloud/source-side estimateBroader-system estimateDirect waterTotal waterSources
AI text promptsUses an everyday text-prompt estimate of about 0.3 Wh while keeping a separate prompt-specific water estimate of 0.26 mL direct and 1.3 mL total.
prompts
Basic text questions
Estimated0.3 Wh0.3 Wh0.26 mL1.3 mL
High-reasoning promptsUses the long high-reasoning 33.8 Wh benchmark rather than the much smaller medium-query comparison value, so this row stays an intentional outlier.
prompts
Long, high-reasoning queries
Inferred33.8 Wh33.8 Wh33.8 mL202.8 mL
AI image generationUses the IEA's 1.7 Wh SD-XL 1.0-base benchmark from controlled H100 testing. Jon Ippolito's What Uses More? comparison prompted the review; the adopted value comes from the underlying IEA report. The benchmark covers GPU electricity only and is carried through both energy columns as a conservative floor. Water remains an internal conversion rather than an image-specific measurement.
images
One SD-XL 1.0-base image under controlled H100 test conditions
Inferred1.7 Wh
GPU electricity only; excludes network energy, facility overhead, and the end-user device.
1.7 Wh
Carries the 1.7 Wh GPU-only benchmark through as a conservative floor; this is not a measured total-system value.
1.7 mL10.2 mL
Coding-agent useUses the current one-hour coding-agent benchmark and adds a 30 Wh device allowance in the total-system column.
hours
Hours of sustained agent use, not prompts
Estimated325 Wh355 Wh325 mL1950 mL
TikTok or short-video scrollingBuilt from device-side social-video measurement plus streaming-style infrastructure assumptions; keep this row estimated until a platform-specific cloud-side benchmark exists.
hours
Video-heavy social feed
Estimated7.5 Wh36 Wh7.5 mL45 mL
Instagram scrollingThis remains an analogy-based estimate built from social-media measurement plus streaming comparisons, useful for relative scale rather than platform accounting.
hours
Mixed image and short-video feed
Estimated5 Wh25 Wh5 mL30 mL
SnapchatAnother low-confidence social-media estimate built from broader comparison logic rather than a platform disclosure.
hours
Short-form messaging and video
Estimated4 Wh20 Wh4 mL24 mL
YouTube watchingUses the same CDN-style video benchmark as Netflix so the calculator keeps an apples-to-apples streaming anchor for the cloud-side and total-system columns.
hours
Streaming video hour
Inferred22 Wh26 Wh22 mL132 mL
Netflix streamingUses the IEA/Kamiya 22 Wh cloud-side and 77 Wh total benchmark used throughout the site's streaming comparisons.
hours
One hour streamed
Inferred22 Wh37 Wh22 mL132 mL
Email, cloud docs, and browsingThis is a teaching bundle for light browsing, email, and cloud documents rather than a per-click benchmark.
daily blocks
A light mixed-work block
Estimated4 Wh30 Wh4 mL24 mL
Zoom as participantUses a one-hour participant meeting estimate in which network plus platform routing form the cloud-side figure and participant device energy is added back for the total-system column.
hours
Joining a class or meeting
Estimated54 Wh74 Wh54 mL324 mL
Zoom as hostUses a hosted Zoom estimate that counts all participant devices in the total-system column.
meetings
One 50-minute, 10-person hosted session
Estimated192 Wh358 Wh192 mL1152 mL
Gaming Console (Xbox Series X + TV)Locally rendered online multiplayer, not cloud gaming. The central estimate includes the console, reference TV, allocated home networking, fixed access and core transport, modeled game-server IT, and data-center overhead. Downloads, patches, manufacturing, standby, and optional texture streaming are excluded.
hours
One active player-hour; local rendering over fixed broadband
Estimated7.7 Wh
Off-prem fixed access and core transport plus modeled game-server facility electricity; excludes the allocated home gateway.
220 Wh
Console, reference TV, allocated home gateway, fixed access and core transport, modeled game-server IT, and PUE overhead for one player-hour.
0.32 mL
Modeled direct cooling and humidification water for the game-server data center only; telecom-facility water is unquantified.
960 mL
U.S.-average operational water consumption: electricity-generation water for quantified components plus modeled direct game-server data-center water.

Source list

Calculator sources

This table lists the main sources used in the calculator and the role each one plays in the comparison model.

SourceUsed forNotes
How Much Energy Does ChatGPT Use?Epoch AI (2025) · Tier 3 · Expert analysis
  • 0.3 Wh AI text-prompt row
  • prompt-specific comparison language in the boundary and water method sections
Used for the 0.3 Wh everyday text-prompt estimate and related prompt-volume framing.
How Hungry is AI? Benchmarking Energy, Water, and Carbon Footprint of LLM InferenceJegham et al. (2025) · Tier 1 · Peer-reviewed or preprint benchmark
  • 33.8 Wh high-reasoning prompt row
  • direct and total water framing for prompt-heavy rows
  • maintenance note preserving the long high-reasoning benchmark
Primary inference benchmark for reasoning-heavy prompt classes and environmental multipliers.
Digital inventory calculator and scenario methodInternal synthesis (2026) · Tier 3 · Internal synthesis
  • scenario-style 1 mL direct to 6 mL total water bridge
  • browsing bundle row
  • preset mix logic
  • total-system add-ons for non-AI rows
Site-built method model that combines prompt benchmarks, streaming comparisons, meeting estimates, and water-conversion rules into the live calculator.
AI, Data Centers and Energy Demand: Reassessing and Exploring the TrendsRoucy-Rochegonde et al. (2025) · Tier 2 · Policy report
  • historical comparison for the pre-v0.2 image-generation row
  • comparison logic in the cloud-side versus total-system bridge
Historical comparator for the pre-v0.2 image coefficient and useful for broader Jevons framing; it is not the source of the current image value and should be paired with Tier 1 sources.
Electricity use of AI coding agentsSimon P. Couch (2026) · Tier 3 · Expert analysis
  • coding-agent use row
  • Gen Z vibe-coder preset
  • cloud-side versus total-system bridge for high-intensity AI use
Useful for the vibe-coding scenario but should remain marked as estimated and napkin-math-derived.
What is the environmental footprint for social media applications? 2021 EditionGreenspector (2021) · Tier 2 · Industry measurement
  • TikTok, Instagram, and Snapchat directional rows
  • cloud-side versus total-system bridge for social-video estimates
  • maintenance note on low-confidence social rows
Used for device-side social-media energy measurements, especially TikTok.
Why Your ChatGPT Prompt Uses Half the Energy of a TikTok VideoAdam Holter (2025) · Tier 4 · Opinion or blog analysis
  • TikTok total-system estimate cross-check
Directional comparison used only as a low-confidence reference for TikTok total-system estimates.
The carbon footprint of streaming video: fact-checking the headlinesKamiya (2020) · Tier 1 · Institutional commentary
  • Netflix row
  • YouTube row
  • streaming-side values used to anchor TikTok and Instagram estimates
Used for the 77 Wh total streaming baseline and the ~22 Wh server-plus-network split adopted for Netflix and YouTube comparisons.
Zoom, video conferencing, energy, and emissionsDavid Mytton (2023) · Tier 3 · Expert analysis
  • Zoom participant row
  • Zoom host row
  • hosted Zoom derivation table
  • worker-hosted-Zoom preset
Used for Zoom scenario modeling; should stay labeled as an estimate rather than a direct measurement of every meeting type.
Video Calls in Mobile Applications: Energy Consumption and Performance AnalysisVerdecchia et al. (2022) · Tier 1 · Peer-reviewed paper
  • participant device add-on for Zoom
  • total-system device add-on in the hosted Zoom derivation
Used for device-side video-call energy and camera-on versus camera-off impacts in the Zoom estimates.
  • water methodology context on direct cooling versus broader electricity water
Primary source for WUE framing, cooling tradeoffs, and provider-scoped production prompt metrics.
2024 United States Data Center Energy Usage ReportLawrence Berkeley National Laboratory (2024) · Tier 1 · National laboratory report
  • water methodology context on electricity-side water intensity
  • gaming-console PUE, WUE, and operational-water scenario
Primary U.S. demand, PUE/WUE, and electricity-related water-intensity context. Gaming uses its U.S. hyperscale and grid-water values only as a modeled scenario, not as provider-specific evidence.
What Uses More? AI Impact Calculator: sourcesIppolito (2025) · Tier 3 · Secondary calculator synthesis
  • provenance for the image-generation evidence review
  • external comparison for the generic water-conversion method
External comparison and provenance source. Ippolito's spreadsheet prompted the image and water review, but underlying studies remain the evidentiary authority for adopted values.
Energy and AICozzi et al. (2025) · Tier 1 · International agency report
  • global electricity-demand and infrastructure context
  • 1.7 Wh per image benchmark for SD-XL 1.0-base under controlled H100 test conditions
Primary institutional source for the adopted 1.7 Wh image-generation benchmark; the reported boundary is controlled H100 testing and GPU electricity only. Also used for global electricity-demand context.
The ML.ENERGY Leaderboard v3.0Chung et al. (2026) · Tier 1 · Academic benchmark and dataset
  • comparative image-generation evidence and configuration sensitivity
Academic benchmark used as comparative evidence for how model, steps, hardware, batching, and resolution change image-generation energy. Current leaderboard results must not be substituted silently for historical configurations cited by other calculators.
We did the math on AI's energy footprint. Here's the story you haven't heardO'Donnell et al. (2025) · Tier 2 · Technical journalism and analysis
  • comparative image-generation estimate in the Ippolito crosswalk
Secondary technical analysis used as a comparison point, including an image-generation estimate derived from measured joules. It does not replace a pinned primary benchmark.
Our contribution to a global environmental standard for AIMistral AI (2025) · Tier 2 · Industry environmental assessment
  • upper-bound context in the generic water-conversion review
Provider environmental assessment reporting 45 mL water and 1.14 gCO2e for a 400-token Le Chat response. It is useful for bounding water estimates but does not directly report mL per Wh.
Xbox Sustainability platform baselinesMicrosoft Xbox (2026) · Tier 1 · First-party laboratory measurement
  • Xbox Series X multiplayer-active high scenario
  • gaming-console method
First-party laboratory platform baseline measured at the wall socket. The 150 W Series X multiplayer-active figure is used as the high console-power scenario, not as a Call of Duty-specific measurement.
Introduction to global platform baselinesMicrosoft Xbox (2026) · Tier 1 · First-party global telemetry model
  • Xbox Series X central console coefficient
  • gaming-console method
First-party AC-wall telemetry model. The 127 W Series X shooter-genre average is the central console coefficient for the fixed gaming reference row.
Call of Duty Matchmaking Series: PingActivision Publishing (2024) · Tier 1 · First-party technical white paper
  • gaming functional unit and server architecture
  • gaming-console method
First-party architectural evidence for dedicated servers, 10 to 12-player Core Multiplayer, distributed data centers, and reserved idle capacity. It reports no server electricity coefficient.
Network energy use not directly proportional to data volumeMytton et al. (2024) · Tier 1 · Peer-reviewed paper
  • fixed-broadband network component model
  • gaming-console method
Peer-reviewed power model used to separate fixed access, core-network, and home CPE allocations from the much smaller usage-sensitive term.
ENERGY STAR Certified TelevisionsU.S. Environmental Protection Agency (2024) · Tier 1 · Government certification dataset
  • 79.5 W reference television coefficient
  • gaming-console method
Official certification dataset. The fixed reference uses the Sansui LE-55TA1 record: 54.7-inch screen and 79.5 W average on-mode power for certification.
Network Anatomy and Real-Time Measurement of Nvidia GeForce NOW Cloud GamingLyu et al. (2024) · Tier 1 · Peer-reviewed conference paper
  • central 0.20 Mbps gaming-traffic assumption
  • gaming-console method
Peer-reviewed cloud-gaming study used only for its contextual statement that a typical locally rendered console game requires roughly 100 to 200 kbps. It is not a Call of Duty packet trace.
PlayFab Multiplayer Server termsMicrosoft PlayFab (2026) · Tier 2 · First-party platform documentation
  • generic multiplayer-server architecture analogy
  • gaming-console method
Generic game-server architecture showing multiple containers per VM and standby capacity. It is analogy evidence only; no public evidence establishes that Call of Duty uses PlayFab or these configurations.

Cloud-side versus total-system bridge

The calculator keeps the first energy column as a cloud-side comparison view and then adds a second total-system column where the research basis supports it.

  • The cloud-side column usually combines server and network demand where the underlying source does not isolate pure data-center energy.
  • AI text and reasoning rows currently keep cloud-side and broader-system energy equal because the live calculator does not model a separate end-user device add-on for those actions.
  • The image row is narrower: its 1.7 Wh source covers GPU electricity only. That value is carried through both energy columns as a conservative floor and must not be described as measured server-plus-network or total-system energy.
  • Media and Zoom rows use a larger bridge from cloud-side to total-system values, which is why those rows show a bigger gap between columns.

Current bridge rules used in the calculator

Row familyCloud-side basisTotal-system basisCurrent calculator resultMaintenance note
AI text / reasoning promptsInference benchmarks used for everyday promptingKept equal to cloud-side in the live calculator0.3/0.3 and 33.8/33.8No separate end-user device model is currently applied
AI image generation1.7 Wh GPU-only IEA benchmarkNo boundary-matched broader-system benchmark; GPU-only value carried through as a conservative floor1.7/1.7 Wh per imageDo not label either stored value as a measured server-plus-network or total-system result
Coding-agent useHigh-intensity coding-agent benchmarkAdds a 30 Wh device allowance325/355 Wh per hourKeep this tied to the current coding-agent estimate, not to prompt counts
Netflix / YouTube22 Wh per hour server + network77 Wh per hour total-system benchmark22/77 Wh per hourUses the IEA/Kamiya streaming split already adopted on the site
TikTokEstimated 7.5 Wh per hour cloud-sideEstimated 36 Wh per hour total-system7.5/36 Wh per hourBuilt from social-video measurement plus streaming-style inference
InstagramEstimated 5 Wh per hour cloud-sideEstimated 25 Wh per hour total-system5/25 Wh per hourAnalogy-based row; keep estimated status
SnapchatEstimated 4 Wh per hour cloud-sideEstimated 20 Wh per hour total-system4/20 Wh per hourLowest-confidence social-media row in the calculator
Email / cloud docs / browsingInternal light-work bundleBundle with device add-on4/30 Wh per daily blockNot a per-click measurement
Zoom as participantOne-hour participant estimateAdds participant device energy54/74 Wh per hourOne-hour meeting framing
Zoom as hostHosted meeting derivation used on the siteAdds all participant devices192/358 Wh per meetingOne 50-minute hosted session with 10 people
Gaming Console (Xbox Series X + TV)7.7 Wh off-prem fixed access, core transport, and modeled game-server facility electricityAdds the Series X, reference 54.7-inch TV, and allocated home gateway7.7/220 Wh per player-hourLocally rendered multiplayer, not cloud gaming; infrastructure is attributional and the server term is low-confidence

Water methodology carried into the calculator

The calculator keeps prompt-specific direct and total water figures where they exist, then uses a broader electricity-to-water bridge for most of the remaining rows.

  • The current model rounds direct cooling water to roughly 1 mL per Wh of server energy and total water to roughly 6 mL per Wh once indirect electricity water is added back.
  • Text prompts keep their own prompt-specific direct and total water values instead of using the generic 1-to-6 rule.
  • Reasoning prompts, image generation, social video, streaming, browsing, and Zoom rows currently follow the broader proportional water rule unless a stronger prompt-specific figure exists.
  • Jon Ippolito's What Uses More? spreadsheet prompted a review of the generic coefficient. Its 7 mL/Wh selection is retained here as comparative synthesis, not adopted as a measured value.
  • Using the spreadsheet's stated 0.3 gCO2/Wh factor, Mistral's 45 mL and 1.14 gCO2e figures imply 11.84 mL/Wh, not 13 mL/Wh. The current 6 mL/Wh broader-water rule therefore remains unchanged pending a boundary-matched source.

Evidence considered in the 2026 water-method review

Evidence or methodWater relationshipBoundaryCurrent decision
Google production Gemini prompt0.26 mL / 0.24 Wh = 1.08 mL/WhDirect data-center cooling water for Google's production serving boundarySupports the rounded 1 mL/Wh direct-water bridge
Mistral 400-token Le Chat response45 mL water and 1.14 gCO2e; not reported per WhProvider life-cycle assessment for one responseUpper-bound context only; do not treat as a direct mL/Wh measurement
Ippolito What Uses More? synthesis7 mL/Wh, selected as a midpoint between about 1 and 13Universal calculator conversionRecorded as external comparison; not adopted
Recalculation of Ippolito's Mistral bridge45 / 1.14 x 0.3 = 11.84 mL/WhCross-metric conversion through a carbon-intensity assumptionDocuments the arithmetic correction; still not boundary-matched evidence
Your Digital Life generic bridge1 mL/Wh direct; 6 mL/Wh broaderApplied to the calculator's row-specific cloud-side energy fieldRetained for v0.2.0 pending stronger activity-specific evidence

Water conversion rules used by the live calculator

Row familyDirect waterTotal waterBasisMaintenance note
Text prompts0.26 mL per prompt1.3 mL per promptPrompt-specific water estimateKeep this special case unless the underlying prompt benchmark changes
Reasoning prompts33.8 mL per prompt202.8 mL per prompt33.8 Wh energy row with a 1:6 water bridge33.8 x 6 = 202.8
Image generation1.7 mL per image10.2 mL per image1.7 Wh IEA image benchmark with a 1:6 water bridge1.7 x 6 = 10.2
Social media / streaming / browsing rows1 mL per Wh6 mL per WhRounded direct-plus-indirect water bridgeUsed for TikTok, Instagram, Snapchat, YouTube, Netflix, and browsing
Zoom participant / host1 mL per Wh6 mL per WhRounded direct-plus-indirect water bridgeUsed for both meeting rows
Coding-agent use325 mL per hour1,950 mL per hour1:6 water bridge325 x 6 = 1,950
Gaming Console (Xbox Series X + TV)0.32 mL per player-hour960 mL per player-hourActivity-specific LBNL U.S.-average operational-water scenario, not the generic 1:6 bridgeIncludes electricity-generation water for console, TV, home gateway, access/core network, and server facility; direct telecom water remains unquantified

Hosted Zoom meeting derivation

The calculator's hosted Zoom row combines a small routing/server term, a larger network term, and participant-device energy.

  • The server term is intentionally small because the model assumes SFU-style routing rather than heavy re-encoding.
  • The network term dominates the cloud-side figure and the participant devices dominate the total-system add-on.
  • This remains an estimate and should stay visibly separate from directly measured prompt benchmarks.

One hosted Zoom meeting with 10 participants over 50 minutes

Energy componentPer-meeting energy (Wh)Basis
Zoom server routing7SFU-style routing estimate
Network across all participants185Mytton energy-per-GB framing
Devices across all participants166Laptop-energy assumption used for participant devices
Server + network subtotal192Cloud-side figure used in the calculator
Total-system energy358Hosted meeting figure used in the calculator

Image-generation evidence and Ippolito crosswalk

The image row now uses a pinned 1.7 Wh IEA benchmark discovered through comparison with Jon Ippolito's What Uses More? source sheet, while keeping Ippolito's 2 Wh figure and other published estimates visible as comparison evidence.

  • Jon Ippolito's What Uses More? spreadsheet prompted this review by selecting 2 Wh for a 1024x1024 image and exposing several candidate estimates.
  • The calculator does not treat Ippolito's 2 Wh synthesis as a primary measurement. It adopts the underlying IEA report's 1.7 Wh benchmark because the report identifies the model, H100 test hardware, controlled experimental context, and GPU-only boundary.
  • The IEA report does not establish a full production-serving or total-system value. The calculator keeps server and total energy equal for this row and labels the result inferred.
  • The image water figures are internal 1 mL/Wh direct and 6 mL/Wh broader conversions. None of the image-energy sources measures image-specific water use.

Image-generation evidence decision

EvidenceFigureWorkload and boundaryDecision role
International Energy Agency, Energy and AI, Figure 1.16 and accompanying text1.7 Wh per imageSD-XL 1.0-base on H100 GPUs; controlled experimental conditions; GPU electricity onlyAdopted v0.2.0 energy coefficient
Jon Ippolito, What Uses More? source sheet2 Wh per 1024x1024 imageSecondary synthesis of multiple image estimatesPrompted the review and remains an explicit comparator; not treated as direct measurement
O'Donnell and Crownhart1.2 Wh from 4,400 JStable Diffusion 3 with 50 denoising steps as summarized in Ippolito's sheetSupporting comparison
ML.ENERGY historical result summarized by Ippolito0.42 Wh from 1,500 JStable Diffusion 3 with 15 denoising steps; historical configuration must remain pinnedLower comparison point; current leaderboard is versioned separately
Prior Your Digital Life coefficient0.48 Wh per imageExact model, hardware, dimensions, and derivation were not recoverable from the included Ifri sourceReplaced in v0.2.0

Gaming Console (Xbox Series X + TV) method

The fixed gaming row estimates one active player-hour of a locally rendered 10 to 12-player shooter on Xbox Series X with a reference 54.7-inch television and fixed broadband. It includes an attributional allocation of shared network infrastructure and a low-confidence modeled game-server term.

  • This is locally rendered online console play, not Xbox Cloud Gaming. Multiplayer traffic carries game state, voice, authentication, matchmaking, anti-cheat, and telemetry; the console renders the game.
  • The central calculator values are rounded because the infrastructure terms are modeled. Exact component arithmetic is retained below for reproducibility.
  • The low, central, and high cases are scenario bundles, not statistical confidence intervals.
  • The game-server IT coefficient is the weakest component. Activision publishes architectural details but no per-player electricity, host power, utilization, provider share, PUE, or WUE.

Central Xbox Series X plus TV component calculation

ComponentCentral energyBoundary and evidenceConfidence
Xbox Series X console127 WhMicrosoft global shooter-genre AC-wall averageHigh for platform measurement; moderate for this workload
Reference television79.5 WhEPA ENERGY STAR Sansui LE-55TA1, 54.7-inch average on-mode certification power; illustrative model, not a market averageHigh for the model; low for representativeness
Allocated home gateway / Wi-Fi5.754 WhMytton power model with 11.5 W idle allocated across two household users plus the 0.20% line-use termModerate-low
Fixed access network5 WhMytton central fixed-access allocation per subscriberModerate-low
Core / transit network1.506 Wh1.5 W baseline + 0.03 W per Mbps at the 0.20 Mbps central traffic assumptionModerate-low
Game-server and support-service IT1 WhProject synthesis allowance informed by dedicated-server architecture and generic containerized server hosting; not a Call of Duty measurementLow
Data-center overhead0.22 Wh1 Wh server IT x (1.22 PUE - 1), using the LBNL hyperscale central scenarioLow
Exact quantified total219.98 Wh127 + 79.5 + 5.754 + 5 + 1.506 + 1 + 0.22; calculator rounds to 220 WhModerate overall

Sensitivity scenarios for one active player-hour

ScenarioConsole / displayHome + off-prem infrastructureTotal-system energyDirect server-DC waterBroader operational water
Low122 Wh / 23.65 Wh6.497 Wh152.147 Wh0.010 mL661.869 mL
Central127 Wh / 79.5 Wh13.480 Wh219.980 Wh; rounded to 2200.320 mL957.440 mL; rounded to 960
High150 Wh / 148.56 Wh31.425 Wh329.985 Wh3.350 mL1,440.213 mL

Published calculator fields and rounding

Published fieldCalculationPublished valueBoundary
Cloud/source-side energy5 access + 1.506 core + 1.22 server facility = 7.726 Wh7.7 WhOff-prem access, core, and game-server facility; home gateway excluded
Broader-system energy127 console + 79.5 TV + 5.754 home gateway + 7.726 off-prem = 219.98 Wh220 WhOperational player-hour; manufacturing, downloads, patches, standby, and cloud rendering excluded
Direct water1 Wh server IT x 0.32 L/kWh IT = 0.32 mL0.32 mLModeled game-server data-center cooling and humidification only
Broader operational water218.76 non-DC Wh x 4.35 mL/Wh + 1.22 DC Wh x 4.52 mL/Wh + 0.32 mL direct = 957.44 mL960 mLU.S.-average electricity-generation water consumption plus modeled direct game-server DC water