sodcalculator

10 Tech How-To

Why Chrome Flags Reset After Restart & Keep Settings

Guide 10-50589 · Updated · Step by step

Chrome flags reset after a restart because they are experimental features that Chrome intentionally resets to default on every launch unless you explicitly enable the “experimental” state for each flag. To keep your settings, you must re-enable each flag after every restart, or use a command-line switch to apply a flag persistently. This article explains why Chrome behaves this way, how to manage flags effectively, and what to do if your flags keep resetting unexpectedly.

What Are Chrome Flags?

Chrome flags are experimental features that are not yet part of the stable Chrome release. They are hidden behind a special page (chrome://flags) where you can enable, disable, or reset them. Flags allow users and developers to test upcoming features before they are officially rolled out. Because they are experimental, they may be unstable, cause performance issues, or conflict with other features, which is why Chrome does not guarantee they will persist across sessions.

Why Chrome Resets Flags on Restart

Chrome resets flags on restart for two main reasons:

  • Stability and security: Flags are not fully tested, and keeping them enabled could lead to crashes, data loss, or security vulnerabilities. Resetting them ensures a clean, stable state on each launch.
  • Intentional design: Chrome treats flags as temporary overrides. The browser is designed to revert to default settings unless a flag is explicitly set to “Enabled” or “Disabled” in the current session. This is a deliberate choice to prevent users from accidentally leaving experimental features on.

In practice, this means that if you enable a flag, close Chrome, and reopen it, the flag will be back to “Default” unless you have taken extra steps to persist it.

How to Keep Chrome Flags Enabled

There are two reliable ways to keep a flag enabled across restarts:

  1. Re-enable the flag manually: After each restart, go to chrome://flags, find the flag, and set it to “Enabled” again. This is tedious but works for occasional use.
  2. Use a command-line switch: Chrome supports command-line switches that can enable certain flags permanently for the current user. For example, to enable the “overlay-scrollbars” flag, you can add --enable-features=OverlayScrollbars to your Chrome shortcut’s target field. This method is more permanent but requires editing the shortcut or launching Chrome from a terminal with the switch.

Note that not all flags have a corresponding command-line switch. For flags that do not, the only way to keep them is to re-enable them after each restart.

Why Flags Reset Even After You Enable Them

If your flags reset even after you enable them, it could be due to one of these reasons:

  • Chrome updates: When Chrome updates, it may reset flags to default as part of the update process. This is more common with major version updates.
  • Corrupted profile: A corrupted user profile can cause Chrome to reset settings, including flags. You can try creating a new user profile to see if that fixes the issue.
  • Group policy: On managed devices (e.g., work or school computers), administrators can set policies that force flags to be reset or disabled. You can check chrome://policy to see if any policies are affecting flags.
  • Chrome Cleanup Tool: If you run Chrome’s cleanup tool, it may reset flags as part of its process.

Should You Use Chrome Flags?

Flags are meant for testing, not for everyday use. They can cause:

  • Browsing instability (crashes, freezes).
  • Security vulnerabilities.
  • Incompatibility with websites or extensions.

If you are not a developer or a power user who understands the risks, it is safer to leave flags at their default state. If you do enable a flag and experience problems, you can reset all flags by going to chrome://flags and clicking “Reset all” at the top of the page.

Alternatives to Chrome Flags

If you want a feature that is currently only available as a flag, consider these alternatives:

  • Wait for the official release: Most flags eventually become stable features in a future Chrome update. You can follow Chrome’s release notes to see when a feature is officially available.
  • Use a Chrome extension: Some flag features have extensions that provide similar functionality, such as dark mode or custom scrollbars.
  • Try Chrome Beta or Canary: These versions include more experimental features by default, but they are also less stable.

Frequently Asked Questions

Can I make Chrome flags permanent?

Yes, for some flags you can use command-line switches to enable them permanently. For others, you must re-enable them after each restart. There is no built-in option to make all flags permanent.

Why did my flags reset after a Chrome update?

Chrome updates can reset flags to default to prevent outdated or incompatible experimental features from causing issues with the new version. This is expected behavior.

Does resetting Chrome flags affect my bookmarks or passwords?

No, resetting flags only affects experimental features. Your bookmarks, passwords, and other browsing data are stored separately and are not affected.

How do I know which flags are safe to enable?

Flags that are marked as “Stable” or “Beta” in the chrome://flags page are generally safer. Flags marked as “Experimental” or “Developer” are more likely to cause issues. Always back up your important data before enabling any flag.

Can I disable a flag that is causing problems?

Yes, go to chrome://flags, find the flag, and set it to “Disabled” or “Default”. If you are unsure which flag is causing the problem, click “Reset all” to revert all flags to their default state.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →