Claude API Key Not Working? Fix Auth Errors, Org Mismatch, and Permissions
If API auth fails, verify key scope, org/project, and environment variables. Rotate the key if compromised and check rate limits.
Step-by-step Claude errors & bugs guides — practical and to the point.
Start with the guides below, then explore the full Claude hub.
Not finding what you need? Browse another category.
If API auth fails, verify key scope, org/project, and environment variables. Rotate the key if compromised and check rate limits.
Claude Pro supports file uploads up to 10 MB per file; supported formats include PDF, Word (.docx), plain text, images (PNG/JPG/GIF/WebP), and most code files. If your attachment fails or won't process, the most common causes are an oversized file, an unsupported format, a stale browser session, or a network/extension block. Clear site data for claude.ai, disable ad blockers, and retry in incognito — that resolves the issue in the majority of cases.
If attachments stay “processing,” retry with smaller files, switch networks, disable VPN, and test another browser. If it fails everywhere, it may be a backend incident.
A Claude blank page or white screen is almost always caused by a stale browser cache, a script-blocking extension, or a VPN blocking WebSocket connections. Open an incognito window and sign in — if Claude loads there, clear all site data for claude.ai in your main browser and disable extensions one at a time. If Claude is blank in incognito too, disable your VPN and check status.anthropic.com for active outages.
If history is missing, verify account/workspace, sign out/in, and test on another device. Missing history across devices can indicate sync issues or an incident.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
If messages don’t save, check network stability, refresh the session, and test another device. Workspace permission issues can also prevent saving.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Fix Claude errors by hard-reloading, clearing cache, reducing request size, and testing another browser/network. Capture the exact error text + timestamp for support if it persists.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Claude's 'error loading chat' message appears when a conversation fails to sync from the server or a browser extension blocks the loading request. Refresh the page once, then try opening the conversation in an incognito window. If a specific chat refuses to load on all devices, that conversation's data may be corrupted on Anthropic's servers — start a new conversation to continue your work.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Report Claude bugs at support.anthropic.com. An effective bug report includes: the exact error message, the specific steps that reproduce it (not just 'it stopped working'), your browser and OS version, whether it happens in incognito, and whether it affects all conversations or just one. Including a screenshot and the approximate timestamp speeds up resolution significantly.
If export fails, try another browser, disable extensions, and allow downloads/popups. If it’s account-wide, contact support with timestamp.
If messages fail to send, refresh the session, disable extensions, switch networks, and slow down retries. If it persists, check whether you hit a usage/rate limit.
If requests fail, switch networks (hotspot), disable VPN, and try another browser. If only one network fails, it’s filtering/DNS/firewall.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify plan/permissions, check status/incidents, and retry on another network. If it persists, capture logs/error details and contact support.
If a project won’t load, confirm the correct workspace/account, refresh in incognito, and test another device. If it fails everywhere, wait and retry later.
The 'something went wrong' error in Claude is a generic message that covers session issues, browser problems, and temporary server errors. Start by refreshing the page and signing out then back in. If the error persists, clear your browser cookies for claude.ai and try a private window. This error almost never indicates an account problem — it is usually a temporary connection or session issue.
Claude stopping mid-response is usually caused by a network interruption, a browser extension blocking the streaming connection, or the response hitting a length or usage limit. The fastest fix is to refresh the page, disable extensions, and retry with a more focused request. If Claude consistently stops at the same point in a response, the content itself may be triggering a safety check — try rephrasing the request.
If webhooks don’t arrive, verify endpoint is public HTTPS, check logs, and implement retries. Confirm you’re listening on the correct environment.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.