How to Decode a JWT in 3 Steps
Inspect encoded authentication tokens safely in seconds:
- Paste Your Token: Paste any raw JSON Web Token (
eyJhbGci...) into the input area above. - Review Header & Payload: The tool decodes the Base64URL strings in real-time, displaying the cryptographic header and JSON payload claims.
- Verify Expiration: The interactive inspector converts the
expUnix timestamp into human-readable UTC time and highlights whether the token is currently active or expired.
Structure of a Standard JSON Web Token
A JSON Web Token consists of three distinct parts separated by dots (.):
- Header: Contains token metadata, typically the signing algorithm (
alg, such as HS256 or RS256) and token type (typ: JWT). - Payload: Contains the claims, such as subject ID (
sub), user roles, issuer (iss), and expiration timestamp (exp). - Signature: Cryptographic hash generated by signing the encoded header and payload with a secret or private key.
Why You Should Never Use Server-Side JWT Decoders
Many popular JWT debugging websites transmit your pasted token across the internet to their backend servers for decoding:
- Session Hijacking Risk: If you paste a production auth token into a remote server, anyone with access to that server's logs can impersonate your active user session.
- Client-Side Safety: BestConverter decodes Base64URL entirely inside client-side JavaScript memory. No network requests are made.
- Offline Capable: Works flawlessly in offline development environments without internet connectivity.
Common JWT Claims Reference
| Claim Key | Standard Name | Description |
|---|---|---|
sub |
Subject | Unique identifier representing the user or entity |
iss |
Issuer | Authority or server that generated and signed the token |
aud |
Audience | Intended recipient or API endpoint for the token |
exp |
Expiration Time | Unix timestamp marking when the token ceases to be valid |
iat |
Issued At | Unix timestamp recording when the token was created |