JWT Decoder/ Client-side

Instantly decode JWT header and payload, view expiry and standard claims. Token never leaves your browser.

JWT Token

Paste a JWT token above to decode it.

Token never leaves your browser.

Did this tool solve your problem?

What is a JWT

A JWT (JSON Web Token) is a compact, URL-safe token format with three parts: Header (algorithm info), Payload (claims/data), and Signature. Commonly used for authentication — the server issues a JWT, the client includes it in requests, and the server verifies the signature without database lookups.

JWT security considerations

Never store sensitive data (passwords, credit cards) in JWT payloads — they're just Base64-encoded and readable by anyone. The signature only ensures data integrity, not confidentiality. Always use HTTPS, set reasonable expiration times (15 minutes to 1 hour recommended), and implement refresh token rotation.

Code Examples

JavaScript (jsonwebtoken)
import jwt from 'jsonwebtoken';

// Sign
const token = jwt.sign(
  { sub: 'user_123', role: 'admin' },
  process.env.JWT_SECRET,
  { expiresIn: '1h' }
);

// Verify
const payload = jwt.verify(
  token, process.env.JWT_SECRET
);
Python (PyJWT)
import jwt

# Sign
token = jwt.encode(
    {"sub": "user_123", "exp": exp_ts},
    secret,
    algorithm="HS256"
)

# Verify
payload = jwt.decode(
    token, secret,
    algorithms=["HS256"]
)
Go (golang-jwt)
import "github.com/golang-jwt/jwt/v5"

// Sign
token := jwt.NewWithClaims(
  jwt.SigningMethodHS256,
  jwt.MapClaims{"sub": "user_123"},
)
signed, _ := token.SignedString(secret)

// Verify
parsed, _ := jwt.Parse(signed,
  func(t *jwt.Token) (any, error) {
    return secret, nil
  })
Decode only (any language)
// JWT = base64url(header)
//       + "."
//       + base64url(payload)
//       + "."
//       + signature

function decodeJwt(token) {
  const [h, p] = token.split('.');
  const decode = s => JSON.parse(
    atob(s.replace(/-/g,'+')
          .replace(/_/g,'/'))
  );
  return { header: decode(h),
           payload: decode(p) };
}

Frequently Asked Questions

What is a JWT?
JWT (JSON Web Token) is an open standard (RFC 7519) for securely transmitting information as a JSON object. It consists of three Base64URL-encoded parts separated by dots: Header (algorithm & token type), Payload (claims), and Signature.
Can a JWT be forged?
The payload is only Base64URL-encoded — anyone can decode and read it. However, the signature cannot be forged without the secret key. JWT security relies entirely on signature verification; sensitive data should not be stored in the payload unless you use JWE (encrypted JWT).
What are exp, iat, and nbf?
These are standard JWT claims: exp (Expiration Time) is when the token expires; iat (Issued At) is when it was issued; nbf (Not Before) means the token is invalid before that time. All timestamps are Unix time (seconds since epoch).
Why can't signature verification be done in the browser?
Verification requires the secret key (for HMAC algorithms) or public key (for RSA/ECDSA). In a pure frontend context, these keys are typically unavailable. Signature verification should always be performed server-side in production.
What's the difference between HS256 and RS256?
HS256 (HMAC-SHA256) uses a single shared secret for both signing and verification — suitable for single-service setups. RS256 (RSA-SHA256) uses a private key to sign and a public key to verify — better for microservices where the public key can be distributed safely.
Is my token safe to paste here?
Yes. This tool runs entirely in your browser with no network requests — your token never leaves your device. That said, for production tokens containing sensitive claims, exercise caution and rotate them if you suspect exposure.