Digital life runs on physical infrastructure. Every stream, search and stored photo ends up as electricity drawn by a data center, a network and a device. That is the hidden energy cost of digital life: it is real, it is growing, and it is far harder to measure precisely than most claims about it admit.
The honest starting point is a definitional one. Merriam-Webster defines "hidden" as being "out of sight or not readily apparent," and that is exactly the problem with digital emissions. Nothing about opening an app feels material, so the impact stays invisible until someone goes looking for it — and the looking is where estimates, assumptions and outright myths pile up.
This explainer separates the two. What follows covers where the energy actually goes, which popular claims rest on solid ground, and which ones do not — with the caveat, stated plainly, that precise figures vary by region, grid mix and methodology, so any single number you see quoted should be treated with suspicion.
Where does the energy actually go?
Three layers carry almost all of it. The first is data centers: the buildings full of servers that store files, run websites and train or serve AI models. Their power goes to the machines themselves and, just as important, to cooling, because dense racks of electronics generate heat that has to be removed.
The second layer is the network — the cables, routers, cell towers and exchange points that move data between the center and the user. The third is the device in your hand or on your desk. Each layer consumes power continuously, and the share each one carries depends on who is counting and how.
What is uncontroversial: demand is rising. More video, more cloud storage, more AI inference, more connected devices. The direction of travel is clear even when the exact wattage is not.
Is streaming really as bad as the scary charts suggest?
Some widely shared charts have claimed that an hour of video streaming emits as much as driving a car several miles. These claims deserve skepticism. Early versions of that comparison relied on worst-case assumptions — for instance, counting every video as high-definition, served from an inefficient data center, over a power-hungry network, to a large television. Real viewing habits, real network efficiency and real data center performance differ enormously.
The measured picture is more modest. Streaming per hour is not free, but estimates that treat it as catastrophic generally rest on stacked worst-case inputs rather than observation. When researchers redo the calculation with realistic assumptions, the per-hour impact drops sharply. That does not make it zero; it makes it small and context-dependent.
What this means for a reader: the honest answer to "is streaming bad?" is "it uses energy, the amount depends heavily on where you are and what you watch, and anyone quoting one universal number per hour is overselling their certainty."
Does deleting an email or an old photo shrink your footprint?
This is one of the most persistent myths, and it deserves a careful answer. Deleting a single email or photo does have some effect — a file that no longer exists is not stored, replicated or backed up — but the effect is vanishingly small. Storage is cheap in energy terms relative to computation. The servers that matter most are the ones actively doing work: serving requests, running models, transcoding video.
There is a defensible version of the cleanup argument, though. At institutional scale — a publisher with millions of archived assets, duplicate renders and abandoned databases — storage hygiene can matter, because it reduces the active footprint of entire server fleets. For an individual, the honest framing is that deleting files is a tidiness habit, not a climate intervention.
The same logic applies to "dark data" — the industry term for stored data nobody uses. At scale, cleaning it up is a legitimate operational and energy question. At the level of one person's inbox, it is mostly folklore.
How does AI change the picture?
AI is the newest and fastest-growing layer of data center demand. Training large models is energy-intensive, and so is serving them: every time a chatbot answers or a search engine summarizes a page, a machine does work that a cached text result would not have required.
For publishers, this intersects with an already-pressuring dynamic. As we covered in our analysis of how AI Overviews cut click-through roughly in half, AI-generated answers change not only how much energy the search ecosystem consumes but who captures the value from it. The energy story and the business story are the same story at bottom: more computation is happening on platforms' machines, less attention and revenue flows to the sites that produced the underlying material. This connects to our earlier piece, AI Overviews cut click-through roughly in half — what the measured data says publishers should do.
What generalizes: AI increases compute demand, and compute demand is the dominant driver of data center energy growth. What does not generalize: any claim that a specific query or model has a fixed, known energy cost. It varies with model size, hardware, location and grid mix.
What can publishers and creators actually do?
Our analysis suggests the useful levers are structural, not symbolic. They sit in choices publishers already make about their own infrastructure:
- Choose hosts on their published terms. Data center operators disclose efficiency metrics and renewable-energy commitments in their documentation. Comparing providers on those published terms is the legitimate way to factor energy into a hosting decision — not a vendor's marketing badge.
- Trim the waste you control. Unused tracking scripts, redundant image sizes and bloated pages consume device and network energy on every visit. Lighter pages are faster and cheaper for readers too, so the incentive aligns without any sacrifice.
- Question your own storage. Duplicate assets and dead databases are an operational cost before they are an energy cost. Cleaning them pays for itself.
- Be honest with audiences. Publishers who cover the climate should not launder worst-case estimates into their own coverage. Measured impact, with its uncertainty stated, is the standard.
Notice what is absent from that list: guilt directed at readers. The individual actions with real weight — where a company hosts, how a site is built, what a platform serves — are decisions made by operators, not audiences.
What remains unknown, and why that matters
The evidence base here is thinner than the volume of claims suggests. Comprehensive, regularly updated measurements of the internet's total energy use do not exist in one place; estimates come from models with different boundaries and assumptions, which is why figures conflict. Data center operators disclose some efficiency data, but end-to-end accounting — from a user's tap to a server's fan — is rarely published and rarely comparable.
What the durable picture looks like: digital infrastructure consumes meaningful and growing energy, computation matters more than storage, worst-case streaming estimates overstate the individual case, and the levers that matter belong to operators and platforms. The rest — the charts assigning a fixed carbon price to your evening of television — is myth dressed as measurement. Treat any precise universal figure the way you would treat any other unverifiable number: as a claim, not a fact.
