Firefox Slow on Mac? Try These Fixes

Firefox on a Mac is in a strange spot. It’s not as tightly integrated as Safari, not as widely used as Chrome. But for users who care about privacy, customisation, or just want a non-Chromium alternative, it’s the obvious pick. When it slows down, the fixes are different from the other browsers — different cache locations, different settings, different gotchas.

Here’s the realistic checklist for getting Firefox back to fast on macOS.

Step one: confirm it’s actually Firefox

Activity Monitor → Memory tab. Look at Memory Pressure (bottom of window). If pressure is yellow or red, the issue is system RAM, not Firefox specifically. Quit other apps first.

If pressure is green and Firefox feels slow, sort Activity Monitor by CPU (top tab) and look at processes named “Firefox” and “Firefox Web Content.” High CPU on the parent Firefox process suggests an internal issue. High CPU on a Web Content process points to a specific tab.

Update Firefox

Firefox menu → About Firefox. It checks for updates and offers to install. You’d be surprised how often a slow Firefox is just an outdated one — Mozilla ships meaningful performance work in nearly every release.

Restart Firefox after the update so the new version is actually running.

Audit your tabs

Same story as every browser, but Firefox handles tabs slightly differently. Each tab is a process, but Firefox has built-in process limits to keep memory under control. Even so, 50+ active tabs add up.

Right-click any tab → Close Tabs to the Right, or Close Other Tabs. Bulk closure in seconds.

For tabs you want to remember without keeping them live, use Firefox’s bookmarks: cmd-shift-D bookmarks all open tabs as a folder. Close them all. Reopen the folder later as needed.

Clear cache and cookies (selectively)

Firefox’s clearing UI is at about:preferences#privacy. Scroll to “Cookies and Site Data.”

• Click “Clear Data…” → tick “Cached Web Content” only → Clear

That clears cache without signing you out everywhere. Cookies stay.

For a specific site, click “Manage Data…” in the same area, find the site, remove its data.

Firefox’s cache lives at ~/Library/Caches/Firefox/Profiles/<your-profile>.default-release/cache2/. On a Firefox running for a year, this can be 1-2 GB. Mostly harmless, but worth clearing if you’re chasing a specific problem.

Check extensions

Extensions are usually the biggest non-tab performance lever. Type about:addons in the address bar.

Disable extensions you haven’t used in a month. The biggest offenders:

• Heavy ad blockers with multiple filter lists (one good one is enough)
• Privacy extensions that overlap (uBlock + Privacy Badger + DuckDuckGo + Ghostery is overkill — pick two at most)
• Old extensions that haven’t been updated in a year
• “Enhancement” extensions for specific sites (YouTube, Twitter)

After disabling, restart Firefox and see how it feels. Re-enable the ones you actually miss.

Use the built-in Task Manager

Firefox has its own task manager: about:processes. It shows CPU and memory per tab and per extension. Way more useful than the system Activity Monitor for finding which Firefox process specifically is the problem.

If you spot an extension high in the list, that’s your culprit. If a single tab is using 2 GB+, that’s the tab to close (or fix).

Refresh Firefox

Mozilla has a built-in “Refresh Firefox” option that resets settings, customisations, and extensions while keeping bookmarks, history, passwords, cookies, and form autofill.

To use: about:support → “Refresh Firefox…” button on the right. Confirm. Firefox restarts with default settings.

This is much less destructive than people fear — your bookmarks and passwords are safe. It’s worth trying when Firefox feels weirdly broken and you can’t pin down why.

Clear caches across every browser at onceSweep clears Safari, Chrome, Firefox, and Arc caches in a single pass. Free download for Mac →

about:config tweaks that actually help

about:config is Firefox’s hidden settings page. Type that in the address bar, accept the warning, and you can change preferences directly. Most of these tweaks are placebo or actively harmful, but a few are genuinely useful:

