Best Chrome Flags to enable in 2026 – Tested on Chrome 148

Most people type chrome://flags into the address bar once, read the warning about experimental features, and close the tab. The warning is not wrong, but it is written for the worst case. For a regular user enabling a handful of well-understood flags, the actual risk is close to zero.

I spent two weeks going through flags on Chrome 148 on a Windows 11 machine, enabling them one at a time, relaunching, and watching what actually changed. Some did nothing visible. A few made things worse. A handful changed how Chrome felt in ways that quietly stuck.

Chrome 148 is the current stable release as of May 2026, version 148.0.7778.96 on Windows. And there is one flag to disable this cycle before you enable anything else.

How to Access Chrome Flags

Type chrome://flags in the address bar and press Enter. Use the search bar at the top to find any flag by name or by its #flag-identifier. Change the dropdown from Default to Enabled or Disabled, then hit Relaunch when Chrome prompts you at the bottom of the screen.

One thing I noticed while testing: flags listed as available on Windows do not always appear on macOS or Linux builds. Everything in this article reflects Chrome 148 on Windows 11 unless stated otherwise.

The Flag to Disable First in 2026

Before the flags worth enabling, this one needs its own section. It became the biggest Chrome story of May 2026.

#optimization-guide-on-device-model

Since Chrome 137, Google has been silently downloading Gemini Nano to eligible machines. Eligible means roughly 16GB RAM, 22GB free disk space, and a GPU with 4GB or more of VRAM. The model lands in a folder called OptGuideOnDeviceModel inside your Chrome profile as a file named weights.bin, and it weighs just under 4GB. Chrome does not ask. If you delete the file, Chrome downloads it again on the next launch.

Security researcher Alexander Hanff documented this in detail in early May 2026, and the thread hit 291 points on Hacker News within hours. Google confirmed the model powers on-device features including scam detection and the Prompt API for developers, and said a Settings toggle to disable it began rolling out in February 2026. If that toggle has not reached your install yet, the flag still works.

To stop it: search optimization-guide-on-device-model in chrome://flags and set it to Disabled. Also disable prompt-api-for-gemini-nano and its multimodal variant. Relaunch Chrome, then delete the OptGuideOnDeviceModel folder from your profile. On Windows it sits at %LOCALAPPDATA%/Google/Chrome/User Data/Default/OptGuideOnDeviceModel. Do the flag step before deleting the folder or Chrome will re-download the model on the next launch.

If you use Chrome AI features like Help me write or on-device scam detection, leave both flags on. The model runs entirely locally with no cloud round-trip, which is genuinely the better privacy arrangement compared to cloud AI. The problem is consent, not the technology itself.

Performance and Rendering Flags

#enable-gpu-rasterization

Moves page rasterization from the CPU to the GPU. On most modern machines Chrome does this by default, but it falls back to software on hardware configurations it considers unsupported. Check chrome://gpu first. If GPU Rasterization shows as Software only, enabling this flag is worth trying. A mid-range laptop I tested that was falling back to software rendering felt noticeably more settled on dense pages after a relaunch. I stopped bracing for the lag before a page finished painting.

#enable-zero-copy

Instead of writing rasterized pixel data to system memory and then copying it to the GPU, this flag lets raster threads write directly to GPU-allocated memory. Less copying, less overhead. The effect is subtle on fast hardware but becomes visible on pages that scroll through large image grids. After enabling this alongside GPU rasterization, a slight stutter I had been half-noticing on image-heavy pages went away. I only identified it as the cause after disabling the flag again.

#disable-accelerated-video-decode

Despite the name, set this to Enabled, which keeps hardware video decode active. When it defaults to off, Chrome burns CPU cycles decoding every video frame in software. On a laptop, the fan difference is the clearest signal on this list. I had this sitting at Default on one machine where Default meant off. The fan ran continuously during any video. After confirming the flag was Enabled, the fan stopped coming on during regular YouTube playback entirely.

#disable-accelerated-video-encode

Same principle for encoding. Matters most during Google Meet calls, Teams in the browser, or screen sharing. With this Enabled, the GPU handles the encode work. Battery drain on a two-hour call dropped noticeably once I stopped Chrome from doing this in software.

#enable-quic

QUIC is the transport protocol underlying HTTP/3. Google’s own properties already use it heavily. Enabling this flag makes Chrome attempt QUIC connections more aggressively across more hosts. The first-connection latency improvement on YouTube, Google services, and QUIC-capable CDNs is real but not dramatic on a fast home connection. On a mobile network it matters more. I left this on and noticed nothing break over two weeks of regular use.

#enable-parallel-downloading

