How JWT Structure, Base64Url Decoding & Claims Verification Work

Why Inspecting JSON Web Tokens Locally Is Essential for Web Developers

JSON Web Tokens (JWT) are widely used for stateless authentication and authorization in modern web applications, REST APIs, and Single Sign-On (SSO) systems. A JWT consists of three parts separated by dots (`.`): the Header (specifying algorithm and token type), the Payload (containing user claims like ID, role, and expiration timestamp), and the Signature (used to verify token integrity). Because payloads are encoded in standard Base64Url rather than encrypted, anyone can decode them. Our browser-based JWT Decoder splits and decodes token components instantly in real time without transmitting your authentication tokens to any remote server.

How to Decode a JWT in 3 Easy Steps

  1. Paste Token String: Paste your encoded eyJ... JWT string into the left input box (or click Load Sample JWT).
  2. Instant Inspection: The decoder splits the dots, parses Base64Url encoding, and formats the header and payload claims.
  3. Analyze Claims: Review user permissions, subject identifiers, and expiration (exp) timestamps on the right.

Base64Url Decoding & JWT Dot-Separation Formula + Worked Example

A JWT string is structurally parsed by splitting on period delimiters and decoding each Base64Url segment into a JSON object:

JWT String = Header . Payload . Signature  |  Decoded Segment = JSON.parse( atob( Base64Url ) )

Worked Example: Pasting a standard authentication token parses the header ({"alg": "HS256", "typ": "JWT"}) and payload claims ({"sub": "1234567890", "name": "John Doe", "iat": 1516239022}) instantly.

JWT Standard Claims, Header Parameters & Security Standards (16 Specs)

Use this authentication reference table to understand standard JWT claims and token structure.

JWT Component / Claim Parameter Name Data Type Description & Standard Purpose
Algorithm alg String Signing algorithm (e.g., HS256, RS256)
Token Type typ String Type of token (typically JWT)
Issuer iss String / URL Identifies principal that issued the JWT
Subject sub String / ID Identifies principal subject (User ID)
Audience aud String / Array Recipients that the JWT is intended for
Expiration Time exp Unix Epoch Time after which JWT expires and is invalid
Not Before nbf Unix Epoch Time before which JWT must not be accepted
Issued At iat Unix Epoch Time when JWT was originally issued
JWT ID jti String Unique identifier for the token (prevents replay)
Base64Url Encoding URL-Safe Base64 String format Replaces + with -, / with _
Signature Verification HMAC / RSA Cryptographic Hash Proves token was not altered in transit
Stateless Authentication No DB Session Required Self-Contained Server verifies claims without database lookups
Token Expiration Check Client Inspection Security Validation Check exp timestamp against current time
Clipboard Integration 1-click copy Workflow Tool Easy token sharing during development
Error Handling Malformed Token Catch Validation Alert Warns if dot separators or base64 are invalid
Data Privacy 100% Client-Side Memory Zero Server Upload Private auth tokens stay secure on your PC

Need to format JSON, encode Base64, generate UUIDs, or test regular expressions? Explore our companion tools:

Frequently Asked Questions

A JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. It contains three dot-separated parts: a Header, a Payload (claims), and a Signature.
This tool is designed for inspecting claims and headers. It decodes the Base64Url payload so you can read user IDs, roles, and expiration times, but it does not test private cryptographic secrets.
Never. All JWT splitting and Base64Url decoding run 100% locally inside your web browser. Your authentication tokens never leave your computer.
JWT payloads are encoded in Base64Url, not encrypted. This allows client applications to read claims like expiration times without decryption keys, while the cryptographic signature prevents tampering.