Mac Slow With Lots of Tabs Open? Here's How Many Are Too Many

Some people close every tab when they’re done. Others have 200 tabs across three browser windows and a horizontal scrollbar of unreadable favicons. The second group includes some of the most productive people I know, and it also includes people whose Macs are perpetually slow. The difference isn’t tab count — it’s what those tabs are doing in the background.

Most “Mac is slow” problems on a daily-driver machine come back to browser tabs. Not because the browser is bad, but because tabs do meaningful work even when you’re not looking at them.

What a Tab Actually Costs

A tab isn’t free, even when sitting in the background. Modern browsers run a process per tab (or per group of related tabs). Each process holds:

• The HTML, CSS, and JavaScript of the page, parsed into memory
• Image and video data in decoded form
• Service workers that may keep running after the tab is “closed”
• WebSocket connections for real-time updates (Slack, Twitter, Linear)
• IndexedDB / LocalStorage for offline data
• Audio and video codec state if media has played
• Web font assets (sometimes 1-3MB per font family)

A simple article page in a background tab might use 30-80MB. A Gmail tab uses 200-400MB. A Figma tab can hit 1GB. A YouTube tab with HD video paused holds the entire video buffer in memory.

For Chrome on a 16GB Mac, the ceiling is roughly 100-200 tabs before performance degrades noticeably. For Safari, the ceiling is higher because of more aggressive tab discarding.

Free up RAM in one clickSweep frees inactive memory and pauses runaway processes. Get Sweep free →

The Real Math: RAM Per Tab

Open Chrome with one tab. Open Activity Monitor. Note the total memory used by all Chrome processes. Now open 50 tabs of varied sites — news, social, web apps, video.

Subtract. Divide by 50.

Typical results in 2026:

• Average tab on Chrome: 80-150MB
• Heavy web app tab: 300MB-1GB
• Idle simple page: 30-50MB
• YouTube/Twitch: 200-500MB even paused
• Google Docs / Sheets: 200-400MB
• Figma / Linear / Notion: 300-800MB

Multiply by your tab count to get actual RAM use. For 100 tabs averaging 100MB, that’s 10GB just for tabs. On a 16GB Mac, that’s most of your memory before macOS, your other apps, or any system services have any.

Why “Sleeping” Tabs Aren’t Free

Both Chrome and Safari have tab discarding features that pause inactive tabs. They help, but with caveats:

1. Service workers keep running even when the tab is discarded. Sites like Slack, Twitter, and Discord have service workers that maintain connections regardless
2. Memory comes back when you click the tab — you’ll wait for the reload
3. Unsaved form state can be lost when a tab is discarded
4. Some sites detect discarding and reload aggressively

For Chrome: Settings > Performance > Memory Saver. For Safari: Tab discarding is more aggressive but invisible — Safari decides on its own.

Even with discarding, the tab still has metadata in memory: title, URL, favicon, history state. Multiply by 200 tabs and the tab metadata alone is hundreds of MB.

The Tab Categories Worth Recognizing

Power tab users tend to have several tab categories without realizing it:

1. Active work — 5-10 tabs you’re actively using
2. “Reference” — docs, Stack Overflow, articles you might consult
3. “To read later” — articles you intended to read
4. Web apps — Gmail, Slack, calendar, chat
5. Project context — tabs related to a specific task
6. Forgotten — tabs you opened weeks ago and never closed

Categories 3 and 6 are pure waste. They consume RAM and you’ll never look at them.

The bookmark-and-close approach handles categories 3 and 6:

• For “to read later”: save to a read-later service (Pocket, Instapaper, Reading List in Safari)
• For “forgotten”: just close them. If you didn’t miss them in two weeks, you don’t need them
• For “reference”: bookmark them in a folder

This regularly cuts tab counts by 50-70% with no loss of actual workflow.

Tab Groups: Helpful but Not a Performance Cure

Both Chrome and Safari have tab groups. They’re great for organization. They are not free.

A tab group with 30 tabs uses the same memory as 30 individual tabs. The visual organization helps you find things, but the underlying processes are the same.

Where tab groups do help:

• Letting you collapse groups (hides them visually but doesn’t free memory)
• Naming and color-coding for context
• Saving groups for later (in Chrome — saves and closes, freeing actual memory)

In Chrome, right-click a tab group > “Save group” turns it into a bookmark folder you can reopen later. This actually closes the tabs and frees the RAM.

Specific Web Apps to Watch For

Some web apps are dramatically heavier than others:

