Skip to content

JWT decoder

Paste a JWT and see its header and payload pretty-printed, with exp, iat and nbf translated into real dates and a plain-language expiry status. Decoding is pure client-side JavaScript — the token is never sent anywhere, which matters because a live JWT is a credential, not a harmless string.

  • Nothing you type leaves this page
  • Works offline once loaded
  • Free forever, no signup
Your token never leaves this page. Decoding runs entirely in your browser's JavaScript — check your browser's Network tab and you'll see nothing sent anywhere. This tool only decodes a JWT; it never checks or verifies the signature.

From a free tool to your own software

Authentication, single sign-on and API security

Tokens decide who gets into your app and what they can reach, and a typical JWT is signed rather than encrypted, so anyone holding one can read what is inside. Teams that bolt login on late end up with tokens that never expire, sensitive data in the payload and a separate password for every internal tool. Planned authentication, with short-lived tokens, verified signatures and central sign-on, closes those gaps early.

  • Single sign-on for internal tools

    Give staff one login across admin panels, dashboards and business apps through an identity provider, with access removed everywhere when someone leaves.

  • Secure login for customer apps

    Add sign-up, OTP or social login to web and mobile apps, with short-lived access tokens, refresh token rotation and a way to revoke sessions.

  • API gateways with access control

    Put partner and mobile APIs behind a gateway that verifies every token's signature, expiry and scopes before a request reaches your business logic.

  • Role and permission systems

    Model who can view, approve or change what across teams, branches and customer accounts, and enforce it on the server rather than trusting the browser.

Who we build this for: SaaS companies, fintech and health-tech teams, and businesses exposing APIs or running several internal apps.

This tool runs entirely in your browser. The team that built it designs custom software for businesses and runs DigiSign, our own signage platform, in production.

How to use this tool

  1. Paste your JWT

    Decoding happens instantly as you type — there is no submit button and no request is ever sent.

  2. Read the header and payload

    Both are pretty-printed JSON, with exp/iat/nbf shown as local dates alongside the raw claim.

  3. Check the expiry badge

    A single line tells you whether the token is currently valid, already expired, or has no expiry at all.

Questions people ask

Is it safe to paste a JWT into an online decoder?

A live JWT is a credential — pasting one into most online tools is a real risk, since some of them log or transmit what you paste. This tool never makes a network request while decoding; open your browser's DevTools Network tab and paste a token to confirm nothing fires.

Does this tool verify the signature?

No, and it never will by design. Verifying a signature needs the issuer's secret or public key, which this tool never asks for. It decodes the header and payload only — both are readable by anyone with the token, signature or not.

What is inside a JWT?

Three base64url-encoded, dot-separated parts: a header describing the algorithm, a payload holding the claims (subject, expiry, custom data), and a signature. The header and payload are never encrypted, only encoded — a JWT hides nothing from anyone who has it.

How do I check when my JWT expires?

Paste it above — the exp claim, if present, is converted to your local time and paired with a plain-English status: "Expires in 2h" or "Expired 3d ago". A token with no exp claim never expires on its own.

Why does decoding fail with a "three parts" error?

A JWT is always header.payload.signature — exactly two dots. That error means what you pasted has been truncated, has extra whitespace mixed in, or was never a JWT (an API key or session cookie, for example) in the first place.

Does decoding a JWT expose a password?

No — JWT payloads hold claims (user ID, roles, expiry), not passwords. Still, treat a live, unexpired token like a key: anyone who has the raw string can use it to authenticate as you until it expires.

Who makes these tools

Bookmark this page — the tool keeps working offline, and your settings stay in this browser. Built by Dynamb Technologies, who build software for businesses.