Chrome running in the background after you’ve closed it is a feature, not a bug — though it doesn’t feel that way when you’re looking at Task Manager and seeing Chrome processes running when the browser window is closed. Background apps, service workers, and Chrome’s own update service all contribute to this. Here’s what each one is and how to stop it. For the bigger picture, our Chrome How-To Guides pulls everything together.
The main background run setting
chrome://settings → System → “Continue running background apps when Google Chrome is closed.” Toggle this Off. This is the setting that allows Chrome extensions and web apps to keep running after the last browser window is closed. With it disabled: Chrome stops completely when you close all windows. No more Chrome process in Task Manager after closing the browser.
What this affects: extensions that provide background functions (Gmail notifier, calendar reminders, push notifications from web apps) stop working when Chrome is closed. If you rely on any of these: weigh whether the background notification is worth the background resource use. For most users, the answer is no.
Specific extensions keeping Chrome alive
Even with the main setting off, some extensions register as “background pages” that run continuously. Shift+Esc (Chrome’s own Task Manager) → look for entries under “Background page” — these are extension processes. An extension keeping Chrome alive shows as a background page even when you have no tabs open.
chrome://extensions → enable “Developer mode” (top right) → each extension now shows “background page” or “service worker” links if it has one. Click the service worker or background page link to see what it’s doing. Extensions with persistent background processes: Grammarly, LastPass, many corporate security tools, email notification extensions.
For extensions you don’t need running in the background: disable them, or look for an option in the extension’s own settings to limit background activity. Some extensions allow configuring notification-only mode that uses far fewer resources than a full background page.
Chrome’s own background processes
Beyond extensions: Chrome runs background processes of its own:
- Google Update: GoogleUpdate.exe runs as a scheduled task to keep Chrome current. This is separate from Chrome itself and isn’t stopped by closing the browser. It’s a Windows service that runs independently.
- Crash reporting service: Chrome installs a crash handler that can run independently of the browser window.
- Chrome’s software reporter tool: occasionally scans for software that conflicts with Chrome. Shows up as software_reporter_tool.exe. This runs on a schedule.
The GoogleUpdate service is the main one people notice. To disable it: Services (Win+R → services.msc) → find “Google Update Service (gupdate)” and “Google Update Service (gupdatem)” → set both to “Disabled.” This stops Google Update from running in the background. Trade-off: Chrome no longer auto-updates. You’ll need to manually check for updates via chrome://settings/help.
Our guide on Chrome memory usage covers the resource impact of background processes, and our article on Chrome stability covers situations where background processes contribute to browser instability. For the technical details of Chrome’s background app architecture, Chrome’s developer documentation covers background service workers and their lifecycle.
Chrome startup and background performance impact
Background Chrome processes consume RAM and occasionally CPU. On machines with 8GB RAM: background Chrome alongside other open applications noticeably reduces available memory. On machines with 4GB: it can cause actual performance issues.
Measured impact: Chrome background processes typically use 100-300MB RAM depending on how many extensions have background pages. GoogleUpdate runs rarely and uses minimal resources when active. The software_reporter_tool can spike CPU usage when it runs — this is normal and temporary, lasting a few minutes every few days.
For machines where performance matters: disabling the background apps setting is worth doing. For machines with plenty of RAM (16GB+): the background processes exist but have minimal practical impact on system performance.
Checking what’s running right now
Windows Task Manager: look for multiple Chrome processes — this is normal when Chrome is open (each tab and extension gets its own process). After closing all Chrome windows:
- If you see Chrome processes: the background apps setting is on, or an extension is keeping it alive
- If you see GoogleUpdate.exe: that’s the update service, not Chrome itself
- If you see software_reporter_tool.exe: Chrome’s software reporter is doing its scan
To see exactly which Chrome background processes are running: Chrome Task Manager (Shift+Esc while Chrome is open) → close the browser → check Windows Task Manager. Any remaining Chrome-associated processes that weren’t in Chrome’s own task manager are the update/reporter services rather than browser processes.
| Process name | What it is | How to stop it |
| chrome.exe (background) | Background apps setting | chrome://settings → System → disable background apps |
| chrome.exe (extension) | Extension background page | Disable the specific extension |
| GoogleUpdate.exe | Chrome auto-updater | Disable gupdate/gupdatem services (manual updates only) |
| software_reporter_tool.exe | Chrome software scanner | Via registry (advanced) or accept it as occasional |
The background apps toggle in System settings resolves the most common “Chrome is still running when closed” complaint and takes one click. The extension background pages require more investigation but are usually the reason the setting needs to exist in the first place — extensions that push notifications or sync data in real time need some form of background presence to function.
macOS: Chrome running in the background
On macOS: Chrome appears in the Dock with a dot indicating it’s running even with no windows open. The equivalent setting is in Chrome → Preferences → System → “Continue running background apps when Google Chrome is closed.” Disable this. Additionally, the macOS Activity Monitor shows Chrome Helper processes — these are Chrome’s process isolation instances for tabs and extensions, same architecture as on Windows.
macOS Login Items may include Chrome or Google Software Update: System Preferences → General → Login Items → remove any Google entries you don’t want starting at boot. Google Update is less aggressive on macOS than Windows but can still run periodically.
Progressive Web Apps (PWAs) and background behaviour
PWAs installed through Chrome (sites that offer “Install as app” option — Spotify Web, Google Docs, Notion, etc.) have their own standalone processes separate from the main browser. An installed PWA can run in the background independently.
Installed PWAs appear in the Windows taskbar or macOS Dock as their own applications. If you want to prevent a PWA from running in the background: open it → the three-dot menu → “Remove app” to uninstall it completely. Or: the app’s own settings may include a “Launch on startup” or “Run in background” option. Disabling these keeps the PWA available to open manually without it consuming resources when you haven’t opened it.
Push notifications without background running
An important distinction: Chrome push notifications don’t require Chrome to be running with the background apps setting enabled on modern Chrome. Chrome’s notification service handles push notifications at a lower level than the browser windows. You can receive push notification messages from sites that have notification permission even with background apps disabled and Chrome closed.
This is because push notifications in Chrome are delivered via the Chrome browser’s notification infrastructure rather than through extension background pages. If you’ve enabled notifications for a web service (say, your project management tool), those notifications can appear even when Chrome isn’t visibly running — which may surprise you if you disabled background apps specifically to prevent this.
To stop push notifications entirely: chrome://settings/content/notifications → either set global default to “Don’t allow sites to send notifications” or remove specific sites from the allowed list. This stops notification delivery completely, regardless of background app settings.
The system is designed with reasonable defaults for most users: background apps off lets Chrome close cleanly while push notifications still work for sites you’ve explicitly permitted. If you want Chrome to have absolutely no background presence: disable background apps, disable push notifications, and disable the GoogleUpdate service. At that point Chrome is entirely dormant until you actively open the browser.
Startup boost — Chrome’s additional background feature
In some Chrome versions and on Windows particularly: Chrome includes a “Startup boost” feature that keeps a minimised browser process running at Windows startup, so Chrome opens faster when you launch it. This is separate from the background apps setting.
chrome://settings → System → “Startup boost — Enable Google Chrome to start faster.” If this is On: Chrome loads a hidden instance at startup so it’s preloaded when you click the icon. Disable this if you don’t want Chrome running in the background from the moment Windows boots.
Combined with the background apps setting, startup boost means Chrome is potentially running from the moment you boot Windows until the moment you shut down. For most users on modern hardware this doesn’t cause noticeable issues. For machines with limited RAM or users who want tight control over what’s running: both settings should be turned off.
Chrome’s memory-saving impact on background tabs
The Memory Saver setting (chrome://settings → Performance → Memory Saver) is related but distinct: it manages open-but-inactive tabs within Chrome, putting them to sleep to save RAM. This doesn’t affect whether Chrome runs in the background when closed; it affects resource use when Chrome is open with many tabs.
Enabling Memory Saver is generally worth doing for anyone with many open tabs — it can halve Chrome’s RAM usage during active browsing. For the specific problem of Chrome running after being closed: the background apps setting and startup boost are the relevant controls. Memory Saver doesn’t help with that scenario.
To summarise the full set of controls for Chrome’s background behaviour: the System section in Chrome settings (chrome://settings → System) contains the main switches — background apps and startup boost. Extensions with background pages are managed per-extension. Google Update is a Windows service managed through Services. Push notifications are managed through chrome://settings/content/notifications. Each of these is a separate system; controlling all of them gives you complete control over Chrome’s presence on your machine when you’re not actively using the browser.
Checking system startup impact
To see Chrome’s actual startup impact on your Windows machine: Task Manager → Startup apps tab → look for Chrome or any Google services. The “Startup impact” column shows “Low,” “Medium,” or “High.” Chrome with startup boost on typically shows Medium or High impact — it’s pre-loading significant browser infrastructure before you open it.
Right-click Chrome in the Startup apps list → Disable. This prevents Chrome from starting any processes at boot. Note: this disables startup boost but also removes Chrome from the startup list entirely. If you had Chrome configured to open at startup intentionally (via a startup shortcut), you may want to handle this differently — disable the startup boost setting in Chrome itself rather than disabling Chrome from the startup list entirely.
For users whose primary concern is boot time rather than ongoing background usage: disabling Chrome from startup apps and turning off startup boost can meaningfully reduce Windows boot time. Boot time improvement varies by machine, but for machines where Chrome is a High-impact startup item: 5-15 seconds of boot time can be recovered.
One more environmental note: in corporate environments, IT departments often control which background Chrome processes run via Group Policy. A managed Chrome installation may have startup boost or background apps settings locked to specific states. If you notice the settings are greyed out or reset after changing them: an administrator policy is controlling them. Check chrome://management to see if Chrome is managed on your device and what policies are active.
For personal machines: all of the settings described in this guide are fully user-controllable. The combination of disabling background apps, turning off startup boost, and reviewing extension background pages gives you precise control over when Chrome runs and what resources it uses when you’re not actively browsing.
If you use Chrome on multiple devices: background app settings, startup boost, and notification permissions are all per-device rather than synced through Chrome Sync. Changing these settings on your work laptop doesn’t affect your home desktop. Each machine needs to be configured independently. This is intentional — a desktop that’s always on might benefit from Chrome’s background notification delivery, while a laptop on battery might not. Device-specific configuration makes sense in this case, even if it means doing the setup more than once. Related: Disable Chrome Auto Sign.
