JWT Decoder

Your token never leaves your browser — decoding and signature checks run on your device. Unlike jwt.io, nothing is ever uploaded for verification.

Paste any JSON Web Token and instantly see its header and payload as readable JSON — plus whether it has expired and whether its HS256 signature matches your secret. Decoding a JWT only reads the Base64URL parts, so it needs no key; verifying the signature does need the secret, and here the check runs in your browser instead of on a server. Free, no signup, and your token never leaves your device.

Frequently asked questions

What is a JWT?

A JSON Web Token is three Base64URL parts separated by dots: a header (algorithm and type), a payload (the claims, like user id and expiry), and a signature. Servers use it to prove a login without storing a session.

Is it safe to paste my token here?

Decoding happens entirely in your browser — the token is never uploaded, stored, or shared. Still, treat tokens like passwords: never paste a production token into any website you do not trust, and revoke it if you think it leaked.

Why does jwt.io send my token to a server?

jwt.io verifies signatures on its server by default, which means your token leaves your browser. This decoder verifies HS256 signatures locally with Web Crypto, so the token stays on your device.

Can I verify any JWT signature?

HS256 signatures can be verified here if you enter the HMAC secret. RS256 and ES256 tokens (signed with a private key) can be decoded, but their signatures cannot be verified without the public key, so this page reports them as unsupported for verification.