Build and inspect Authorization headers — Basic, Bearer, API key — with JWTs decoded, never verified, and base64 shown for the encoding it is.
Waiting for a header
Nothing is transmitted, logged or stored.
Waiting for a header
Paste an Authorization header value.
Authorization Header Tool runs entirely on your device — no token, password or key is ever uploaded, logged or stored.
You’re on the Free plan. Compare plans
Two ideas are kept apart here, and keeping them apart is the whole value of the tool. Decoding a token tells you what it says. Verifying it tells you whether to believe it. This tool decodes. It never verifies, and it never describes a token as valid because it parsed.
A JWT that comes apart cleanly gets its header and payload shown, its claims explained, and its expiry read against the clock — alongside a standing note that none of that is verification. A token signed with a key nobody holds decodes exactly as well as a genuine one, which is the point.
`alg: none` is called out specifically. A token claiming to need no signature is accepted by any verifier that honours the header, which was a real and widespread vulnerability. The fix is for your verifier to name the algorithms it accepts rather than trusting the token to say.
Basic authentication is shown for what it is: base64 of `username:password`, reversible by anyone who sees it, encoding and not encryption. The tool decodes it in one step precisely so that this is obvious, and says that Basic is acceptable over TLS and never acceptable in a URL, a log or a repository.
Nothing is uploaded, logged or written to browser storage. No token, password or key you type here leaves the page.
No, and it never says a token is valid. Verification needs the signing key and is a different operation. A forged token decodes exactly as cleanly as a real one, which is why decoding proves nothing.
It claims the token needs no signature. A verifier that honours the header accepts anything a caller invents. Current libraries reject it by default, and your verification should name the algorithms you accept rather than reading them from the token.
No. It is base64 of `username:password` — an encoding, reversible by anyone who sees the header. It is acceptable over TLS and never acceptable in a URL, a log file or a repository.
HS256 is symmetric: the same secret signs and verifies, so everyone who can verify can also forge. Where tokens cross a trust boundary, an asymmetric algorithm lets verifiers hold only a public key.
No. It is decoded in your browser, never logged, and never written to browser storage. Nothing you paste here leaves the page.