Why Chromium opens at startup and what it means
Chromium can open on startup because it (or a shortcut) is listed in your operating system startup area, or because a legitimate feature, task, or launcher is configured to launch Chromium at sign-in. On Windows this is often a Startup folder shortcut or a registry/run entry; on macOS a Launch Agent or Login Item; on Linux a .desktop file in autostart directories or a desktop environment autostart setting. Sometimes Chromium creates these entries by default during install, or a site or extension adds them. Understanding where each entry lives is the fastest way to review and remove only what you do not want.
Common causes of Chromium opening at startup
Browser-level settings and features
Chromium itself does not add a system-wide autostart entry on most official builds, but some distributions, third-party packages, or custom installers may change defaults. A common cause is shortcuts placed in Operating System Startup locations or an option in Settings set to open on startup. Extensions, background pages, or launcher apps that open Chromium windows for workflows can also appear as "Chromium starting" at boot. System-level entries are more persistent across browser updates, so checking in your OS and desktop environment is usually most effective.
Platform-specific startup locations
Because the fix depends on where the entry lives, here is a concise reference of typical startup locations that can launch Chromium (or any app). Use it to quickly audit what runs at login.
| Platform | Startup location | What it stores | Typical Chromium entry |
|---|---|---|---|
| Windows | Startup folder (per user or all users) | Shortcuts (.lnk) | Chromium.lnk or wrapper.lnk pointing to chromium.exe |
| Windows | Registry Run keys (HKCU or HKLM) | String values listing executables | "C:\...\chromium.exe" --no-first-run etc. |
| Windows | Task Scheduler | Tasks triggered at logon | Task launching chromium.exe |
| macOS | Login Items (System Settings or launch agents) | Apps or helper agents | Chromium.app in Login Items |
| Linux | XDG autostart (~/.config/autostart or /etc/xdg/autostart) | .desktop files | chromium.desktop or custom.desktop with exec=chromium |
| Linux (DE-specific) | Desktop environment autostart (GNOME/KDE/etc.) | GUI or ~/.config/autostart/*.desktop | Same .desktop mechanism, managed by the DE |
How to stop Chromium from opening on startup on Windows
Remove shortcuts from the Startup folder
Open the user Startup folder with shell:startup, and delete any Chromium shortcuts. To check all users, also open the public Startup folder (common start menu Programs > Start > Startup for all users). Deleting these prevents the shortcut from launching at sign-in without affecting the browser installation.
Check the Registry Run keys carefully
Open regedit and review HKCU\Software\Microsoft\Windows\CurrentVersion\Run and HKLM\Software\Microsoft\Windows\CurrentVersion\Run for entries pointing to chromium.exe. If you find one, you can delete the value name or clear its data. Back up the registry first and be cautious editing HKLM, as it affects all users. If an entry reappears after removal, something (installer, extension, or task) is recreating it.
Inspect Task Scheduler
Open Task Scheduler and look under Task Scheduler Library for tasks that launch chromium.exe. Disable or delete tasks you do not recognize. Tasks created by installers or updaters sometimes reschedule the browser on updates, so check the triggers and actions before removing.
Check system tray and background apps
Some Chromium-based launchers or PWAs can open background windows on startup. In Windows Settings > Apps > Startup, ensure apps you do not want launching are set to Off. If Chromium entries appear there, toggle them off. Then restart to confirm behavior is resolved.
How to stop Chromium from opening on startup on macOS
Manage Login Items in System Settings
Go to System Settings > Users & Groups > Login Items, find Chromium, and remove it by clicking the minus button. This removes the app from launching for your user at login without uninstalling the application.
Check launch agents and daemons
User launch agents are in ~/Library/LaunchAgents; system agents in /Library/LaunchAgents and /Library/LaunchDaemons. Look for .plist files referencing chromium and unload or remove ones you do not recognize. Prefer user-level changes when possible, and verify file ownership before editing system locations.
How to stop Chromium from opening on startup on Linux
Disable autostart .desktop files
Look for Chromium desktop entries in ~/.config/autostart/ and /etc/xdg/autostart/. You can rename or remove the .desktop file for Chromium (e.g., mv ~/.config/autostart/chromium.desktop ~/.config/autostart/chromium.desktop.bak). Some distros also manage autostart via desktop environment settings; if so, remove the entry from the DE’s startup applications list.
Check desktop environment autostart managers
GNOME uses Settings > Applications > Startup; KDE uses System Settings > Startup and Shutdown > Autostart. Remove any Chromium or Chromium-based launchers you do not want. After removing entries, log out and back in (or reboot) to ensure changes take effect.
Verify the change took effect
After you remove entries, restart your machine or log out and back in, and observe whether Chromium launches automatically. If it still starts, repeat the checks in the relevant sections for other user profiles, system-level locations, or background tasks that may be triggering it. On Windows, Autoruns (by Microsoft/Sysinternals) can show exactly what is configured to run at boot; use it cautiously to confirm cleanup.
Keeping Chromium from returning at startup
To prevent Chromium (or a Chromium-based app) from re-adding autostart entries, avoid "installers" that bundle options to launch on startup, and review permissions before installing extensions or utilities that manage windows. Periodically audit startup locations after major updates. If Chromium updates and reintroduces an entry, repeat the relevant removal steps for your platform. On Windows, monitoring the Startup folder and Registry Run keys is usually sufficient to catch most recurrences early.
When the behavior looks unusual or malicious
Unexpected new entries, multiple copies of Chromium, or processes that respawn after removal can indicate unwanted software or adware. In these cases, run anti-malware scans with reputable tools for your platform, update your browser and OS, and remove unknown startup entries. If you are unsure whether an entry is safe, capture its file path and command line (via Autoruns or terminal inspection) before deleting it, so you can restore it if needed.
Conclusion
Stopping Chromium from opening on startup is usually a matter of finding the entry in the correct OS startup location and removing or disabling it. Check the Startup folder, registry, Login Items, or autostart .desktop files depending on your platform, then confirm the fix by restarting. Regular audits of startup items help keep your system clean and prevent Chromium or other apps from re-adding themselves without your consent.