Browsers
Why Your Browser Is Eating Your Mac's RAM
Browsers are RAM hogs by design. Here's what's actually happening, why each tab costs so much, and how to keep usage reasonable without giving up tabs.
Open Activity Monitor on a typical Mac and sort by Memory. Whichever browser you’re running is almost certainly in the top three, and on most days it’s number one. This isn’t a bug — it’s how modern browsers work. Each tab is essentially its own program. Multiply that by the 30 tabs you’ve accumulated, add the extensions, and you’ve got 4-8 GB of memory just for “browsing the web.”
Here’s why, and what you can actually do about it without becoming a tab minimalist.
Why each tab costs so much
Modern browsers run each tab in its own process for security and stability. If one tab crashes or gets compromised, it can’t take down the whole browser. The cost: every tab needs its own slice of memory for:
- The page’s HTML and CSS
- The JavaScript engine state
- The DOM (the structured representation of the page)
- Any images, fonts, and assets
- The web rendering engine instance
- Tracking by extensions installed in that tab
A simple article page might use 100 MB. A heavy web app like Gmail, Figma, or Notion can sit at 500 MB - 1 GB per tab. A tab with autoplay video and ads can hit 800 MB easily.
Twenty tabs, average 250 MB each, equals 5 GB. That’s just the tabs. The browser itself needs another 500 MB - 1 GB.
The “browser uses my whole computer” feeling
Most Mac users buy 16 GB RAM as the comfortable middle ground. With macOS itself using 2-3 GB, system processes another 1-2 GB, and miscellaneous apps another 2-3 GB, you’ve got maybe 8 GB free for browsers and work apps. A heavy browser session can eat all of that.
The result: memory pressure climbs to yellow, swap usage starts climbing, and your Mac feels slow. Switching apps takes longer. Apps beachball. Even closing tabs takes a moment.
This isn’t because the browser is “broken.” It’s because you’ve asked it to keep 50 things alive simultaneously.
Chrome vs Safari vs Firefox vs Arc
In rough order of memory use per tab:
- Safari — leanest by a meaningful margin on Mac. WebKit on Apple Silicon is heavily optimised.
- Firefox — middle of the pack. Process model is similar to Chrome but with built-in process limits.
- Arc — based on Chromium. Similar to Chrome with some additional UI features that add slight overhead.
- Chrome — heaviest, especially with multiple profiles and many extensions.
- Edge / Brave / Opera — all Chromium-based, similar to Chrome.
Real numbers: 30 tabs of typical content uses roughly 4 GB in Safari, 5 GB in Firefox, 6-7 GB in Chrome. Your mileage varies based on which sites are heavy.
Extensions multiply the cost
Every extension runs in every tab. Five extensions across thirty tabs means 150 extension instances. Heavy extensions add 20-50 MB per tab. Lighter ones add 5-10 MB.
This is why “I just have a few extensions” is misleading. The cost is per-tab, not per-extension.
The worst memory offenders:
- Ad blockers with multiple filter lists (one strong list is enough)
- Tools that read all page content (translation extensions, productivity overlays)
- Extensions with large background databases (some password managers, some screenshot tools)
- “Site improvers” for sites you don’t use often
Auditing extensions is one of the highest-leverage things you can do. Disable anything you haven’t deliberately used in 30 days.
Memory savers built into each browser
Modern browsers have built-in mechanisms to reduce memory usage. They’re often off by default or under-used.
Chrome: chrome://settings/performance → enable Memory Saver. Chrome puts inactive tabs to sleep, freeing their memory. Tabs reload when clicked. Can be set to Moderate, Balanced, or Maximum.
Safari: No explicit memory saver, but Safari’s tab discarding is pretty aggressive automatically. iCloud Tabs syncing means you can close a tab and reopen it later from your tab history.
Firefox: Tab Unloader automatically discards inactive tabs when memory is low. about:unloads shows what’s been unloaded. about:config has browser.tabs.unloadOnLowMemory (default true).
Arc: Has tab archiving — tabs auto-archive after a configurable period, freeing memory.
Use whichever your browser provides. Memory Saver alone can cut Chrome’s memory use in half on a tab-heavy session.
The cache is not the memory
A common confusion: clearing your browser’s cache doesn’t free RAM. The cache is on disk, not in memory. It’s a separate problem.
Cache helps page load times by storing copies of resources. Memory is what active tabs use right now. Clearing one doesn’t directly help the other.
That said: if your browser’s eating both lots of RAM and lots of disk, both problems compound the system’s overall slowness. Tackle each.
Tab groups and sessions
The realistic answer to “I need 50 tabs open” is usually “you need 50 tabs accessible, not 50 tabs running.”
- Safari Tab Groups: Window → Tab Groups → Save current tabs. Keeps a named group you can recall. Closed tabs don’t use memory.
- Chrome Tab Groups: Right-click a tab → Add Tab to New Group. Groups can be collapsed (still active) but not properly hibernated unless you also use Memory Saver.
- Firefox: No native tab groups, but Containers and Tree Style Tabs extensions help. Bookmarks-as-folders works as a manual session manager.
- Arc: Spaces and Pinned Tabs serve a similar purpose. Daily tabs auto-archive.
The mental shift: tabs aren’t bookmarks. Use bookmarks (or tab groups) for things you want to find later. Use tabs for things you’re actively reading.
Web apps as separate apps
If you have one or two web apps you keep open all day (Gmail, Slack, Notion, Linear), consider running them as standalone Progressive Web Apps. macOS supports PWA installation from any browser:
- Safari (Sonoma 14+): File → Add to Dock. The site becomes its own app icon.
- Chrome: address bar shows an “install” icon for PWA-ready sites. Click it.
- Arc: has “boost” and external apps features.
PWAs run in their own process, separate from your main browser. They can be quit independently. Memory accounting is cleaner. Some Mac users move 4-5 web apps to PWAs and find their main browser much lighter.
Diagnose with the browser’s task manager
System Activity Monitor shows you total browser memory but not per-tab.
- Chrome: Window → Task Manager (or shift-Esc)
- Safari: Window → Activity (cmd-option-A)
- Firefox: about:processes
- Arc: Settings → Performance → similar to Chrome’s
These show CPU and memory per tab and per extension. The big tabs are usually obvious. End them or reload them.
When to actually quit the browser
Browsers are meant to run for a long time. But every browser has small memory leaks and long-term growth. A weekly habit of quit-and-reopen (with session restore) keeps things lean.
This is especially true for:
- Anyone with many always-open tabs
- Anyone running 5+ extensions
- Anyone who keeps the browser open for weeks at a time
Quit completely (cmd-Q), wait a few seconds, reopen. Memory drops noticeably. Tabs come back via session restore.
When the system is the bottleneck, not the browser
If your Mac has 8 GB RAM, no browser will feel “lean” with 30 tabs. The math doesn’t work — the demands of modern web apps simply exceed what 8 GB can serve while macOS also needs RAM for everything else.
Options:
- Reduce demand: fewer tabs, fewer extensions, lighter browser (Safari)
- Live with swap: some performance cost, but workable for many users
- Upgrade RAM next time you buy: 16 GB minimum, 24-32 GB if you’re a power user
You can’t add RAM to an Apple Silicon Mac after purchase. Plan accordingly.
What “fixing” your browser memory usage looks like
A realistic outcome:
- Audit extensions: drop 3-5 you don’t actively use
- Enable your browser’s Memory Saver (or equivalent)
- Adopt Tab Groups for “tabs I want to access later”
- Quit and restart your browser weekly
- Run a fresh cache clear monthly
Result for a typical user: browser memory drops from 6 GB to 3-4 GB during a normal session. Memory pressure stays green. The Mac feels fast.
A note on “memory cleaners”
A bunch of apps in the Mac App Store promise to “free up RAM” or “boost browser memory.” Most of them just call macOS’s purge command (which is free). Some are essentially placebo. A few are scams.
Sweep’s speed boost feature does flush inactive memory, identify the heaviest processes, and suggest pausing runaway ones — but the real work for browser RAM is reducing demand, not flushing cache. We’re honest about that. The cache and storage cleanup is what we save you time on; the tab discipline is on you.