How to Encode and Decode Base64

Base64 shows up the moment binary data has to travel through a text-only channel. Email attachments, data URLs, API tokens, and config files all use it to carry bytes as safe, printable characters. Encoding turns data into a Base64 string; decoding turns it back. This guide explains what Base64 actually is, why it exists, and the misconception that gets people into trouble.

What Base64 is

Base64 is an *encoding* — a reversible way of representing binary data using 64 printable characters (A–Z, a–z, 0–9, plus two symbols). It takes arbitrary bytes and makes them safe to put anywhere text is allowed. That is its entire purpose: moving binary through systems built for text.

How to encode or decode with this tool

1. Open the Base64 Encoder/Decoder tool.
2. Paste text or Base64.
3. Choose encode or decode.
4. Copy the result.

Everything runs in your browser, so your data — which may include tokens — is never uploaded.

Why Base64 exists

Some channels only reliably handle plain text. Email was designed for text; certain config formats and URLs choke on raw binary or special characters. Base64 solves this by re-expressing binary data in a limited, universally safe character set, so an image, a file, or binary credentials can ride through unharmed. On the other side, decoding restores the original bytes exactly — it is lossless.

The misconception that matters: encoding is not encryption

This is the single most important thing to understand, and it catches people constantly. Base64 provides zero security. Anyone can decode a Base64 string instantly — it is not a password, not a cipher, not protection of any kind. The consequences:

• Never treat Base64 as hiding anything. A "Base64-encoded password" in a config is effectively plain text to anyone who sees it.
• A JWT's readable parts are Base64, not encrypted — which is why you should never put secrets in a token payload. See JWT Decoder.
• Use real encryption for real secrecy. To actually protect data, encrypt it — for example with Encrypt File — not encode it.

Base64 makes data *portable*, never *private*.

Common uses

• Decode a Base64 blob from a config, header, or API response.
• Encode data to embed in a URL or JSON.
• Inspect a token's encoded segments.
• Move binary through a text-only channel.

Related tools

For images specifically, Image to Base64 and Base64 to Image handle the picture case with a preview. For URL-safe escaping of text, URL Encoder/Decoder is the related tool.

Privacy and limits

Encoding and decoding are fully local — no upload, nothing stored, offline once loaded. Open the Base64 Encoder/Decoder tool to convert data to and from text.