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.
THE TOOLBOX / SECURITY & AUTHENTICATION
Decode JWT headers, payloads, and exp/iat/nbf timestamps instantly with zero network requests—auto-strips Bearer prefixes and highlights expiration status.
Paste a compact 3-part JWT below. Leading Bearer prefixes are stripped automatically.
169 / 100,000 UTF-16 code units · 169 UTF-8 bytes
{
"alg": "none",
"typ": "JWT"
}{
"iss": "example-auth",
"sub": "fictional-user-42",
"aud": "demo-api",
"iat": 1700000000,
"exp": 1900000000
}(empty signature — unsigned token)
RFC 7519 REFERENCE
| Claim | RFC 7519 Name | Format | Purpose |
|---|---|---|---|
| iss / sub | Issuer / Subject | String or URI | Identifies who issued the token and which user it belongs to |
| aud | Audience | String or String[] | Target API or service allowed to accept the token |
| exp / nbf | Expiration / Not Before | Unix seconds | Exact validity window in UTC epoch seconds |
| iat / jti | Issued At / JWT ID | Unix s / String | Issuance timestamp and unique replay-prevention ID |
Base64URL is encoding, not encryption. Always verify the cryptographic signature on your backend against a pinned algorithm allow-list before trusting any claim.
Passing Date.now() (13 digits) instead of Math.floor(Date.now() / 1000) (10 digits) pushes expiration thousands of years into the future.
Never paste live production Bearer tokens into server-backed decoders. Everything here executes strictly inside your local browser tab.
Convert Unix epochs in Timestamp Converter, format JSON payloads in JSON Formatter, or compare token payloads in Diff Checker.
Yes. All Base64URL decoding, claim inspection, and timestamp conversions run 100% locally inside your browser. Zero tokens or headers ever leave your device.
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.
No. The decoder automatically strips leading "Authorization: Bearer " or "Bearer " prefixes so you can paste directly from DevTools or curl headers.
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.
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.
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.