4 items
See each tab's estimated memory and carbon draw, then auto-sleep idle tabs to save energy. Tab management as an eco habit. Every tab you leave open is quietly using memory and electricity. EcoTab shows you how much — and then does something about it. WHAT YOU SEE A live carbon readout — your current browsing draw in grams of CO₂ per hour, plus an eco score from 0 to 100 for the whole session. A per-tab breakdown — every open tab with its estimated memory and power, colour-coded on an efficiency spectrum so the heavy ones are obvious at a glance. Real system memory — how full your machine's memory actually is, measured directly. WHAT IT DOES Auto-sleep — tabs you haven't touched for a while are automatically suspended using Chrome's native tab discarding. Their memory is freed, but nothing is lost: the tab stays in place and reloads exactly where you left it when you click back. One-click control — sleep any tab yourself, wake it again, or wake everything at once. Nothing is one-way. Protection built in — pinned tabs and tabs playing audio are never auto-slept by default, and you can shield any individual tab from sleeping. THE PART THAT MAKES IT STICK Saved energy accumulates into a tree that grows as you go — seed, sprout, sapling, mature tree, flourishing grove — with milestones along the way. Your savings are also translated into things you can picture: how long a real tree would take to absorb the same CO₂, or how far you'd have to not drive a car. HOW THE NUMBERS WORK Suspending a tab stops the energy it was spending. EcoTab estimates that from three parts: the tab's memory working set (about 150 mW per GB on laptops and 300 mW per GB on desktops, based on published DDR4 power measurements), the background CPU a live tab always spends, and media decoding when a tab is playing audio or video. That total is converted to CO₂ using your local grid's carbon intensity, which you can set for your region — a clean grid like France's is around 55 gCO₂/kWh, the world average around 475, a coal-heavy grid 700 or more. Being straight with you: per-tab memory is an estimate. Browsers don't expose exact per-tab memory to extensions, so EcoTab labels which figures are estimated and which are 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. BUILT TO BE LIGHT Tab managers have a reputation for being slow and bloated. This one is deliberately lean: plain vanilla JavaScript, zero dependencies, no frameworks, no build step. It tracks tabs through browser events rather than constant polling, and runs a single one-minute check instead of holding a permanent timer, so it stays out of your way. PRIVACY No accounts. No tracking. No analytics. No network requests of any kind. Your settings and your saved-CO₂ total stay on your device, and nothing is ever sent anywhere or sold.
Jul 20, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.