If you can’t open Claude, messages won’t send, or the page shows a white screen, it’s usually not that “the model is broken,” but rather an issue with your network, browser cache, or account status. Below is a prioritized, actionable troubleshooting sequence to help you get back up and running quickly with minimal hassle.
Start with three basic troubleshooting steps: network, refresh, status page
First, switch networks: move from your company network to a mobile hotspot, or vice versa, and see whether it recovers immediately. Second, force-refresh the page (Windows: Ctrl+F5, Mac: Cmd+Shift+R). Many “stuck and not moving” issues are simply caused by old resources not updating. Third, open Claude’s official status page (status.anthropic.com) to confirm whether the platform is under maintenance, so you don’t mistake a platform outage for a local issue.
Messages won’t send / keeps spinning: troubleshoot starting from the input content
When sending fails, “slim down” the input first and troubleshoot from there: remove extra-long paragraphs, dense lists, special symbols, or split it into multiple sends. If you’re attaching files/images, send plain text alone first to confirm the path is working, then add attachments one by one to pinpoint the problem. If the same message repeatedly fails, copy the content into a new chat and send again—this often bypasses an abnormal state in a single conversation.
White screen, buttons unresponsive: troubleshoot browser cache and extensions
If the page is blank or the sidebar won’t load, prioritize browser-level troubleshooting: open Claude in an incognito window and see whether it works. If it does, it’s very likely caused by cache or extensions. Next, disable ad blockers, script managers, and privacy/anti-tracking extensions, then clear cookies and cache for the site and sign in again. Finally, check whether your browser is outdated—upgrading to the latest version often resolves compatibility issues directly.
Frequent logouts / “access restricted” prompt: troubleshoot account and environment
If you keep getting signed out or see an access-restricted message, troubleshooting should focus on whether your “environment is stable”: frequently switching VPN nodes, using shared proxies, or going through a company gateway can trigger risk controls. It’s recommended to stick to a single network and reduce repeated logins within a short time. Confirm that email verification, two-factor authentication, and other security settings are working to avoid being forced out due to verification failures. If it’s clearly an account restriction, submit a ticket via the Help Center and provide screenshots and an approximate timestamp—this is more effective than repeatedly refreshing.
Still not fixed: the most time-saving troubleshooting checklist
Do one final troubleshooting pass in this order: 1) log in via an incognito window; 2) switch browsers (choose one of Chrome/Edge/Firefox); 3) switch networks; 4) disable all extensions; 5) clear site data and sign in again; 6) check whether the status page shows an incident. If none of the above works, it can basically be determined as a platform-side issue or an account-side restriction. Save the error message and page screenshots, then contact official support.
