What are Chrome flags?
Chrome flags are switches for features Google is still building, testing or retiring. They sit on one internal page, chrome://flags, titled Experiments. Each flag has a display name, a short description, an internal id (the part after the # in a flag link) and a menu that starts on Default.
Default means Chrome decides. Choosing Enabled or Disabled overrides that for every profile in this Chrome installation. Chromium saves your choices in the browser's Local State file, under the browser.enabled_labs_experiments preference, and applies them the next time Chrome starts. That's why nothing changes until you relaunch.
The flags Chrome shows depend on your version and your system. A Windows laptop, a Mac and an Android phone each see a different list. Entries built for other systems move to the Unavailable tab with the note "Not available on your platform."
How do I open chrome://flags?
Type chrome://flags into Chrome's address bar and press Enter. Typing about:flags opens the same page, which is where the older name "chrome about flags" comes from.
- Open a new tab in Chrome on Windows, macOS, Linux, ChromeOS or Android.
- Click the address bar, type
chrome://flagsand press Enter. - Use the Search flags box at the top to filter by name, id or description.
- To jump straight to one flag, add its id:
chrome://flags/#enable-parallel-downloadingopens the page and highlights that entry.
chrome://flags
about:flags
chrome://flags/#enable-parallel-downloadingHow to enable Chrome flags settings
Find the flag, change its menu from Default to Enabled, then click Relaunch. That's the whole process for any flag on the page.
- Open the flag's address, for example
chrome://flags/#enable-tab-audio-muting(copy it from the explorer above). - Open the menu next to the highlighted flag. Most offer Default, Enabled and Disabled. Some list named options, such as scrollbar styles or colour profiles.
- A Relaunch button appears at the bottom of the page. Save any unfinished work, then click it. Chrome reopens your tabs.
- Check the result. If nothing looks different, reload the page you're testing; the feature may also already be on by default.
A few flags take text instead of a menu. Insecure origins treated as secure has a box for a comma-separated list such as http://192.168.1.20:8080, meant for developers testing on a local server.
Chrome about flags settings on work and school devices
An administrator can block the flags page on a managed browser. On ChromeOS, flags that apply to the whole system can only be set by the device owner, and the page tells you who that is.
How to reset Chrome flags
Open chrome://flags, click Reset all at the top of the page, then click Relaunch. Every flag returns to Default. Try this first whenever Chrome starts crashing, flickering or showing blank pages after a flag change.
If Chrome won't open after changing a flag
With Chrome fully closed, rename the Local State file in Chrome's user data folder (for example to Local State.old). Chrome starts with default flags and creates a fresh file. This also resets other browser-wide state kept in that file, so use Reset all whenever Chrome can still open.
| System | Folder that contains Local State |
|---|---|
| Windows | %LOCALAPPDATA%\Google\Chrome\User Data |
| macOS | ~/Library/Application Support/Google/Chrome |
| Linux | ~/.config/google-chrome |
| ChromeOS and Android | Not user-accessible; use Reset all, or clear Chrome's app data on Android as a last resort |
Are Chrome flags safe?
Most flags are safe to try because they're easy to undo, but none are supported. The flags page opens with a warning: "By enabling these features, you could lose browser data or compromise your security or privacy." How risky a flag is depends on what it touches.
| Rating | What it means | Examples |
|---|---|---|
| Low risk | Cosmetic or easy to undo. Worst case is a visual glitch. | Tab audio muting, Overlay Scrollbars, Parallel downloading |
| Some risk | Can cause rendering glitches, break some sites, or change while it's developed. | GPU rasterization, Strict-Origin-Isolation, Experimental Web Platform features |
| High risk | Weakens a security check or forces hardware Chrome has blocked. | Override software rendering list, Insecure origins treated as secure, Unsafe WebGPU Support |
- Change one flag at a time, so you know which one caused a problem.
- Note what you changed. Reset all is quick, but it also clears the flags you wanted to keep.
- Switch developer flags off when you finish testing.
- Remember that the warning says enabled features apply to all users of this browser, not just your profile.
The best Chrome flags worth trying
There's no universal best list. The useful ones fix a specific annoyance. These are the flags in the explorer with a concrete everyday reason to try them; each is low risk and easy to reverse.
| Flag | Try it if | Set to |
|---|---|---|
| Parallel downloading | Large downloads from a fast server feel slow | Enabled |
| Tab audio muting UI control | You silence noisy tabs often | Enabled |
| Auto Dark Mode for Web Contents | You want every site dark with nothing installed | Enabled |
| Hardware Media Key Handling | Media keys pause a browser tab instead of your music app | Disabled |
| Force Global Privacy Control signal | You want a do-not-sell signal on every site | Enabled |
| Hardware-accelerated video decode | Videos show green frames or black boxes | Disabled |
Chrome flags for speed
Most speed flags make little difference on a healthy computer, because Chrome already uses GPU rasterization, prerendering and QUIC on most devices. Parallel downloading can help big downloads. Override software rendering list is for broken graphics setups and often makes things worse. If Chrome feels slow, too many open tabs and heavy extensions are the usual cause, and a tab manager helps more than any flag.
Chrome flags dark mode option
The dark mode flag is Auto Dark Mode for Web Contents (#enable-force-dark). It darkens every site, including ones with no dark theme, but has no per-site toggle and can make images and logos look wrong. It only affects web pages; Chrome's own tabs and toolbar follow your system theme. For per-site control, Dark Reader does the same job without a flag, and our dark mode extensions page compares the options.
Chrome flags on Android, iOS and ChromeOS
Flags on Android work the same way: type chrome://flags in the address bar, change a flag and tap Relaunch. The list differs from the desktop one, and the Platform filter above shows which entries apply.
- Android: same page, same Reset all button. Flags like Smooth Scrolling and Elastic Overscroll apply; tab strip and picture-in-picture window flags don't.
- iPhone and iPad: Chrome for iOS keeps a separate, much shorter flag list in its own source file. The flags in this explorer are for desktop and Android.
- ChromeOS: the page also holds flags for the ChromeOS system interface. System-wide flags can only be set by the device owner, and the button says Restart instead of Relaunch.
The ash debug shortcuts flag
#ash-debug-shortcuts (Debugging keyboard shortcuts) is a ChromeOS-only flag that adds extra keyboard shortcuts for debugging Ash, the ChromeOS system interface. It's present in Chrome 155 with no expiry set. It's meant for developers and does nothing on Windows, macOS or Linux.
Why is a flag missing from chrome://flags?
Usually because it expired or was removed. Every flag has an expiry milestone, and Chrome hides it once your major version is past that number. Flags for features that launched, or were dropped, get deleted from the source.
- Recently expired: for two releases a temporary flag, such as
temporary-unexpire-flags-m154in Chrome 155, brings back flags that just expired. After that they're gone. - Removed: once-popular flags such as SameSite by default cookies, tab hover card images and the scrollable tab strip no longer exist in Chrome 155. Guides that still mention them are out of date.
- Wrong platform: the entry sits under the Unavailable tab, marked "Not available on your platform."
- Different name: search by internal id as well as by name, because ids are what flag links use.
Flags vs extensions: which should you use?
Use a flag to change how Chrome itself behaves for a while. Use an extension when you want a feature that's configurable and survives updates. A flag can vanish in any release; a well-maintained extension keeps working.
| Goal | Flag route | Extension route |
|---|---|---|
| Dark mode on every site | Auto Dark Mode for Web Contents | Dark Reader, with per-site toggles |
| Fewer open tabs, less memory | No reliable flag | OneTab or another tab manager |
| Clear the cache in one click | None | Clear Cache |
| Mute noisy tabs | Tab audio muting UI control | Not needed once the flag is on |
Before following an online flag guide, check your exact Chrome version with What's My Browser, because the list changes between versions. Moving browsers? The bookmarks converter opens exported bookmark files, and the ad blocker test confirms blocking still works after you change privacy flags.
