Under Open at Login , look for Google Chrome . Select it and click the minus (–) button to remove it. Chrome will still launch fine when you open it manually. This just stops it from auto-launching at login.
Step 3: Disable Chrome’s Background Helpers
Under Allow in Background , look for any entries labeled Google Chrome or Google Chrome Helper . Toggle each one off . These processes keep Chrome running after you close every window, consuming memory and battery with no visible indication they’re there.
Note: Disabling background helpers means web apps that send push notifications (like Google Meet or certain web-based tools) won’t deliver notifications when Chrome is closed. If you rely on those, leave the specific helper enabled.
Step 4: Change Chrome’s Startup Behavior
Open Chrome, go to chrome://settings/onStartup, and select Open the New Tab page instead of Continue where you left off . If you want specific sites to load at launch, choose Open a specific page or set of pages and keep the list short. Three or fewer is ideal.
Expected result: Chrome opens in 2–4 seconds instead of 10–30 seconds on your next launch.
Fix 2: Stop Chrome from Freezing Your Mac {#fix-2}
Why macOS Memory Pressure Is Different from Windows
On Windows, Chrome can lean on virtual memory aggressively without much visible penalty. macOS works differently. It compresses memory first, then writes to disk (swap). The whole system slows down when it hits what Apple calls memory pressure . Chrome’s multi-process model, where every tab and extension gets its own process, makes it one of the fastest apps to push an <a href=”https://www.switchingtomac.com/is-8gb-ram-good-enough-for-a-mac/”>8GB Mac</a> into the yellow or red zone.
You can watch this happen in real time.
Step 1: Check Memory Pressure in Activity Monitor
Open Activity Monitor (go to Applications > Utilities > Activity Monitor , or press Cmd + Space and type “Activity Monitor”). Click the Memory tab. Look at the Memory Pressure graph at the bottom.
Green : You’re fineYellow : macOS is under strain. Chrome is likely a contributorRed : Your Mac is actively struggling; expect beach balls
Step 2: Identify Which Tabs and Extensions Are Eating Memory
In Chrome, open the built-in Task Manager: go to Window > Task Manager (or press Shift + Esc on a keyboard with a Search key). Click the Memory Footprint column header to sort by memory usage, highest first.
Any tab using more than 500MB is worth closing. Any extension using more than 100MB deserves a closer look.
Step 3: Enable Memory Saver
Go to chrome://settings/performance and make sure Memory Saver is toggled on . With Memory Saver enabled, Chrome automatically suspends inactive tabs and frees up RAM for the ones you’re actually using. On 8GB Macs, this single setting can keep you out of memory pressure during a normal browsing session.
Step 4: Enable Energy Saver (MacBook Users)
On the same chrome://settings/performance page, make sure Energy Saver is enabled. This reduces Chrome’s background activity when your MacBook is on battery. It prevents Chrome from triggering <a href=”https://www.switchingtomac.com/how-to-stop-a-macbook-from-overheating/”>thermal throttling</a> that drags down the whole system.
Step 5: Disable High-Memory Extensions
Go to chrome://extensions. Toggle off any extensions you don’t use daily. Each one runs as a separate process in macOS, and the overhead accumulates faster on Mac than on Windows.
Expected result: The Memory Pressure graph in Activity Monitor stays green during normal browsing.
Fix 3: Stop Chrome from Crashing on Your Mac {#fix-3}
Step 1: Check Whether Chrome Is Running Natively on Apple Silicon
If you have an M-series Mac (M1, M2, M3, M4), verify this first. Open Activity Monitor , find Google Chrome in the list, and look at the Kind column.
Apple = Chrome is running natively on Apple Silicon ✓Intel = Chrome is running through Rosetta 2 translation, with a significant performance penalty
If it says Intel , go to chrome://settings/help to check your version, then <a href=”https://www.switchingtomac.com/how-to-download-and-install-google-chrome-on-your-mac/”>download the correct build</a> from <a href=”https://www.google.com/chrome/” target=”_blank” rel=”noopener noreferrer”>google.com/chrome</a>. The site should auto-detect your chip, but look for an explicit Mac with Apple chip option to be certain.
Is Chrome faster on Apple Silicon? Yes, significantly. The native Apple Silicon build outperforms the Intel/Rosetta version in both speed and battery life. If you’ve been running the wrong build, switching alone can feel like a hardware upgrade.
Step 2: Disable All Extensions and Test
Go to chrome://extensions and toggle every extension off . Restart Chrome. If it stops crashing, a bad extension is the cause. Re-enable them one at a time, restarting Chrome after each, until you find it.
Step 3: Test with a New Chrome Profile
Go to chrome://settings, scroll to You and Google , and click Add under People to create a new profile. Browse normally with the new profile. If Chrome is stable, your original profile’s data is corrupted. Fix 7 covers how to safely reset it.
Step 4: Check macOS Crash Logs
Open Console (Cmd + Space, type “Console”). Search for Google Chrome in the search bar. Crash reports show the specific failure type, such as a GPU crash, extension crash, or Keychain issue, which narrows down the fix considerably.
Fix 4: Fix Chrome’s Keychain Access Hangs {#fix-4}
Chrome on Mac stores its encryption keys in the macOS Keychain , something Windows Chrome never does. If that Keychain entry gets corrupted after a macOS update or a password change, Chrome will hang on launch, prompt you repeatedly for Keychain access, or freeze during autofill. Here’s how to fix it.
Step 1: Open Keychain Access
Press Cmd + Space, type “Keychain Access”, then press Return .
Step 2: Search for Chrome’s Keychain Entry
In the Keychain Access search bar, type:
Chrome Safe Storage
Step 3: Delete the Corrupted Entry
If you see one or more entries named Chrome Safe Storage , especially duplicates or entries with a lock icon, right-click each one and select Delete . Confirm the deletion.
Important: Deleting Chrome Safe Storage means Chrome can no longer decrypt passwords stored only in its local encrypted database. Before doing this, make sure your passwords are synced to your Google account. Go to chrome://settings/passwords and confirm sync is enabled. Synced passwords are safe and will restore automatically.
Step 4: Relaunch Chrome and Allow Access
Fully quit Chrome with Cmd + Q, then reopen it. Chrome will create a new, clean Keychain entry. When macOS prompts “Chrome wants to use your confidential information stored in ‘Chrome Safe Storage’ in your keychain” , click Always Allow .
Expected result: No more repeated Keychain prompts; autofill works without hanging.
Fix 5: Fix Chrome Slowdowns on Video and Graphics-Heavy Sites {#fix-5}
Chrome uses Apple’s Metal GPU API for hardware-accelerated rendering. After some macOS updates, Chrome’s GPU process can conflict with Metal and fall back to slower software rendering, or the GPU process crashes and restarts in a loop. The symptoms are loud fans, sluggish scrolling, and stuttering video.
Step 1: Check Chrome’s GPU Status
Go to chrome://gpu in Chrome’s address bar. Look at the Graphics Feature Status list at the top.
Lines marked Software only, hardware acceleration unavailable mean Chrome has fallen back to software rendering. That’s the problem.
Step 2: Check Activity Monitor for a Misbehaving GPU Process
In Activity Monitor , click the CPU tab and look for Google Chrome Helper (GPU) . If its CPU usage stays above 30–50% on a normal page (not a video), the GPU process is misbehaving. This is similar to how <a href=”https://www.switchingtomac.com/what-is-kernel_task-on-mac-and-why-does-it-cause-high-cpu-usage/”>kernel_task can cause high CPU usage</a> on Mac — a background process consuming resources in ways that aren’t immediately obvious.
Step 3: Toggle Hardware Acceleration
Go to chrome://settings/system. Uncheck Use hardware acceleration when available , then click Relaunch .
Test the slow site. If it’s now smooth, Chrome’s Metal integration is the issue on your current macOS version. Check chrome://settings/help for a pending Chrome update. Google usually patches Metal compatibility problems quickly after macOS releases.
If performance gets worse with hardware acceleration off, turn it back on. Your GPU is fine, and software rendering is slower for your use case.
Step 4: Clear Chrome’s GPU Cache via Terminal
If toggling hardware acceleration didn’t help, clear Chrome’s GPU cache. This is safe. Chrome rebuilds it on next launch.
Fully quit Chrome (Cmd + Q).
Open Terminal (Cmd + Space, type “Terminal”, press Return ).
Copy and paste this command exactly, then press Return :
rm -rf ~/Library/Application\ Support/Google/Chrome/Default/GPUCacheExpected result: Chrome rebuilds a clean GPU cache and hardware acceleration works correctly again.
Fix 6: Fix Chrome Crashes When Printing, Using the Camera, or Accessing Files {#fix-6}
macOS requires explicit permission for Chrome to access your camera, microphone, Downloads folder, and other system resources. If you denied a permission by accident, or if macOS reset permissions after an update, Chrome fails silently or crashes when it tries to use that resource. macOS won’t re-prompt you automatically, which makes this frustrating to diagnose.
Step 1: Open Privacy & Security Settings
Go to Apple menu > System Settings > Privacy & Security .
Step 2: Check Chrome’s Permissions
Check each of these categories and confirm Chrome is listed and toggled on for any you need:
Camera , needed for video calls in ChromeMicrophone , needed for voice calls and recordingLocation Services , needed for location-aware sitesFiles and Folders , look for Downloads Folder specifically; Chrome needs this to save filesScreen Recording , needed for some video conferencing extensions
Step 3: Grant Any Missing Permissions
Toggle Chrome on for any category where it’s off. If Chrome isn’t listed under a category at all, trigger the permission prompt by performing the action in Chrome (like starting a video call) and macOS will ask you to allow or deny.
Step 4: Restart Chrome
After changing any permissions, fully quit Chrome (Cmd + Q) and relaunch it. macOS permission changes often don’t take effect until the app restarts.
Expected result: The specific action that was crashing Chrome, whether printing, camera access, or file downloads, now works without crashing.
🪟 Windows Switcher Callout: Why Chrome Feels Different on Mac {#windows-switcher}
If you switched from Windows and Chrome feels slower on your Mac, you’re not imagining it. It’s also not a hardware problem.
On Windows, Chrome uses virtual memory aggressively, runs with fewer sandbox restrictions, and operates where background processes are managed loosely. On macOS, Chrome runs inside a tighter security sandbox. It relies on macOS’s memory compression instead of Windows-style virtual memory. Every tab and extension process is visible to the OS’s resource accounting. The overhead is real.
The good news: with the right settings, Chrome on Apple Silicon is fast. The fixes that matter most for Windows switchers:
Verify you’re running the Apple Silicon build (Fix 3, Step 1). This is the single biggest performance differenceEnable Memory Saver (Fix 2, Step 3). This compensates for macOS’s stricter memory managementReduce your extension count , the per-process overhead is more noticeable on macOSAccept that macOS rewards fewer active tabs , Chrome’s Memory Saver automates this, but closing unused tabs helps immediately
<a href=”https://appleinsider.com/articles/26/06/06/chrome-for-macos-soundly-beats-browser-benchmark-records” target=”_blank” rel=”noopener noreferrer”>Chrome on a native Apple Silicon Mac with these settings configured is genuinely fast.</a> The learning curve is knowing which macOS-level knobs to turn.
Fix 7: Reset a Corrupted Chrome Profile (Without Losing Your Bookmarks) {#fix-7}
If Chrome crashes consistently but a new profile (Fix 3, Step 3) is stable, your original profile data is corrupted. Here’s how to safely reset it. Your bookmarks and passwords sync from Google’s servers, so as long as sync is enabled, you won’t lose them.
Step 1: Verify Sync Is Enabled
Before touching any files, open Chrome and go to chrome://settings. Confirm you’re signed into your Google account and sync is active. A Sync is on status means your bookmarks and passwords are backed up to Google.
Step 2: Fully Quit Chrome
Press Cmd + Q to quit Chrome. Then open Activity Monitor and confirm no Chrome processes are still running. If any are, select them and click the Force Quit (X) button.
Step 3: Navigate to Chrome’s Profile Folder
Open Finder , then press Cmd + Shift + G to open the Go to Folder dialog. Type the following path and press Return :
~/Library/Application Support/Google/Chrome/
You’ll see a folder called Default and a file called Local State .
Step 4: Back Up Before You Change Anything
Select both Default and Local State , right-click, and choose Compress 2 Items . Move the resulting zip to your Desktop so you can restore it if needed.
Step 5: Reset the Local State File (Less Destructive, Try This First)
Open Terminal and run:
mv ~/Library/Application\ Support/Google/Chrome/Local\ State ~/Library/Application\ Support/Google/Chrome/Local\ State.bakRelaunch Chrome. If the crashes stop, you’re done. Chrome created a fresh Local State file, and your bookmarks and history in the Default folder are untouched.
Step 6: Reset the Full Default Profile (If Step 5 Didn’t Fix It)
If Chrome still crashes, reset the entire Default profile. In Terminal, run:
mv ~/Library/Application\ Support/Google/Chrome/Default ~/Library/Application\ Support/Google/Chrome/Default.bakRelaunch Chrome. It will create a fresh Default folder. Sign into your Google account when prompted and your bookmarks, passwords, and extensions will restore from Google’s servers within a few minutes.
What you’ll lose with a full Default reset: Local browsing history, cached site data, and any extension settings that weren’t synced to Google. Everything tied to your Google account, including bookmarks, passwords, extensions list, and most settings, restores automatically.
Prevention: Chrome Settings to Configure on a Fresh Mac Install or After a macOS Upgrade
If you’ve just set up a new Mac or upgraded macOS, configure these settings before Chrome has a chance to degrade.
Step 1: Verify Chrome Architecture
On an M-series Mac, open Activity Monitor immediately after installing Chrome and confirm the Kind column shows Apple . If it shows Intel , re-download Chrome from <a href=”https://www.google.com/chrome/” target=”_blank” rel=”noopener noreferrer”>google.com/chrome</a> and select the Mac with Apple chip option explicitly.
Step 2: Configure Performance Settings
Go to chrome://settings/performance and set:
Memory Saver : OnEnergy Saver : On (set to activate on battery or when battery is low)
Step 3: Disable Background Apps
Go to chrome://settings/system and turn off Continue running background apps when Google Chrome is closed . This prevents Chrome from consuming RAM and battery when you’re not using it.
Step 4: Manage Login Items Immediately
Go to System Settings > General > Login Items & Extensions and remove Chrome from Open at Login if you don’t want it auto-launching. Disable Chrome entries under Allow in Background unless you specifically need web app notifications when Chrome is closed.
Step 5: Grant Permissions Proactively
Go to System Settings > Privacy & Security and confirm Chrome has the permissions it needs, especially Camera , Microphone , and Files and Folders > Downloads Folder . Granting these now prevents the silent failures that look like crashes later.
Step 6: Keep Chrome Updated
Go to chrome://settings/help and make sure Chrome is up to date. Chrome updates frequently patch macOS-specific compatibility issues, especially after new macOS releases. Enable automatic updates if prompted. Note that <a href=”https://support.google.com/chrome/thread/404150391/sunsetting-support-for-macos-12-monterey-in-mid-2026?hl=en” target=”_blank” rel=”noopener noreferrer”>Google is sunsetting support for macOS 12 Monterey in mid-2026</a>, so staying on a supported macOS version is important for continued Chrome updates.
Summary Checklist: All Fixes at a Glance
Fix Action Symptom It Addresses 1 Remove Chrome from Login Items in System Settings > General > Login Items & Extensions Slow startup 1 Disable Chrome background helpers in Allow in Background Slow startup, idle battery drain 1 Set Chrome startup to Open the New Tab page Slow startup 2 Check Memory Pressure in Activity Monitor > Memory tab Freezing, beach ball 2 Use Chrome Task Manager to find memory-hungry tabs/extensions Freezing, beach ball 2 Enable Memory Saver at chrome://settings/performance Freezing, beach ball 2 Enable Energy Saver at chrome://settings/performance Battery drain, thermal throttling 2 Disable unused extensions at chrome://extensions Freezing, slow performance 3 Confirm Chrome shows Apple (not Intel) in Activity Monitor Kind column Crashes, general slowness on M-series Macs 3 Disable all extensions and re-enable one by one Crashes 3 Test with a new Chrome profile Crashes 4 Delete Chrome Safe Storage entries in Keychain Access Repeated Keychain prompts, hangs on autofill 5 Check chrome://gpu for software-only rendering Slow video, graphics-heavy sites 5 Toggle Use hardware acceleration when available at chrome://settings/system Slow video, GPU process crashes 5 Clear GPU cache via Terminal (rm -rf ~/Library/Application\ Support/Google/Chrome/Default/GPUCache) GPU rendering issues 6 Check System Settings > Privacy & Security for Camera, Microphone, Files and Folders permissions Crashes when printing, using camera, or accessing files 7 Rename Local State to Local State.bak via Terminal Profile corruption, persistent crashes 7 Rename Default to Default.bak via Terminal Severe profile corruption
Wrapping Up
Most Chrome performance problems on Mac trace back to macOS integration, not Chrome itself. Start with Login Items and Memory Saver. They fix the most common issues in under five minutes. Work through the other fixes that match your symptom, and only escalate to the Terminal-based profile reset if the lighter fixes don’t hold.
For ongoing reference, Google’s official Chrome speed guide and Apple’s Activity Monitor documentation are worth bookmarking. Both are updated alongside new Chrome and macOS releases.
Resources
