Start Here: How to Use Flags and Disable Gemini Nano
Before turning on any Chrome flags to enable performance features, head to chrome://flags in your address bar. Use the search box to locate specific flags, switch them from Default to Enabled or Disabled, then click Relaunch when prompted. All recommendations here are based on hands-on testing in Chrome 148 on a Windows 11 machine, enabling flags one by one and watching for real-world changes in speed, smoothness, and stability. The first step is actually to disable one flag: optimization-guide-on-device-model. On powerful hardware, Chrome may silently download a roughly 4GB Gemini Nano model into your profile, potentially chewing up disk space and resources. Set this flag to Disabled, along with prompt-api-for-gemini-nano and its multimodal variant, then relaunch and delete the OptGuideOnDeviceModel folder. If you rely on Chrome’s AI writing help or on-device scam detection, you can keep these enabled; otherwise, disabling them removes an invisible performance drain.
GPU Performance Flags: Unlock Smoother Rendering and Video
For real Chrome browser optimization, start with GPU-related flags. Visit chrome://gpu and check whether GPU Rasterization is marked as Software only. If it is, enable-gpu-rasterization can shift page rasterization from CPU to GPU, reducing jank on complex, image-heavy sites. Pair it with enable-zero-copy, which lets raster threads write directly into GPU memory instead of copying from system RAM, trimming overhead that often shows up as micro-stutters while scrolling large grids or long feeds. Next, make sure video work is off your CPU. Despite their names, setting disable-accelerated-video-decode and disable-accelerated-video-encode to Enabled keeps hardware acceleration active. During video playback and browser-based calls, this offloads decoding and encoding to the GPU. In testing, that translated into cooler, quieter laptops and less battery drain during long video calls. These GPU performance Chrome tweaks don’t radically transform benchmarks, but they make everyday browsing feel calmer, especially on mid-range hardware.
Vertical Tabs and Smarter Tab Management for Productivity
If you live with 20+ tabs, the vertical tabs Chrome flag can be a game-changer. Enable vertical-tabs in chrome://flags and Chrome’s tab strip shifts into a collapsible sidebar on the left. This layout makes better use of widescreen displays, allowing more visible tab titles instead of a cramped row of tiny favicons. It also makes scanning and reorganizing tabs feel more like working with a structured list than juggling a pile of cards. Combined with Chrome’s built-in tab groups and search, vertical tabs improve focus: it is easier to park background work in collapsed groups and keep only one or two clusters fully visible. In testing, this layout stuck around simply because it reduced the friction of context switching between projects. If you work with documentation, dashboards, and communication tools simultaneously, this single flag often delivers a bigger usability win than any micro-optimization to page load time.
Parallel Downloads and Network Tweaks for Faster Transfers
For large files, the parallel downloads flag is one of the most tangible speed boosts available. Enable enable-parallel-downloading and Chrome will attempt to split supported downloads into multiple simultaneous connections, then reassemble them. On servers that support range requests, this turned a 2.1GB ISO download from just over four minutes into about ninety seconds on the same connection during testing. It does not help every site, but there were no failed downloads in normal use. To further sharpen perceived speed, enable enable-quic. This pushes Chrome to use QUIC, the transport protocol behind HTTP/3, more aggressively when sites support it. The improvement is most noticeable on high-latency or mobile connections, trimming the delay before the first bytes arrive from services like YouTube or other QUIC-enabled CDNs. Together, these network-related Chrome flags to enable do not change how you browse, but they make every big download and many first-page loads feel snappier.
Privacy-Focused Flags and Smarter Address Bar Suggestions
Beyond raw speed, a few flags quietly improve privacy and everyday flow. Chrome’s on-device features already avoid sending Gemini Nano data to the cloud, but if you do not need them, disabling their flags reduces attack surface and disk usage. That gives you a leaner baseline to layer other enhancements on top. For faster, smarter searching, look at a few omnibox flags. Enabling omnibox-search-prefetch and omnibox-search-client-prefetch allows Chrome to prefetch search result pages it predicts you are about to open, so results appear almost instantly after pressing Enter. omnibox-ml-url-scoring replaces blunt frequency-based ranking with an on-device model that learns which pages actually matter to you, surfacing time-worthy sites over ones you barely glanced at. omnibox-zero-suggest-prefetching-on-srp preloads suggestions when you click the address bar on a results page. None of these change privacy settings directly, but they keep more intelligence on-device and make Chrome feel anticipatory instead of sluggish.