Developer utility
JWT Decoder
Inspect a supported three-segment JWT-shaped token in this browser. Decoding does not verify a signature, authenticity, trust, authorization, or expiry.
Tokens can contain bearer credentials and personal data. Processing is designed to stay in this browser, but you remain responsible for the data you enter.
Decoded header
Decode a token to inspect its header.
Decoded payload
Decode a token to inspect its payload.
Informational claims
How to use JWT Decoder
A compact JWT-shaped value has a Base64URL-encoded header, payload, and signature separated by dots. This tool decodes only the header and payload as UTF-8 JSON objects. It does not verify the signature or prove that any claim is true.
Registered claims include iss, sub, aud, exp, nbf, iat, and jti; custom claims remain visible. NumericDate values use seconds since the Unix epoch, not milliseconds. Local clock assessments are informational only: clock skew or an incorrect device clock can make a time assessment misleading, and it never establishes authentication.
Only bounded three-segment tokens are supported. Encrypted five-segment tokens require decryption and are not decoded here. Malformed encoding, oversized/deep objects, and invalid JSON fail safely. Decoded values are rendered as text, never executed as HTML or followed as links.
Frequently asked questions
Does decoding verify a JWT?
No. Decoding only reveals the supplied header and payload. It does not validate the signature, issuer, audience, expiry, authorization, or trustworthiness.
Can I paste a production bearer token?
Do not. Use synthetic or already-redacted tokens for troubleshooting. This page is designed for browser-local inspection, but it is not a replacement for your organization’s secret-handling policy.
Related tools: Base64 Encoder & Decoder and JSON Formatter & Validator.