Skip to content

Free JWT Decoder

Decode a JWT header and payload locally. Completely free, with no sign-up and no upload.

  • 100% free
  • No sign-up
  • No watermark
  • Works in your browser

Also called: JWT parser, decode JWT token.

About JWT Decoder

Paste a JSON Web Token to read its header and payload in plain JSON, with expiry, not-before and issued-at times converted to readable dates. It helps when debugging sign-in problems and checking what claims a token carries. Decoding happens entirely in your browser — the token is never sent anywhere.

How to use JWT Decoder

  1. Paste your JWT (a “Bearer ” prefix is fine).
  2. Read the decoded header and payload.
  3. Check the expiry status shown for exp, nbf and iat.
  4. Copy any part you need.

Tips and good to know

  • This tool decodes only. It does not verify the signature, so a decoded token is not proof that the token is genuine.
  • A JWT payload is only Base64-encoded, not encrypted — never put secrets in it.
  • Avoid pasting production tokens into any site you do not trust.

Decoding is not verifying

A JSON Web Token has three parts separated by dots: a header, a payload and a signature, each Base64URL-encoded. Anyone can decode the header and payload; they are not encrypted, so never put passwords or private data in a JWT. Trust comes only from verifying the signature with the right key on your server and checking claims such as exp (expiry), iss (issuer) and aud (audience). Decoding is for debugging: seeing what a token contains and why it might be rejected.

Anatomy of a JWT

A JSON Web Token has three parts separated by dots: a header (which says how the token is signed), a payload (the claims, such as user ID, roles and expiry time) and a signature. The first two are only Base64URL-encoded JSON, which is why anyone can read them. The signature lets the server that issued the token detect whether it has been changed.

Standard claims have short names: “sub” is the subject (usually a user ID), “iss” the issuer, “aud” the intended audience, and “exp”, “nbf” and “iat” are times in seconds since 1 January 1970 (Unix time).

Frequently asked questions

Why does it say the signature is not verified?

Verifying needs the secret or public key, which this tool never asks for. Verification should be done in your own server code.

Is JWT Decoder free?

Yes. JWT Decoder is 100% free: no sign-up, no paid plan, no trial and no limit on how often you use it. It runs in your browser, and ToolzAura is paid for by ads, so every tool stays free.

Are my files uploaded?

No. This tool runs in your browser, so your input stays on your device.

Maintained by Malik Shaheer · Last reviewed · How we test tools · Report a problem

Guides for JWT Decoder

Related tools

Password Strength Checker

Test how resistant a password is to guessing.

Developer Tools

Unix Timestamp Converter

Convert between Unix timestamps and readable dates.

Developer Tools

TOTP Code Generator

Generate time-based one-time codes from a secret.

Developer Tools

URL Encode and Decode

Percent-encode or decode URLs and text.

Developer Tools

URL Parser

Split a URL into its parts and query parameters.

Developer Tools

UUID Generator

Generate v4 UUIDs in bulk.

Developer Tools