Suspend Tabs in Brave: Memory Saver vs Extensions (2026)

Key takeaways

• Find Brave’s built-in suspender under Settings → System → Performance as Memory Saver, with a toggle and an exceptions list
• Accept that Memory Saver runs on Chromium’s own heuristics with no timer you can set
• Install a suspender extension when you want timer control and app protection on top of Shields

Brave has a built-in tab suspender. It is called Memory Saver, it lives under Settings → System, and it discards inactive tabs so they stop consuming RAM until you click back. What it lacks is control: no inactivity timer, no automatic protection for work apps. A suspender extension from the Chrome Web Store adds both, freeing 90-95% of each idle tab’s memory on a schedule you set.

Where Brave Hides Its Tab Suspender

Open brave://settings/system (Menu → Settings → System → Performance) and look for Memory Saver. Toggle it on, and Brave deactivates tabs you have not used for a while. When you return to a suspended tab, it reloads from the network.

Two related controls are worth knowing:

• Exceptions list. You can add sites that should always stay active. Useful for a web mail tab or a music player you never want reloaded.
• Inactive tab indicator. Suspended tabs show a dotted circle around the favicon. If that annoys you, turn it off under Settings → Appearance → Tabs.

One quirk: the setting briefly vanished from the System section in a 2024 release (Brave 1.69) and was only reachable through settings search until a fix landed. If your version does not show it where expected, type “memory saver” into the settings search box.

What Memory Saver Does Well, and Where It Stops

Memory Saver is upstream Chromium code, the same machinery behind Chrome’s version of the feature. It decides when to discard a tab based on its own heuristics, and that decision is not yours to tune. Brave exposes no slider for “suspend after N minutes.”

Users have asked. A GitHub feature request for a configurable timer has been open since 2023. A separate 2025 issue, filed against Brave 1.80, complains that even the most aggressive mode leaves ten idle tabs holding 100MB+ each for long stretches; Brave tagged it low-priority, awaiting upstream Chromium changes. As of Brave 1.91 (Chromium 149, June 2026), neither has shipped.

The result is a suspender that works, but on its own clock. If your machine is not under memory pressure, idle tabs can sit fully loaded for a long time. That is fine on a 32GB desktop. On an 8GB laptop running Brave next to a video call, it means the relief arrives later than you would choose.

Worth keeping in perspective: Brave already starts from a lighter baseline than stock Chrome because Shields strips ads and trackers before they reach the renderer. Our Brave vs Chrome RAM breakdown covers why, and the cross-browser RAM comparison shows where that lands Brave against Edge and Firefox. Shields reduces what each tab weighs. Suspension reduces how many tabs weigh anything at all. They are different levers.

Memory Saver vs a Suspender Extension in Brave

The mechanism row is the important one. Both tools call the same Chromium discard machinery, so a suspended tab behaves identically either way: it stays visible in the tab bar, keeps its title and favicon at a cost of roughly 5-10MB, and reloads when clicked. The difference is who decides when, and what gets spared.

When the Built-In Option Is Enough

Skip the extension if any of these describe you:

• You keep under 10-15 tabs open. Shields already trims each tab’s footprint, and at low tab counts the RAM at stake rarely justifies new software.
• You want zero added permissions. A suspender extension needs broad access to manage tabs. Memory Saver needs nothing beyond the browser you already trust.
• You only care about pressure relief, not scheduling. If “Brave eventually frees memory when things get tight” meets your bar, the toggle plus a few exceptions does the job.

This is the honest case for native: it is free, already installed, and maintained by the browser vendor. The category has earned some caution too. The most popular suspender of the last decade was removed from the Chrome Web Store for malware after changing owners, which is a good reason to prefer either the built-in or an extension whose data practices you have checked.

What an Extension Adds on Brave

Installing works exactly like Chrome: open the extension’s Chrome Web Store page in Brave and click Add to Brave. Brave’s documentation states that any extension in the Chrome Web Store will also work in Brave, and the company has even committed to keeping select Manifest V2 extensions like uBlock Origin alive after Chrome dropped MV2 support. SuperchargePerformance is built and tested against Chrome; the chrome.tabs.discard() API it relies on is part of the Chromium platform Brave ships.

What you gain over the native toggle:

• A timer you choose. 15 minutes on the low level, 5 minutes on the default, custom seconds with PRO. Idle tabs are freed before pressure builds, not in response to it.
• Protection without list maintenance. 25+ web apps are auto-protected out of the box: Figma, Notion, Slack, Discord, Google Docs, Spotify, WhatsApp Web, Zoom, and more. Tabs playing audio, pinned tabs, and tabs with unsaved form input are skipped automatically.
• Visible results. A toolbar badge counts estimated RAM freed, so you can tell whether the thing is working instead of guessing.

One overlap to flag: SuperchargePerformance also blocks ads and trackers via declarativeNetRequest. Brave Shields already does that natively, so on Brave the suspension features carry the value. Everything is toggleable per feature and per site, so you can run it as a pure suspender and leave blocking to Shields.

Run Both, or Pick One?

They coexist cleanly. Both paths end at the same Chromium discard call, and a 5-minute timer fires long before Memory Saver’s heuristics typically act, so the extension leads and the native feature becomes a backstop. There is no double-suspension failure mode; a discarded tab is simply discarded.

So the decision comes down to tab habits. If you hover around a dozen tabs and never feel Brave slow down, turn Memory Saver on, add your two or three precious sites to the exceptions, and stop there. If you live at 30+ tabs, run unsaved work in browser apps, or want idle tabs gone in minutes rather than whenever Chromium decides, add a timer-based suspender on top. And if your real question is whether Brave itself is the lightest place to keep those tabs, start with the browser RAM comparison before optimizing inside it.