1. gfx.webrender.compositor — set to true if not already. Improves rendering performance on macOS.
2. browser.sessionstore.interval — default is 15 seconds. If you have many tabs, increasing this to 60000 (60 seconds) reduces disk writes.
3. browser.cache.disk.enable — leave this true. Some guides suggest disabling disk cache for performance; it’s wrong. Disk cache makes pages faster on revisit.
4. network.http.max-persistent-connections-per-server — default is 6. Doesn’t usually need changing.

Don’t blindly apply random about:config tweaks from the internet. Most of them are speculative or based on outdated assumptions.

Hardware acceleration

about:preferences → General → Performance. If “Use recommended performance settings” is on, hardware acceleration is enabled by default — usually correct.

If you uncheck that, you can manually toggle “Use hardware acceleration when available.” Apple Silicon Macs almost always benefit from hardware acceleration on. Older Intel Macs sometimes have driver issues — try toggling it off and on to see which is faster on your machine.

After toggling, restart Firefox.

Check Firefox’s data folder size

Firefox stores everything in ~/Library/Application Support/Firefox/Profiles/. Open Finder, cmd-shift-G, paste that path. cmd-I on the Profiles folder for total size.

A healthy Firefox profile is 500 MB - 2 GB. If yours is 5+ GB, something’s grown. The biggest culprits:

• cache2/ — disk cache (clear via UI)
• places.sqlite — bookmarks and history. After years, can be 200+ MB. about:support → “Clear Startup Cache” can help.
• storage/default/ — site storage (LocalStorage, IndexedDB) for web apps. Heavy users of web apps like Notion or Figma accumulate this.
• OfflineCache — old offline content

Most of this is recoverable through Firefox’s UI. Don’t manually delete files — Firefox can rebuild what it needs but gets confused by manual deletions.

Disable telemetry if you want

about:preferences#privacy → scroll to “Firefox Data Collection and Use.” Uncheck the boxes if you’d rather not send Mozilla diagnostic data.

This isn’t really a performance fix — telemetry is lightweight — but some users prefer it off for privacy reasons. While you’re there, also consider:

• “Allow Firefox to send technical and interaction data” — uncheck
• “Allow Firefox to install and run studies” — uncheck

Firefox respects these settings.

Memory leaks: when Firefox grows over days

Like Slack and other long-running apps, Firefox can develop memory leaks if left running for many days. The fix is simple: quit Firefox completely (cmd-Q, not just close window) and reopen. Tabs come back via Restore Previous Session.

If you make this a once-a-week routine, Firefox stays much leaner.

When sites are specifically slow

Some sites work better in Chrome than Firefox (and vice versa). Real causes:

• Site uses Chrome-specific APIs Firefox handles differently
• Site has been tested less thoroughly in Firefox
• Site has user-agent sniffing that delivers an inferior version to Firefox

For one-off slow sites, you can try:

• Reader View (book icon in address bar) — strips heavy elements
• Right-click → “Open in Container” if you use Multi-Account Containers — sometimes helps
• Just opening that site in another browser if it really matters

It’s rarely worth tuning Firefox to make one specific stubborn site fast.

There’s a faster waySweep does the same hunt in seconds, with a preview before anything is removed. Try Sweep free →

Compare to Safari

If you’re considering switching: Safari uses noticeably less memory and battery on Mac because it’s tightly integrated with the OS. Firefox has better customisation, better privacy controls (Multi-Account Containers, more granular tracking protection), and is genuinely independent of the Chromium duopoly.

For Mac users who want Firefox’s features, the right approach is to keep it tuned (extensions, tabs, occasional refresh) rather than switch. The speed gap is small once Firefox is configured well.

A quick checklist

In order:

1. Update Firefox
2. Use about:processes to find the heavy thing
3. Audit extensions, disable unused ones
4. Clear cache via Settings → Privacy
5. Restart Firefox completely
6. Try Refresh Firefox if still bad
7. Tune hardware acceleration setting

Most users don’t need to go past step 4.

Sweep keeps Firefox’s cache (and Safari’s, Chrome’s, and Arc’s) clean in one pass. It also surfaces large files and forgotten downloads across your Mac so the system as a whole stays responsive — which directly helps Firefox feel faster, even though the browser itself is on you.