Skip to content
claudecookie
Back to the converter

Check a Claude sessionKey cookie: is it still valid?

Paste a Netscape or JSON export. The check reads the account, plan, and the 5-hour and weekly usage windows — the same numbers Claude shows in Settings.

What the check reads

Account & plan

The email on the session and which Claude plan it belongs to — Free, Pro, or Max.

5-hour window

How much of the current 5-hour usage window is spent, and when it resets.

Weekly window

The same for the rolling weekly limit Claude enforces on paid plans.

Formats it accepts

A Netscape cookies.txt export, a JSON cookie array (Cookie-Editor or Puppeteer), or a raw Cookie: header. Only sessionKey / sessionKeyV3 is required.

The paste is encrypted in your browser, then sent to this site’s backend and to Anthropic to run the check. How this is handled.

claude session check
# paste your claude.ai session cookie above
sessionKey = sk-ant-sid01-…   (or sessionKeyV3)
✔ Valid — you@example.com · Claude Max
  5-hour window   ▓▓▓▓▓░░░░░  42%  · resets 14:20
  weekly window   ▓▓▓▓▓▓▓░░░  68%  · resets Sat 03:00

How to get your Claude session cookie

  1. 01

    Open claude.ai while logged in

    In your browser, open DevTools (F12) → Application → Cookies → https://claude.ai and copy the sessionKey (or sessionKeyV3) value. Or use the Cookie-Editor extension → Export → JSON to grab the whole set at once.

  2. 02

    Paste it above

    Drop the cookies.txt or JSON export into the box, or paste just the sessionKey line. The paste is encrypted in your browser before it is sent — only the sessionKey / sessionKeyV3 is actually required.

  3. 03

    Read the result

    The checker calls Claude with the cookie and reports whether the session is still valid, the account email and plan (Free, Pro or Max), and how much of the 5-hour and weekly usage windows are left.

Claude cookie & session — questions

It is the cookie claude.ai sets when you sign in — a long token (sessionKey, or the newer sessionKeyV3) that authenticates your browser to Claude. Anyone who has it can act as your account, so treat it like a password. Claude Code stores the equivalent credential as an OAuth token in ~/.claude/.credentials.json rather than as this cookie.

Either one. Both are session cookies claude.ai sets; sessionKeyV3 is the newer format and some accounts have both. The checker reads whichever is present — only one is required.

Roughly 30 days, unless it is revoked sooner. It rotates — and the old value stops working — when you log out, change your password, or sign out of your other sessions. After any of those you need a fresh export.

No. The check only reads the account, plan and usage windows; it does not log you out or rotate the key. It runs one lightweight request, the same one claude.ai makes to draw your usage screen.

The token Claude holds is dead. Common causes: it aged out (the ~30-day cookie, or an access token that failed its background refresh), you changed your password, you signed out elsewhere, an admin revoked sessions, or your system clock is wrong. One more to check in Claude Code: an ANTHROPIC_API_KEY environment variable competing with your subscription login. The reliable fix is /logout then /login; if it loops, delete ~/.claude/.credentials.json and sign in again.

Claude Pro and Max meter usage two ways: a rolling 5-hour session window and a fixed weekly window, and that usage is shared across claude.ai, Claude Code and Claude Desktop. The 5-hour window resets five hours after your first message in it; the weekly window resets on a fixed day and time shown in Settings → Usage. This checker shows how much of each you have spent.

Claude Code signs in through its own OAuth flow (/login) and stores its credential in ~/.claude/.credentials.json, not as a pasted cookie. This page checks a claude.ai browser session — the same account — so it is useful for confirming your session is alive and seeing the plan and limits Claude Code will be subject to.

The converter runs entirely in your browser. The session check is different: it has to send the cookie to this site’s backend and to Anthropic to run the check, so the paste is encrypted in your browser first. Only ever paste cookies for an account you control, and read the privacy page for exactly what happens.