• Figma — 500MB-1.5GB per file open
• Linear — 300-600MB per workspace
• Notion — 200-500MB per workspace
• Google Docs — 200-400MB per doc, more for large ones
• Trello — 200-300MB per board
• Slack web — 500MB-1GB
• Discord web — similar to Slack
• Twitter / X — 200-400MB with active timeline
• YouTube with playlist — 300-500MB
• Google Sheets with formulas — can hit 1GB easily

If you have multiple of these open simultaneously, your tab budget is much smaller than for content sites.

For chat apps especially, consider native apps. Slack desktop is heavy too, but it’s a single optimized instance — no tab metadata duplication.

Skip the manual huntSweep finds the buildup slowing your Mac and clears it in seconds. Download Sweep free →

How Many Tabs Is “Too Many”?

There’s no universal answer, but rough guidelines for 2026 macOS:

• 8GB Mac: 20-40 tabs maximum, fewer if running heavy web apps
• 16GB Mac: 50-100 tabs comfortable, depending on tab mix
• 32GB Mac: 200+ tabs okay if mostly light pages
• 64GB+ Mac: budget basically unlimited for tabs, but memory pressure can still happen with the wrong mix

These assume you’re also using the Mac for other things. If your only app is the browser, double these numbers.

The metric to watch isn’t tab count — it’s Memory Pressure in Activity Monitor’s Memory tab. Green is fine regardless of tab count. Yellow means swap is starting. Red means you need to close things now.

A Quick Sweep Through Your Tabs

A useful 5-minute exercise to reclaim performance:

1. Open every browser window
2. For each, view tab overview (Cmd+Shift+\ in Safari, similar in Chrome)
3. Close every tab you don’t recognize
4. For each cluster of related tabs, ask: “Am I using this today?”
5. Bookmark anything you might want later
6. Close everything else

Most people find they had 60-80% noise. Cutting that recovers 5-10GB of RAM.

When Heavy Tabs Are Unavoidable

Some workflows genuinely need many heavy tabs open at once. Designers in Figma with multiple files. Developers with multiple Linear/Github/Slack workspaces. Researchers with many sources.

For these, the strategies are different:

• Use multiple browsers strategically — Chrome for one workspace, Safari for another. This isolates the memory
• Use browser profiles — Chrome’s profile feature creates isolated sessions, each with its own memory
• Run on a Mac with 32GB+ — sometimes hardware is the answer
• Be ruthless with auto-refresh tabs — sites that refresh themselves are extra heavy
• Pin web apps to the Dock as PWAs — Safari and Chrome both support this, and PWAs are slightly lighter than tabs

There’s a faster waySweep diagnoses what’s eating your performance and clears it in seconds. Try Sweep free →

What Your Browser Tells You

Both Chrome and Safari have built-in task managers showing per-tab resource use:

• Chrome: Window menu > Task Manager
• Safari: Window menu > Activity Monitor (inside Safari)

Sort by Energy Impact. The tabs at the top are eating your battery and CPU. Often, one or two tabs disproportionately impact performance — closing just those gives you most of the benefit.

Make this a habit. When the Mac feels slow, check the in-browser activity monitor first. Find the worst offender. Decide whether you really need it open.

A Diagnostic for “Too Many Tabs” Slowness

When your Mac is slow and you suspect tabs:

1. Check Activity Monitor’s Memory tab. What color is the pressure graph?
2. Check your browser’s task manager. What’s the heaviest tab?
3. Close it. Watch memory pressure
4. If still red/yellow, close more. Start with anything you didn’t recognize
5. Restart the browser if memory doesn’t recover after closing tabs (long sessions accumulate leaks)
6. Save groups for later instead of leaving them all open

Long-Term Habits

The habits that keep tabs from being a perpetual drag:

1. One project per window. When the project’s done, close the window
2. Use bookmarks like a real tool. Folders organized by topic
3. Use a read-later service. Stop using browser tabs as a queue
4. Restart your browser daily. Long-running sessions accumulate memory leaks
5. Quit your browser at the end of the day. Restoring sessions on launch is fast and frees overnight RAM

Browsers have gotten dramatically better at handling many tabs since 2018. Chrome’s Memory Saver, Safari’s tab discarding, Firefox’s tab unloading — all of them help. But they all rely on you closing things eventually. The browser can pause a tab; it can’t decide that you don’t need it.

Sweep handles the macOS side — clearing browser caches, finding old downloads, surfacing what’s really using your RAM. Together with sensible tab habits, your Mac stays fast even on a base-spec machine. The math is in your favor: 30 well-managed tabs are dramatically lighter than 200 forgotten ones, and the productivity hit from closing the noise is essentially zero.