Chrome normally downloads a file as a single stream. This flag splits larger downloads into multiple parallel connections and reassembles them. On a fast connection with a server that supports range requests, the improvement is real and immediate. A 2.1GB ISO that previously took just over four minutes finished in around ninety seconds on the same connection. Not every server supports range requests, but I have not seen a failed download from this flag in normal use.

Best Chrome Flags for the Address Bar

#omnibox-search-prefetch

When you type in the address bar and Chrome sees a high-confidence autocomplete prediction, this flag pre-fetches the likely search results page before you press Enter. The page was partially loaded by the time my keystroke completed. At first I thought search had gotten faster. It had not. Chrome had just started fetching before I finished asking it to.

#omnibox-search-client-prefetch

A companion to the above. Requires the previous flag enabled first. This one lets Chrome decide client-side which suggestion is likely enough to prefetch, rather than relying entirely on server signals. Together both flags make the address bar feel anticipatory rather than reactive.

#omnibox-ml-url-scoring

Replaces the traditional frequency-based URL ranking with an on-device ML model. After about a week of use, suggestions started reflecting how I actually browse rather than just how often I visit a URL. Pages I had visited once but spent real time on started surfacing more reliably than pages I had glanced at dozens of times briefly.

#omnibox-zero-suggest-prefetching-on-srp

When you click into the address bar while on a search results page, Chrome pre-fetches the zero-prefix suggestions before you type anything. The suggestion list appears a fraction of a second sooner than it otherwise would. Not dramatic, but across a day of heavy search use it accumulates.

Tab Management Flags

#vertical-tabs

Vertical tabs remain flag-only in Chrome 148. The tab strip moves to the left side as a collapsible sidebar. If you routinely have more than fifteen tabs open, this is the biggest quality-of-life flag on this list. Tab titles become readable again. The collapsed sidebar takes barely any horizontal space. I switched to vertical tabs on my main machine in March and now find horizontal tab strips disorienting on other machines. The retrain period was about an afternoon of reaching for the wrong place.

#vertical-tabs-expand-on-hover

Works alongside the above. When the vertical strip is collapsed to favicons only, hovering expands it to show full titles temporarily. You get the information when you need it and the viewport space back when you do not.

#tab-strip-declutter

Chrome dims tabs you have not visited recently. They stay open and loaded but visually fade back. Recently active tabs stand out by contrast. My usual sprawl of thirty-plus tabs became genuinely navigable. The first time it activated I thought something was wrong with the rendering. By day three I stopped noticing it consciously and just found the right tab faster.

#tab-groups-focusing

When you click a tab group label, the strip narrows to show only that group’s tabs. Everything else steps back. I used this across a research session with four separate topic clusters open simultaneously and found myself opening fewer reflexive extra tabs because switching contexts had visible friction again.

#split-view-link-open

Adds Ctrl+Alt+Click on Windows and Linux or Cmd+Alt+Click on macOS to open a link alongside the current tab in a split view. Not a full split-screen browser, but enough to compare a reference page with your working tab without opening a second window. Desktop only, not available on Android.

Video and Media Flags

#auto-picture-in-picture-for-video-playback

When you navigate away from a tab with video playing, Chrome automatically floats it into a Picture-in-Picture window in the corner of your screen. No right-clicking, no hunting for the PiP button. I had this enabled for two weeks and only found it annoying once, when a tab I had forgotten about was auto-playing something. Every other time it was a quiet convenience I stopped registering consciously.

#hardware-media-key-handling

Lets Chrome respond to the play, pause, next track, and previous track keys on your keyboard even when the browser is backgrounded. If you pause Spotify Web Player from your keyboard while working in a different app, this is the flag making that possible. On most machines it is Default, which typically means on. Worth confirming if your media keys are working inconsistently in Chrome.

Reading and Focus Flags

#read-anything-docs-integration

Extends Chrome’s built-in Reading Mode to work on Google Docs pages. Reading Mode strips the editor interface and renders just the document text in a clean resizable sidebar. For reviewing long documents without the visual weight of the Docs UI, this is the right flag. The sidebar occasionally loses position on very long documents after a scroll jump, but for reading sessions it holds up well.

#read-anything-line-focus

Adds a line highlight to Reading Mode that moves as you read. The current line is emphasized while surrounding text dims slightly. Subtle enough that I was not sure it was doing anything for the first day. Then I read a long research paper without losing my place once, which had not happened in months.

#enable-force-dark

Forces a dark theme on every page Chrome renders, including sites with no native dark mode. The implementation is algorithmic so results vary. Pages built with strong contrast hold up well. Pages with complex background images can look wrong. I used this for a week without a dark mode extension and found it acceptable on around eighty percent of my regular sites. The other twenty percent looked broken enough that I kept a dark mode extension running for those cases.

