Header and payload decoded, exp as a live green/red countdown, HS256 signing and tamper checks, RS256 public-key verification.
EVIDENCE BENCHRFC 7519 · Base64URL · WebCrypto
!
Fair warning: a JWT is signed, not encrypted. The payload is Base64URL-encoded - that is a transport encoding, not encryption, and anyone holding the token can read it. The signature proves the token was not tampered with, not that it was never read. Keep passwords and phone numbers out of the payload.
1. Raw token
2. Decoded header + payload
3. Sign a token HS256
RS256 verification (optional): verify RS / PS / ES tokens with a public key
Tokens and secrets are processed inside this device's browser only - nothing is uploaded, nothing is collected, and it works offline; interface preferences live in this browser's localStorage and are lost if you switch devices or clear site data. To remove them, use "Clear my data" in the footer. And never paste production secrets into any online tool - including this one.
Three steps, done
PasteDrop the full eyJ-prefixed token into pane 1; pane 2 immediately shows the header, payload and exp status.
Verify or signKnow the secret? Hit "Verify signature". Need a token? Fill the secret and payload in pane 3 and sign.
Take it awaySigned tokens land back in pane 1 for inspection; change one character and re-verify - watch it must fail.
Parameters and boundaries
Input
JWS compact serialization (three dot-separated Base64URL segments); payload JSON + secret text for signing; PEM public key for RS256
Output
Decoded view (header/payload key-values + exp in local time); a fully signed HS256 token; verdicts (pass / signature mismatch / format error)
Key parameters
HS256 (HMAC-SHA256) by default; RS256/PS256/ES-family parse and public-key verify only; token up to 1MB
Processing
Browser-local WebCrypto - no uploads, no accounts; preferences in localStorage (nothing written on first load)
Limits
Token up to 1MB per run (rejected with a message beyond that); payload JSON up to 1MB
Known limits
Payload is never encrypted (that is JWT default - keep secrets out); no JWE decryption; iss/aud/nbf claims are shown but not policy-checked; bring your own PEM public key - the page does not generate key pairs
FAQ
Is a JWT encrypted? Can I put passwords in the payload?
No - underline that three times. A JWT is signed by default, not encrypted: the payload is Base64URL-encoded, which is a transport encoding and not encryption, so anyone who grabs the token can read its contents directly. The signature guarantees the token was not tampered with, not that it was never read. Passwords, phone numbers and ID numbers never belong in a payload; confidentiality belongs to TLS on the transport layer or to actual encryption schemes like JWE.
HS256 or RS256 - which one should I use?
HS256 is symmetric: the same secret signs and verifies, which is fast and simple - a good fit for a monolith that issues and checks its own tokens. RS256 is asymmetric: a private key signs, a public key verifies, which suits multi-party setups - the auth service holds the private key while every other service only gets the public key, so verifiers never gain issuing power. This tool signs and verifies HS256, and parses plus public-key-verifies RS256.
What does a signature mismatch actually mean?
Two possibilities: the token was modified - touch one character of the payload and the recomputed signature stops matching, which is the entire point of signatures - or the key is wrong, meaning the verifier is not using the same secret as the issuer. Try editing one payload character and re-verifying: it must fail, and watching that failure succeed is how you know the check actually works.
Why did the exp box turn red?
exp in the payload is a Unix timestamp - the latest moment this token should be accepted. The page converts it to your local timezone and compares it with the clock: green with remaining time before expiry, red once it has passed. Note that exp is only a claim; the token itself never disappears, and whether an expired token gets rejected is the verifier's policy.
Is my token or secret uploaded anywhere?
No. Parsing, signing and verifying all run in this device's browser via WebCrypto - there is no upload endpoint and it works offline. Only interface preferences live in this browser's localStorage; they do not follow you to another device, and Clear my data in the footer removes them. And do not paste production secrets into any online tool - including this one.