Chrome screen flickering is one of the more disruptive browser problems — it makes reading and working uncomfortable and the cause is not always obvious. Most cases come down to a hardware acceleration conflict or a GPU driver issue, and both are fixable without reinstalling Chrome.
Fix 1: Disable Hardware Acceleration
This is the right first step because it immediately isolates whether your GPU is involved.
- Type
chrome://settings/systemin the address bar and press Enter. - Find “Use hardware acceleration when available” and toggle it off.
- Click the Relaunch button that appears.
If the flickering stops, your GPU or driver is the underlying cause. You can leave hardware acceleration off permanently or move on to Fix 2 (updating your driver) and then re-enable it.
Fix 2: Update Your GPU Driver
Hardware acceleration conflicts are almost always caused by outdated or buggy GPU drivers.
On Windows:
- Open Device Manager (press Win+X, select Device Manager).
- Expand Display adapters, right-click your GPU, and choose Update driver.
- Alternatively, go directly to your GPU manufacturer’s site: NVIDIA, AMD, or Intel.
- Restart the computer after installing.
On Mac: GPU drivers ship with macOS. Go to System Settings > General > Software Update and install any pending updates.
On Linux: Use your distribution’s package manager to update the mesa or nvidia/amd driver packages, depending on your GPU.
Fix 3: Disable Smooth Scrolling in Chrome Flags
The smooth scrolling flag can conflict with certain GPU configurations and cause flickering during page scrolling.
- Type
chrome://flagsin the address bar and press Enter. - In the search box at the top, type
smooth scrolling. - Change the Smooth Scrolling entry from Default to Disabled.
- Click Relaunch.
Fix 4: Reset All Chrome Flags
If you have enabled experimental flags and cannot remember which ones, resetting all of them to default is the fastest fix.
- Go to
chrome://flags. - Click the Reset all button near the top right.
- Click Relaunch.
This does not delete bookmarks, history, or passwords. It only resets experimental features.
Fix 5: Disable All Extensions and Test
Extensions that inject JavaScript or CSS into every page can interfere with rendering.
- Go to
chrome://extensions. - Toggle off all extensions.
- Reload the pages where flickering occurred.
If flickering stops, re-enable extensions one at a time — waiting a minute between each — until you identify which one causes the problem.
Fix 6: Check Display Refresh Rate and Scaling (Windows)
A mismatch between your monitor’s refresh rate setting and what Chrome renders can cause independent flickering.
- Right-click the desktop, choose Display settings.
- Scroll down to Advanced display settings.
- Make sure all monitors are set to their native refresh rate (typically 60Hz, 144Hz, or 240Hz, depending on your monitor).
- Also verify that Display scale is set to a value Chrome handles cleanly — 100%, 125%, 150%, or 200% are the most stable options.
If you have two monitors at different refresh rates, try setting them to the same rate and see if flickering improves.
Fix 7: Clear the GPU Shader Cache (Windows)
The shader cache stores pre-compiled GPU instructions and can become corrupted.
- Close Chrome completely.
- Press Win+R and type
%localappdata%\Google\Chrome\User Data\ShaderCache. - Press Enter and delete all files inside that folder.
- Reopen Chrome.
Fix 8: Adjust V-Sync in Your GPU Control Panel
V-Sync forces your GPU to sync output to your monitor’s refresh rate, which can eliminate tearing and some forms of flicker.
- NVIDIA: Right-click the desktop, open NVIDIA Control Panel, go to Manage 3D settings > Global Settings, and set Vertical sync to On.
- AMD: Open Radeon Software, go to Gaming > Global Settings, and enable Wait for Vertical Refresh.
- Intel: Open Intel Graphics Command Center, look for V-Sync in the Display or Game settings.
Fix 9: Update Chrome Itself
Running an outdated version of Chrome means missing bug fixes for known rendering issues.
- Click the three-dot menu at the top right.
- Go to Help > About Google Chrome.
- Chrome will check for updates and download them automatically. Click Relaunch to apply.
Understanding the Root Causes of Chrome Flickering
Knowing what causes flickering helps you prioritize the right fix first.
Hardware acceleration conflict — Chrome offloads graphics rendering to the GPU by default. When Chrome’s rendering calls and the GPU driver do not agree on how to process certain operations, the result can be a flickering or flashing display. This is the most common root cause, and disabling hardware acceleration (Fix 1) tests it immediately.
Outdated or buggy GPU drivers — GPU manufacturers release driver updates that include rendering bug fixes. An out-of-date driver may have a known bug that manifests as Chrome flickering, especially during video playback or on pages with complex animations.
Refresh rate and frame timing mismatch — If your monitor is running at 144Hz but Chrome renders at a rate that does not align cleanly with the display’s refresh cycle, you can get flickering that looks like a heartbeat pattern during scrolling. V-Sync (Fix 8) and checking your refresh rate (Fix 6) address this.
Experimental Chrome flags — The chrome://flags page exposes features that are not yet stable. Some of these flags change how Chrome uses the GPU or renders pages, and a misconfigured or buggy flag can cause flickering that disappears after resetting all flags to default (Fix 4).
Extension rendering interference — Extensions can inject CSS or JavaScript that forces page repaints on every scroll event. If the extension’s injected code causes Chrome to redraw the page more often than necessary, you can see a flickering effect that tracks your scrolling.
Flickering vs. Tearing vs. Stuttering
These three display problems have different causes and different fixes:
| Problem | What it looks like | Primary cause |
|---|---|---|
| Flickering | Rapid on/off or brightness change | Hardware acceleration conflict, GPU driver |
| Tearing | Horizontal lines splitting the image | Refresh rate mismatch, V-Sync off |
| Stuttering | Choppy, uneven scrolling | Low frame rate, extension overhead, hardware acceleration |
If you have screen tearing (not flickering), enabling V-Sync in your GPU control panel (Fix 8) is the most direct solution. Stuttering without flickering usually points to an overloaded CPU/GPU rather than a rendering conflict.
Flickering Specific to Video Playback
If Chrome flickers only while watching videos — on YouTube, Netflix, Twitch, or similar sites — but not on regular web pages, the cause is almost always hardware-accelerated video decoding specifically. Chrome uses the GPU to decode video in a separate process from the normal page rendering pipeline, and a driver bug may affect only that video decoding path.
Steps to isolate:
- Disable hardware acceleration entirely (Fix 1) and test video playback. If the flickering stops, the GPU pipeline is involved.
- With hardware acceleration re-enabled, go to
chrome://flagsand search for “Hardware-accelerated video decode.” Try disabling that flag specifically rather than disabling all hardware acceleration. - If flickering appears on some video platforms but not others, the issue may be format-specific. YouTube uses VP9 and AV1 codecs; many other platforms use H.264. If VP9 or AV1 content flickers but H.264 does not, that points to a specific codec path in your GPU driver that needs updating.
Updating the GPU driver is the proper long-term fix for codec-specific video flickering. Disabling hardware-accelerated video decode is a targeted workaround that may preserve better overall performance than turning off all hardware acceleration globally.
Flickering After a Chrome Update
When Chrome flickering starts immediately after a specific Chrome update, the update likely introduced a rendering regression. A few things to do:
Check your Chrome version: Go to chrome://version and note the exact version number (for example, 127.0.6533.88).
Search the Chrome bug tracker: Visit bugs.chromium.org and search for your version number alongside “flickering” or “screen flicker.” Rendering regressions introduced by updates are often reported and acknowledged within days. If other users are seeing the same issue, a fix is usually included in the next point release within a week or two.
Report the issue: If you cannot find an existing report, filing a new bug at crbug.com helps the Chrome team identify and patch regressions faster.
In the meantime, disabling hardware acceleration (Fix 1) typically resolves update-related rendering regressions while you wait for a patch.
Mac-Specific Flickering Notes
On macOS, Chrome uses the Metal graphics API rather than the older OpenGL path. A few Mac-specific causes worth checking:
macOS version and Chrome compatibility: A Chrome version compiled for a newer macOS Metal feature may render less cleanly on an older macOS version. Keeping macOS updated via System Settings > General > Software Update eliminates this class of issue.
Multiple displays with different resolutions: Mac setups that pair a Retina display with a standard external monitor can produce Chrome flickering at the display boundary — particularly when a window spans both screens or when Chrome renders near the edge of one display. If you see flickering only when a Chrome window is on a specific monitor, move it fully onto the other monitor and test.
Third-party menu bar apps: Some applications that add animated icons to the Mac menu bar can cause a refresh-rate-level screen interference that appears as flickering at the very top of the Chrome window rather than within page content. Try quitting menu bar apps one at a time if the flickering is localized to the top edge of Chrome.
When None of These Fixes Work
If you have gone through all nine fixes and flickering persists, the issue may be hardware-level — a failing GPU, a monitor with a dying panel, or a cable problem. Try a different cable (DisplayPort vs. HDMI) and test Chrome on a different monitor if you have one available. You can also create a new Chrome profile to rule out a corrupted profile: go to the profile icon at the top right, click Add, and test in the fresh profile without restoring any extensions.
If the flickering only happens in Chrome and not in other apps, the cause is almost certainly software (driver, extension, or flag). If flickering happens in all apps or even on the desktop background, the cause is hardware or OS-level — Chrome is not the root problem, just a manifestation of it.
A passing note: if you use Chrome bookmarks heavily and are concerned about losing data during a troubleshooting session that involves resetting Chrome or creating a new profile, Bookmend can back up and search your existing bookmarks without any migration or account required.
Frequently asked questions
The most common causes are a conflict between Chrome's hardware acceleration and your GPU driver, a mismatch between your monitor's refresh rate and the frame rate Chrome is trying to render, or a malfunctioning extension. In some cases, an experimental flag enabled in chrome://flags is the culprit.
Go to chrome://settings/system in your address bar. Find 'Use hardware acceleration when available' and toggle it off. Click the Relaunch button that appears. Chrome will restart with hardware acceleration disabled.
It can make video playback and graphics-heavy pages slightly less smooth, but for everyday browsing most users notice no difference. Try it and re-enable if performance is unacceptable.
The most commonly reported ones are GPU rasterization and smooth scrolling. You can disable smooth scrolling at chrome://flags by searching for 'smooth scrolling' and setting it to Disabled. Resetting all flags to default is the safest broad fix.
Open Device Manager (Win+X, then Device Manager), expand Display adapters, right-click your GPU, and choose Update driver. Alternatively, download the latest driver directly from NVIDIA, AMD, or Intel's website for your specific model.
On macOS, GPU drivers are bundled with the operating system. Go to System Settings > General > Software Update and install any pending updates.
Yes. Extensions that inject code into every page — ad blockers, certain productivity tools — can interfere with rendering. Disable all extensions, check if flickering stops, then re-enable them one at a time to find the culprit.
It resets every experimental Chrome feature back to its default state. It does not delete your bookmarks, passwords, or history. It is safe to use and a good step when an unknown flag is causing display issues.
Video sites use hardware-accelerated decoding. If your GPU driver has a bug with a specific codec, flickering appears only during video playback. Disabling hardware acceleration or updating the driver usually resolves this.
Yes. If your display scale is set to anything other than 100% and Chrome's rendering does not align with it, you may see flickering. Try setting display scaling to 100% in Windows Settings > Display as a test. Some users also disable Chrome's automatic DPI adjustment in the .exe compatibility settings.
Check that both monitors are running at the same refresh rate in Windows Settings > System > Display. A primary monitor at 144Hz and a secondary at 60Hz can cause Chrome to flicker on one or both screens when the window is moved or when Chrome renders across both.
Rarely, but malicious extensions or adware injected into Chrome can cause rendering anomalies. If you have exhausted the standard fixes, run a scan with a reputable tool like Malwarebytes Free and also review your installed extensions.
The fastest test is disabling hardware acceleration (chrome://settings/system > toggle off 'Use hardware acceleration when available' > Relaunch). If the flickering stops, the GPU pipeline is involved. A more targeted test on Windows: right-click your Chrome shortcut > Properties > Target field, add ' --disable-gpu' at the end (after the closing quote), and launch Chrome. This forces software rendering entirely. If flickering stops with --disable-gpu, the cause is definitively GPU-related. Remove the flag from the shortcut after testing.
Yes. This usually indicates a hardware-accelerated video decoding conflict rather than a general rendering issue. The GPU handles video decoding in a separate pipeline from page rendering, so a driver bug can affect video specifically without causing flickering elsewhere. Fix: update your GPU driver first, then try disabling the 'Hardware-accelerated video decode' flag at chrome://flags as a temporary workaround.

