Developer Tools TutorialTested & Verified100% Client-Side

How to Decode a JWT and Read What Is Inside It

4 min read•Updated 2026-10-18

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.

Quick Summary

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

How to Decode a JWT and Read What Is Inside It: visual tutorial process diagram and workflow architecture

JWT Decoder Process Workflow

3 Simple Steps
1
Paste the token
2
Read the header
3
Read the payload
Process Architecture • JWT DecoderInteractive Workflow Graphic
Input SourceTXT
Unprocessed Asset
In-Browser EngineWebCrypto & AST Syntax Evaluator
0% Server Upload100% Private
Verified ResultJSON
Ready for Production
Figure 1.1: Verified end-to-end processing pipeline for JWT Decoder. Data is transformed entirely within local browser memory with zero network roundtrips.

Before You Start

  • A JWT string

Step-by-Step Instructions

Follow these verified steps to complete the task with JWT Decoder.

Step 01Drag & Drop Zone

Paste the token

Drop the whole token in, dots included. Decoding happens in the page; the token is never sent anywhere.

Step 01: Visual walkthrough of Paste the token
Drag & drop file here or click to browse
Select or specify JWT Decoder input data
Helpful Tip: Ensure all input parameters match your destination requirements.
Step 02Configuration Controls

Read the header

It names the signing algorithm and the token type. An algorithm of none is a red flag worth investigating.

Step 02: Visual walkthrough of Read the header
Target Settings & FormatSelect or specify JWT Decoder input data
Helpful Tip: Ensure all input parameters match your destination requirements.
Step 03One-Click Export

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.

Step 03: Visual walkthrough of Read the payload
Processing complete • Ready to save
Step 3 validation and preview complete
Helpful Tip: Ensure all input parameters match your destination requirements.

JWT Decoder Results Comparison

Zero Syntax Errors
Visual before and after comparison demonstrating Raw Unformatted Input transformed to Validated Clean Output
Before / InputRaw string · 1,420 chars · Hard to read or debug

Raw Unformatted Input

Minified 1-line payload with escaped characters & nested keys
After / ProcessedStructured hierarchy · Verified schema · Copy-ready

Validated Clean Output

Color-coded, indented, syntax-validated structure

Settings & Configuration Guide

SettingRecommended ValueHow It Works & Impact
Indentation Spacing2 Spaces

Configures visual code formatting and structure readability.

Impact: Standard formatting convention for JSON, JavaScript, and YAML payloads.
Key OrderingPreserve 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.

Solution: Close unused browser tabs, or process files in smaller batches (e.g. 5-10 files at a time instead of 30).

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.

Solution: Select standard backwards-compatible export formats like PNG, JPG, or MP3 in the tool settings dropdown.

Quality appears different from expected output

Possible Cause: Aggressive lossy compression or incorrect aspect ratio scaling settings selected in the interface.

Solution: Adjust the quality slider to 85%+ or choose lossless processing mode to retain original fidelity.
Client-Side Processing: JWT Decoder runs entirely in your browser memory via HTML5 Canvas / WebAssembly. Your files and data are never transmitted or stored on any remote server.

Frequently Asked Questions

No. It is base64url encoded, which is reversible by anyone. Never put a secret in a JWT payload.