How to Stop Chrome From Running in the Background on Windows

Why Chrome is still running after you close it

Background apps are a Chrome feature, not a malfunction: the browser keeps selected extensions and web apps running after the last window closes, so they can keep notifications, sync and music players alive. The visual clue is easy to miss — a small Chrome icon sits in the system tray near the clock, and Task Manager shows a tree of chrome.exe entries under Google Chrome. With the feature on, Chrome also registers itself among Windows startup entries, so background apps get a head start the moment you log on. The price is real: those processes hold tens to a few hundred megabytes of RAM and occasionally wake the CPU for notification checks.

The usual reason the switch is on at all is an extension that asked for it — messengers, cloud-drive sync tools and download managers are the classic examples. Chrome enables the mode the first time such an extension needs it, and it stays on even after the extension is gone. Newer Chrome builds add one more warm-keeping option on the same page: “Startup boost”, which pre-loads the browser at sign-in — a related idea, but a separate switch with its own job.

• Chrome's icon stays in the system tray near the clock after all windows are closed
• Task Manager shows a tree of chrome.exe entries under Google Chrome, holding tens to a few hundred MB
• Extensions and web apps keep delivering notifications and syncing with the window closed
• With background mode on, Chrome lists itself among Windows startup entries and launches at logon
• Newer Chrome builds add a separate “Startup boost” switch on the same System page — it also keeps processes warm
• Extensions with background permission — messengers, cloud sync, download managers — are what usually turn the mode on

Turning background apps off, step by step

Open chrome://settings/system (three-dot menu → Settings → System) and switch off “Continue running background apps when Google Chrome is closed”. If you see a “Startup boost” line on the same page, turn that off too — the same idea under a different name. Existing processes do not die on their own: fully quit Chrome via the three-dot menu → Exit, or right-click the tray icon → Exit, or open Task Manager (Ctrl+Shift+Esc), select Google Chrome and click “End task”. Re-check Task Manager after a minute — with the switches off, no chrome.exe should survive.

The browser itself works exactly as before — nothing changes while Chrome is open. What changes is the closed state: no tray icon, no notifications, no chrome.exe at next logon unless you launch Chrome yourself. Extension settings stay untouched; if one of them truly needs background mode (a messenger that must stay reachable, say), Chrome will ask about it the next time — and that will be a conscious choice.

What you lose — and what you don't

The trade-off is narrow and worth knowing in advance. After this change, web apps go silent when Chrome is closed: Gmail desktop notifications, WhatsApp Web pings and calendar reminders arrive only while a window is open. That is the entire downside; speed, tabs, bookmarks, passwords and extensions are untouched, and Chrome opens no slower than before.

Two pieces of fine print. Chrome updates and freshly installed extensions occasionally flip settings back, so if chrome.exe reappears after a major version jump, re-check the System page before blaming the PC. And if your goal is a lean startup in general, open Task Manager → Startup apps and disable everything you do not want at logon — Chrome's own entry is already gone once the background switch is off.

Questions and Answers

Read next

All articles · FAQ