JWT Decoder
Decode a JSON Web Token and inspect its claims.
Build and sign a JSON Web Token with HMAC.
HS256, HS384 and HS512, the HMAC family, which the Web Crypto API implements natively. RS and ES algorithms need an asymmetric private key, which does not belong in a browser tool.
A token with alg set to none carries no signature at all. Libraries that honour the header have historically accepted such tokens as valid, letting anyone forge any claim. Always pin the expected algorithm on the verifying side rather than trusting the header.
No. HMAC signing runs in your browser through the Web Crypto API. The key stays in the page and is discarded when you close the tab.
Decode a JSON Web Token and inspect its claims.
Convert text and binary data to Base64 and back.
Generate a SHA-256 digest of any text.
Your input is saved in this browser so a refresh does not lose it. Tools handling credentials are never saved.