aceEmerging evidence
Published recordClimateProblem Space
More
Impacts of data center expansion on global energy demand: Sustainability challenges in the age of artificial intelligence
- Truvace record
- TRV-2026-2599raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Commentary, opinion, or narrative review
- Sources
- 1 sourcePeer-reviewed
- sha256
- 0023103c7b1b…check it
Digital transformation and advances in artificial intelligence have driven the expansion of data centers and increased their share of global electricity demand. This article analyzes the impacts of this growth on power systems and discusses the main challenges to the sector's sustainability. The study adopts a qualitative, exploratory, and descriptive approach and was conducted through a bibliographic and documentary review of 18 sources published between 2019 and 2025. Technical reports, standards, regulatory a…
The problem
A review of 18 reports and standards found that data centers, AI and crypto could use 620 to 1,050 TWh of electricity in 2026 (up from about 460 TWh in 2022), and that they can be built faster than grids can expand.
What this doesn’t fix
The findings rest on a review of 18 existing documents and on projections; the authors note that some companies do not disclose detailed consumption data, so estimates carry significant uncertainty.
Sources
1 on file- World Journal of Advanced Engineering Technology and Sciencesdoi:10.30574/wjaets.2026.20.1.0397
Cite this record
v1Truvace Impact Record TRV-2026-2599, v1: “Impacts of data center expansion on global energy demand: Sustainability challenges in the age of artificial intelligence.” Truvace, 2026-11-12. /record/TRV-2026-2599 (accessed on the day you copy it). sha256 0023103c7b1b0e34…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2599 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.