A blank white page in Chrome is arguably the most annoying type of failure because it gives you nothing to work with. No error code, no message, no hint about what went wrong. The URL looks right, the spinner spins briefly, and then — nothing. White page. We go deeper on the whole subject in our Google Chrome Errors.
The reason there’s no error code is that Chrome actually received something from the server. This is a different failure layer from network errors like ERR_NAME_NOT_RESOLVED, where Chrome can’t reach the server at all. The blank screen means Chrome got a response and then something went wrong during the rendering process — GPU issues, extensions blocking content, JavaScript failing silently, or a corrupt Chrome installation. That distinction tells you where to look.
Which Type of Blank Screen?
The cause and fix depends heavily on the specific pattern. A few quick checks narrow things down before touching any settings:
Does it happen on all sites or just specific ones? All sites going blank points to hardware acceleration or Chrome profile corruption. A specific site going blank more often points to JavaScript issues, extensions, or cached corrupt page data for that site.
Does the page load in an Incognito window? Press Ctrl + Shift + N. If a blank site loads normally in Incognito, the cause is either a browser extension or cached data in the normal profile — both fixable quickly. If it’s also blank in Incognito, extensions aren’t the issue.
Did it start after a Chrome update or GPU driver change? Blank pages appearing right after a system update are usually hardware acceleration problems — the new driver or Chrome version has a compatibility issue.
Fix 1: Hard Reload — 30 Seconds, Try First
Before anything else: Ctrl + Shift + R. This bypasses Chrome’s cache and forces a completely fresh request. A page that renders blank once due to a temporary rendering glitch often loads correctly on a hard reload.
Also try scrolling the blank page — occasionally Chrome renders content below the visible viewport and a scroll reveals it. Try zooming out with Ctrl + minus a few times; rendering at non-standard zoom levels sometimes triggers content to appear. Neither of these is a real fix, but they take five seconds and occasionally work when the rendering issue is minor.
Fix 2: Disable Hardware Acceleration
This is the most common fix for blank screens that affect multiple sites or started after a system update. Hardware acceleration uses the GPU to render web content, which is faster on most systems. But when the GPU driver has a bug, is out of date, or isn’t fully compatible with Chrome’s version, the rendering completes but nothing actually appears on screen — the content exists in the GPU’s memory but never makes it to the display.
The first time I saw a Chrome blank screen, this was the cause. Pages were technically loading — the tab title changed, the address bar updated, the page registered as loaded — but the page area stayed white. Toggling hardware acceleration off fixed it in about 30 seconds.
- Click the three-dot menu → Settings → System
- Toggle off Use hardware acceleration when available
- Click Relaunch
- Test the pages that were blank
If that fixes it, update your GPU driver. Device Manager → Display Adapters → right-click your GPU → Update driver, or download directly from NVIDIA, AMD, or Intel’s website depending on your GPU. After updating, re-enable hardware acceleration and test again — the updated driver will usually work correctly with it enabled.
Fix 3: Disable Extensions
Content-blocking extensions, script blockers, and privacy tools can prevent the JavaScript or content that fills a page from loading — leaving the page’s HTML shell visible as a blank white page. This is the cause when Incognito loads the page but the normal Chrome window doesn’t, since Incognito runs without extensions.
- Test in Incognito (Ctrl + Shift + N) — if the page loads, extensions are involved
- Go to chrome://extensions
- Toggle all extensions off
- Reload the page in a normal Chrome window
- If it loads: re-enable extensions one at a time and reload after each — the blank screen returns when you enable the problem extension
Common culprits for blank page rendering: uBlock Origin with aggressive filter lists that block JavaScript execution, Privacy Badger blocking tracking scripts that some sites also use for content loading, and developer extensions (React DevTools, Redux DevTools) that occasionally interfere with page rendering on specific sites.
Fix 4: Clear Cache and Cookies
A corrupt cached version of a page renders blank because Chrome loads the damaged cached data instead of fetching fresh content. This commonly happens after a site redesign — Chrome’s cached version of the old page structure is incompatible with the new site, and the incompatibility produces a blank result rather than an error.
Press Ctrl + Shift + Delete → set time range to All time → check Cookies and other site data and Cached images and files → Clear data. Restart Chrome and reload. If a specific site was blank while others worked, you can clear just that site’s data: click the padlock icon in the address bar → Cookies and site data → Manage → delete entries for that domain.
Fix 5: Check JavaScript Settings
Modern websites are largely JavaScript applications. The HTML that Chrome loads is often just a skeleton — JavaScript executes after load and populates the page with actual content. If JavaScript is disabled in Chrome, or if an extension is blocking the specific scripts a site depends on, Chrome loads the empty HTML skeleton and displays it as a blank white page.
- Chrome Settings → Privacy and security → Site settings → JavaScript
- Confirm Sites can use JavaScript is selected (not Blocked)
- If a site is listed under “Not allowed to use JavaScript,” remove it from that list
To diagnose JavaScript errors causing the blank screen: right-click the blank page → Inspect → click the Console tab. Red error messages here identify exactly which scripts are failing. This is particularly useful for identifying extension conflicts — extension errors often appear in the console on pages they’re partially blocking.
Fix 6: Reset Chrome or Reinstall
For blank pages that persist through all the above — still blank with hardware acceleration off, still blank with extensions disabled, still blank after clearing all cache — the Chrome profile itself has accumulated enough corruption to require a reset. This is rare but happens, particularly on machines where Chrome has been through many version updates and had frequent extension changes.
Three-dot menu → Settings → scroll to bottom → Reset settings → Restore settings to their original defaults → Reset settings. This clears custom settings but preserves your bookmarks and saved passwords (they’re stored in your Google account if sync is enabled).
If reset doesn’t fix it, a fresh Chrome installation usually will. Uninstall Chrome via Settings → Apps, then delete the profile data at C:Users[YourName]AppDataLocalGoogleChrome (this removes all local data including profiles not synced to Google), then download and install fresh from google.com/chrome. The blank screen issue consistently resolves after a clean installation in cases where profile corruption is the cause.
| Blank screen pattern | Likely cause | Fix |
|---|---|---|
| All pages blank, no error | Hardware acceleration GPU rendering failure | Fix 2 — disable hardware acceleration |
| Specific sites blank, others fine | Corrupt cache or JavaScript blocked | Fix 4 (clear cache); Fix 5 (JavaScript settings) |
| Loads in Incognito, blank normally | Extension blocking content | Fix 3 — disable extensions one by one |
| Blank after site redesign | Stale cached page structure | Fix 4 — clear all cached data |
| All the above tried | Corrupt Chrome profile | Fix 6 — reset or reinstall |
Our guide on Chrome crashing at startup covers the stability failures that sometimes accompany blank page rendering when hardware acceleration issues are severe enough to crash the browser rather than produce a white page. For error-code variants — where Chrome shows ERR_NAME_NOT_RESOLVED or ERR_TIMED_OUT instead of a blank page — see our Chrome not loading pages guide for the network-side fixes. The Google Chrome support pages include additional blank page troubleshooting for managed Chrome deployments where policy settings affect page rendering.
Chrome’s task manager provides useful diagnostic information for blank page issues that the main interface doesn’t expose. Press Shift + Esc while Chrome is open to open Chrome’s internal task manager. Each open tab shows its memory usage and CPU usage. A tab that shows a blank page but is consuming significant CPU may be actively running JavaScript that’s producing no visible output — which can mean an extension is running on that page and blocking content, or that the page is rendering but the output isn’t reaching the display (pointing to hardware acceleration). A tab showing a blank page with zero CPU usage is more likely genuinely empty — either the HTML was delivered but contains nothing, or the content-loading JavaScript failed silently at startup.
Site isolation and memory pressure are factors on lower-specification machines. Chrome’s Site Isolation feature runs each site in its own process, and on machines with limited RAM, Chrome may silently fail to allocate the memory needed to render certain pages — particularly complex, JavaScript-heavy applications — and display a blank page rather than an out-of-memory error. Chrome flags allow adjusting site isolation behaviour for troubleshooting: navigating to chrome://flags/#site-isolation-trial-opt-out and opting out temporarily can confirm whether site isolation is contributing to blank rendering on low-memory machines, though this is a diagnostic step rather than a permanent fix, as site isolation provides meaningful security benefits.
Renderer process crashes sometimes produce blank pages rather than the more visible crash tab (the blue dinosaur icon with “Aw, Snap!”). When a renderer crashes immediately after page load, the tab shows blank because the rendering process died before drawing anything — and Chrome doesn’t always display the crash indicator before attempting a silent restart. If a blank tab spontaneously reloads itself and then loads the page correctly on the second attempt without you doing anything, a silent renderer crash is likely. These correlate strongly with hardware acceleration issues and with low-memory conditions. Chrome’s internal crash reporting at chrome://crashes logs renderer crashes if reporting is enabled — checking this list for recent crashes with timestamps matching when blank pages appeared confirms the crash theory.
For developers encountering blank pages specifically in development environments: blank pages in Chrome’s DevTools device emulation mode (the mobile device simulation) are occasionally caused by viewport meta tag conflicts. Some sites use JavaScript to set viewport properties that conflict with Chrome’s simulated viewport settings, producing a blank canvas in emulation mode while the desktop view works normally. Toggling responsive design mode on and off, or clearing the cached resources for the page in DevTools (Ctrl + Shift + R while DevTools is open performs a cache-clearing reload), typically resolves emulation-specific blank page rendering without affecting normal browsing.
Sandboxing and security software can interfere with Chrome’s rendering process in specific environments. Some endpoint security products, particularly those deployed on corporate managed devices, hook into Chrome’s renderer process for content scanning and occasionally interfere with the rendering pipeline in ways that produce blank pages on specific content types. If Chrome blank pages appear only on work-managed machines and only on specific categories of sites, the endpoint security product is worth investigating. IT administrators can typically configure exceptions for Chrome’s renderer process in the security product’s settings, or escalate to the vendor if the interference is causing productivity issues.
Profile corruption causing blank pages often has a specific pattern: blank pages appear for one user account on the machine but not others, or blank pages appear in Chrome’s default profile but not in a newly created profile. Testing this is straightforward — in Chrome, click the profile icon in the top-right corner → Add → create a guest profile or a new account. If the same pages load correctly in the new profile, the existing profile’s data is corrupted. The resolution is either resetting the existing profile (which preserves synced data but clears local data) or migrating to the new profile. For users who heavily rely on locally-stored data that hasn’t been synced to a Google account, profile migration is preferable to resetting — copy the bookmarks and password exports from the old profile before abandoning it.
A final practical tip for diagnosing intermittent blank pages that don’t reproduce consistently: enable Chrome’s net-export logging. Go to chrome://net-export/, click Start Logging to Disk, reproduce the blank page, then click Stop Logging. The log file captures the complete network activity for every resource Chrome tried to load during that period. Analysing the log (using the netlog_viewer tool at netlog-viewer.appspot.com) shows whether the blank page was caused by network resource failures, blocked requests, or other network-layer events — versus a pure rendering issue where all resources loaded but nothing displayed. This level of diagnosis is usually only needed for complex persistent blank page issues where the simpler fixes haven’t identified the cause. Related: Chrome Loading Pages Slowly.
