JWT decoder
Paste a JSON Web Token to see its header and payload as formatted JSON, its algorithm, and whether it has expired. It decodes only: the signature is not verified.
Runs in your browser. The token is decoded on your device and is never sent to or stored by EpiFive.
Decoded only; the signature is NOT verified. Anyone can create a token with any payload, so never trust these claims without checking the signature on your server. This page decodes in your browser and sends nothing anywhere, but as a habit, don’t paste live production tokens into websites.
Guides that use this tool
- SMTP AUTH with OAuth client credentials for apps on Exchange Online
Move an application from Basic auth SMTP to OAuth: register an Entra app with SMTP.SendAsApp, register its service…
- Set Up Business Central OAuth Service-to-Service Access with Microsoft Entra
Register a Microsoft Entra app, grant API.ReadWrite.All, add it on the Microsoft Entra Applications page and call…
- Dataverse Application Users: Server-to-Server Auth with an Entra App
Register a Microsoft Entra app, create a Dataverse application user with a least-privilege security role, get a client…
- Secure APIs in Azure API Management with validate-jwt and Rate Limits
Protect backend APIs behind Azure API Management by validating Microsoft Entra access tokens with validate-jwt and…
How to use it
- Paste the token. A leading
Bearerfrom an Authorization header is removed for you. - Check the status line: expired, not valid yet, within its window, or no expiry at all.
- Read the algorithm and the time claims in your local time and UTC.
- Copy the header or payload JSON if you need it in a bug report (remove personal data first).
How a JWT is built
- Header: JSON with the signing algorithm (alg) and usually typ and kid.
- Payload: JSON claims such as sub, aud, iss, exp and any custom data. It is encoded, not encrypted.
- Signature: computed over the first two parts with a secret or private key. Only the server can check it.
Related tools
- Base64 encode and decode: Encode or decode Base64 text (UTF-8 safe) and convert files to and from Base64.
- JSON formatter: Format, validate and minify JSON, with the line and column of any error.
- Hash generator: MD5, SHA-1, SHA-256 and SHA-512 hashes of text or files, and checksum verification.
- Regex tester: Test JavaScript regular expressions with live match highlighting, capture groups and flags.
Related guides
Questions people ask
Does this verify the JWT signature?
No. It only decodes. The header and payload of a signed JWT are just Base64url-encoded JSON, so anyone can read them, and anyone can also forge a token with any payload. Your server must verify the signature with the right key and algorithm before trusting a single claim.
Is it safe to paste a token here?
This page decodes in your browser and sends nothing anywhere. But a valid token is a password-equivalent until it expires: treat production tokens carefully and avoid pasting them into sites you have not checked.
What do iat, nbf and exp mean?
They are times in seconds since 1 January 1970 UTC. iat is when the token was issued, nbf is the earliest time it may be used, and exp is when it expires. Servers usually allow a minute or two of clock skew around nbf and exp.
Why is alg: none dangerous?
A token with alg set to none has no signature at all. Libraries that accept it would let an attacker write any claims they like. Servers should allow only the specific algorithms they expect, such as RS256 or ES256.
Why can’t I decode my token?
Check that you copied all three dot-separated parts without spaces or line breaks. A token with five parts is an encrypted JWE, whose payload can’t be read without the decryption key. Opaque access tokens (random strings) are not JWTs at all.