TruaceTracing the truth around AIWednesday, July 22, 2026
TRV-2026-0433Certified recordPeer-reviewed

The carbon and water footprints of data centers and what this could mean for artificial intelligence

Although there are ways to estimate the global power demand of artificial intelligence (AI) systems, it remains challenging to quantify the associated carbon and water footprints. The lack of distinction between AI and non-AI workloads in the environmental reports of data center operators makes it possible to assess the environmental impact of AI workloads only by approximating them through data centers' general performance metrics. The environmental disclosure of tech companies is, however, often insufficient t…

Climate · P Space — documented harm · certified 2026-07-20 · v1 · article view · machine-readable

Current reading — problem

AI workloads' environmental impact is growing rapidly but remains hard to quantify because data center operators do not separate AI and non-AI reporting, with AI alone projected to reach 32.6-79.7 million tons CO2 and 312.5-764.6 billion liters of water in 2025.

What this doesn’t fix

Quantification remains approximate because operators do not distinguish AI from non-AI workloads and disclosures are insufficient to determine total data center performance.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0433, v1: “The carbon and water footprints of data centers and what this could mean for artificial intelligence.” Truvace, 2026-07-20. /record/TRV-2026-0433 (accessed at citation time). sha256 9ac18e080b4c1913

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv19ac18e080b4c

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0433 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.