Decode JWTs, encode/decode Base64 and URLs, generate SHA hashes and UUIDs. A fast developer encoder toolbox that runs client-side.
Pick the operation you need — Base64 encode or decode, URL encode or decode, SHA hashing, UUID generation or JWT decoding — paste your input, and the result appears instantly. Each tool works both ways where it makes sense, so you can encode a value and decode it back to confirm the round trip.
Copy the output with one click. Because the tools are grouped together, you can move a value through several steps — for example decode a token, then hash a field from it — without leaving the page.
Developers constantly bump into encoded values: Base64 blobs in config, percent-encoded URLs in logs, hashes in checksums, JWTs in auth headers. Decoding them by hand is tedious and error-prone. Having the common encoders in one place turns a five-minute detour into a quick paste-and-read.
Doing this in the browser also keeps sensitive values — tokens, secrets, personal identifiers — off third-party servers, which matters when you are debugging real credentials.
Each encoder uses standard browser APIs: btoa/atob for Base64, encodeURIComponent for URLs, and the Web Crypto API for SHA hashes and random UUIDs. JWTs are split on their dots and Base64URL-decoded to reveal the header and payload. None of these operations contact a server.
That means whatever you paste — including secrets — is processed entirely on your device and never transmitted.
No. Base64 is an encoding, not encryption. It makes binary data safe to transmit as text but provides no security on its own.
Yes. SHA hashes use the browser's Web Crypto API, so your input never leaves your device.
Yes. Paste a token to read its header and payload; a dedicated JWT decoder is also available for that alone.
They are random version 4 UUIDs from a cryptographic source, so collisions are astronomically unlikely.