MafLabs
Free client-side developer utility

JWT Decoder Online

Inspect, decode, and verify JSON Web Tokens in real time. Decodes token headers, claims payload, expiration state, and verifies signatures without sending data anywhere.

Runs in your browser. Nothing is uploaded.

Encoded Token

0 chars
Header Payload Signature

Important: Decoding is not verifying. Never trust a token only because it decodes. Always verify its cryptographic signature on your server.

Token Status:Waiting for token
HEADERAlgorithm & Token Type
No valid header decoded yet
PAYLOADClaims & User Data
No valid payload decoded yet

Decoded Registered Claims

ClaimRaw ValuePlain-English Meaning & Timestamp Conversion
No claims to show
SIGNATURECryptographic Verification
Algorithm: HS256
No signature
Web Crypto API in-browser

How to Use MafLabs JWT Decoder

1

Paste Token

Insert your compact JSON Web Token into the input textarea, drag and drop a file, or click “Sample” to load an example.

2

Inspect Claims

Review human-readable JSON payloads, scopes, user roles, subject IDs, and issuer values in formatted, color-coded cards.

3

Check Expiry

Instantly see whether the token is currently active, expired, or not yet valid, along with precise UTC and relative time calculations.

4

Verify Signature

Supply your symmetric secret key or public certificate to cryptographically test signatures directly via the browser Web Crypto API.

Example: Sample Token and Decoded Output

Below is a typical compact JSON Web Token issued during an authentication exchange, followed by its corresponding decoded header, payload claims, and signature breakdown:

Compact Raw Token:
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkphbmUgRGV2ZWxvcGVyIiwiYWRtaW4iOnRydWUsImlhdCI6MTUxNjIzOTAyMiwiZXhwIjoxODkzNDU2MDAwfQ.PpQkjEiXNWAY0anNByKHkxY4HZE0YT9_oP582n9u07o
Decoded Header:
{
  "alg": "HS256",
  "typ": "JWT"
}
Decoded Payload:
{
  "sub": "1234567890",
  "name": "Jane Developer",
  "admin": true,
  "iat": 1516239022,
  "exp": 1893456000
}

Understanding JSON Web Tokens (JWT)

A JSON Web Token (JWT), formalized under RFC 7519, is an open, industry-standard specification for representing claims securely between two parties. JWTs are widely employed in modern web applications, microservice architectures, single sign-on (SSO) systems, and OAuth 2.0 / OpenID Connect (OIDC) authentication flows.

The Three Parts of a JWT

In its compact serialized form, a JWT consists of three distinct segments separated by dots (.):

  • 1. Header: Contains cryptographic metadata about the token, most notably the signing algorithm (alg, such as HS256, RS256, or ES256) and the token type (typ: "JWT"). It may also optionally specify key identifiers (kid).
  • 2. Payload (Claims): Contains the actual statements or assertions regarding the entity (typically an authenticated user) and additional contextual data. RFC 7519 defines registered claims such as iss (issuer), sub (subject), aud (audience), and exp (expiration time). Applications may also append custom public or private claims.
  • 3. Signature: Produced by hashing the encoded header and payload together with a cryptographic secret (for symmetric algorithms like HS256) or signing with a private key (for asymmetric algorithms like RS256 or ES256). The signature verifies that the sender is authentic and ensures that the message contents have not been tampered with along the network transport path.

When and Why to Decode a JWT

Developers and security engineers frequently inspect JWTs when debugging API authorization bugs, diagnosing expired session errors, inspecting OAuth scope allocations, or validating user identity claims. Because tokens are simply Base64URL-encoded JSON, anyone holding the token can decode and view its claims in plaintext. However, decoding is merely reading the data—it does not prove authenticity. Authenticity requires cryptographic signature verification on the receiving server or via trusted public key certificates.

Frequently Asked Questions

Is it safe to paste a JWT here?

Yes. MafLabs JWT Decoder executes 100% locally in your client web browser. No network requests are made, no tokens are stored in cookies or localStorage, and no analytics track token inputs.

Does decoding verify the token?

No. Decoding simply Base64URL-decodes the JSON payload so you can read it. It does not verify that the signature is authentic or untampered. You should never trust authorization based purely on decoding.

What do exp, iat, and nbf mean?

These are standardized timestamp claims under RFC 7519:
• exp (Expiration Time): The timestamp after which the token must not be accepted.
• iat (Issued At): The time when the JWT was originated.
• nbf (Not Before): The token must not be accepted for processing before this timestamp.

Why does my token show as expired?

When the exp claim value is lower than the current Unix epoch time (in seconds), the token is considered stale. If your backend APIs receive an expired token, they will return an HTTP 401 Unauthorized status.

What is the difference between HS256 and RS256?

HS256 is a symmetric HMAC SHA-256 algorithm requiring the exact same shared secret to sign and verify. RS256 is an asymmetric algorithm that signs with a private RSA key and verifies with a public key certificate.

Related Developer Tools

Check out our related developer utilities on MafLabs: Base64 decoder for raw byte inspection and decoding, and timestamp converter for converting Unix seconds and milliseconds to human-readable dates.