Paste a JSON Web Token to inspect the header and payload claims, then verify the signature with your secret. Runs in your browser — nothing uploaded.
Enter the secret used to sign the JWT (HS256 / HS384 / HS512):
header.payload.signature) into Encoded JWT — a sample is preloaded.alg, typ).sub, iat, exp.How do I know if the secret is valid? Enter it under Signature verification. For HS256/HS384/HS512 you will see Signature verified or Invalid signature.
Does editing the payload change the encoded JWT? Yes. Header and payload edits re-encode those segments; the previous signature will usually become invalid until you re-sign elsewhere.
Does this upload my token? No. Everything runs client-side.
Related: Base64 encode · Base64 decode · Epoch converter · Current Unix time · All developer tools