Bookmend
← BlogCHROME TIPS & FIXES

Chrome Flags Explained: 15 Worth Turning On (and How to Reset Them)

By
⚡
THE SHORT ANSWER

Chrome flags are experimental settings at chrome://flags — features Google is testing before releasing to everyone. Most flags are safe to try, but they can change, break, or disappear between Chrome updates. Enable them one at a time, and reset all flags at once via the Reset all button at the top of chrome://flags if something goes wrong. Useful ones to try: #enable-parallel-downloading for faster downloads, #enable-force-dark for dark mode on all sites, and #smooth-scrolling for fluid page navigation.

Chrome Flags Explained: 15 Worth Turning On (and How to Reset Them)

Chrome has a hidden page called chrome://flags that exposes experimental features before they’re available to everyone. Most Chrome users never open it. Some features that are now standard in Chrome — like certain performance improvements and the Reading List — started as flags. Here’s what it is, how to use it safely, and 15 flags that are currently real and worth trying.

Important caveat upfront: Flags are experimental. They can change between Chrome updates, stop working, or be removed entirely. The 15 flags listed below were verified as real, searchable flags in Chrome as of this writing, but any individual flag may be updated, renamed, or removed in a future Chrome release. Always note what you’ve enabled so you can reverse changes if needed.

What chrome://flags Is

Type chrome://flags into the address bar and press Enter. You’ll see a page with hundreds of toggles, each controlling an experimental feature. The page is divided into a main section showing flags available for your platform, and the controls for each flag are usually a dropdown with options like Default, Enabled, and Disabled.

Why these features exist here instead of in Settings: Google’s Chrome team uses flags as a testing mechanism. They can enable a feature for a subset of users, gather data on stability and usage, and then graduate it to a permanent setting — or remove it if it causes problems. Flags are the staging area.

What happens when you change a flag: Chrome asks you to relaunch. The new setting takes effect on the next startup. Most flags only affect Chrome’s behavior on your current device — they don’t sync to other devices the way Sync settings do.

How to reset everything: At the top-right of the chrome://flags page, there’s a Reset all button. Clicking it restores every flag to Default and prompts a relaunch. Use this if you’ve enabled several flags and something breaks — it’s the fastest way back to a clean state.

15 Flags Worth Trying

Performance Flags

1. Parallel Downloading Search term in flags: parallel-downloading Flag: #enable-parallel-downloading

Splits file downloads into multiple simultaneous connections, working like a built-in download accelerator. Particularly useful for large files (installers, videos, archives) on connections with headroom. Small files show no noticeable difference.


2. GPU Rasterization Search term: gpu-rasterization Flag: #enable-gpu-rasterization

Offloads page rendering from the CPU to the GPU. Can improve scrolling performance and reduce CPU load on pages with complex layouts or animations. If Chrome becomes unstable after enabling this, your GPU drivers may be outdated — disable the flag and update drivers first.


3. Zero-Copy Rasterizer Search term: zero-copy Flag: #enable-zero-copy

Reduces memory-copying operations between Chrome’s rendering process and the display. The result is better RAM efficiency and reduced battery consumption, particularly on systems with integrated graphics. Best combined with GPU Rasterization.


4. Smooth Scrolling Search term: smooth-scrolling Flag: #smooth-scrolling

Enables hardware-accelerated, animated scrolling instead of jumping in discrete steps. Pages flow as you scroll rather than snapping to positions. Some users find the animation adds perceived latency; others find it significantly more comfortable. A matter of preference.


5. Prerender2 Search term: prerender2 Flag: #prerender2

Pre-loads pages that Chrome predicts you’re likely to navigate to next (based on links you hover over or the structure of the current page). When you click, the page loads from a pre-rendered state rather than from scratch. The improvement is most noticeable on slower connections.


Network Flags

6. Experimental QUIC Protocol Search term: quic Flag: #enable-quic

Enables the QUIC network protocol, which uses UDP instead of TCP. QUIC handles packet loss and connection interruptions better than TCP, reduces connection setup overhead, and can improve page load speed on connections with any latency. Originally developed by Google and now an IETF standard (HTTP/3). Most major sites support it.


7. Test Third-Party Cookie Phaseout Search term: third-party-cookie Flag: #test-third-party-cookie-phaseout

Simulates browsing without third-party cookies, so you can see which sites break or behave differently without cross-site tracking. Useful if you want to preview what a more privacy-preserving web looks like before it becomes standard. Some sites will show authentication issues or broken personalization with this enabled.


Visual and UI Flags

