JWT decoder
Paste a JSON Web Token and read it: the header and payload pretty-printed, the registered claims in a table with exp, nbf and iat as dates and an expiry status, warnings for the usual mistakes, and HS256/HS384/HS512 signature verification with a pasted secret. Everything runs in your browser — nothing is sent anywhere. No account needed.
Decoding happens in your browser; nothing is sent to Nodlume. The token is not put in the URL, stored, or reported to analytics.
nodlume-demo-secret so you can try verification too.Nothing leaves the tab
Decoding is base64url and JSON in page memory; verification is WebCrypto's HMAC in the same tab. The token is never put in the URL, stored, or sent to analytics — there is deliberately no share link for a decode.
Dates you can read
Every NumericDate becomes an ISO timestamp and a relative time against your clock, so “expired three hours ago” is visible without arithmetic. Milliseconds where seconds belong, a missing exp, an expiry a year out and alg: none are all called out.
Honest about signatures
HMAC tokens verify against a secret, with a constant-time compare. RS, PS, ES and EdDSA tokens need the issuer's public key, so the tool names the algorithm and stops rather than inviting a private key into a web page.
JSON Web Tokens, answered
- Is it safe to paste a token here?
- The page decodes and verifies entirely in your browser: the token is held in the page's memory only, never sent to Nodlume, never put in the URL, never stored, and never reported to analytics. Even so, a token is a bearer credential — whoever holds it is you, to the server that issued it — so treat a production token the way you would a password: prefer a test token, and if you must inspect a live one, consider it compromised once it has been pasted into any tool you do not control.
- What are the header, payload and signature?
- A JWT is three base64url segments joined by dots. The header is a small JSON object naming the signing algorithm (alg) and usually a type (typ) or key id (kid). The payload is the claims: who issued the token (iss), who it is for (aud), who it is about (sub), when it expires (exp), plus whatever the issuer adds. The signature is a MAC or digital signature over the first two segments, which is what lets a server detect a token that was altered after issue.
- What does exp mean, and why is it a number?
- exp is the expiry, and like nbf (not before) and iat (issued at) it is a NumericDate — seconds since the Unix epoch, 1 January 1970 UTC, not milliseconds. 1700000000 is November 2023. This tool renders each one as an ISO timestamp and as a relative time, and reports the token as not expired, expired, or not yet valid from exp and nbf against your clock. A value in the trillions is almost always milliseconds by mistake, and the tool says so.
- Why does decoding not prove a token is valid?
- Because base64url is an encoding, not encryption or authentication: anyone can decode a JWT, and anyone can write one. A token is only trustworthy when its signature verifies against the issuer's key AND its claims pass — exp has not passed, nbf has, aud names the server checking it, and iss is the expected issuer. Decoding shows you what a token claims; verification is what makes the claim worth anything.
- What is alg "none"?
- An unsigned token: the header declares alg: "none" and the signature segment is empty. The spec allows it for contexts where integrity is guaranteed another way, but in practice it is a classic attack — strip the signature, set alg to none, and hope the verifier accepts whatever the header says. The tool flags it, refuses to "verify" it, and a server should reject it outright by pinning the algorithms it accepts.
- Can this verify RS256 or ES256 tokens?
- No, on purpose. RS256, PS256, ES256 and EdDSA tokens are signed with the issuer's private key and verified with the matching public key, usually published at the issuer's JWKS URL. There is nothing sensible to paste into a secret box for them — a private key certainly should not be — so the tool names the algorithm, explains the difference and stops. HS256, HS384 and HS512 are HMACs over a shared secret, which is a check that can honestly run here.
- Where do I get the secret or the public key?
- The HMAC secret is whatever your server signs with — a JWT_SECRET environment variable, the signing key in your auth library's config, or the value a provider shows in its dashboard (some providers give it base64-encoded; there is a checkbox for that). Public keys for RS/ES tokens come from the issuer's JWKS endpoint, often at /.well-known/jwks.json, keyed by the header's kid. Neither is in the token itself, which is the whole point.
Where the token goes next
A token is one line of an auth design: who issues it, which routes require it, and which roles its claims map to. In the Nodlume workspace the Structure Painter paints auth guards onto a route tree and the generated project carries the session chain for them; the Zod schema builder types the claims a route handler reads, and the MCP server generator scaffolds a server whose tools can be put behind a bearer token like this one.