How to Fix Claude 'Page Unresponsive' Error & Freezes

The "Page Unresponsive" or "Aw, Snap!" error occurs when Claude's web interface (Claude.ai) freezes, stops responding to input, or crashes completely. This issue is typically caused by a script execution freeze. It can happen during high traffic when Claude's database lags, or locally when browser memory leaks, excessively long chat histories are loaded, or aggressive browser extensions interfere with the web application.

If you are locked out of your chats by a freezing interface, follow these steps to isolate the issue, clean your browser's workspace environment, and restore performance.

1. Force Kill the Frozen Browser Tab When a tab becomes unresponsive, trying to close it by clicking the 'X' button might not work or may freeze your entire browser window. You must terminate the underlying script process.

* On Google Chrome & Microsoft Edge: 1. Press Shift + Esc to open the built-in browser Task Manager. 2. Scroll through the tasks to find Tab: Claude. 3. Click on the Claude tab process to highlight it, then click End Process at the bottom-right. 4. Reload the tab. * On macOS Safari / Firefox: If the browser as a whole is locked up, press Cmd + Option + Esc to open the Force Quit applications menu, choose your browser, and force close it.

2. Terminate and Archive Long Chat Threads Claude processes the entire active chat history with every new message you send to maintain context. If you have an exceptionally long chat thread containing large code blocks, PDFs, or system rules, the browser's JavaScript V8 engine can run out of memory trying to render and update the Document Object Model (DOM).

If your page freezes on a specific thread: 1. Re-open Claude.ai but do not click on the problematic thread. 2. If possible, click the Starred/Recent list and locate the thread. 3. Click the options menu (three dots) beside the thread name and select Delete or start a completely New Chat. 4. Moving forward, limit long conversations by starting a new chat session once you reach 20-30 conversational turns.

3. Disable Memory-Heavy Browser Extensions Browser extensions, especially ad-blockers, script-blockers, translation modules, and automated webpage parsers, can conflict with Claude's streaming scripts. If an extension attempts to parse Claude’s dynamic Markdown formatting in real-time, it can cause the browser thread to lock up.

To identify a conflicting extension: 1. Open an Incognito / Private Browsing window (which usually has extensions disabled by default). 2. Navigate to Claude.ai and log in. 3. Test the interface. If the "Page Unresponsive" error disappears, an extension is causing the crash. 4. Go to your browser's Extensions / Add-ons manager. 5. Toggle extensions off one by one (starting with ad-blockers or web-scrapers) to isolate the culprit, then whitelist claude.ai in that extension's settings.

4. Toggle Browser Hardware Acceleration If your browser's hardware acceleration is misconfigured or conflicting with outdated graphics drivers, rendering complex real-time elements (like Claude’s dynamic code blocks and formatting) can cause the web page to freeze.

• In Google Chrome:
• Click the three dots in the top-right corner and select Settings.
• Search for "Hardware Acceleration" in the settings search bar.
• Toggle the option Use graphics acceleration when available to its opposite state.
• Click Relaunch to apply the changes.
• In Firefox:
• Go to Settings > General.
• Scroll down to Performance.
• Uncheck Use recommended performance settings.
• Uncheck Use hardware acceleration when available.
• Restart Firefox.

5. Clear Local Application Data in DevTools If corrupted data is stored in your local indexedDB or application cache, it can trigger an infinite loading loop that freezes the page on startup.

1. Go to Claude.ai.
2. Press F12 or Ctrl + Shift + I (Mac: Cmd + Option + I) to open developer tools.
3. Go to the Application tab (in Chrome/Edge) or Storage tab (in Firefox).
4. Under Storage, select Clear site data.
5. Make sure all boxes (including Local storage, Session storage, IndexedDB, and Cookies) are checked, and click Clear site data.
6. Refresh the page and log back in.

When to Escalate If Claude remains completely unresponsive across multiple browsers (e.g., trying both Chrome and Firefox yields the same result) and your device has sufficient RAM, check `status.anthropic.com` to see if there is an active incident report concerning database delays or degraded web performance. If the platform status is normal, contact Anthropic support at support@anthropic.com. Include details about your operating system, browser version, and whether the freeze happens on all chats or just on specific conversations containing files.