Free JWT Debugger & Decoder
Paste a JSON Web Token to decode its header and payload · and get flagged for alg:none, weak algorithms, missing expiry, and sensitive claims.
100% client-side · nothing you enter is ever sent to a server or stored.
Preview · sign in with a free account to run it
How to use it
- Paste a JSON Web Token: the three dot-separated parts that start with eyJ.
- Read the decoded header and payload as JSON.
- Check the security analysis for unsigned tokens, missing expiry, long lifetimes and sensitive claims.
- For an HS256 token, paste the secret to verify the signature locally.
Example
An HS256 token that carries a role but never expires.
Input
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJ1c2VyXzEyMyIsInJvbGUiOiJhZG1pbiIsImlhdCI6MTc5NTA0NjQwMH0.mKEnDA9FEn5H_AdH1Y0trKovhdiHytNnlHI2z8fHp38
Result
Header { "alg": "HS256", "typ": "JWT" }
Payload { "sub": "user_123", "role": "admin", "iat": 1795046400 }
⚠ HS256 (symmetric) · anyone with the shared secret can mint
valid tokens. Confirm the secret is strong and server-only.
✗ No exp claim · this token never expires.
Secret "demo-secret" → Signature valid · the secret matches.What the warnings mean
- alg is "none"
- The token isn't signed, so anyone can edit the payload and your server would accept it. Reject alg none in your verification code.
- HS256 / HS384 / HS512 (symmetric)
- The same secret signs and verifies. That's fine when only your server holds it, and dangerous if the secret is short, shared with a client, or committed to code.
- No exp claim
- The token never expires, so if it leaks it works for ever. Give access tokens a short lifetime.
- Very long-lived token (> 30 days)
- A leaked token stays valid for weeks. Use short access tokens with refresh tokens.
- No iat (issued-at) claim
- Without it you can't tell how old a token is or revoke tokens issued before a date.
- Sensitive claims
- Keys named password, secret, ssn, credit_card and similar. JWT payloads are only Base64-encoded, not encrypted, so anyone holding the token can read them.
Go deeper
Page updated
Frequently asked questions
Is my token sent anywhere?
No. Decoding, security analysis, and optional HS256 signature verification all run entirely in your browser with the Web Crypto API. The token never touches a server.
What security issues does it flag?
alg:none (unsigned tokens), weak or symmetric algorithms where asymmetric is expected, missing or far-future expiry, tokens with no exp at all, and sensitive claim names (password, secret, ssn, credit_card) that shouldn't live in a JWT.
Can it verify the signature?
For HS256 tokens you can paste the secret and the tool will verify the signature locally. RS/ES signatures are decoded and inspected but not cryptographically verified in the browser.
Can I paste a production token here?
Decoding and checking run in your browser, so the token isn't sent anywhere. A live token still grants access, though, so prefer an expired one or revoke it after testing.
Why does my Supabase token show HS256?
Projects that sign with a shared JWT secret use HS256. That's expected; the warning reminds you the secret must stay on the server. Newer Supabase projects can use asymmetric signing keys instead.
Want the full picture?
This tool covers one narrow check. A full SimplyScan runs 60 checks across 14 categories · exposed keys, RLS, XSS, auth, and speed · in 30 seconds.
Run a full security scanRelated tools
CSP Evaluator
Paste a Content-Security-Policy and get an A-F grade · with specific fixes for unsafe-inline, unsafe-eval, wildcards, and missing directives.
Password Strength Checker
Test any password's strength · entropy, estimated crack time, and detection of common patterns and dictionary words.
Email Header Analyzer
Paste raw email headers and get the story: did SPF, DKIM and DMARC pass, what path did the message take, and does anything look spoofed.