How to Decode a JWT and Read What Is Inside It
A JSON Web Token is three base64url segments separated by dots: a header, a payload and a signature. The first two are encoded, not encrypted, so anyone holding the token can read them. That is exactly why you should not paste a live token into a web service you do not control.
A JSON Web Token is three base64url segments separated by dots: a header, a payload and a signature. The first two are encoded, not encrypted, so anyone holding the token can read them. That is exactly why you should not
JWT Decoder Process Workflow
3 Simple StepsBefore You Start
- A JWT string
Step-by-Step Instructions
Follow these verified steps to complete the task with JWT Decoder.
Paste the token
Drop the whole token in, dots included. Decoding happens in the page; the token is never sent anywhere.
Read the header
It names the signing algorithm and the token type. An algorithm of none is a red flag worth investigating.
Read the payload
Here are the claims: who issued it, who it is for, and when it expires. Timestamps are seconds since the Unix epoch.
JWT Decoder Results Comparison
Raw Unformatted Input
Minified 1-line payload with escaped characters & nested keysValidated Clean Output
Color-coded, indented, syntax-validated structureSettings & Configuration Guide
| Setting | Recommended Value | How It Works & Impact |
|---|---|---|
| Indentation Spacing | 2 Spaces | Configures visual code formatting and structure readability. Impact: Standard formatting convention for JSON, JavaScript, and YAML payloads. |
| Key Ordering | Preserve Original | Maintains semantic order or sorts keys alphabetically for diffing. Impact: Prevents unintended schema validation discrepancies in strict parsers. |
Best Practices & Key Considerations
Expert Recommendations
- Decoding is not verifying. Reading a payload tells you what the token says, not whether the signature is valid or the token is trusted.
- Treat any token from a real system as a live credential. If you have pasted one into an online decoder, rotate it.
Common Mistakes to Avoid
- Selecting overly aggressive compression settings before checking visual clarity.
- Attempting to process corrupt, encrypted, or unsupported file extensions.
- Exceeding the browser memory threshold by loading too many high-resolution files at once.
Troubleshooting & Common Issues
Processing fails or browser tab becomes unresponsive
Possible Cause: Very large files can exhaust available browser tab heap memory during heavy graphics or media decoding.
Output format or file extension does not open in third-party viewer
Possible Cause: Certain legacy desktop applications lack codecs for modern formats like WebP, AVIF, or Opus.
Quality appears different from expected output
Possible Cause: Aggressive lossy compression or incorrect aspect ratio scaling settings selected in the interface.