FIX Chrome Checkerboard Glitch When Scrolling (2026)

Key takeaways

• White squares when scrolling mean the compositor scrolled past tiles the GPU hasn’t painted yet. Not a Chrome bug.
• Outdated GPU drivers slow the rasterizer. Update drivers first, then verify rasterization is on at chrome://gpu.
• Background video tabs consume shared VRAM, leaving less for the active page. Close them to recover rasterizer headroom.

You scroll down a page and briefly get a grid of white or gray squares where the content should be. It loads a moment later, but the flicker is annoying and gets worse on image-heavy pages. This is checkerboarding — Chrome divides pages into tiles and paints them onto the GPU. When the compositor scrolls faster than the raster threads can paint, unpainted tiles show as blank squares. The faster you scroll, the more tiles you outrun.

Quick Diagnosis

Fix 1: Enable GPU Rasterization

By default, Chrome may use CPU-based rasterization for some pages. GPU rasterization moves tile painting to the GPU, which is significantly faster and reduces checkerboarding during fast scrolls.

1. Navigate to chrome://flags/#enable-gpu-rasterization — note that GPU rasterization is enabled by default in Chrome 100+, so this flag may no longer appear
2. If the flag exists, set it to Enabled and click Relaunch
3. If the flag is absent, GPU rasterization is already active — verify at chrome://gpu under “Rasterization”

Expected result: Rasterization speed increases and checkerboard flashes are shorter or disappear.

Fix 2: Update GPU Drivers

Outdated drivers can cause the GPU rasterizer to be slower or less stable.

1. On Windows: open Device Manager > Display adapters, right-click your GPU, choose Update driver
2. Alternatively, download directly from NVIDIA, AMD, or Intel
3. After updating, restart Chrome and check chrome://gpu to confirm the new driver version is listed

Fix 3: Check Hardware Acceleration Status

1. Navigate to chrome://settings/system
2. Verify that Use hardware acceleration when available is enabled
3. If it is already enabled and checkerboarding persists, try toggling it off, relaunching, and testing — some driver/Chrome combinations work better in software mode

Fix 4: Reduce GPU Load from Background Tabs

VRAM is shared across all open tabs. Background tabs playing video or running CSS animations consume rasterizer capacity.

1. Press Shift+Esc to open Chrome Task Manager
2. Identify tabs with high memory usage — close or suspend them
3. Close video-playing tabs (YouTube, Twitch) that are not in active use

Reducing Background Rasterization Load

Chrome’s raster worker threads and VRAM are shared across all open tabs. If background tabs are running animated ads or video previews, they are consuming the same raster capacity your active page needs to paint tiles ahead of your scroll.

Suspending background tabs is the most direct fix here — it stops all rendering in those tabs. SuperchargePerformance automates this:

• Tab suspension via chrome.tabs.discard() halts all rendering in background tabs, freeing raster threads and VRAM for the active tab
• Script blocking reduces JavaScript-driven layout recalculations in background tabs competing for main thread time
• Ad blocking via declarativeNetRequest prevents animated ad creatives from loading — one of the biggest sources of background rasterization demand

Manually closing video tabs (Fix 4) achieves the same result at no cost. The extension is most useful when you need the tabs to stay available for later.

Technical Background

Chrome’s rendering pipeline separates two jobs: the compositor thread handles scrolling at full frame rate, and raster threads paint new tiles as they come into view. The compositor can scroll faster than the rasters can paint, especially when:

• The main thread is blocked by JavaScript (layout recalculation, script execution)
• The GPU rasterizer queue is backed up by concurrent work from other tabs
• VRAM is fragmented or exhausted, forcing fallback to slower paths

When a tile is needed but not yet painted, Chrome shows the checkerboard placeholder. The fix is either faster rasterization (GPU flags, driver updates) or less competing work (fewer active background tabs).

Related Articles

• Fix YouTube Stuttering on High-End PC in Chrome — related GPU pipeline and rendering issue
• Fix dwm.exe High GPU Usage Caused by Chrome (2026) — Windows compositor GPU contention that compounds checkerboarding
• Fix WebGPU Device Lost Error in Chrome — VRAM exhaustion causing GPU rendering failures