8. Auto Dark Mode for Web Contents Search term: force-dark Flag: #enable-force-dark

Forces a dark theme on every website. Chrome analyzes each page and inverts light elements. Quality varies by site — well-designed pages often look fine, others can look patchy. If you use dark mode everywhere else in your system, this fills the gap for sites that haven’t implemented their own dark mode. Can be configured for different inversion strategies from the dropdown.


9. Vertical Tabs Search term: vertical-tabs Flag: #vertical-tabs

Moves the tab strip from the top of the window to a collapsible left sidebar. Useful for power users with many tabs open simultaneously — vertical space is typically less constrained than horizontal. Note: availability of this specific flag varies by Chrome version; search for “vertical” in chrome://flags to see what’s currently present.


10. Tab Strip Declutter Search term: tab-strip-declutter Flag: #tab-strip-declutter

Dims tabs you haven’t used recently so they stand out less from the active tab. A visual nudge rather than a functional change — it doesn’t close or hide tabs. Useful for people who work with 10-20+ tabs open and want the active tabs to be more visually distinct.


11. Tab Audio Muting UI Control Search term: tab-audio-muting Flag: #enable-tab-audio-muting

Adds a direct mute control to tab audio indicators. Instead of right-clicking the tab and choosing “Mute site,” you can click the audio icon on the tab directly to mute/unmute. Small quality-of-life improvement if you frequently manage tabs that start playing audio.


12. Tab Hover Card Images Search term: tab-hover-cards Flag: #tab-hover-card-images

Shows a thumbnail preview of the page when you hover over a tab in the tab strip. Useful for identifying what’s in a tab when you have many tabs open and the titles are truncated. The preview shows the last visible state of the page.


Privacy and Features

13. Show Autofill Type Predictions Search term: autofill-type-predictions Flag: #show-autofill-type-predictions

Displays Chrome’s autofill field type predictions as placeholder text in form fields. Helps Chrome fill in complex forms more accurately by making the predicted field types visible to you during form interaction. Technical, but useful if Chrome autofill frequently gets field types wrong.


14. Reading Mode Search term: read-anything Flag: #read-anything

Adds a Reader Mode feature that strips ads and distracting elements from articles, presenting text in a clean, adjustable reading view. If this flag is no longer present in your Chrome version, the feature may have graduated to a permanent setting — check the three-dot menu or the address bar for a reading mode icon on article pages.


15. Omnibox Steady State Suggestions Search term: omnibox-steady-state Flag: #omnibox-steady-state-suggestions

Adjusts how Chrome presents URL and search suggestions in the address bar (omnibox) when you’re on a stable, loaded page. Affects the look and behavior of address bar suggestions when not actively typing. Useful to try if you find the default address bar suggestion behavior cluttered.


How to Enable a Flag

  1. Type chrome://flags in the address bar and press Enter
  2. Use the search box at the top to find the flag by keyword
  3. Click the dropdown next to the flag and select Enabled
  4. Click Relaunch when Chrome prompts you

Enable one at a time: If you enable several flags at once and something breaks, you won’t know which one caused it. Enable, test, then enable the next.

How to Disable a Specific Flag

  1. Go to chrome://flags
  2. Search for the flag
  3. Change its dropdown back to Default
  4. Relaunch Chrome

How to Reset All Flags at Once

Go to chrome://flags and click the Reset all button at the top-right. This restores every flag to Default in a single action. Use this as the recovery option when multiple flags are enabled and something is behaving unexpectedly — it’s faster than tracking down each one individually.

Flags vs Chrome Settings

Not everything that looks like a flag belongs in chrome://flags. Chrome has a separate page at chrome://settings for user-facing, stable settings — like default search engine, privacy controls, and extension management. Flags are specifically for experimental and in-development features. If a feature you enabled via a flag later appears in Settings, it’s been graduated from experimental to stable.

Chrome Channels and Flags

Chrome is distributed through four release channels: Stable, Beta, Dev, and Canary. Each channel has its own flags page and its own set of available flags. Flags that appear in Chrome Canary or Dev may not be available in Stable Chrome — they are typically testing grounds for features that will gradually move toward Stable.

Stable Chrome (what most users run): The flags page contains a limited set of experimental options that have been deemed stable enough to expose to all users.

Beta Chrome: Available at google.com/chrome/beta. Has more flags than Stable and lets you preview features one or two releases ahead.

Chrome Canary: Available at google.com/chrome/canary. Runs on the bleeding edge, updates daily, and has the most flags. Canary can be installed alongside Stable Chrome and uses a separate profile — useful for testing flags without affecting your main browsing.

