Security & Encoding

Encode, decode, and inspect Base64 strings, percent-encoded URLs, and JWT tokens, all processed locally with nothing sent to a server.

JWT Debugger

Decode and inspect JSON Web Tokens locally.

Base64 Encoder

Convert plain text or binary into Base64 format.

Base64 Decoder

Decode Base64 strings back into original data.

URL Encoder

Encode URI components safely for web transport.

URL Decoder

Decode percent-encoded strings back to plain text.

About Security & Encoding

Underneath most web traffic is a handful of encoding schemes doing quiet, unglamorous work: turning binary data into text-safe strings, making special characters safe inside a URL, and packaging authentication claims into a portable token. This category is where you decode and inspect that traffic instead of guessing at it.

Base64 Encoder and Base64 Decoder handle the conversion between raw text or binary data and the ASCII-safe string format used in email attachments, embedded images, and API payloads that can't carry binary directly — encode when you need to send something, decode when you've received something and need to see what's actually inside it. URL Encoder and URL Decoder do the equivalent job for query parameters and path segments, converting reserved characters like spaces and ampersands into their percent-encoded form and back, which matters the moment a URL breaks because of an unescaped character.

The JWT Debugger is the odd one out in the best way: instead of a reversible encoding, it decodes the header and payload of a JSON Web Token so you can read the claims — user ID, expiry, scopes — that your authentication system is actually sending. Because a JWT payload usually contains real user data, this is the one tool in the category where privacy matters most: everything decodes in your browser's memory, never on a server that could log it.