Brave Browser Using Too Much RAM? 7 Fixes That Work (2026)

Brave climbing past 2-4 GB of RAM is a tab-count problem, not a browser defect. Brave 1.91 runs on Chromium 149, which gives every website its own renderer process: 30 open tabs means roughly 30 processes. Memory Saver, Shields, and five settings changes claw most of it back, and the fastest fix takes 30 seconds.

Settings paths below were checked against Brave 1.91.168 (Chromium 149, released June 4, 2026) on June 9, 2026.

Find the Actual Memory Hog First

Before changing settings, spend 60 seconds in Brave’s task manager. Open Menu → More tools → Task Manager (or press Shift+Esc on Windows and Linux) and sort by Memory footprint. You will see one process per site, plus the browser process, the GPU process, and one process per extension.

If the top entries are individual sites you have not touched in hours, Fix 1 solves it. If a single extension sits near the top, jump to Fix 4. And if you landed here comparing browsers rather than fixing this one, the structural picture is in our Brave vs Chrome RAM breakdown.

Fix 1: Turn On Memory Saver

Brave ships a built-in tab sleeper — check that yours is actually on.

1. Open brave://settings/system (Menu → Settings → System)
2. Toggle on Memory Saver (if you don’t see it, type “memory” in the settings search box)
3. Add exceptions for sites that must never sleep, such as a web mail tab or a music player

Sleeping tabs show a dotted circle around the favicon; hover one and the preview card shows how much memory the sleep freed. Click it and it reloads. Discarding a tab kills its renderer process and releases nearly everything that tab was holding, so on a 30-tab session this is by far the largest single lever.

The limitation: Brave decides when a tab qualifies as inactive. There is no user-facing timer, and a long-standing GitHub feature request for one remains unimplemented. Fix 6 covers the workaround.

Fix 2: Keep Shields On (and Go Aggressive on Heavy Sites)

A surprising number of high-RAM reports trace back to Shields being globally disabled, usually during some earlier troubleshooting session and then forgotten. That is backwards for memory. Shields blocks ads, trackers, and third-party scripts at the network level before they reach the renderer, so each tab’s process holds a smaller DOM and fewer JavaScript heaps.

1. Open brave://settings/shields
2. Confirm Trackers & ads blocking is enabled; on ad-heavy sites, Aggressive blocks more third-party content than Standard
3. If one site breaks, click the lion icon in the address bar and lower Shields for that site only. Never globally.

Brave’s 1.91.168 release notes also list improved performance from caching compiled ad-block lists, so Shields is getting cheaper to run, not pricier.

Fix 3: Switch Off Background Features You Never Use

Brave bundles Rewards, Wallet, News, a VPN upsell, and the Leo AI assistant. None of these is a gigabyte. Wallet, for instance, only spawns a process when you actually open it. But together they add background work, toolbar surfaces, and new-tab content that you pay for in small slices:

• Brave News: open a new tab, click Customize at the bottom of the page, and toggle Show Brave News off. A feed of cards with thumbnails is real renderer weight on every new tab.
• Rewards: Menu → Settings → Rewards, toggle the ads options off. Hide the icon by right-clicking it and choosing Hide.
• Leo AI: Menu → Settings → Appearance → Leo AI Assistant, switch off the Ask Leo address-bar suggestion. Right-click the toolbar icon to hide it.
• Wallet: right-click the wallet icon and hide it. Unopened, it costs little; hidden, it costs nothing and stops tempting misclicks.

Brave has also announced Brave Origin, a de-bloated paid edition ($59.99 one-time, free on Linux, announced in early June 2026) that strips all of the above at the build level. The free toggles get you most of the way there.

Fix 4: Audit Extensions in the Task Manager

Every extension you install runs its own process, in Brave exactly as in Chrome. With the task manager from the diagnosis step still open, look for extension entries holding 200 MB or more.

1. Open brave://extensions
2. Disable the top memory consumer, wait a minute, re-check the task manager
3. Repeat until the heavy one is identified, then decide whether its job justifies its footprint

Grammarly-style writing assistants and video downloaders are frequent offenders because they inject scripts into every page. One bloated extension can outweigh ten ordinary tabs.

Fix 5: Toggle Hardware Acceleration and Background Apps

Two switches live at brave://settings/system next to Memory Saver:

• Use hardware acceleration when available: this shifts rendering work between GPU and CPU. Disabling it sometimes lowers reported memory, but it can raise CPU load and make video playback worse. Toggle it, relaunch, measure in the task manager, and revert if your machine feels slower. This is a try-and-measure fix, not a guaranteed win.
• Continue running background apps when Brave is closed: switch this off if Brave processes linger in your OS task manager after you quit the browser.

Fix 6: Add a Timer-Based Tab Suspender

Brave’s Memory Saver works, but it keeps two decisions to itself: when a tab counts as inactive, and which tabs deserve protection beyond your manual exception list. A dedicated tab suspender from the Chrome Web Store (Brave installs CWS extensions directly) puts both under your control: suspend after a fixed inactivity window, whitelist per domain, and see how much RAM suspension is saving you.

This is the same category that exploded after The Great Suspender was pulled from the store; the modern, MV3-safe options are covered in our Great Suspender alternative guide. For a Brave-specific breakdown of what the built-in misses versus a dedicated extension, see suspending tabs in Brave: Memory Saver vs extensions.

How SuperchargePerformance Helps

SuperchargePerformance is our tab suspender, built and tested for Chrome. Brave installs the same Chrome Web Store package and supports the chrome.tabs.discard() API, which triggers the same tab-discarding machinery as its own Memory Saver, though our testing happens on Chrome.

• Suspends inactive tabs on a timer you set: 15 or 5 minutes free, custom seconds on PRO
• Skips tabs that should not sleep: active, pinned, playing audio, holding unsaved form input, plus auto-protected web apps like Figma, Notion, and Slack
• Keeps a running total of the RAM suspension has saved, right on the toolbar icon
• 100% local, zero data collection, free core, no account

Fix 7: Rebuild a Bloated Profile

A profile that has accumulated years of cache, site data, and half-corrupted state can hold memory no settings change recovers.

Start cheap: Menu → Settings → Privacy and security → Clear browsing data, select All time, and clear cached images and files. If memory usage is still abnormal with few tabs and no extensions, create a fresh profile via Menu → More tools → Add new profile and test the same workload there. A fresh profile that uses half the memory of your old one answers the question. Migrate bookmarks and let the old profile go.

Why Brave Still Uses Gigabytes: The Architecture

Brave inherits Chromium’s Site Isolation security model, which puts every website in its own sandboxed renderer process. This is a deliberate defense against Spectre-class attacks, and Brave does not weaken it. The consequence is that memory scales with open tab count across every Chromium browser: Brave, Chrome, and Edge all behave this way, and since Firefox switched on its own site isolation (Fission), it largely does too. The full cross-browser picture is in which browser uses the least RAM in 2026.

So a Brave session reading 3 GB with 40 tabs open is the architecture working as designed, not a leak. Shields makes each process lighter than Chrome’s equivalent. It cannot make 40 processes cost what 8 would.

Where that leaves you:

• If RAM grows with tab count → Fix 1, then Fix 6 for timer control. Suspension attacks the process count directly.
• If a handful of tabs already hurts → Fix 4 first; one heavy extension outweighs many tabs.
• If you suspect the browser itself → Fix 7’s fresh-profile test settles it in five minutes.
• If Brave still doesn’t fit your machine → an 8 GB laptop may simply be better served by the measurement methodology in our Brave vs Chrome RAM comparison than by another settings pass: measure, then decide.