Complete guide — how to use Claude, fix common errors, manage billing, and get the most out of every feature.
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.
Try incognito mode, clear cookies for the service, disable extensions, and retry. If you use Google/Apple login, re-authorize the provider and check for outages.
Try incognito mode, clear cookies for the service, disable extensions, and retry. If you use Google/Apple login, re-authorize the provider and check for outages.
Update your payment method, confirm your card supports international/recurring charges, and check your bank for blocked transactions. If charged but not activated, wait a few minutes and contact support.
Update your payment method, confirm your card supports international/recurring charges, and check your bank for blocked transactions. If charged but not activated, wait a few minutes and contact support.
If API auth fails, verify key scope, org/project, and environment variables. Rotate the key if compromised and check rate limits.
Claude Artifacts are self-contained outputs — code, HTML pages, React components, SVG graphics, or documents — displayed in a dedicated side panel next to the chat. The Artifact panel appears automatically whenever Claude generates code or a structured document, giving you a clean space to view, edit, copy, and preview output without scrolling through the conversation. Artifacts are available to all Claude users at claude.ai; no setup required.
If you hit an attachment count limit, remove older attachments, split work into multiple chats, compress files, and upgrade plan only if the limit is plan-based.
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.
If billing history is empty, confirm correct account/workspace, refresh in incognito, and compare with bank records. Escalate if posted charges don’t appear after 24h.
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.
Claude's billing page fails to load most often because of browser extensions blocking payment scripts or a stale session. Open the billing page in an incognito window without any extensions — this resolves the issue in most cases. Go to Settings → Billing after signing in. If the page loads in incognito but not your regular browser, the culprit is an ad blocker or privacy extension.
To change your Claude plan, go to Settings → Billing → Change Plan on claude.ai. Upgrading from Free to Pro ($20/month) activates immediately. Downgrading from Pro to Free takes effect at the end of your current billing period — you keep Pro access until then. You will not lose your conversation history when changing plans, but Projects require a Pro subscription to remain active.
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 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.
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.
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.
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.
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.
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.
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.
Try incognito mode, clear cookies for the service, disable extensions, and retry. If you use Google/Apple login, re-authorize the provider and check for outages.
Claude supports 3 login methods: Google OAuth, Apple ID, and email+password — using the wrong method for your account type is the single most common cause of login failure. Start by clearing cookies for claude.ai, trying incognito mode, and confirming you are using the exact sign-in method you registered with. Verification code delays average under 2 minutes; check your spam folder for emails from noreply@anthropic.com and wait 5 minutes before requesting a new code.
If your card is declined, ask your bank to allow international + recurring online payments and ensure 3DS works. Retry once in incognito on a stable network.
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.
Update your payment method, confirm your card supports international/recurring charges, and check your bank for blocked transactions. If charged but not activated, wait a few minutes and contact support.
Update your payment method, confirm your card supports international/recurring charges, and check your bank for blocked transactions. If charged but not activated, wait a few minutes and contact support.
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.
If a coupon won’t apply, confirm eligibility and region, try a clean billing session, and ensure you’re redeeming on the billing owner account.
If account deletion won’t complete, try a clean session, ensure email verification works, and contact support with screenshots if it keeps failing.
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 a feature is unavailable, confirm plan/workspace, refresh billing state, and retry in a clean session. If it’s a rollout, wait and retry.
Claude's context window holds up to 200,000 tokens on paid plans — roughly 150,000 words. As conversations grow long, Claude's accuracy on earlier content degrades before the hard limit is hit. The most effective strategy is to start fresh conversations with a structured summary of essential context rather than continuing one extremely long thread. Keep project files concise and use Claude Projects to persist only what Claude genuinely needs.
To use Claude, go to claude.ai, create a free account with Google, Apple, or email, and start typing in the chat box. Claude responds immediately and handles writing, analysis, coding, research, and conversation well. The free plan uses Claude Haiku; Claude Pro ($20/month) unlocks the more capable Claude Sonnet and Opus models with higher usage limits. No setup required.
If an invite link is expired, request a new invite from the owner, ensure you’re logged into the correct email, and accept in incognito if redirects loop.
If invoices are missing, verify the billing owner account, refresh billing in incognito, and check pending vs posted charges. Escalate after 24h with timestamps.
Claude invoices appear in Settings → Billing on claude.ai and are also emailed from Anthropic within minutes of a successful payment. If your invoice is not showing, first confirm you are logged into the correct account — the receipt goes to the email used for purchase. Billing history can take up to 24 hours to appear for new subscriptions. If no invoice arrives after 24 hours, contact support.anthropic.com.
Claude temporary restrictions occur when usage patterns trigger automated safety checks — sending many rapid messages, unusual request patterns, or content that approaches policy limits. Most restrictions are temporary and lift within a few hours. To avoid them: use Claude at a natural pace, start new conversations instead of sending dozens of messages in a single thread, and avoid testing content policy limits with repeated edge-case requests.
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 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.
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 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.
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.
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 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.
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.
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.
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.
Claude's desktop app login failures are usually caused by a corrupted app session, outdated app version, or a network issue specific to the desktop app's built-in browser. Try signing out completely and back in, then update the app to the latest version. If the app login continues to fail, use claude.ai in a regular web browser as a working alternative while you troubleshoot.
Mobile Claude login failures are most commonly fixed by force-closing and reopening the app, then signing out and back in. If the login screen does not load, check your internet connection and update the app to the latest version — outdated mobile apps frequently have authentication issues. Google and Apple login on mobile requires the native app (not a webview) to complete the OAuth handshake properly.
Clear browser data, verify your email address, or try logging in with a different authentication method (Google, email link).
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.
Hard refresh the page, disable extensions, clear cache/cookies, and try another browser or network. If it still won’t load, check for outages or regional blocking.
Fix Claude login problems by clearing site cookies, disabling extensions/VPN, completing OAuth re‑authorization (Google/Apple), and trying a different network. If you’re stuck in a loop, reset the session and verify you’re using the same login method as the account.
If Claude keeps redirecting back to login, test incognito first. If it works, clear site data and disable extensions/VPN. If it fails across devices, it’s likely SSO/workspace or a platform auth incident.
If Claude keeps redirecting you back to the login page, test incognito first. If it works there, clear site data for claude.ai, disable extensions, and turn off VPN/proxy. If it fails across devices and networks, it’s likely an SSO/workspace access issue or a platform-side auth incident.
Claude login stuck on a callback or redirect URL means the OAuth handshake completed on the provider side (Google/Apple) but the redirect back to Claude failed. Clear cookies for claude.ai, disable extensions that block redirects, and try the login again in incognito mode. If the URL in your browser ends with '/callback' or '/oauth' and never changes, that is the stuck point — a fresh session with no extensions resolves this in most cases.
Apple ID login failures on Claude are almost always caused by a blocked OAuth popup or a stale browser session. Open Claude in incognito mode, allow popups for claude.ai, and try signing in with Apple again — this resolves the problem in most cases. If you used iCloud's Hide My Email feature during signup, confirm the relay address is still active and forwarding to your real inbox.
Fix Claude login problems by clearing site cookies, disabling extensions/VPN, completing OAuth re‑authorization (Google/Apple), and trying a different network. If you’re stuck in a loop, reset the session and verify you’re using the same login method as the account.
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.
Claude Free users typically get around 10-20 messages before hitting a usage pause. Claude Pro ($20/month) gives approximately 5x more capacity. Limits are based on compute usage — not a fixed message count — so long responses drain your quota faster than short ones. When you hit the limit, Claude tells you and shows a cooldown timer. The most effective way to avoid lockouts: keep conversations shorter, start new chats instead of extending old ones, and use Claude for targeted tasks rather than open-ended exploration.
If requests fail, switch networks (hotspot), disable VPN, and try another browser. If only one network fails, it’s filtering/DNS/firewall.
Claude is available in most countries but is restricted in a handful of regions due to legal and compliance requirements. If you see a 'not available in your region' message, this is a genuine geographic restriction that cannot be bypassed through normal troubleshooting. However, if you are receiving the error despite being in a supported country, the issue is likely your IP address appearing to be in a restricted region — disabling your VPN or switching to a different network usually resolves this.
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.
Claude Pro costs $20/month and payment declines are almost always caused by your bank blocking the charge, not a problem with Claude itself. Call your bank or approve the transaction in your banking app, then retry in a clean incognito window. If a 3D Secure prompt appeared and timed out, that is the most common single cause — complete the bank verification step and retry.
Update your payment method, confirm your card supports international/recurring charges, and check your bank for blocked transactions. If charged but not activated, wait a few minutes and contact support.
Update your payment method, confirm your card supports international/recurring charges, and check your bank for blocked transactions. If charged but not activated, wait a few minutes and contact support.
Update your payment method, confirm your card supports international/recurring charges, and check your bank for blocked transactions. If charged but not activated, wait a few minutes and contact support.
Claude payment failures fall into four categories: bank block (most common), expired or incorrect card details, billing address mismatch, or a temporary issue with Anthropic's Stripe-powered payment processor. Go to Settings → Billing → Manage Subscription to update your card and retry. If the error says 'card declined,' call your bank first before retrying — multiple failed attempts can trigger a longer fraud block.
If updating payment fails, retry in incognito without VPN/extensions, verify billing address, and try another card. If it fails everywhere, contact support.
If charged but not upgraded, wait 15–30 minutes, sign out/in, verify account, then contact support with charge details if still not active.
Update your payment method, confirm your card supports international/recurring charges, and check your bank for blocked transactions. If charged but not activated, wait a few minutes and contact support.
Update your payment method, confirm your card supports international/recurring charges, and check your bank for blocked transactions. If charged but not activated, wait a few minutes and contact support.
Claude Pro costs $20/month (or $18/month billed annually) and gives approximately 5x the message quota of the free tier, plus priority access during peak hours. The exact daily message count is not published by Anthropic, but Pro users consistently report 100+ messages per day under normal use before hitting any cap. Limits reset on a rolling 8-hour window, not at a fixed midnight.
Claude Pro costs $20/month and should activate within 5 minutes of a successful payment. If Pro features are still missing, log out and back in to refresh your session token. If the problem persists after 30 minutes, check that the charge posted to your bank (not just pending) and contact support at support.anthropic.com with your receipt.
Claude Free gives you limited access to Claude 3.5 Sonnet with a low message cap (roughly 10-20 messages before hitting a pause). Claude Pro ($20/month) gives you 5x more usage, priority access during peak times, access to Claude 3 Opus, Projects for persistent memory, and longer context. If you use Claude daily or for long conversations, Free runs out fast — Pro is designed for sustained use.
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.
Claude Projects give you a persistent workspace where uploaded documents and instructions stay available across every conversation in that project. Create one from the sidebar, upload relevant files, add custom instructions, then start conversations — Claude always has your context without you re-pasting it. Projects require Claude Pro ($20/month).
Claude follows detailed instructions well, so specificity is the biggest lever for quality. Tell Claude your role, the audience, the desired format, and what to avoid. Use the full context window — Claude handles long prompts better than most models. Ask for multiple versions, give iterative feedback, and specify constraints upfront rather than correcting after. The prompt is your only interface; writing it well is the skill.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use an alternative workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use an alternative workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use an alternative workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use an alternative workflow until the window resets.
If you hit rate limits, slow down requests, wait, and avoid rapid retries. If using automation, add exponential backoff and reduce concurrency.
Claude Pro enforces a 5-hour rolling usage window — not a daily reset. When you exhaust that window, you must wait until the oldest messages age out before the quota refreshes. Free users face stricter caps with no fixed window. As of May 6, 2026, Anthropic removed peak-hour throttling for Pro and Max subscribers, so you no longer get slower responses during busy periods (5am–11am PT). To continue working sooner: upgrade to Max ($100–$200/month for 5x–20x more headroom), batch your messages, or switch to shorter conversations.
To request a refund, collect charge details and submit a structured request. If denied, reply with timestamps and evidence instead of opening multiple tickets.
When Claude Pro renews but still shows free tier limits, the issue is almost always a stale browser session — your session token was issued before the renewal and still carries the old entitlements. Sign out completely, wait 30 seconds, and sign back in. This forces Claude to issue a new session that reflects the current Pro status. If the problem persists after signing back in, go to Settings → Billing to confirm the subscription shows as Active.
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 request is too large, shorten context, remove big uploads, and split prompts. Use multiple turns and avoid pasting huge logs in one go.
Try incognito mode, clear cookies for Claude/Anthropic, disable extensions, and retry. If you use Sign in with Google/Apple, re-authorize the provider and check for outages.
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 Claude keeps verifying without completing, use incognito + hotspot to isolate browser vs network. Clear cookies for claude.ai, disable extensions, and avoid VPN. If it reproduces everywhere, contact support with timestamps.
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 cancellation doesn’t stick, verify correct account, refresh in incognito, and check end date. If charged again, contact support with screenshots and timestamps.
Claude throttles Pro and Max users during peak hours (5 AM to 11 AM PT / 8 AM to 2 PM ET / 13:00 to 19:00 GMT), causing the 5-hour usage window to deplete 2–3x faster than normal. Between March and May 2026, some Claude Max users reported their full session quota exhausting in under 19 minutes during peak times. On May 6, 2026, Anthropic partially removed peak-hour throttling for Pro and Max users, but heavy usage during high-demand periods can still trigger slowdowns.
If you hit too many requests, slow down, wait, and avoid rapid retries. If using automation, add backoff. Test another network to rule out VPN loops.
When Claude blocks you due to limits: pause retries, check your plan/usage window, reduce concurrency, and avoid automation spikes. If limits are plan-based, wait for reset or upgrade.
When Claude blocks you due to limits: pause retries, check your plan/usage window, reduce concurrency, and avoid automation spikes. If limits are plan-based, wait for reset or upgrade.
Claude's usage limits reset on a rolling 8-hour window, not at a fixed midnight. Free users typically get 10–20 messages before hitting the cap; Claude Pro users get approximately 5x that amount with priority access during peak hours. To continue immediately: upgrade to Claude Pro ($18/month billed annually), switch to Claude Haiku (separate, lighter cap), or start a fresh conversation to avoid heavy context overhead.
Claude Pro does not reset at a fixed daily time. Instead, it uses a rolling 5-hour window: your usage allowance refills 5 hours after your first message in a session, not at midnight. Claude Max ($100–$200/month) uses the same rolling system but with a significantly higher cap. The most efficient times to use Claude Pro are between 11 PM and 5 AM PT, when server load is lowest and your quota stretches furthest.
Claude verification codes typically arrive within 60 seconds but can take up to 10 minutes during high traffic. Check your spam and promotions folders before requesting another code — clicking resend multiple times can trigger a rate limit that delays all subsequent codes by 15–30 minutes. If using a corporate, iCloud, or Outlook email, check quarantine folders as Anthropic's emails are frequently filtered.
Claude verification codes expire within 10 minutes and are invalidated when a newer code is requested. If your code is rejected, request one fresh code, enter it within 2 minutes by typing it manually (not copy-pasting), and complete the process in a single browser tab. If it keeps failing, try the entire login flow in a new incognito window.
If webhooks don’t arrive, verify endpoint is public HTTPS, check logs, and implement retries. Confirm you’re listening on the correct environment.
If workspace access is denied, verify correct account/workspace, check SSO requirements, and ask the owner to confirm role. Test incognito to rule out stale sessions.
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.
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.
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.
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.