JWT Decoder — Decode JSON Web Tokens Online Instantly

Safely decode JSON Web Tokens (JWT) to inspect their headers and payloads in a readable format.

JWT
Decodes header/payload locally. This tool does not verify signatures.
Paste a JWT to decode it.
Privacy note: All processing happens entirely in your browser. No data is sent to our servers.

About this tool

JSON Web Tokens carry signed claims in three Base64URL parts: header, payload, signature. Decode and inspect claims without verifying signature—ideal for debugging auth in development.

Never paste production secrets into untrusted online tools; this decoder runs locally in your browser.

Common use cases

  • Inspecting exp, iat, and sub claims during API debug
  • Verifying issuer and audience in OIDC tokens
  • Teaching JWT structure in security workshops
  • Checking clock skew when tokens appear expired

How to use

  1. Paste a JWT string into the input.
  2. View decoded header and payload JSON.
  3. Check expiration (exp) against current Unix time.
  4. Use signature verification in your app—not this viewer—for trust.

This page is available at /tools/jwt-decoder/.

Understanding the result

  • Header typically shows alg and typ; payload holds arbitrary JSON claims.
  • exp is Unix seconds—token invalid after that instant unless clock skew allowed.
  • Decoded payload is not trusted without cryptographic signature verification.
  • Padding-free Base64URL uses - and _ instead of + and /.

FAQ

Does this validate the signature?

Decoders show payload only. Verify signatures server-side with the correct secret or public key.

What is exp claim?

Expiration time as Unix timestamp. Compare with current time to see if token is still valid.

Bearer vs JWT?

Bearer is an HTTP scheme. JWT is a token format often sent as Authorization: Bearer <token>.

Is my token stored?

Local decoders should not persist tokens. Clear the field after debugging.