Digital Impact

Browse all digital-impact calculators – pick the one that matches your usage.

🌐

Digital Carbon Footprint Calculator

Calculate your digital carbon footprint from streaming, emails, cloud storage, video calls and devices – with category breakdown.

The Two Clocks Behind Every Digital Action

Close the app. Put the phone down. Walk away. Almost everything keeps running. The photos from five years ago are still being copied between data centers, the inbox is still polling for new mail, the smart speaker is still listening for its name, the laptop in sleep is still pulling background updates, and somewhere on the other side of a fiber line the model that answered your last question is still warmed up and waiting. The active part of digital life — the tap, the search, the watch — is the visible tip. The rest is a tax that runs whether anyone is looking or not.

Digital impact runs on two clocks at once. The active clock ticks when you do something — open the stream, send the prompt, sync the file. The always-on clock ticks regardless: backups, retention, idle compute, infrastructure waiting at peak readiness for a load that has not arrived yet. Most sustainability conversations about technology focus on the active clock because it is the one a user can see. Most of the real environmental cost lives on the other one.

What Counts as Digital Impact

Digital impact is the resource cost of the physical systems behind every screen — and it has four major components, each with both an active and a passive half.

Data centers and infrastructure handle the active work (your query, your stream, your sync) and the always-on work (storing files no one has opened in years, keeping standby compute warm so the next request is fast, replicating data across regions for resilience). The active half is what you trigger. The passive half is what you signed up for years ago and forgot about.

Networks and transmission systems carry the bytes when you ask for them — and run continuously between requests. Every cable, every cell tower, every CDN node sits in standby readiness for the next packet, the way a kitchen tap is plumbed for the moment someone turns it.

End-user devices contribute through use (the screen on, the chip working) and through what was already spent before the box was opened: mining, manufacturing, shipping, assembly. The German Environment Agency and other national bodies have documented this consistently — for most personal devices, the manufacturing share dominates the lifetime total.

Software and cloud ecosystems decide how hard the other three have to work. A heavier app, a chattier protocol, an inefficient model — each translates directly into more data center load, more network load, more device load. The Green Software Foundation formalizes this idea: the carbon intensity of software is a property of how the code is written, what grid it runs on, and how much demand it serves.

Why Digital Impact Resists a Single Number

The always-on clock is the reason no single figure captures digital impact cleanly. The active clock is at least personal — your stream, your query, your sync. The always-on clock is shared. A data center serving millions of users does not run at one one-millionth speed when you log off; it stays at peak readiness so the next user gets a fast response. The cost of that readiness is distributed across the crowd in ways that depend entirely on where the accountant draws the line.

Three things make that distribution hard to pin down. First, infrastructure is shared: cloud regions, CDN nodes, network backbones, and AI inference clusters all serve mixed workloads, and assigning a slice to one user requires assumptions about allocation that the GHG Protocol exists specifically to standardize. Second, usage patterns vary: the same monthly streaming hours have a different footprint depending on resolution, codec, time of day, and grid region. Third, the technology itself is moving — a streaming hour or an AI query in 2026 is not the same workload it was in 2020, and any number more than a few years old needs re-checking.

Honest digital sustainability writing names its boundary up front. The International Telecommunication Union, the IEA, and the major cloud providers all publish sector-level disclosures, and the figures are usually compatible at the scale of "the whole industry" but diverge sharply when squeezed down to per-user numbers. Both perspectives are legitimate; they answer different questions.

The Areas Where the Always-On Clock Runs Hardest

Cloud and Infrastructure

Cloud is the architectural reason the always-on clock exists at scale. Data centers run continuously because demand is global and continuous — somewhere it is the morning rush — and because cold systems cannot serve hot requests. The International Energy Agency's 2024 electricity tracking places the data center share of global electricity in the low single digits today, with growth driven less by individual user actions and more by the buildout itself: more regions, more redundancy, more capacity in waiting.

Streaming and Media Consumption

Streaming is the textbook example of the two clocks running together. The active clock is the show you are watching. The always-on clock is the pre-loading of the next episode in the queue, the cached versions of content sitting on regional CDN servers nobody asked for in the last hour, and the encoding pipelines re-mastering libraries in the background. Sandvine's Global Internet Phenomena reports have placed video at well over half of all downstream internet traffic for years — most of which is the active half, but a meaningful share is preparation for views that may never happen.

Software and Applications

Software efficiency is the lever that decides how much work the other three components have to do. A poorly written app polls the server every few seconds; a well-written one polls when something changes. A bloated framework ships many times the bytes a lean one would. The active cost is what the user triggers; the always-on cost is what the architecture chose for them. The Sustainable Web Design initiative tracks this from the page-weight angle — the average website has grown several times heavier in the last decade, and the always-on share grew with it.

AI and Compute-Heavy Systems

AI is the area where the always-on clock has expanded fastest. Training a large model is a single, enormous, one-time spend — a passive cost amortized across every later query. Inference (answering a prompt) is the active cost. Both have grown rapidly as generative models scaled. The Green Software Foundation has flagged AI workloads as the fastest-growing category inside data centers, because the always-on infrastructure required to serve them — GPU clusters, high-bandwidth interconnects, cooling — has expanded faster than overall data-center capacity.

