See what your tabs actually cost.
EcoTab shows the memory and energy behind every open tab, then puts the idle ones to sleep — turning tab cleanup into an eco habit.
What it does
Live carbon readout
Your browsing draw in grams of CO₂ per hour, plus an eco score for the session.
Per-tab breakdown
Every tab with its estimated memory and power, colour-coded so heavy ones stand out.
Auto-sleep
Idle tabs are suspended natively. Nothing is lost — they reload right where you left off.
A tree that grows
Saved CO₂ accumulates into a tree, from seed to flourishing grove.
How the numbers work
Suspending a tab stops the energy it was spending. EcoTab estimates that from the tab's memory working set, the background CPU a live tab always uses, and media decoding when something is playing — then converts watts to CO₂ using your local grid's carbon intensity.
saved_gCO₂ = saved_watts ÷ 1000 × grid_intensity
kMem is roughly 150 mW/GB on laptops and 300 mW/GB on desktops, based on published DDR4 power measurements (~0.28–0.375 W/GB). Grid intensity is yours to set — around 55 gCO₂/kWh on a clean grid, 475 as a world average, 700+ where coal dominates.
Being straight about it: per-tab memory is an estimate. Browsers don't expose exact per-tab memory to extensions, so EcoTab labels what is estimated and what is measured rather than pretending to precision it doesn't have. Treat the footprint as a directional signal and a habit-builder, not a certified audit.
Privacy
No accounts, no tracking, no analytics, and no network requests of any kind. Everything stays on your device. Read the full privacy policy.
Built light
Plain vanilla JavaScript, zero dependencies, no frameworks, no build step. Tab tracking runs on browser events rather than constant polling, with a single one-minute check instead of a permanent timer.