If a flag you read about online does not appear in your chrome://flags, it may only exist in Canary or a newer version than you are running. Check your Chrome version at chrome://settings/help and compare it to the version where the flag was introduced.

What Happens When a Flag Disappears

Flags are removed for one of two reasons:

  1. The feature graduated to a permanent setting. It is now enabled for everyone or available in chrome://settings. If you had a flag enabled for a feature that is now standard, Chrome will continue to show the behavior — the flag just no longer controls it.

  2. The feature was abandoned or removed. The experiment was cancelled. The behavior goes away when you update Chrome. If you enabled a flag for a feature that has since been removed, Chrome will behave as if the flag never existed after the update.

You can check what Chrome version removed a particular flag by searching the Chromium project’s Gerrit code review tool (chromium-review.googlesource.com) or the Chromium bug tracker (bugs.chromium.org), where flag additions and removals are tracked with commit history.

A Note on Bookmend and Chrome Settings

If you’re looking to improve how Chrome handles your saved bookmarks specifically — rather than Chrome’s browser performance — Bookmend is a Chrome extension that adds full-text search, dead-link detection, and Wayback Machine recovery to your existing bookmark collection. It works alongside whatever Chrome flags you have enabled and installs from the Chrome Web Store without any flag changes needed.

Frequently asked questions

Chrome://flags is a built-in Chrome page that exposes experimental features not yet enabled for all users. These are features Google is testing or developing — some will become permanent Chrome features, some will be removed, and some will stay as optional settings indefinitely. You access it by typing chrome://flags into the address bar and pressing Enter.

Most flags are safe to try, but they are experimental by definition. A flag can change behavior between Chrome updates, stop working, cause certain sites to break, or occasionally cause Chrome to crash. The standard advice is: enable flags one at a time, test after each change, and note what you've changed so you can reverse it if needed. The 'Reset all' button at the top of chrome://flags restores every flag to default.

Go to chrome://flags and click the Reset all button at the top-right of the page. This restores every flag to its default state. Relaunch Chrome when prompted.

Sometimes. Flags you've enabled may persist across Chrome updates, or they may be reset. Some flags are removed entirely in newer versions — if a flag you enabled no longer appears after an update, it was removed (often because the feature was either shipped as a permanent feature or abandoned).

The #enable-parallel-downloading flag splits a file download into multiple simultaneous connections. Instead of downloading a file sequentially end-to-end, Chrome grabs several segments simultaneously and reassembles them. For large files on stable connections, this can significantly reduce download time. It has no effect on small files or already-fast connections.

The #enable-force-dark flag (Auto Dark Mode for Web Contents) applies a dark theme to every website, even those without a native dark mode. Chrome inverts light colors to dark. It's imperfect — some sites look awkward — but for heavy dark-mode users who find certain sites eye-straining at night, it's a useful option without needing an extension.

QUIC (#enable-quic) is a network protocol developed by Google that uses UDP instead of TCP. It reduces connection setup time and handles packet loss better, resulting in faster page loads on connections with some latency or packet loss. It's particularly helpful on mobile networks and less-than-ideal Wi-Fi.

It can, particularly on systems where the GPU is underutilized. GPU Rasterization (#enable-gpu-rasterization) offloads page rendering from the CPU to the GPU, which can improve scrolling smoothness and reduce CPU load on graphics-heavy pages. If Chrome becomes unstable after enabling this, disable it — GPU driver compatibility varies.

Tab Strip Declutter (#tab-strip-declutter) visually fades tabs you haven't used recently so they're less prominent in the tab bar. It's a visual nudge for people who habitually open many tabs — inactive tabs appear dimmer, making the active ones easier to identify. It doesn't close or remove tabs.

There has been a #vertical-tabs flag in some Chrome versions, but vertical tab functionality in Chrome's official implementation has been in and out of flags as it's been developed. Check chrome://flags and search 'vertical' to see what's currently available in your Chrome version.

Go to chrome://flags and use the search box at the top of the page. Type a keyword (like 'download' or 'dark') and matching flags appear. This is much faster than scrolling through the full list.

Nafiul Hasan
WRITTEN BY

Nafiul Hasan is the founder of Bookmend. He builds tools that fix small, specific frustrations rather than reinvent them — Bookmend started after losing a decade of bookmarked research links to dead pages he couldn't get back. He writes here about link rot, how the Wayback Machine actually works, and what's real versus marketing in the browser-extension space.

Drafted with AI assistance, reviewed and edited by Nafiul Hasan.How we write

FounderChrome extension builderWrites about link rot & bookmarks