By default, Google Chrome is set to open on startup across supported platforms, which can slow boot times and consume system resources. This evergreen explainer describes why Chrome starts with your system, the behaviors you might see on Windows, macOS, ChromeOS, Android, and iOS, and how to change or disable startup launch safely. You will find step-by-step instructions, related settings to check, and practical considerations for managed devices, so you can keep Chrome available when you need it without it opening automatically each time you start your computer or phone.
Why Chrome opens on startup
Chrome enables a startup launch so you can quickly access your tabs, extensions, and apps after signing in. On most systems, this option is enabled by default during first launch or after an update that reinstalls components. Browser vendors treat startup launch as a user convenience, but it can conflict with faster boot times, limited system memory, or strict device policies in schools and workplaces. Understanding how Chrome registers itself as a startup item helps you manage the behavior rather than merely reacting to it each time you turn on your device.
How to stop Chrome from opening on startup
To prevent Chrome from opening on startup, change the setting inside Chrome, then confirm the operating system is not also configured to launch the browser independently. The steps differ slightly by platform, but the overall pattern is to open Chrome settings, locate System or On startup, toggle a switch to a disabled state, and verify that no other launcher is still triggering Chrome. Use the tables and lists below as quick references for each platform and for checking common edge cases such as pinned shortcuts or managed policies.
Windows
On Windows, Chrome can start via the Startup folder, Task Scheduler, or the startup apps list in Settings. The simplest method is to toggle a setting in Chrome, then remove or disable any remaining shortcut entries. Combining both approaches reduces the chance that Chrome will reappear after updates or user profile changes.
macOS
macOS stores login items per user account and in system-visible locations such as LaunchAgents. Removing Chrome from Users & Groups Login Items and disabling the corresponding LaunchAgent plist entries ensures Chrome does not open automatically at boot. If your organization manages profiles, confirm with IT before editing system-level agents.
ChromeOS
ChromeOS primarily relies on the sign-in state rather than a separate startup app list. Controlling which apps and extensions restore at sign-in is the main way to limit automatic Chrome behavior. In most educational or managed deployments, startup behavior is controlled by administrator policies at the organizational level.
Android
On Android, Chrome rarely opens on its own at device boot, but apps and widgets on your home screen or the Chrome tab restore setting can create the impression it does. Disabling tab restore and restricting background activity for Chrome prevents unwanted launching and conserves battery and memory.
iOS
iOS suspends most background apps after you leave them, so Chrome is not actively running between launches. However, features like StandBy or widgets on the Lock Screen can make Chrome appear to open. Adjusting preferences for tab restoration and disabling unnecessary widgets removes these visual cues.
Chrome in-app settings for startup launch
Chrome includes a straightforward toggle that controls whether the browser attempts to start with the system. This setting is present on Windows, macOS, Linux, and ChromeOS, and it synchronizes across signed-in devices when Sync is enabled. Changing it applies across user profiles on the same machine, though local OS settings or policies can still override it in managed contexts.
Chrome desktop and ChromeOS
| Platform | Setting location | Action to stop Chrome from opening on startup |
|---|---|---|
| Windows and macOS | Chrome menu > Settings > System | Toggle off “Open Chrome on startup” or “Start Chrome and its links in the background” |
| ChromeOS | Chrome menu > Settings > System > On startup | Toggle off “Open the New Tab page” or change startup behavior to “Continue where you left off” only if you do not want automatic restoration |
Android and iOS considerations
Neither Android nor iOS exposes a direct Chrome startup toggle labeled “open on startup.” Instead, control is managed through Chrome settings for tab restoration and through the operating system’s background restrictions. For a leaner start experience, disable tab restoration and minimize background activity for Chrome.
Check OS-level startup settings
After changing Chrome’s internal setting, verify the operating system is not still launching Chrome independently. If shortcuts, scheduled tasks, or login items remain, they can cause Chrome to open even when the browser’s own toggle is disabled. Use the lists and checks below to ensure no lingering entries re-enable automatic launching.
Windows checks
- Open Settings > Apps > Startup and ensure Chrome is set to Off.
- Inspect the current user Startup folder (%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup) for Chrome shortcuts and remove them if present.
- Review Task Scheduler for tasks named with Chrome or containing google_update, and confirm they are disabled or not set to run at logon.
macOS checks
- Open System Settings > Users & Groups > Login Items and remove Chrome.
- Check ~/Library/LaunchAgents for any com.google.*.plist files related to Chrome and move them to a backup folder if needed.
- Confirm no LaunchDaemons or system-level agents are configured by IT or managed software.
ChromeOS checks
- Verify the device is not forcing kiosk or autolaunch policies via administrator settings.
- Confirm that the New Tab page restore or app shortcuts are not configured to open automatically at boot.
Android and iOS checks
- On Android, review Settings > Apps > Chrome > Battery and set background restriction if necessary.
- On iOS, remove any Chrome widgets from the Lock Screen and Home Screen and disable tab restoration in Settings > Chrome.
Behavior and edge cases to expect
Even after disabling startup launch, you might still see Chrome appear in certain situations. These cases are usually by design or related to other system settings, not a failure of the steps above.
- Updates to Chrome can reapply the startup toggle on some platforms; recheck the setting after a major update if Chrome begins opening automatically again.
- Desktop shortcuts or pinned taskbar entries that you double-click manually will open Chrome but are not automatic startup launches.
- In enterprise or school environments, group policies or MDM configurations can override local settings and keep Chrome at sign-in; contact IT to adjust or confirm policy intent.
- If Chrome was set to restore previous sessions, closing the browser without using “Exit” may cause tabs to reappear next time you manually open Chrome, but this is not the same as a system-level startup launch.
Related settings and troubleshooting steps
Several other settings can affect how Chrome behaves at startup and may explain why it seems to reopen. Check these options if you continue to experience unexpected launches or slow boots.
Session restore versus startup launch
Chrome can restore your previous tabs without launching at OS boot. This happens when you close Chrome while tabs are open and enable “Continue where you left off.” That is distinct from opening on startup, but can feel similar if you regularly shut down with windows open. You can adjust this under Settings > On startup or ChromeOS startup behavior.
Background processes and site permissions
Background sync, notifications, and site-specific permissions can cause Chrome processes to wake up after boot even when the browser window is not visible. Limit unnecessary background activity in Settings > Privacy and security > Site settings and adjust your battery and data preferences on mobile devices.
Conflicting software and fast startup
Fast startup features in Windows can delay the full shutdown process and cause apps to reload oddly after a reboot. If Chrome behaves inconsistently after you enable Fast Startup, test by temporarily disabling Fast Startup in Control Panel > Power Options > Choose what the power buttons do > Change unavailable settings > uncheck Turn on fast startup.
When managed settings apply
Schools, enterprises, and other managed environments often control browser behavior through policies that cannot be changed by standard users. If you cannot disable startup launch, the setting may be enforced by an administrator. In these cases, contact IT support with the device and policy details rather than attempting workarounds that might violate acceptable use policies.
Performance and battery impact
Leaving Chrome open on startup can increase boot time, consume RAM, and slightly reduce battery life on laptops and mobile devices. The magnitude varies based on your machine specs, number of tabs restored, and active extensions. If you rely on quick start times or run low on resources, disabling unnecessary startup launches is one of the more effective optimizations, especially on older hardware or devices with constrained memory.
Quick summary checklist
| Platform | Primary action | Secondary checks |
|---|---|---|
| Windows | Toggle Chrome off in Chrome Settings > System and set Chrome to Off in Windows Settings > Apps > Startup. | Remove shortcuts from Startup folder and disable related tasks in Task Scheduler. |
| macOS | Toggle Chrome off in Chrome Settings > System. | Remove Chrome from Login Items and check ~/Library/LaunchAgents for lingering plist entries. |
| ChromeOS | Toggle off “Open Chrome on startup” in Settings > System > On startup. | Confirm kiosk or autolaunch policies are not enforced by admin. |
| Android | Disable tab restoration and restrict background activity for Chrome. | Remove Chrome widgets and avoid third-party autostart managers that may interfere. |
| iOS | Disable tab restoration and remove any Chrome Lock Screen widgets. | Close apps without using Exit so they do not restore as sessions. |
Security and privacy considerations
Disabling Chrome from opening on startup does not affect your ability to use the browser; it only changes whether Chrome launches automatically when you sign in or boot the device. Your bookmarks, history, passwords, and extensions remain intact. If you share a device or are subject to organizational policies, consult IT before changing settings that may be centrally managed.
When to re-enable startup launch
There are valid reasons to keep Chrome opening on startup, such as ensuring communication tools or dashboards are immediately available for work or monitoring. If you decide to re-enable the feature, use the same paths above and toggle the setting back on, or add the desired shortcut to the appropriate startup location for your platform. Maintaining awareness of how startup items affect boot time and system performance helps you make informed decisions over time.
Final notes
Controlling whether Chrome opens on startup is straightforward once you know where to look. The most reliable approach is to disable the setting inside Chrome and confirm that no operating system–level entries or policies are still launching the browser. Periodically review these settings after updates and when working in managed environments to ensure the behavior remains aligned with your preferences and device performance goals.