Memory release

Release memory without closing the tabs you still need.

When Chrome feels heavy, SignalTabs lets you review eligible background tabs, confirm once, and ask Chrome to unload them. The tabs stay in their windows. Clicking one reloads the page.

Add to Chrome Compare cleanup choices
Shows after 20+ eligible tabs
Requires confirmation
Tabs stay in place
MB/GB is approximate
What it does

SignalTabs uses Chrome's discard behavior.

Chrome exposes a tab state where page content is unloaded from memory while the tab remains visible in the tab strip. Chrome's own documentation says discarded tab content reloads the next time the tab is activated.

SignalTabs wraps that browser behavior in a product flow: detect eligible tabs across ordinary windows in the current Chrome Profile, show what will happen, let you adjust protection, then execute only after confirmation.

Eligible

What can be released

  • Background tabs in ordinary Chrome windows.
  • Pinned tabs, if they are not otherwise protected.
  • Background tabs that are playing audio or muted, with a visible risk warning.
  • Tabs across the same Chrome Profile, not across other browser profiles.
Protected

What SignalTabs protects

  • The current active tab in each window.
  • Tabs still loading.
  • Chrome internal pages and SignalTabs internal pages.
  • Tabs that are already discarded.
  • Sites you mark as keep active.
Estimate

Why the number says approximately.

SignalTabs does not request Chrome process, debugger, or system-memory permissions just to show a memory number. The MB/GB value is a conservative local estimate based on the number of tabs processed, not a measurement of exact system memory released.

Public wording should say "approximately," "estimated," "预计," or use "≈" near the number. It should never claim exact measured memory.
Tradeoff

What may change after release

The tab stays in the same window and position, but the page has to reload when opened. That means background audio may stop, and unsaved form input, scroll position, or temporary in-page state can be lost if the page did not save it.

Sources

Built on Chrome behavior, with product guardrails.

This page summarizes SignalTabs behavior and links to the relevant Chrome references for the underlying browser lifecycle.