Chrome flags are experimental settings that aren’t ready for the standard settings interface. They live at chrome://flags — an internal page that looks like a developer tool but is accessible to anyone. Some flags improve performance or add useful features before they’re officially released; others break things. Resetting them is sometimes necessary when something starts behaving unexpectedly after experimentation. If you want the full context, see our How to Manage Google Chrome.
What Chrome flags actually are
Each flag is a toggle for a specific feature that Chrome’s development team is testing. They exist in a “maybe this is a good idea, maybe not” state. Google ships these in the browser to get real-world data before deciding whether to make them permanent settings or abandon them.
When you enable a flag: you’re opting into a feature that may not work correctly, may have side effects on other features, or may disappear in the next Chrome update. Most users never touch flags. Those who do tend to be tech-curious people who read about a specific flag that sounds useful — GPU acceleration improvements, tab management experiments, new UI options — and enable it.
How to reset all Chrome flags to defaults
Navigate to chrome://flags → at the top of the page, click “Reset all” button → Chrome shows a “Relaunch” button → click it. Chrome restarts and all experimental settings return to default values. This takes about 30 seconds.
This is the complete reset — every flag you’ve changed goes back to default. If you remember which specific flag was causing a problem and want to keep the others: find it in the flags list using the search box → change just that flag to “Default.”
Finding and resetting a specific flag
chrome://flags → the search box at the top → type a keyword related to the feature. Flags that are currently enabled (non-default) show at the top of the list regardless of the search, making recently-changed flags easy to find.
Individual flag states: each flag shows a dropdown with “Default,” “Enabled,” or “Disabled.” Setting a flag to “Default” doesn’t necessarily mean “Off” — it means Chrome uses whatever the current default behaviour is for that feature. The default changes between Chrome versions as features graduate from experimental to stable. A flag you set to “Enabled” months ago might now be the default behaviour, making the setting redundant.
Common reasons to reset flags
- Chrome started behaving oddly after you enabled a flag and you’re not sure which one caused it
- A site stopped working correctly and disabling extensions didn’t help
- Chrome’s UI looks different in an unexpected way
- Performance degraded after enabling a “performance improvement” flag that turned out to cause more problems than it solved
- You’re updating to a new Chrome version and want a clean baseline before the version-specific flags take effect
The reset is non-destructive for everything outside flags — your bookmarks, passwords, history, and extensions are unaffected. It only resets the experimental flag states.
Flags to be careful with
Not all flags are equally benign. Some categories worth being cautious about:
- Security flags: disabling security features (certificate verification experiments, sandboxing flags) can expose you to risks. If a “security” flag made browsing feel better, be skeptical about keeping it enabled.
- GPU and rendering flags: enabling GPU features on hardware that doesn’t fully support them causes visual glitches, driver crashes, or freezes. These are the flags most likely to make Chrome unstable.
- Network flags: experimental protocol changes (QUIC, HTTP/3 experiments) work on most sites but break specific servers that don’t support them.
Our guide on Chrome performance optimisation covers the performance settings that don’t require flag modification, and our Chrome stability troubleshooting covers when experimental settings contribute to crashes. For a current list of available flags and their descriptions, Chromium’s developer blog covers new flags in each Chrome release with context on what they do.
Will resetting flags break anything
Generally no. Flags are meant to be toggled — that’s their purpose. Returning to default is always a safe operation. The one scenario where a reset has unintended side effects: if you enabled a flag specifically because something wasn’t working without it. Resetting will remove that fix and the original issue returns.
Example: you enabled “Ignore GPU blocklist” because Chrome wasn’t using hardware acceleration on your specific GPU combination. Resetting flags re-enables the GPU blocklist, and hardware acceleration stops working again. For flags you rely on as fixes: note them down before resetting, then re-enable specifically what you need after the reset clears the problematic ones.
Flags vs Chrome settings — the difference
Regular Chrome settings (chrome://settings) are stable, supported features. Changing them won’t cause instability, and they persist correctly across updates. Flags (chrome://flags) are unstable, unsupported experiments that may change or disappear with any update.
| Feature | Location | Stability |
| Hardware acceleration | chrome://settings → System | Stable |
| Memory Saver | chrome://settings → Performance | Stable |
| Tab grouping (experimental layout) | chrome://flags | May change |
| GPU experiments | chrome://flags | Unstable, hardware-dependent |
| Privacy settings | chrome://settings → Privacy | Stable |
| New tab UI experiments | chrome://flags | May change or be removed |
The practical guidance: use chrome://settings for any setting you want to be reliable and persistent. Use chrome://flags only for temporary experimentation with features you’re willing to reset or lose. If a flag becomes important to your browsing experience: it will eventually graduate to a proper setting in chrome://settings, at which point you can set it there and stop relying on the experimental version.
Chrome updates sometimes change the default state of flags without notice. A flag you enabled six months ago might now be “Default: Enabled” in the new Chrome version, meaning your explicit “Enabled” flag state is now redundant — or a flag you disabled might be removed entirely, with Chrome just handling the feature differently now. After major Chrome updates: it’s worth a quick visit to chrome://flags to check if any of your customised flags have changed context.
Popular flags that often get enabled
Some flags have become well-known in Chrome power-user circles. Worth knowing about even if you’re just reviewing what might be active:
- #enable-parallel-downloading: downloads files in parallel chunks for faster downloads. Now graduated to a permanent Chrome feature, but the flag version was popular for a while.
- #smooth-scrolling: enables pixel-by-pixel scrolling rather than line-by-line. Often enabled on laptops with trackpads. On some systems can cause choppy scrolling rather than smooth — worth experimenting.
- #tab-hover-card-images: shows a thumbnail preview when hovering over a tab. Visual and optional.
- #enable-tab-groups-auto-create: automatically groups related tabs. Divisive — some people love it, others find it intrusive.
- #global-media-controls: consolidated media control toolbar. Now standard in Chrome, but was a flag first.
Many flags that were popular in 2020-2022 have now graduated to standard Chrome settings or been removed. If you’re following old guides that tell you to enable specific flags: always verify that the flag still exists in your current Chrome version before assuming the old guidance is still relevant.
Developer use of flags
Web developers use flags to test sites against upcoming Chrome features before they reach stable users. A common workflow: enable a flag for an experimental CSS feature → test how the site renders → disable flag → adjust site CSS if needed. This way the site works correctly before the feature reaches the majority of Chrome users.
Developers also use flags to simulate older Chrome behaviour for debugging: if a flag controls a feature that broke something, disabling it returns the browser to an older behaviour state for testing. The “Reset all” option is particularly useful after a debugging session — it ensures the development environment returns to a clean state rather than carrying over experiment-specific flag combinations.
Chrome flags on mobile (Android)
chrome://flags works on Chrome for Android too, accessible from the address bar on your phone. Many of the same flags are available, and some are mobile-specific (touch UI experiments, gesture navigation options). The “Reset all” button works the same way on mobile — tap it and relaunch Chrome.
Mobile-specific flags worth knowing about:
- #enable-reader-mode: simplified reading view for articles. Useful on small screens.
- #offline-pages-live-page-sharing: allows sharing current page for offline reading
- #close-tab-suggestions: Chrome proactively suggests closing tabs you haven’t used recently
As with desktop, these flags change between Chrome versions. What’s experimental on one version may be a permanent feature (or gone) in the next update.
The key takeaway for flags: they’re not dangerous to use, but they’re not permanent or reliable either. Use chrome://settings for settings you depend on, chrome://flags for experimentation. The reset button is there precisely because experiments don’t always work as expected, and returning to a clean baseline should be easy. It is — one click, one relaunch, everything experimental is cleared.
Flags and Chrome profiles
An important detail: Chrome flags apply to the entire browser installation, not to individual profiles. If you have a Work profile and a Personal profile in Chrome, changing a flag in one profile affects both. The flag system operates at the browser binary level, below the profile layer.
This is different from Chrome settings, which are profile-specific. Your Work profile can have different extensions, bookmarks, and saved passwords from your Personal profile. But flags are shared. If you’re experimenting with a flag that might cause instability: it affects your Work profile too, not just the profile you’re testing in.
For development testing where you need a completely isolated Chrome environment: use a separate Chrome installation (Chrome Canary, Chrome Beta, or a separate user account with its own Chrome installation) rather than relying on profile separation for flag isolation. This is the proper way to test experimental Chrome features without risk to a browser you rely on for everyday use.
When Chrome resets flags automatically
Chrome may automatically reset flag states in certain circumstances:
- After a major Chrome version update that removes a flag entirely
- After a Windows reinstall or profile migration where Chrome preferences don’t fully carry over
- When Chrome’s local data gets corrupted and the preferences file resets
Chrome doesn’t notify you when a flag is automatically reset — you may just notice the behaviour change. If Chrome starts behaving differently after an update and you had flags enabled: visiting chrome://flags and checking the “Recently changed” section (flags currently at non-default states) shows what’s active. If a flag you relied on disappeared: search for its previous name to see if it was renamed or graduated to a proper setting.
Resetting Chrome flags is one of the safest troubleshooting steps available — no data is lost, no settings outside of flags change, and the operation is instantly reversible by re-enabling specific flags afterward. When Chrome is misbehaving and you’ve tried the standard fixes: a flag reset is a sensible next step that takes under a minute and often resolves unexplained behaviour in experimental feature combinations.
Reporting flag issues to Google
If a flag causes a reproducible problem — a specific crash, a rendering bug, or a feature that clearly doesn’t work as described — you can report it through the Chrome feedback mechanism. Chrome menu (three dots) → Help → Report an issue → in the description, include the flag name (found at chrome://flags), the exact behaviour, and the Chrome version (chrome://version).
Google’s Chrome team actively monitors these reports. Flags that consistently cause problems get reverted quickly; flags that work well graduate to permanent features. User reports of flag-specific issues are part of how Google decides which experimental features are ready for production. This is the actual point of flags as a system — Google gets real-world testing data, users get early access to features, and the feedback loop shapes which experiments become permanent parts of the browser.
For most users: the only flag-related action you’ll ever need is the Reset All button when something goes wrong. The investigation into which specific flag caused a problem, the notes on flags worth re-enabling, and the reporting mechanism for bugs — these are for power users and developers who actively use the flags system. For everyone else: if Chrome is misbehaving and you’ve touched flags at some point, visit chrome://flags → Reset All → Relaunch. Clean state, 30 seconds, and the problem often disappears. You might also run into How to Reset Chrome Settings Safely.
