53/100

Moderate evidence

ProblemPublished recordClimateProblem Space

Public perceptions of AI energy consumption: Awareness, responsibility attribution, and strategies

Truvace record
TRV-2026-2701raw data (JSON)
Version
v1Published
First published
Evidence type
Survey
Sources
1 sourcePeer-reviewed
sha256
935550d5ed98…check it

Abstract Generative artificial intelligence (GenAI) is widely used in the gig economy and electronic markets. However, its progress incurs substantial environmental costs due to its high and constantly increasing energy consumption. As inference—the process by which GenAI generates output—accounts for a large part of this demand, individual usage patterns are becoming a key factor in understanding the overall energy footprint and a crucial prerequisite for developing effective educational strategies and policies…

The problem

In a survey of 1,080 US adults, respondents gave users 22.18 of 100 responsibility points for generative AI's energy use versus 38.82 for household appliances, and only 5.7% of suggested fixes involved optimizing how AI is used.

What this doesn’t fix

Responses come from a Prolific crowdsourced panel, and the strategies people proposed were not tested for their real effect on energy use.

Sources

1 on file
  1. Electronic Marketsdoi:10.1007/s12525-026-00908-w
    Peer-reviewed2026-06-25

Cite this record

v1

Truvace Impact Record TRV-2026-2701, v1: “Public perceptions of AI energy consumption: Awareness, responsibility attribution, and strategies.” Truvace, 2026-11-12. /record/TRV-2026-2701 (accessed on the day you copy it). sha256 935550d5ed98fbf5…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1935550d5ed98…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2701 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.