Skip to main content
100% private — runs in your browser

JWT Decoder

Decode JWT header and payload claims locally (signature not verified).

JWT token

Signature is not verified. This tool only decodes the token locally; never paste production secrets.

How to use JWT Decoder

  1. Paste a JWT

    Enter the full token (header.payload.signature).

  2. Decode

    View the decoded header and payload as formatted JSON.

  3. Inspect claims

    Check common claims like exp/iat (shown with readable timestamps) to debug issues.

Frequently asked questions

Does this tool verify the JWT signature?

No. It only decodes the header and payload. Signature verification must be done with the appropriate secret or public key.

Is my token uploaded anywhere?

No. Decoding happens locally in your browser.

Why can I read the payload if it is a security token?

Standard JWTs are signed, not encrypted. Signing ensures integrity, but the contents are Base64URL-encoded and readable.

What do exp, iat, and nbf mean?

They are Unix timestamps: exp is expiration, iat is issued-at, and nbf is not-before. The tool shows their human-readable UTC times.

Is it safe to paste production tokens here?

The tool runs locally, but tokens are credentials. Prefer using non-production tokens and follow your organization’s security practices.

About JWT Decoder

The JWT Decoder parses a JSON Web Token and displays its header and payload in readable JSON, along with common claims such as issuer, subject, audience, and expiration. Decoding happens entirely in your browser, so the token is not sent to any server. This is useful for debugging authentication flows and inspecting claims — but remember that decoding is not the same as verifying a token’s signature or trustworthiness.

What a JWT contains

A JWT is typically three Base64URL-encoded parts separated by dots: header, payload, and signature. The header describes the token type and signing algorithm. The payload contains claims — statements about a subject (like user id) and metadata (like issued-at and expiration times). Because these parts are encoded, not encrypted (unless using JWE), anyone with the token can read the header and payload, which is why sensitive secrets should never be placed inside them.

Decoding vs verifying

This tool decodes and pretty-prints the token so you can inspect its contents. It does not verify the signature, check the issuer, or validate expiration against your auth server’s rules. A token that decodes successfully may still be expired, tampered with, or issued by an untrusted party. Signature verification requires the correct secret or public key and should be performed by your application or identity provider.

Privacy and safe usage

All decoding runs locally in the browser with no network requests. Even so, treat tokens as sensitive credentials: avoid pasting production access tokens into shared environments, and never expose private keys. Use this decoder for development and troubleshooting, and rely on proper validation libraries and secure key handling in your backend for real authentication decisions.

Use JWT Decoder on your site

This tool runs free and private in the browser. Paste it anywhere — blog posts, documentation, team wikis — and your visitors will use it without leaving your site. The embed includes a small "Made with The Tools Today" credit link.

Open the tool page →

Your privacy, your choice

We use cookies to understand how the site is used and to show relevant ads. Every tool on this site runs entirely in your browser, so the files and text you process are never uploaded. Read our privacy policy.