Chrome Won't Quit on Mac? How to Force-Quit It
Force quit Chrome with ⌥⌘⎋ (Option-Command-Escape): pick Google Chrome and click Force Quit. If it stays alive, a stuck Helper process is the cause. Kill every chrome row in Activity Monitor, or run killall "Google Chrome" in Terminal.
Chrome on macOS is not one program. It is a small army of processes: a main browser process, plus a stack of Google Chrome Helper processes (one or more per tab), plus separate helpers for the GPU and extensions. That split keeps a single bad tab from taking down the whole browser. It also means Chrome can hang while the menu bar acts like nothing is wrong. You press ⌘Q and nothing happens, the window stops redrawing, and the beachball spins.
Here is the order I use to unstick Chrome on current macOS (Sonoma and Sequoia), starting with the polite fix and ending with the hard kill.
First, try a normal Quit (⌘Q)
Click a Chrome window to bring it to the front, then press ⌘Q. Or use the menu bar: Chrome → Quit Google Chrome. If Chrome is set to warn before quitting, hold ⌘Q for a second.
Give it a few seconds before you panic. A tab finishing a download or upload can make Chrome slow to answer without being truly frozen. If one tab is the culprit, you can often skip the full quit entirely. Open Chrome's own task manager from Window → Task Manager, select the stuck tab or extension, and click End Process. That kills only that page and usually frees the rest of the browser.
Still ignored? Beachball won't quit? Chrome is hung. Force quit it.
Force Quit window (⌥⌘⎋)
This is the fastest reliable fix. Press ⌥⌘⎋ (Option-Command-Escape) to open the Force Quit Applications window. You can also open it from the Apple menu () → Force Quit.
- Select Google Chrome. A frozen Chrome usually shows (not responding) next to the name.
- Click Force Quit.
- Confirm in the dialog.
This kills the main Chrome process, which should drag its helpers down with it. You skip Chrome's clean shutdown, but your session is safe: reopen Chrome and click Restore, or use History → Recently Closed to pull your tabs back. The full walkthrough of this window lives in our force quit on Mac guide, and the keyboard shortcut reference covers the keys.
Force quit from the Dock
Don't want to leave the app you're in? Go straight to the Dock icon. Right-click (or Control-click) Chrome's icon in the Dock.
- Right-click the Dock icon. You'll see a Quit option.
- Hold the Option key. Quit turns into Force Quit.
- Click Force Quit while you keep holding Option.
Same result as the Force Quit window, with no extra dialog. We break this down further in force quit an app from the Dock.
Use Activity Monitor for the Helper processes
This is the step most people skip with Chrome, and it is the one that actually matters. Even after the main app quits, a single hung Google Chrome Helper can keep the browser running in the background. That is why Chrome sometimes "won't die" or relaunches on its own. Open Activity Monitor (in Applications → Utilities, or hit ⌘Space and type its name).
- Type chrome in the search box at the top right. You'll see Google Chrome along with several Google Chrome Helper, Helper (Renderer), and Helper (GPU) rows.
- Select the main Google Chrome process first, click the Stop button (the octagon with an X), then choose Force Quit.
- If any Helper rows are still listed, force quit each one the same way until the search comes back empty.
Sort by % CPU or Memory to spot which tab or extension is pinned and dragging your Mac down. Chrome is a famous RAM hog, so if the whole machine feels slow, see Mac running slow, free up RAM. Our Activity Monitor guide goes deeper on reading the columns.
Kill it from Terminal (killall and kill -9)
When the windows refuse to cooperate, Terminal (in Applications → Utilities) ends Chrome in one line. The app name has a space, so wrap it in quotes:
- killall "Google Chrome": ends every process named exactly that. This stops the main browser process, and the helpers usually follow.
- pkill -f "Google Chrome": a broader match that also catches Helper processes whose names start differently. Reach for this when a stubborn helper survives killall.
If one process still refuses, find its ID and send the hard signal:
- Run ps aux | grep -i chrome to list the processes and their PIDs (the number in the second column).
- Run kill -9 PID, swapping PID for that number, for example kill -9 1234.
kill -9 sends SIGKILL, a signal a process cannot catch or ignore. It saves nothing on the way out, so use it only after the gentler options fail. If even that does nothing, read force quit not working on Mac. For the wider "app is frozen" case, see when an app won't quit.
The instant, no-menu way: MEGAKILL
If Chrome hangs on you every other day, the menu dance gets old fast. MEGAKILL is a macOS menu-bar app for macOS 14 (Sonoma) or later that turns a force quit into a single click. Hold its shortcut (Option-Command by default, the option glyph plus the command glyph, configurable in the menu) and your cursor becomes a DOOM-style double-barrel shotgun. Click Chrome's Dock icon to kill the whole browser, helpers and all. Shoot a single Chrome window instead and wound mode closes just that window. Right-click reloads (two shots per reload), and kills rack up streaks with screen shake and real shotgun sounds you can toggle off in the menu. Finder, the Dock, and critical system processes are shielded, so a stray shot cannot break your Mac. It is a notarized Developer ID app from outside the App Store, it auto-updates through Sparkle, and it is free for your first 100 kills, then a one-time 1.99 EUR.
When nothing works: last resort
If even kill -9 can't end a Chrome process, it is probably stuck in an uninterruptible state, usually waiting on a slow disk, a network mount, or a sync extension. At that point:
- Wait a minute. A process stuck on slow I/O sometimes recovers on its own.
- Log out and back in (Apple menu → Log Out) to clear your session.
- Restart the Mac (Apple menu → Restart).
- If the Mac won't restart, force a shutdown: hold the power button for about 10 seconds until it powers off, then turn it back on.
Save the power-button hold for a fully locked machine, since it can corrupt open files. Once you are back in, update Chrome (Chrome → About Google Chrome applies any pending update) and update macOS, because a chronic hang is often a bug that a newer build already fixed. If you tend to close a pile of tabs and windows at once, our guide on closing all apps on Mac may help.
Force-quit, the fun way
Tired of chasing Chrome Helper processes through Activity Monitor? MEGAKILL turns killing a frozen browser into an event. Hold the shortcut, your cursor becomes a shotgun, and you blast Chrome's Dock icon or window out of existence in one click. Instant force-quit, screen shake, kill streaks, real shotgun sounds. Free for your first 100 kills, then a one-time 1.99 EUR for unlimited. Rip and tear.
Download MEGAKILL, freeFrequently asked questions
Why won't Chrome quit on my Mac?
Chrome runs a separate process for the browser, the GPU, and most tabs and extensions. If one of those Helper processes is hung on a stuck page or a misbehaving extension, the main window stops responding and ignores Quit, so you have to force quit it.
How do I force quit Chrome on a Mac?
Press Option-Command-Escape to open the Force Quit window, pick Google Chrome, and click Force Quit. If that fails, open Activity Monitor and stop the Google Chrome process and its Helper processes, or run killall "Google Chrome" in Terminal.
What are the Google Chrome Helper processes?
Chrome splits work across many processes: a main Google Chrome process plus several Google Chrome Helper, Helper (Renderer), Helper (GPU), and Helper (Plugin) processes for tabs, extensions, and graphics. Killing the main process should take the helpers with it, but a stuck helper can keep the browser alive.
Will I lose my open tabs if I force quit Chrome?
Usually not. Chrome saves your session, so when you reopen it you can click Restore or use History then Recently Closed to bring tabs back. Unsaved form text inside a page can still be lost, so copy anything important first when you can.
Chrome force quit but reopens or keeps running. What now?
A leftover Helper process is holding on. Open Activity Monitor, search for chrome, and force quit every matching row, or run killall "Google Chrome" in Terminal. If one row refuses, note its PID and run kill -9 followed by that number.
MEGAKILL