How to Fix Claude Blank White Screen Errors

A blank white screen on claude.ai usually points to a frontend compilation error. This happens when the developers push a new software update to the platform, but your browser is running an older, cached version of the React/Next.js application bundle. The mismatch causes a silent runtime JavaScript crash, leaving you with a completely blank screen.

This can also occur during or immediately following a server outage when content delivery network (CDN) routing becomes unsynchronized. Here is how to trace and fix the issue.

1. Unregister Stale Service Workers Claude uses background scripts called Service Workers to cache assets for faster loading. If these workers get stuck during a system update, they will persistently serve broken, blank pages. 1. Go to `claude.ai` (even if it is blank). 2. Open the Developer Tools console (Press `F12` or `Ctrl` + `Shift` + `I` on Windows; `Cmd` + `Option` + `I` on macOS). 3. Go to the **Application** tab (or **Storage** -> **Service Workers** in some browsers). 4. Click on **Service Workers** in the left sidebar. 5. Look for the service worker associated with `claude.ai` and click **Unregister** or **Stop**. 6. Reload the webpage.

2. Hard Reset Site-Specific Cache Clearing your entire browser history is annoying and unnecessary. You can target and delete only the broken files associated with Claude. 1. Click the lock icon (or settings icon) directly to the left of `claude.ai` in your browser's address bar. 2. Click on **Site settings** or **Cookies and site data**. 3. Click **Manage cookies and site data** (or click **Clear data** if in the site settings menu). 4. Delete all listed storage, cookies, and local databases for the domain. 5. Restart your browser and reload the page.

3. Check for Console Compilation Errors Identifying the exact error can tell you if the problem is on your end or if it is a broken code release from the engineers. 1. Right-click anywhere on the blank white screen and select **Inspect**. 2. Click the **Console** tab at the top of the Developer Tools panel. 3. Look for red error messages. * If you see `Failed to load resource: net::ERR_CONNECTION_REFUSED` or `404 Not Found` for files ending in `.js`, the CDN is currently failing to serve critical assets. This is an infrastructure issue; you must wait for the CDN to re-sync. * If you see `Uncaught TypeError` or `SyntaxError`, a bad update was deployed. Try switching to a different web browser to see if a different build is being served there.

4. Disable Strict Tracking Protection Some browsers with built-in privacy protections (like Brave, Firefox, or Safari) block essential cross-origin scripts that Claude relies on to run its interface. 1. If using Brave, click the Shield icon in the address bar and toggle it **Off** for `claude.ai`. 2. If using Firefox, click the shield icon to the left of the URL and disable **Enhanced Tracking Protection** for the site. 3. Check if you are using a VPN with built-in ad-blocking (like NordVPN's Threat Protection or ExpressVPN's blocks). Turn these features off temporarily to see if they are blocking Claude's frontend assets.

When to Escalate If you have cleared your service workers, deleted site-specific cookies, disabled all browser extensions, and still see a blank white screen across multiple web browsers (such as both Chrome and Safari), the issue may be a localized ISP block or a regional CDN routing error. Reach out to the support team at support.anthropic.com. When you contact them, paste any red error messages displayed in your browser's developer console, as this will immediately pinpoint the broken file path.