ToolSphere

JWT Decoder

More tools

Paste a JSON Web Token to see its header, payload and algorithm, with exp and iat shown as readable dates. Decoded in your browser, never sent anywhere.

On this browser only

Give feedback

Did this tool help?

Tell us what worked, what didn’t, or what you’d like next.

Opens Google Forms in a new tab with this tool’s name filled in. No sign-in or email required. Feedback is optional.

How to use JWT Decoder

  1. 1Paste your raw JSON Web Token (JWT) into the input box.
  2. 2The token is decoded client-side without sending it over the network.
  3. 3View the decoded Header and Payload segments color-coded in separate panels.
  4. 4Inspect token metadata such as expiration date, issued at time, and signature status.

About JWT Decoder

What is a JSON Web Token?

A JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWTs can be signed using a secret (with the HMAC algorithm) or a public/private key pair using RSA or ECDSA.

In modern web development, JWTs are most commonly used for authorization and authentication. When a user logs in, the authentication server issues a JWT token. The client then includes this token in subsequent API requests (typically in the Authorization header as a Bearer token), enabling stateless communication.

Structure of a JWT

A JWT consists of three parts separated by dots (.):

  1. Header: Typically consists of two parts: the type of the token (which is JWT) and the signing algorithm being used (such as HS256 or RS256).
  2. Payload: Contains the claims. Claims are statements about an entity (typically, the user) and additional metadata (such as expiration timestamp exp and issuer iss).
  3. Signature: Used to verify that the sender of the JWT is who it claims to be and to ensure that the message wasn't changed along the way. It is created by signing the encoded header, encoded payload, and a secret or key.

Time Claims and Token Validation

Our JWT Decoder automatically parses key time-based claims inside the payload:

  • exp (Expiration Time): The timestamp after which the token must not be accepted for processing.
  • iat (Issued At): The timestamp at which the token was created.
  • nbf (Not Before): The timestamp before which the token must not be accepted.

The tool calculates relative times dynamically (e.g. "Expires in 10 minutes") to help developers debug token expiration windows or timezone discrepancies.

Because your token may contain sensitive payloads (user IDs, emails, roles, or authorization credentials), keeping decoding 100% client-side in the browser prevents security leaks.

Guides and tutorials

Frequently asked questions

Does this tool verify the signature of my JWT?

This tool decodes and displays the token structure. It does not verify signature authenticity, as signature verification requires your application's private key or secret, which should never be uploaded online.

Why are JWT tokens base64url encoded instead of standard base64?

Base64url encoding replaces characters that have special meanings in URLs (like '+' and '/') with safe characters ('-' and '_'), allowing the token to be passed in headers, parameters, or URLs without issues.

Is the data in a JWT encrypted?

By default, no. JWTs are signed to prevent tampering, but the payload is only encoded (not encrypted). Anyone who intercepts the token can decode it. Do not store sensitive info like passwords in a standard JWT.

Have a suggestion for JWT Decoder?Share your feedback ↗