How to Speed Up Chrome on Your Mac

Chrome has a reputation for being a memory hog on Mac. Mostly deserved — but it’s tunable. With a few minutes of cleanup and the right settings, Chrome can run noticeably faster, use less RAM, and stop dragging the rest of your Mac down.

Here’s the realistic checklist, in order of impact.

First, an honest assessment

Open Activity Monitor and sort by Memory. Count how many “Google Chrome Helper (Renderer)” processes you see. That’s roughly your tab count plus a few helpers. If you’ve got 40+, the problem is straightforward: you have too many tabs.

Each tab in Chrome is its own process — partly for security, partly for stability. The downside: 40 tabs = 40 processes = a lot of RAM. There’s no Chrome setting that makes this fundamentally different. Tab discipline is the single biggest performance lever you have.

Use Chrome’s built-in Memory Saver

Chrome has a feature called Memory Saver that puts inactive tabs to sleep. They stay in your tab strip but stop using memory. They reload when you click them.

To enable: chrome://settings/performance — toggle Memory Saver on. Pick the level (Moderate, Balanced, Maximum). Maximum is fine for most people.

You can also exclude specific sites from being put to sleep — useful for things you want to stay live (Slack, dashboards, music players).

This alone can cut Chrome’s memory use in half if you’re a heavy tab user.

Energy Saver mode

Same settings page (chrome://settings/performance) has Energy Saver. Two modes:

• “When my battery is at 20% or lower”
• “When my computer is unplugged”

Turning this on extends battery life by reducing background activity, animation smoothness, and video frame rates slightly. Cosmetic on most Macs, but real on laptops.

Audit your extensions

Extensions are the second-biggest performance lever. Every extension runs in every tab and consumes memory. Some extensions have permission to “read and modify all your data on websites” — those are doing significant work behind the scenes.

Go to chrome://extensions/. For each one, ask: have I used this in the last month? If no, disable it (toggle off, don’t remove yet — you might miss it).

The worst offenders for performance:

• Ad blockers with multiple filter lists (one is plenty)
• “Page improvers” for major sites (YouTube enhancers, Twitter modifiers)
• Screenshot tools that monitor every page
• “Productivity” extensions with always-on overlays
• Any extension that hasn’t been updated in two years

After disabling, reload all your tabs and see how Chrome feels. Usually a noticeable difference.

Clear the cache (and a bit more)

Chrome caches resources to speed up repeat visits. When the cache gets bloated or corrupted, individual pages can feel slower. Clear it:

1. cmd-shift-Delete
2. Basic tab
3. “Cached images and files” only
4. Time range: All time
5. Clear data

You’ll lose nothing important. Cookies and history remain (since you only ticked cache).

If you have multiple Chrome profiles (avatar in top right), repeat for each profile — caches are per-profile.

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

Reset Chrome’s flags if you’ve been tinkering

If you’ve ever set custom flags at chrome://flags, they can stick around through updates and cause weird performance regressions. To reset:

1. Visit chrome://flags
2. Click “Reset all” at the top right
3. Restart Chrome

Default flags are fine for almost everyone. Custom flags are mostly for developers testing experimental features.

Disable hardware acceleration (or enable it)

This one’s counterintuitive — sometimes turning it off helps, sometimes turning it on does.

chrome://settings → System → “Use graphics acceleration when available.”

The default is on. If Chrome is glitchy or slow to render, try off. If it’s already off and pages render slowly, try on. Restart Chrome after toggling.

Apple Silicon Macs almost always benefit from this being on. Older Intel Macs with discrete GPUs sometimes don’t.

Update Chrome

Sounds obvious, but Chrome’s auto-update can be paused if you’ve been ignoring restart prompts. chrome://settings/help — it’ll tell you if you’re current and prompt to relaunch if not.

Chrome ships meaningful performance improvements every few months. Being two major versions behind can mean missing real speed gains.

Update macOS

Chrome runs on top of macOS. If your macOS is several versions old, you’re missing system-level improvements (memory management, networking, GPU drivers) that affect Chrome too. System Settings → General → Software Update.

The Chrome Task Manager

When something specific is slow, use Chrome’s built-in Task Manager: Window → Task Manager (shift-Esc on macOS — though the menu is the reliable way).

You’ll see CPU and memory per tab and per extension. Sort by memory: top offenders revealed. End the worst ones (or just close those tabs).

This is far more useful than the system Activity Monitor for diagnosing Chrome specifically.

Profile management

If you have multiple Chrome profiles you don’t actively use, consider deleting them. Each profile keeps its own cache, history, extensions, and storage. Five profiles you don’t use can collectively eat 5+ GB of disk and add startup time.

To remove: chrome://settings → “You and Google” → click your avatar → “Customize profile” → there’s a “Delete” option for non-current profiles.

Reduce Chrome’s startup load

Chrome → Preferences → On startup. Options:

• “Open the New Tab page” — fastest startup
• “Continue where you left off” — slowest, restores all previous tabs
• “Open a specific page or set of pages” — opens just what you list

If you’ve been seeing slow Chrome launches, “Continue where you left off” is restoring 50 tabs at startup. Switch to New Tab page and use Memory Saver to manage tabs you want to revisit.

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

Disable Chrome’s prerendering if it’s noisy

Chrome prerenders pages it thinks you’re about to visit. This usually makes things faster, but on slow networks it can cause weird stalls.

chrome://settings/cookies — find “Preload pages for faster browsing and searching.” Toggle it off if you suspect it’s causing issues. Most users should leave it on.

What about RAM limits?

There’s no built-in setting to cap Chrome’s RAM. Memory Saver is the closest thing — it discards inactive tabs to keep usage down.

There are extensions that claim to “limit Chrome’s RAM” but they’re mostly placebo. Chrome’s memory usage is determined by what tabs and extensions you have open. Discipline plus Memory Saver is the realistic answer.

When the issue isn’t Chrome at all

If Chrome’s slow but Activity Monitor shows it using normal CPU and memory, the bottleneck might be:

• Your network — try the speed test (fast.com)
• Your overall RAM — if memory pressure is yellow/red across the system, every app feels slow
• Your SSD being nearly full — under 15% free, everything slows
• Spotlight reindexing — mds_stores and mdworker_shared eat I/O for a few hours after big changes

Fix those system-level things and Chrome’s speed comes back too.

A quick checklist

In order, fastest to slowest impact:

1. Enable Memory Saver
2. Audit extensions, disable ones you don’t use
3. Close tabs you’ve forgotten about (and use Tab Groups to save sets)
4. Clear cache
5. Update Chrome and macOS
6. Reset flags if you’ve tinkered
7. Reduce profile count

Most of this takes 10 minutes total. The improvement is usually obvious.

Why bother instead of switching browsers

You can. Safari is faster on a Mac for many users, especially battery-wise. Arc is a Chromium-based alternative with cleaner tab management. Brave handles extensions like Chrome but with better default privacy.

But if you’re already deep in Chrome (extensions, profiles, sync, password manager all wired in), tuning it is faster than switching. The above checklist gets you 80% of the way to “Chrome doesn’t feel like a hog anymore.”

Sweep won’t tune Chrome’s settings — that’s on you. What it does is keep cache and disk usage from compounding the problem, across Chrome and any other browser you have installed. One scan, all four major Mac browsers cleaned in one pass, with a preview before anything is removed.