You click the Chrome icon. It bounces once in the Dock, then settles right back down like nothing happened. Sometimes there’s not even a bounce, just silence. Annoying, sure. But this is a well-known issue with a known set of fixes, and you almost never need to call in outside help to solve it.
One thing before we start: this guide is for launch failures, meaning Chrome won’t open at all when you click it. If Chrome opens fine but then crashes, freezes on a specific tab, or quits partway through your browsing session, that’s a different problem with different causes, and this guide won’t fix it. Everything below assumes you’ve already tried the obvious stuff (restarting Chrome, clicking the icon a few more times out of frustration) and you’re ready for actual solutions.
Quick Diagnosis
Before working through the full list of fixes, run through these basics. They take under a minute and solve more cases than you’d expect.
- Check your Mac’s available storage. Go to Apple menu > About This Mac > Storage. If you’re nearly out of space, macOS can block apps from launching properly. Free up a few gigabytes and try again.
- Check for a second monitor or Space issue. Chrome can sometimes open a window on a disconnected display or an empty desktop Space. Try
Mission Control(swipe up with three fingers, or pressF3) to check for a stray window. - Confirm you’re opening the real app. Open Finder > Applications and double-click Google Chrome directly, rather than a Dock shortcut or an alias that might point to a moved or deleted file.
If none of that fixes it, work through the numbered issues below in order. They’re arranged from the quickest checks to the deepest fixes.
Common Issues and Solutions
1. Chrome Is Already Running in the Background
Symptoms:
- The Dock icon bounces once and settles back down with no window appearing
- Nothing seems to happen, but you notice a small dot under the Chrome icon in the Dock
- Chrome worked a moment ago and you haven’t quit it since
Why it happens: Chrome can end up running invisibly, all its windows closed, but the app itself still active in memory. macOS sees Chrome as “already open” and simply activates the existing (windowless) instance instead of launching a new one, so nothing visibly happens.
Fix:
- Look at the Dock. If there’s a small dot beneath the Chrome icon, Chrome is running.
- Right-click (or Control-click) the Chrome icon in the Dock and choose Quit.
- Wait two or three seconds, then click the Chrome icon again to relaunch it.
Verify it worked: A normal Chrome window with your tabs (or the New Tab page) should appear within a few seconds of relaunching.
2. Chrome Is Frozen and Won’t Respond to Quit
Symptoms:
- Right-clicking the Dock icon and choosing Quit does nothing
- The Chrome icon stays in the Dock with the running indicator no matter how long you wait
- Clicking the icon again just makes it bounce without opening a window
Why it happens: Chrome’s main process has stopped responding but hasn’t fully crashed, so macOS can’t cleanly shut it down through a normal Quit command.
Fix:
- Press
Cmd + Option + Escto open the Force Quit Applications window (or choose Apple menu > Force Quit…). - Select Google Chrome in the list.
- Click Force Quit, then confirm if prompted.
- Wait a few seconds and relaunch Chrome from Applications or the Dock.
Verify it worked: The Dock indicator dot disappears, and a fresh Chrome window opens when you relaunch it.
Tip: This is the same tool used to force quit any unresponsive Mac app. Worth remembering for Chrome problems and beyond.
3. A Hidden Chrome Process Survives Force Quit
Symptoms:
- You force quit Chrome via the Force Quit window, but the problem returns immediately when you relaunch
- Chrome still won’t show a window after multiple force quit attempts
Why it happens: Chrome runs as several linked processes: the main browser plus a helper process for each extension, tab, and GPU task. Occasionally, one of these helper processes survives a force quit and keeps macOS from starting a clean new session.
Fix:
- Open Activity Monitor. You can find it via Spotlight (
Cmd + Space, then type “Activity Monitor”) or in Applications > Utilities. - Click the CPU tab and type “Chrome” into the search field in the top-right corner.
- You’ll likely see multiple entries: Google Chrome, Google Chrome Helper, Google Chrome Helper (Renderer), and similar.
- Select each Chrome-related process one at a time and click the Stop (⊗) icon in the toolbar, then confirm Force Quit.
- Once every Chrome process is gone from the list, relaunch Chrome.
Verify it worked: Searching “Chrome” in Activity Monitor returns zero results before you relaunch. That’s your confirmation of a clean slate.
4. Restarting the Mac Doesn’t Fix It
Symptoms:
- You’ve force quit every Chrome process and restarted your Mac, but Chrome still won’t open
- The issue happens consistently, even right after a fresh boot
Why it happens: A restart clears stuck processes, but it won’t fix a corrupted user profile or a damaged app file. Those problems live on disk, and they survive a reboot just fine.
Fix:
- Choose Apple menu > Restart… and let your Mac fully reboot.
- Once you’re back at the desktop, wait about 30 seconds for background login items to finish loading. This matters: launching Chrome too early after login can look like a launch failure when it’s really just contention with other startup apps.
- Try opening Chrome from Applications.
Verify it worked: If Chrome opens now, you’re done. If it still won’t launch, move on. The cause here is something that survives a restart, so a second restart won’t help either.
5. A Misbehaving Extension or Corrupted Profile Is Blocking Launch
Symptoms:
- Chrome opens fine on other Macs or for other user accounts, but not yours
- The problem started after installing a new extension or after Chrome synced settings from another device
- Force quitting and restarting had no effect
Why it happens: Chrome loads your entire profile every time it starts, bookmarks, extensions, saved passwords, cached settings, all of it. If one of those files is corrupted, or an extension is trying to do something Chrome can’t handle at startup, the whole launch can hang before a window ever appears.
Fix: Rather than deleting your profile (which would wipe your bookmarks and saved passwords), rename the folder so Chrome is forced to build a brand-new one. Your old data stays intact in case you need to recover something from it later.
- In Finder, click the Go menu and choose Go to Folder… (or press
Cmd + Shift + G). - Enter this path and press Return:
~/Library/Application Support/Google/
- You’ll see a folder named Chrome. Rename it to something like Chrome Backup (click once to select it, press Return to edit the name, then type the new name).
- Relaunch Chrome. It will automatically generate a fresh Chrome folder and a clean default profile.
Verify it worked: Chrome opens to a blank New Tab page with no bookmarks or extensions. That’s expected, since it’s a brand-new profile. Sign in to your Google Account and Chrome will sync your bookmarks, passwords, and open tabs back down within a minute or two, without you having imported anything manually.
Tip: If Chrome opens successfully with the fresh profile, the corrupted old profile was the cause. You can safely delete the Chrome Backup folder once you’ve confirmed everything you need has synced back.
6. macOS Is Blocking Chrome from Opening (Gatekeeper)
Symptoms:
- Nothing happens at all when you click Chrome: no bounce, no window, no Dock indicator
- This started right after installing or reinstalling Chrome
- You may briefly see a message about Chrome being from an “unidentified developer” or that it “cannot be opened”
Why it happens: macOS uses a security system called Gatekeeper to check that downloaded apps are safe before letting them run. If the Chrome installer’s file attributes got flagged, or if your Mac’s security settings are more restrictive than usual, Gatekeeper can silently block Chrome from launching. No error, no warning, it just refuses.
Fix:
- Open System Settings > Privacy & Security.
- Scroll down to the Security section and check the Allow applications downloaded from setting.
- If you see a message mentioning Google Chrome was blocked, click Open Anyway next to it.
- If there’s no on-screen prompt but Chrome still won’t launch, open Terminal (Applications > Utilities > Terminal) and run this command to clear any quarantine flags on the app:
xattr -cr /Applications/Google\ Chrome.app- Try opening Chrome again from Applications.
Verify it worked: Chrome launches without any security prompt. This is the one and only Terminal command you should need for this entire process. You don’t need any other command-line tools to fix a Chrome launch failure.
7. Chrome Stopped Opening After a macOS Update
Symptoms:
- Chrome worked fine before you updated macOS (for example, to macOS Sonoma, Sequoia, or Tahoe) and now won’t launch
- Other apps open normally, so the problem seems specific to Chrome
- You may notice general Wi-Fi or network flakiness alongside the Chrome issue
Why it happens: Recent versions of macOS introduced stricter network privacy controls, including a setting called Limit IP Address Tracking. In some configurations, this setting interferes with how Chrome establishes its initial network connections at startup, which can stall the launch process entirely.
Fix:
- Open System Settings > Network.
- Select your active connection (Wi-Fi or Ethernet) and click Details….
- Look for Limit IP Address Tracking and turn it off.
- Close System Settings and try opening Chrome again.
- If that doesn’t help, check the Chrome Releases Blog to see if Google has shipped an update addressing compatibility with your macOS version, and update Chrome using the method in Fix 8 below.
Verify it worked: Chrome launches normally, and other network-dependent apps (Mail, Messages, App Store) continue working fine with the setting off.
8. Nothing Above Worked: Update, Reset, or Reinstall Chrome
Symptoms:
- You’ve tried every fix above and Chrome still won’t open
- The problem has persisted across multiple restarts and profile resets
Why it happens: At this point, the most likely culprit is the Chrome application bundle itself: a damaged or incompletely downloaded copy of the app that no amount of profile or settings changes can fix. Sometimes you just need to start over.
Fix:
Since Chrome itself won’t open, use a different browser (Safari works fine, since it’s already on your Mac) to download a fresh copy.
- Open Safari and go to the official Chrome download page.
- Click Download Chrome and save the
.dmgfile. - Before installing the fresh copy, remove the old one: open Applications, drag the existing Google Chrome icon to the Trash, then empty the Trash.
- Open the downloaded
.dmgfile and drag Google Chrome into the Applications folder shown in the installer window. - Eject the installer disk image, then open Chrome from Applications or Launchpad.
- Sign in with your Google Account to restore your bookmarks, passwords, and extensions from sync.
Verify it worked: Chrome opens to your synced New Tab page, and quitting and relaunching it works consistently across at least a couple of tries.
Tip: If Chrome still won’t open even after a clean reinstall, the issue is likely deeper than Chrome itself. Boot into Safe Mode (hold the power button until “Loading startup options” appears, hold
Shift, then choose Continue in Safe Mode) and try launching Chrome there. If it opens in Safe Mode, try creating a new administrator account in System Settings > Users & Groups to see if the problem is isolated to your original user account.
Error Messages Table
| Message or Symptom | What It Means | Fix |
|---|---|---|
| Icon bounces once, no window appears | Chrome is likely already running invisibly | Fix 1: Check background process |
| Nothing happens at all when clicked | Gatekeeper may be blocking the app, or the bundle is damaged | Fix 6: Check Privacy & Security, run xattr -cr |
| “Google Chrome can’t be opened because Apple cannot check it for malicious software” | macOS flagged the downloaded app | Fix 6: Allow it in Privacy & Security, or clear quarantine attributes |
| Chrome won’t quit from the Dock menu | Main process is unresponsive | Fix 2: Force Quit via Cmd + Option + Esc |
| Force quit succeeds, but relaunch still fails | A helper process is still running | Fix 3: End all Chrome processes in Activity Monitor |
| Works for other users, not you | Profile corruption specific to your account | Fix 5: Rename the Chrome profile folder |
| Broke right after a macOS update | Network privacy setting interference | Fix 7: Turn off Limit IP Address Tracking |
Platform-Specific Issues
On macOS
The fixes above are written for macOS 14 Sonoma and later, including macOS Tahoe, and they apply the same way across Intel and Apple silicon Macs. The one macOS-specific wrinkle is Gatekeeper (Fix 6); Windows doesn’t have a direct equivalent, so this step is unique to the Mac. If you’re troubleshooting on multiple Macs, the profile folder path (~/Library/Application Support/Google/Chrome) is identical on every one, since it’s tied to your macOS user account rather than the machine.
On Windows
If you use Chrome on both a Mac and a Windows PC, the same launch-failure logic applies, just with different tools:
- Check for a hidden process: Right-click the taskbar and choose Task Manager, or press
Ctrl + Shift + Esc. Look for Google Chrome under the Processes tab. - End unresponsive processes: Select each Chrome entry and click End task.
- Reset the profile: Press
Win + R, type%LOCALAPPDATA%\Google\Chrome\User Data, and press Enter. Rename the Default folder to Default Backup, then relaunch Chrome to generate a fresh profile. - Reinstall Chrome: Go to Settings > Apps > Installed apps, find Google Chrome, click the ⋯ menu, and choose Uninstall. Then download a fresh installer from the official Chrome page and run it.
Windows doesn’t have a Gatekeeper equivalent, but Windows Defender SmartScreen can occasionally flag a downloaded installer; if you see a SmartScreen warning, click More info then Run anyway to proceed with a trusted download from google.com.
Configuration Issues
A few mistakes make this troubleshooting process harder than it needs to be:
- Deleting the profile folder instead of renaming it. If you delete
~/Library/Application Support/Google/Chromeoutright, you lose the ability to recover locally saved data if sync doesn’t restore everything. Always rename first. - Running
xattron the wrong path. The command only works if you type the path exactly as shown, including the escaped space (Google\ Chrome.app). A typo will return a “No such file” error rather than actually fixing anything. - Turning off “Allow apps downloaded from” entirely. Setting Gatekeeper to a highly restrictive mode can block Chrome (and other legitimate apps) from ever launching again. Use Open Anyway for a specific blocked app instead of changing the global security posture.
- Skipping the reinstall step because “it should just work.” If a profile reset doesn’t fix things, don’t keep repeating force-quit and restart cycles. Move on to a clean reinstall rather than looping through the same fixes.
Getting Help
If you’ve worked through every fix above and Chrome still won’t launch, gather this information before reaching out for help:
- Chrome version (once it does open): go to
chrome://versionin the address bar - macOS version: Apple menu > About This Mac
- Crash logs: Open Console.app (Applications > Utilities > Console), select Crash Reports in the sidebar, and look for recent entries mentioning “Google Chrome”
- Profile location:
~/Library/Application Support/Google/Chrome
For community troubleshooting threads specific to launch failures, check the official Google Chrome Help Community, including the “Google Chrome isn’t opening” and macOS Tahoe-specific threads at support.google.com/chrome. Google’s Chrome Releases Blog is also worth checking if the problem started right after a Chrome or macOS update; it lists known issues and fixes for recent versions.
Prevention Tips
- Keep Chrome updated automatically. Go to Chrome menu > About Google Chrome periodically to trigger an update check. Chrome usually updates itself in the background, but a manual check now and then catches anything that got stuck.
- Quit Chrome fully before major macOS updates. Use Chrome menu > Quit Google Chrome (
Cmd + Q) rather than just closing all windows, so no hidden process survives into the new OS version. - Be cautious with extensions from outside the Chrome Web Store. Unofficial extension installs are a common source of profile corruption that leads to launch failures.
- Don’t force-quit your Mac during a Chrome update. Interrupting an in-progress update is one of the most common causes of a damaged app bundle.
Frequently Asked Questions
Why won’t Chrome open when I click the icon on my Mac?
The most common causes are Chrome already running invisibly in the background, a corrupted user profile, or macOS Gatekeeper blocking the app. Work through the fixes in order, starting with the background process check.
How do I force quit Chrome if it’s frozen or hidden?
Press Cmd + Option + Esc to open Force Quit Applications, select Google Chrome, and click Force Quit. If that doesn’t fully clear it, use Activity Monitor to end every Chrome-related process individually.
How do I reset my Chrome profile without losing bookmarks or passwords?
Rename (don’t delete) the folder at ~/Library/Application Support/Google/Chrome, then relaunch Chrome and sign back in. Your data syncs back down from your Google Account within a minute or two.
How do I reinstall Chrome on a Mac?
Drag the existing Google Chrome app from Applications to the Trash, empty the Trash, then download a fresh copy from google.com/chrome using Safari and drag it into Applications.
Why did Chrome stop opening after a macOS update?
Newer macOS versions include a network privacy setting called Limit IP Address Tracking that can interfere with Chrome’s startup network connections. Turn it off in System Settings > Network > Details.
What’s the difference between Chrome not opening and Chrome crashing after it opens?
A launch failure means no window ever appears: the icon bounces or nothing happens at all. A crash means Chrome opens successfully and then quits unexpectedly later, often tied to a specific tab or extension. This guide covers only launch failures.
Do I need to use Terminal to fix Chrome on Mac?
Only in one case: clearing Gatekeeper’s quarantine flag with xattr -cr /Applications/Google\ Chrome.app. Every other fix here uses only the standard macOS interface, no other command-line tools required.
Wrapping Up
Most Chrome launch failures on Mac come down to one of three things: a hidden background process, a corrupted profile, or macOS blocking the app outright. The fixes above handle all three without any risk to your saved bookmarks and passwords.
Start at the top of the list and work down. You’ll likely be back in a normal Chrome window well before you reach the reinstall step.
| Step | Action | Applies To |
|---|---|---|
| 1 | Check for a hidden background process | All launch failures |
| 2 | Force Quit via Cmd + Option + Esc | Frozen/unresponsive Chrome |
| 3 | End all Chrome processes in Activity Monitor | Force Quit doesn’t work |
| 4 | Restart the Mac | Persistent issues |
| 5 | Rename the Chrome profile folder | Profile corruption |
| 6 | Check Privacy & Security / run xattr -cr | Gatekeeper blocking |
| 7 | Turn off Limit IP Address Tracking | Broke after macOS update |
| 8 | Reinstall Chrome | Nothing else worked |
Last updated: August 16, 2026 | Applies to Google Chrome on macOS 14 Sonoma and later (including macOS Tahoe), and Windows 10/11