Chrome Showing a White Screen? How to Fix It

A white screen in Chrome means the browser opened but rendered nothing — or rendered nothing useful. The cause determines the fix, and fortunately most white screen problems fall into a small set of categories that are easy to test systematically. Work through these fixes in order from fastest to most thorough.

Fix 1: Disable Hardware Acceleration

This is the right starting point because GPU conflicts cause white screens more than anything else.

1. Type chrome://settings/system in the address bar and press Enter.
2. Find Use hardware acceleration when available and toggle it off.
3. Click Relaunch.

If the white screen disappears, your GPU driver is the underlying problem. Update the driver:

• Windows: Use Device Manager (Win+X > Device Manager > Display adapters > right-click GPU > Update driver), or download directly from NVIDIA, AMD, or Intel’s website.
• Mac: GPU drivers ship with macOS — install any pending system updates via System Settings > General > Software Update.
• Linux: Update your graphics packages through your distribution’s package manager.

After updating the driver, you can try re-enabling hardware acceleration to confirm the fix is complete.

Fix 2: Disable All Extensions and Test

A content script injected by an extension can cause a white screen across all pages. Disabling everything at once tells you immediately whether an extension is involved.

1. Go to chrome://extensions.
2. Toggle off every extension (or click the three-dot menu > Disable to disable each one).
3. Reload the page showing the white screen (or restart Chrome).

If the white screen is gone, re-enable extensions one at a time, restarting Chrome after each, until the problem returns. The last extension you re-enabled before the screen went white again is the culprit. Remove it or look for an update from the extension developer.

Fix 3: Clear the Cache

Corrupted cached data can cause rendering failures on specific pages or across Chrome.

1. Press Ctrl+Shift+Delete (Cmd+Shift+Delete on Mac), or go to chrome://settings/clearBrowserData.
2. Set the time range to All time.
3. Check Cached images and files.
4. Click Clear data.
5. Restart Chrome.

For a full walkthrough of clearing Chrome’s cache and what each option does, see How to Clear Cache in Chrome.

Fix 4: Reset Chrome Flags

Experimental flags in chrome://flags can conflict with Chrome’s rendering pipeline and cause white screens.

1. Go to chrome://flags.
2. Click Reset all in the top right.
3. Click Relaunch.

This does not delete bookmarks, history, or passwords. It only resets experimental feature overrides.

Fix 5: Clear the GPU Shader Cache (Windows)

The shader cache stores pre-compiled GPU rendering instructions and can become corrupted.

1. Close Chrome completely.
2. Press Win+R and type: %localappdata%\Google\Chrome\User Data\ShaderCache
3. Press Enter.
4. Select all files in the folder and delete them.
5. Reopen Chrome.

Fix 6: Create a New Chrome Profile

A corrupted user profile — the folder containing your settings, extensions, local storage, and other data — is a common cause of persistent white screens that other fixes do not resolve.

Creating a new profile does not delete your existing one; it creates a fresh one to test with:

1. Click the profile icon at the top right of Chrome (circle with photo or initials).
2. Click Add.
3. Follow the prompts (you can skip signing in for testing purposes).
4. A new Chrome window opens with a completely fresh profile — no extensions, no custom settings.

If the white screen does not appear in the new profile, the problem is isolated to your original profile. You can migrate by signing into your Google account in the new profile (which syncs bookmarks, passwords, and history from your account), and then reinstalling extensions fresh from the Chrome Web Store.

Note: If you sign back into your Google account and restore the same extensions, you may also restore whatever caused the problem. Install extensions one at a time and test between each installation.

Fix 7: Update Chrome

Running an outdated version of Chrome can mean missing patches for known rendering bugs.

1. Click the three-dot menu > Help > About Google Chrome.
2. Chrome checks for updates and downloads them automatically.
3. Click Relaunch to apply the update.

Fix 8: Reinstall Chrome (Last Resort)

If the white screen appears immediately on launch before any page loads, the Chrome installation itself may be corrupted.

1. Uninstall Chrome through your system’s standard uninstall process (Control Panel > Programs on Windows; drag to Trash on Mac).
2. Download the latest version from google.com/chrome.
3. Install and launch.

