Guide

THE TOOLBOX / SECURITY & AUTHENTICATION

Inspect any JWT,
100% locally in your browser.

Decode JWT headers, payloads, and exp/iat/nbf timestamps instantly with zero network requests—auto-strips Bearer prefixes and highlights expiration status.

Decoded only — not verified. Decoding inspects Base64URL claims locally in your browser; it does not verify signatures, issuers, or audiences.● 100% client-side · zero network requests

Encoded JWT Token

Paste a compact 3-part JWT below. Leading Bearer prefixes are stripped automatically.

169 / 100,000 UTF-16 code units · 169 UTF-8 bytes

eyJhbGciOiJub25lIiwidHlwIjoiSldUIn0.eyJpc3MiOiJleGFtcGxlLWF1dGgiLCJzdWIiOiJmaWN0aW9uYWwtdXNlci00MiIsImF1ZCI6ImRlbW8tYXBpIiwiaWF0IjoxNzAwMDAwMDAwLCJleHAiOjE5MDAwMDAwMDB9.(empty signature)
■ Header■ Payload■ Signature

Decoded Inspection

alg: nonetyp: JWTUnexpired (exp > now)Unsigned (empty sig)

Header UNVERIFIED

{
  "alg": "none",
  "typ": "JWT"
}

Payload UNVERIFIED

{
  "iss": "example-auth",
  "sub": "fictional-user-42",
  "aud": "demo-api",
  "iat": 1700000000,
  "exp": 1900000000
}

Registered Claims LOCAL CLOCK

iss · Issuer
"example-auth"
sub · Subject
"fictional-user-42"
aud · Audience
"demo-api"
exp · Expiration time
2030-03-17T17:46:40.000Z (UTC) · 3/17/2030, 5:46:40 PM (your device time zone)
iat · Issued-at time
2023-11-14T22:13:20.000Z (UTC) · 11/14/2023, 10:13:20 PM (your device time zone)

Signature NOT VERIFIED

(empty signature — unsigned token)

RFC 7519 REFERENCE

Registered JWT claims & common debugging pitfalls.

ClaimRFC 7519 NameFormatPurpose
iss / subIssuer / SubjectString or URIIdentifies who issued the token and which user it belongs to
audAudienceString or String[]Target API or service allowed to accept the token
exp / nbfExpiration / Not BeforeUnix secondsExact validity window in UTC epoch seconds
iat / jtiIssued At / JWT IDUnix s / StringIssuance timestamp and unique replay-prevention ID

1. Decoding Is Not Verification

Base64URL is encoding, not encryption. Always verify the cryptographic signature on your backend against a pinned algorithm allow-list before trusting any claim.

2. Seconds vs. Milliseconds in exp

Passing Date.now() (13 digits) instead of Math.floor(Date.now() / 1000) (10 digits) pushes expiration thousands of years into the future.

3. Zero Token Egress

Never paste live production Bearer tokens into server-backed decoders. Everything here executes strictly inside your local browser tab.

Frequently Asked Questions

Is it safe to paste a JWT into this decoder?

Yes. All Base64URL decoding, claim inspection, and timestamp conversions run 100% locally inside your browser. Zero tokens or headers ever leave your device.

Does decoding a JWT verify its signature?

No. Decoding only reveals the Base64URL-encoded JSON header and payload for debugging. Anyone can craft fake claims, so your backend must always verify the cryptographic signature using a trusted key.

Do I need to remove "Bearer " before pasting my token?

No. The decoder automatically strips leading "Authorization: Bearer " or "Bearer " prefixes so you can paste directly from DevTools or curl headers.

How are exp, iat, and nbf timestamps formatted in JWTs?

Under RFC 7519, NumericDate claims (exp, iat, and nbf) are integer Unix Epoch seconds—not milliseconds. The inspector converts them into readable UTC and local dates and flags whether exp has already passed.

Why does my token have 5 dot-separated parts instead of 3?

A 3-part token (header.payload.signature) is a signed JWS token whose claims are readable via Base64URL. A 5-part token is an encrypted JWE token (RFC 7516) whose payload cannot be read without the private decryption key.

Why is alg: "none" flagged as a warning?

A token with alg: "none" has no cryptographic signature. Production servers must explicitly reject alg: "none" and enforce an allow-list of expected signing algorithms.