JWT Decoder

Decode and inspect JWT token header, payload and signature.

JWT Token

Decoded JWT

Algorithm—
Token Type—
Issued At—
Expires At—

Header


Payload


Signature is NOT verified. This tool is for inspection only — never share tokens containing sensitive data.

About the JWT Decoder

The JWT Decoder reads a JSON Web Token and shows its three parts: the header, the payload and the signature. It also surfaces the registered claims, such as the algorithm, the issue time and the expiry, in readable form.

A JWT is three base64url strings joined by dots. The header says which algorithm signed it, the payload carries the claims, and the signature is the cryptographic proof. Decoding is just base64 decoding: it needs no key and proves nothing.

That distinction is the security point. Decoding tells you what a token claims, not whether it is genuine. Only the server holding the key can verify the signature. Never trust a token's contents until it has been verified, and treat any token you paste anywhere as a secret, since a valid one is as good as a password.

Common questions about JWT Decoder

Does decoding verify the token?

No. It only decodes the base64 parts. Verification requires the signing key and happens on the server.

What are the three parts?

Header, payload and signature, separated by dots. The first two are base64url encoded JSON.

What does exp mean?

Expiry time, as a Unix timestamp in seconds. After that moment the token should be rejected.

Is it safe to paste a token here?

The decoding runs in your browser, but a live token is a credential. Avoid pasting production tokens anywhere, and revoke one if you do.

Why does my token fail to decode?

Usually the base64 padding or a copy that lost characters. Tokens are base64url, which uses - and _ instead of + and /.

Can I create a token with this?

No, this only reads them. Signing needs the private key and belongs on the server.

Related Tools in Developer Tools

JSON FormatterBase64 Encoder/DecoderURL Encoder/Decoder