Category: Developer tools
JWT Decoder
Inspect a JWT header, payload, signature segment and time claims
Decode a JWT header, payload and time claims, inspect its signature segment and expiry status. Processing stays local and does not verify the signature.
{
"alg": "HS256",
"typ": "JWT"
}{
"sub": "1234567890",
"name": "Ada Lovelace",
"role": "editor",
"iat": 1700000000,
"exp": 1900000000
}S2R4bV9sb2NhbC1zaWduYXR1cmUtZXhhbXBsZQ
Signature not verified. This page only decodes the token in your browser; it never sends it anywhere and does not check whether the signature is valid.
Everything on this page is processed in your browser. Nothing is uploaded.
What this tool does
This JWT decoder reads the Base64URL header and payload of a compact token and displays them as formatted JSON. It also shows the raw signature segment, common alg and typ fields, and iat, nbf and exp timestamps with a status based on your browser clock. Decoding does not verify a signature, issuer or audience and does not prove that the token is authentic.
How to use it
- Paste a compact JWT containing three dot-separated segments.
- Inspect the decoded header, payload, signature segment and time status.
- Treat the result as inspection only; verify the signature separately before trusting the token.
Privacy
This tool runs entirely in your browser. Your input is never uploaded, stored or shared — closing the tab removes it.
Frequently asked questions
- Can anyone decode a JWT?
- The header and payload of a typical unencrypted JWT can be read because they use Base64URL encoding, not encryption. Secrets should not be placed in the payload.
- Does decoding a JWT verify its signature?
- No. Decoding reads content; verification needs the correct secret or public key plus the required algorithm and validation rules.
- Why is a JWT marked expired or not yet valid?
- The tool compares exp and nbf claims with the current clock on your device. An incorrect device clock can affect the displayed status.
- Can I decode a JWT without the secret key?
- You can read the header and payload without a key, but that does not prove the signature is valid or the token can be trusted.
- Is the pasted JWT uploaded?
- No. Decoding happens in the browser and LocalTools does not receive the token or result. You should still avoid sharing real sensitive tokens.