Devices and End-User Hardware

The device on your desk is the only piece of digital infrastructure a user actually owns and controls. Its always-on share is the manufacturing footprint, already spent before the device powered on for the first time. Its active share is the energy used in operation. For most personal hardware, the manufacturing share outweighs the operational share — which is why hardware lifespan, repair, and reuse decisions move the result more than any single operational efficiency tweak.

Why Digital Sustainability Is Becoming Hard to Ignore

The reason digital sustainability has moved from a niche topic to a mainstream one is straightforward: the always-on clock is getting louder. Cloud services that were "occasional" in 2010 are continuous in 2026. AI workloads that did not exist as a category five years ago now run constantly across most large cloud regions. The number of always-on devices in the average household has multiplied — phone, laptop, watch, speaker, hub, doorbell, lights — each adding a small steady draw to the background.

Individual actions matter; the always-on side matters more. Scope decisions — what subscriptions to keep, which features to leave on by default, how long to hold onto a device — shape the result far more than any single in-the-moment choice. That is also why simple advice ("just stream in lower resolution") tends to under-promise the impact of bigger ones ("keep the laptop two years longer, retire one cloud sync you never use").

When Concepts Aren't Enough and a Number Helps

Awareness on its own is a starting point, not a planning tool. There are four moments where a conceptual understanding stops being enough and a structured estimate starts being useful: choosing between services with comparable function (which streaming tier, which cloud plan, which AI model), evaluating an organization's digital footprint against a baseline, planning a tech refresh or retirement cycle, or producing a report that needs to hold up under scrutiny.

For those moments, deeper analytical resources translate the categories above into a directional number. The digital sustainability analysis tools on this site sit one layer deeper than this page — they take the conceptual split between active and always-on, between data center, network, device, and software, and produce an estimate that can be compared, repeated, and improved. The point is not precision for its own sake; it is having a directional figure that backs the planning, rather than guessing.

Where Awareness, Comparison, and Measurement Each Belong

Different decisions need different depths. Awareness — the conceptual layer on this page — is enough when the goal is to understand which categories matter at all, what trade-offs are inherent, and where the always-on clock is hiding. It is the right depth for setting policy direction, framing a conversation with a non-technical audience, or deciding whether to look further at all.

Comparison becomes useful when two real choices are on the table — service A versus service B, cloud region versus on-prem, model X versus model Y. Conceptual framing alone will not separate two options that look similar at the surface; that needs a structured side-by-side.

Structured tools come in when comparison turns into ongoing planning — tracking, baselining, target-setting. Detailed assessments are the territory of researchers, compliance teams, and procurement officers, and they use the same conceptual layers as this page, just with deeper data and tighter boundaries.

The right path through is usually depth on demand: start with the framing here, move to comparison when a decision is on the table, move to structured estimation when the decision needs a number behind it.

Common Questions About Digital Sustainability

What is digital sustainability?
Digital sustainability is the practice of designing, using, and retiring digital systems in a way that accounts for the resource cost of the physical infrastructure behind them — data centers, networks, devices, and the software that drives demand on all three. It treats software, cloud services, and connected hardware as part of the environmental conversation, not separate from it, and it covers both the active cost of use and the always-on cost of being available.
Why does digital technology have an environmental impact?
Because every digital action runs on physical infrastructure that consumes electricity, water for cooling, and materials in its construction. A query touches data centers, networks, and devices, each drawing on a grid mixed from many sources and each manufactured from extracted resources. The impact is real but mostly invisible to the user — the bill is paid by the operator and the supply chain, not the individual, which is why the cost is easy to miss.
What contributes to digital resource use?
Four broad components: data centers and the infrastructure they sit in, the networks that carry data, the end-user devices that produce and consume it, and the software ecosystems that decide how hard each of those has to work. Each of those four has an active half (the work triggered by a user) and an always-on half (the standby readiness, manufacturing, and architectural overhead that exists regardless). At scale, the always-on half dominates.
Why is digital impact hard to measure?
Because most of the resource cost is shared across users on infrastructure no individual owns. A data center serving millions of requests does not have a clean per-user split; the per-user share depends on how the accountant allocates the always-on portion of the load. The GHG Protocol exists in part to standardize this kind of accounting, and the same activity can show very different numbers under different boundaries — Scope 1, 2, or 3, with or without supply chain, with or without idle infrastructure.
How does infrastructure affect digital systems?
Infrastructure decides what is possible and what is costly. A cloud region powered by a clean grid serves the same workload with a fraction of the carbon a coal-heavy grid would. A modern data center cooled by outside air spends less than one running on chillers. A network architected for caching at the edge moves less data than one routing everything to a central origin. None of that is visible to the user, but each shifts the result materially — which is why infrastructure choices, especially at the organizational level, carry far more weight than individual usage tweaks.
Why do estimates of digital impact vary so much?
Because the boundary varies. A figure that counts only direct device energy will be much smaller than one that includes network transit, data-center load, and manufacturing. A figure for an individual user looks different from a figure for the whole industry divided by user count, because the always-on share gets allocated differently each time. Honest estimates name their boundary, their baseline year, and the things they deliberately left out — and any single number stripped of those assumptions tends to mislead more than it informs.

Adjacent Sections