Important: Uninstalling Chrome does not remove your user profile (bookmarks, passwords, history) on most systems. The profile folder stays on disk and is picked up by the new installation. If the white screen was caused by profile corruption rather than installation corruption, this step will not resolve it — use Fix 6 (new profile) instead.

Using Chrome’s Command-Line Flags for Diagnosis

When the standard fixes do not identify the cause, Chrome’s command-line flags can isolate the problem precisely.

–disable-gpu: Forces Chrome to use software rendering entirely, bypassing the GPU pipeline. If the white screen disappears with this flag, the GPU is definitively involved.

On Windows: right-click your Chrome shortcut > Properties > Target field, add --disable-gpu after the closing quote mark. Click OK and launch Chrome from that shortcut.

On Mac: open Terminal and run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --disable-gpu

After testing, remove the flag from the shortcut. Running Chrome without GPU acceleration is a diagnostic step, not a long-term configuration.

–incognito: Launches Chrome directly in incognito mode, which disables extensions. If the white screen does not appear in this mode, the cause is an extension or profile-level data problem, not the Chrome installation or GPU.

–profile-directory=“Default”: Launches Chrome using a specific profile. If you have multiple profiles, this helps confirm whether the issue is isolated to one profile. Replace “Default” with “Profile 1,” “Profile 2,” etc. to test other profiles from the command line.

White Screen in Fullscreen or Presentation Mode

A white screen that appears specifically when Chrome enters fullscreen — triggered by F11 on Windows, the green traffic light on Mac, or a webpage requesting fullscreen for video — has a distinct cause from general white screens during normal browsing.

When Chrome switches to fullscreen, it changes to a different rendering path. If the GPU driver handles this transition incorrectly, the result is a white screen that resolves when you press Escape or F11 to exit fullscreen.

Fixes for fullscreen-specific white screens:

• Update your GPU driver — this is the primary fix. Fullscreen rendering transitions are a common area where driver bugs manifest.
• Disable hardware acceleration (Fix 1) — this usually resolves fullscreen white screens because it removes the GPU rendering path that the fullscreen transition was triggering.
• Check display resolution settings — on Windows, some fullscreen rendering issues are tied to running at a non-native display resolution. Confirm your monitor is set to its native resolution in Settings > System > Display.
• On Mac: in rare cases, the “Reduce motion” setting in System Settings > Accessibility > Motion can affect how Chrome handles fullscreen transitions. Try toggling it.

Video entering fullscreen: White screens that appear specifically when a video enters fullscreen (on YouTube, streaming services, etc.) are usually hardware-accelerated video decoding conflicts. Update the GPU driver or disable hardware acceleration (Fix 1) to resolve.

Chrome White Screen Across Multiple Monitors

If the white screen appears only when Chrome is on a specific monitor — particularly a secondary monitor — or when you move a Chrome window between monitors, the cause is likely a monitor configuration mismatch:

Different refresh rates. If your primary monitor is at 144Hz and your secondary is at 60Hz, Chrome may fail to render correctly when the window moves between them. Set both monitors to the same refresh rate in Windows Settings > System > Display > Advanced display settings.

Different scaling levels. Windows allows per-monitor DPI scaling. If one monitor is at 125% and another at 150%, Chrome can encounter rendering issues when moved between them. Try setting both to the same scaling value as a test.

Connection type. Display rendering issues that appear on one monitor but not another are sometimes cable-related. A marginal HDMI or DisplayPort cable can cause intermittent rendering failures. Test by swapping cables or using a different port.

When the White Screen Is on a Specific Site Only

If the white screen only happens on one website or a specific type of page (video sites, pages with complex JavaScript), the issue is more likely:

• Hardware acceleration — especially on video-heavy sites. Fix 1 applies.
• Site-specific cached data — clear storage for that site only: go to chrome://settings/content/all, find the site in the list, and click the trash icon.
• Extension conflict with that site — some ad blockers or content scripts conflict with specific sites. Test with extensions disabled.

Protecting Your Bookmarks Through Troubleshooting

If you are creating a new Chrome profile or resetting significant Chrome settings, your bookmarks stay tied to your Google account if sync was enabled. If sync was off, do an HTML export before starting: open the Bookmark Manager (Ctrl+Shift+O), click the three-dot icon, and choose Export bookmarks. Bookmend can also help maintain a searchable, dead-link-checked version of your bookmarks regardless of which Chrome profile you use.