Auto Tab Discard is a browser extension for Chrome, Edge, Firefox and Opera that uses the native chrome.tabs.discard API to automatically free memory held by inactive tabs.
What it is
Auto Tab Discard is an open-source WebExtension written in JavaScript and released under the Mozilla Public License 2.0. It lives in the browser-extension ecosystem and targets four engines at once, shipping separate listings for Chrome, Edge, Firefox and Opera. Its single job is memory: when a tab is inactive, the extension asks the browser itself to discard that tab, which releases the tab's memory while keeping the tab visible in the tab strip so it can be restored on click.
The concrete problem it solves is browser memory pressure. The specific thing it replaces is the DOM replacement method used by alternative extensions, which swap a page's content out from the extension side rather than asking the browser to unload the tab. The README states directly that Auto Tab Discard is more efficient and should be less buggy than those alternatives because discarding is handled by the browser natively instead of simulated by the extension.
Key capabilities
- Discards inactive tabs through the native
chrome.tabs.discard call rather than DOM replacement.
- Automatically reduces memory usage of inactive tabs without closing them.
- Distributed across four store channels: Chrome Web Store, Microsoft Edge Add-ons, Firefox Add-ons and Opera add-ons.
- Tagged as a WebExtension, covering
browser-extension, chrome-extension, firefox-addon and firefox-extension.
- Published under MPL-2.0, with the source written in JavaScript.
- Ships a public privacy policy at
webextension.org/privacy-policy/extension/tab-discard.html.
- Documented through a homepage listing at
webextension.org/listing/tab-discard.html, a product review post and a YouTube preview.
Who uses it and how
- Individual users who keep large numbers of tabs open and hit browser memory limits.
- Chrome and Edge users who want discarding behaviour without switching browsers or adding a heavier extension.
- Firefox users installing from addons.mozilla.org, where the add-on is listed separately from the Chromium builds.
- Opera users, who get a dedicated listing rather than a sideloaded Chromium package.
- Users who want the mechanism handled by the browser engine itself, since the extension delegates the memory release to the native API instead of rewriting page content.
Getting started
Install it from the relevant store: Chrome Web Store, Microsoft Edge Add-ons, Firefox Add-ons or Opera add-ons, all linked from the homepage at https://webextension.org/listing/tab-discard.html. There is no package to build and no server component; the extension runs entirely inside the browser.
How it compares
The README positions Auto Tab Discard against other tab-suspension extensions that use DOM replacement, arguing the native discard path is more efficient and less prone to bugs. Among the tools named in the facts, it is the one that leans on the browser's own tab lifecycle rather than reimplementing suspension in extension code. It is also MPL-2.0 and cross-browser, in contrast to single-store alternatives.
When to use it — and when not to
There is nothing to self-host: no database, no storage backend, no SMTP, and no server-side component, so the operational cost is limited to installing and configuring the extension in a browser. Users who need a supported product with a defined release cadence, a service-level commitment or vendor support should look elsewhere, because this is a community extension rather than a commercial product. The repository also carries 189 open issues against 1206 stars and 107 forks, and its README is short — largely a preview video and store links — so anyone evaluating it should expect to read the issue tracker rather than the documentation for detail on behaviour and known defects.
