Encode, decode, hash, cipher and inspect. All 13 tools below run locally in your browser — nothing is uploaded.
Encoding is how data survives a trip through something that would otherwise mangle it — a URL, an HTTP header, an HTML page, a text-only transport. These tools do that translation in both directions, plus the one-way transformations (hashing) that verify data rather than move it.
Everything here runs on your own machine, which matters more in this category than any other: pasting a JWT, an API token or a password hash into a website that posts it to a backend means handing over the credential itself. Nothing you paste leaves the page.
Yes. The token is parsed in JavaScript on your device and never transmitted — you can disconnect from the network and it still works. That is not true of most online JWT decoders, which send the token to a server.
Encoding is reversible — Base64, URL and hex all convert back to the original. Hashing is one-way: SHA-256 produces a fixed-length fingerprint that cannot be turned back into the input, which is why it is used for integrity checks rather than storage.
Yes. The encoder is UTF-8 safe, so accented characters, emoji and non-Latin scripts round-trip correctly instead of breaking on the way through.