Privacy and Security Flags

#enable-webrtc-hide-local-ips-with-mdns

By default, WebRTC exposes your local IP address during real-time communication, even through a VPN. This flag replaces your local IP with an mDNS hostname in WebRTC traffic, closing the standard WebRTC IP leak that privacy tools have warned about for years. Worth enabling if you use a VPN and care about what is actually leaking at the network layer.

#strict-origin-isolation

Tightens site isolation by using the full origin, including subdomain and protocol, as the process boundary. Cross-site attacks become harder to execute. The trade-off is slightly higher memory use per tab. On a machine with 16GB RAM this is not a practical concern. On an 8GB machine with many tabs open it can add real pressure.

#notification-one-tap-unsubscribe-on-desktop

Replaces the Site Settings button on desktop push notifications with an Unsubscribe button. Instead of navigating into settings to revoke notification permission, you do it directly from the notification itself. The first time it appeared I almost dismissed the notification thinking it was different UI. After that I stopped accumulating notification permissions from sites I had visited once out of curiosity.

Developer-Adjacent Flags Worth Knowing

#enable-jxl-image-format

Adds JPEG XL decoding and includes image/jxl in Chrome’s Accept header. JXL offers meaningfully better compression than standard JPEG at equivalent quality. Web adoption is still limited in 2026, but enabling this means Chrome renders JXL images correctly on sites that do serve them. No downside for regular browsing.

#fill-on-account-select

Changes autofill so passwords populate only when you explicitly select an account from the dropdown, rather than being inserted automatically on page load. Useful on shared machines and for anyone who wants one moment of deliberate confirmation before Chrome commits credentials to a form.

#import-export-flags

Adds the ability to export your flags configuration as a file and import it on another Chrome install. Worked reliably in testing on Chrome 148. Genuinely useful if you manage more than one machine and want consistent flag settings without re-enabling each one manually.

#use-persistent-cache-for-code-cache and #inline-script-cache

These two work together. The first switches Chrome’s JavaScript and WebAssembly code cache to a persistent disk backend. The second extends that to inline scripts embedded in HTML. Together they reduce how often Chrome recompiles scripts on pages you visit regularly. Sites with heavy JavaScript, Figma in the browser, Google Sheets, Notion, felt quicker to become interactive after the cache built up over a few sessions. The improvement was not there on day one. It was clear by day four.

Flags to Leave Alone

#site-isolation-trial-opt-out disables site isolation, a core Spectre-class CPU attack mitigation. Disabling it reduces per-tab memory but reopens a real security gap. Not worth it for any regular use case.

#enable-unsafe-webgpu exposes WebGPU on unsupported hardware and gives websites developer-level GPU access. The name is accurate. Leave it off.

#webtransport-developer-mode removes certificate validation for WebTransport connections. Fine in a local dev environment, risky on any machine used for normal browsing.

How to Reset If Something Breaks

Go to chrome://flags and click Reset all at the top right. Every flag returns to Default and Chrome relaunches. Your bookmarks, history, extensions, and passwords are not affected by flag resets in any way.

If Chrome will not open at all, run it from the command line with --no-experiments. On Windows, open the Chrome installation folder and run chrome.exe --no-experiments. This starts Chrome with all flags suppressed without touching your profile data.

The flags in this article were confirmed present on Chrome 148.0.7778.96 on Windows 11 in May 2026. Chrome 149 is expected to hit stable around June 2, 2026. Enable flags one at a time with a relaunch between each so you can isolate which one causes a problem if something does go wrong. Most will not.

Frequently Asked Questions

Are Chrome flags safe to enable in 2026?

Most are safe for regular users. The flags marked as risky in this article carry genuine risk and should be left alone. Everything else can be reverted instantly with the Reset all button at chrome://flags.

Do Chrome flags apply to all user profiles on the same browser?

Yes. Chrome explicitly states that enabled flags apply to all users of that browser installation, not just the current profile.

How do I know if a flag I enabled is actually working?

Relaunch Chrome after enabling any flag, since changes do not take effect until a restart. Some effects are immediate, like tab strip changes. Others, like code caching improvements, only become noticeable after a few sessions.

Can I use Chrome flags on Android?

Yes, chrome://flags works on Chrome for Android. Some flags in this article are desktop-only and will not appear on mobile. Parallel downloading and GPU rasterization are both available on Android.

Will Chrome reset my flags after an update?

Usually no, Chrome preserves flag settings across version updates. However, flags controlling the Gemini Nano model download have been reported to reset after major version updates, so it is worth rechecking those after Chrome 149 ships.