How to stop Chrome from opening on startup

To stop Chrome from opening on startup, quit Chrome, then disable it in your operating system’s startup settings. On Windows, open Task Manager > Startup > set Chrome to Disabled. On macOS, go to System Settings > Login Items and remove Chrome. On ChromeOS, manage apps in Settings > Startup apps. On Android, restrict background activity and notifications; on iOS, update background app refresh settings. These evergreen steps address common causes and include verification checks to confirm Chrome no longer launches automatically across platforms.

Verify Chrome is set to not start automatically

After changing settings, restart your device and confirm Chrome does not open on startup. Watch Task Manager (Windows), Activity Monitor or Login Items (macOS), or your system’s startup app list to verify. If Chrome still opens, a shortcut, scheduled task, extension, or profile may override your changes. The following sections provide step-by-step guidance per platform, explain related settings, and help you troubleshoot remaining causes.

Understand why Chrome might open on startup

Chrome can launch at startup through multiple mechanisms. On each platform, different settings and data can cause it to start automatically:

Operating system startup applications list.
Chrome settings such as Continue where you left off or open specific pages.
Scheduled tasks or background services (Windows Task Scheduler, macOS launch agents/daemons).
Browser extensions or third-party utilities that register Chrome at boot.
User profile or shortcut configurations (e.g., a startup shortcut pointing to Chrome).

Identifying the mechanism helps you choose the right fix and avoid repeated attempts if the root cause persists.

How to stop Chrome from opening on startup on Windows

Use Task Manager to prevent Chrome from starting with Windows. If that doesn’t resolve it, check the Startup folder and Task Scheduler.

Disable via Task Manager

Right-click the taskbar, select Task Manager, go to the Startup tab, find Google Chrome, and click Disable. Reboot to confirm it no longer starts. If it remains enabled, you may need to disable it from other locations.

Disable via Startup folder

Press Win + R, paste shell:startup to open the current user’s Startup folder, and remove any Chrome shortcuts. Also check the all-users Startup folder (shell:common startup) and remove shortcuts there.

Check Task Scheduler

Open Task Scheduler and search for tasks referencing chrome.exe. If a task is set to run at log on and is enabled, review its details and disable or delete it if appropriate. Be cautious with built-in Windows tasks that may launch processes intentionally.

How to stop Chrome from opening on startup on macOS

macOS controls startup items in System Settings. Removing Chrome from Login Items stops it from launching automatically.

Go to System Settings > Users & Groups > Login Items, locate Google Chrome, and remove it by clicking the minus (−) button. You can also drag items to reorder or disable without removing them.

Check user agents and background services

Some apps install launch agents or background helpers. Inspect common locations like ~/Library/LaunchAgents, /Library/LaunchAgents, ~/Library/LaunchDaemons, and /Library/LaunchDaemons for any .plist files referencing Chrome. Use launchctl list to review loaded services if you’re comfortable with the command line.

How to stop Chrome from opening on startup on ChromeOS

ChromeOS manages startup apps in Settings. Disabling them prevents Chrome or extensions from auto-starting at boot.

Settings > Apps > Startup apps

Open Settings, go to Apps > Startup apps, and toggle off any items you don’t want to start automatically. Items that open Chrome or rely on Chrome extensions will appear here if configured to start at boot.

How to stop Chrome from opening on startup on Android

Android controls app start behavior through multiple settings: background restrictions, battery optimizations, and notification permissions.

Restrict background activity

Go to Settings > Apps > Chrome > Battery and restrict background activity if available. Note that this may affect background sync and notifications.

Battery optimization

Settings > Apps > Special app access > Battery optimization allows you to set Chrome to Don’t optimize so it’s excluded from aggressive battery restrictions, but this isn’t the same as preventing startup. For less aggressive starts, choose optimized and observe behavior.

Disable unwanted notifications and autostart permissions

Settings > Apps > Special app access > Autostart lets you control whether apps can start at boot. Disable autostart for Chrome if present. Also review notifications and clear defaults if needed.

How to stop Chrome from opening on startup on iOS

iOS apps can’t typically launch at boot like desktop OSes, but background app refresh and settings can affect perceived startup behavior.

Background App Refresh

Go to Settings > General > Background App Refresh and set Chrome to Off or choose Low Data Mode to limit background fetches.

Notifications and extensions

Settings > Notifications > Chrome should be reviewed if you see frequent alert triggers. Also check Settings > Safari > Extensions to remove or disable Chrome-related extensions that might affect behavior.

Troubleshooting when Chrome still opens on startup

If Chrome still opens after following the platform-specific steps, check these common causes:

Shortcuts: Remove Chrome shortcuts from the Startup folder (Windows), desktop, or applications folder (macOS).
Chrome settings: Continue where you left off or open specific pages on startup; turn these off in Settings > On Startup.
Extensions or policies: Extensions and enterprise policies can modify startup behavior. Audit installed extensions and check policies if applicable.
User profile issues: Create a new Chrome profile to test if the behavior is profile-specific.
Third-party apps: Some utilities manage app starts across platforms; verify their configurations.

Platform	Primary setting location	Verification method	Typical scope
Windows	Task Manager > Startup tab	Restart and observe Task Manager’s startup Apps status	User + system-wide if placed in common Startup folder
macOS	System Settings > Users & Groups > Login Items	Restart and check Login Items list or use activity monitoring	User-specific; agents/daemons require user or system directory inspection
ChromeOS	Settings > Apps > Startup apps	Reboot and review startup apps list	Device-level for managed users; per-user settings apply
Android	Settings > Apps > Chrome > Battery; Autostart if available	Check app behavior after reboot and review battery usage	Device-level; OEM variations may change paths slightly
iOS	Settings > General > Background App Refresh; Notifications	Monitor background activity after reboot and review notification settings	Device-level; limited background execution by default

Chrome offers in-browser controls that influence what opens when the browser starts:

Open tabs: Continue where you left off, open the new tab page, or open specific pages on startup.
Session management: Sessions and restores can create the impression of automatic start if a session was not closed properly.
Extensions: Some extensions can restore pages or inject behavior at startup. Audit and remove unnecessary extensions.

Review Settings > On Startup (or chrome://settings/onStartup) and set it to Open the new tab page or Show empty page if you don’t want Chrome to restore previous sessions automatically.

When to seek additional help

If you’ve disabled startup entries and Chrome still opens, consider advanced diagnostics:

Create a new Chrome profile to test profile-specific issues.
Check for enterprise policies that may enforce startup behavior (chrome://policy).
Review scheduled tasks (Windows) or launch agents (macOS) for non-standard entries.
Temporarily disable extensions and restart to isolate extension-related causes.

Platform-specific support resources and forums can help if the issue persists after these steps. This evergreen guide remains applicable across Chrome versions and OS updates unless platform behaviors change fundamentally.