Base64 Encoder Decoder
Encode and decode Base64 — text to Base64 and back, both directions.
How to use Base64 Encoder Decoder
- To encode: paste text, get Base64.
- To decode: paste Base64, get the original text.
- Use it for data transport — data URIs, API values, email, config.
- Never for secrecy — Base64 is instantly reversible; it hides nothing.
What is Base64 Encoder Decoder?
A Base64 encoder/decoder converts between text and Base64 — the encoding that represents binary or text data using 64 safe ASCII characters (A–Z, a–z, 0–9, + and /). Encode "Hello" and get "SGVsbG8="; decode it back to "Hello". Both directions, one tool.
Base64's job is making data safe to transport through systems that expect text — it lets binary data (images, files) or awkward characters ride through email, URLs, JSON and config files that would otherwise mangle them. The trade is size: Base64 is ~33% larger than the original, the cost of the safety.
About the Base64 Encoder Decoder
Paste text to encode it to Base64, or paste Base64 to decode it back — in your browser.
Where Base64 appears: data URIs — embedding images directly in HTML/CSS as base64 (our Image to Base64 tool); API tokens and headers — Basic Auth encodes credentials as base64, and many APIs pass base64-encoded values; email attachments — MIME encodes binary attachments as base64 to survive text-only email transport; JWT tokens — the header and payload are base64url-encoded (our JWT Decoder reads them); and config and data storage — embedding binary data in text formats.
The crucial thing to understand: Base64 is encoding, NOT encryption. It provides zero security — anyone can decode base64 instantly (this tool does). It's trivially reversible obfuscation at best. So never use it to "hide" passwords, secrets or sensitive data — base64-encoded credentials in code or config are as exposed as plaintext (Basic Auth's base64 is why it requires HTTPS — the encoding hides nothing, the transport encryption does the protecting). Use it for its real purpose (safe data transport), never for secrecy. This is the same as our Base64 Encode/Decode tools. Everything runs locally; nothing you paste is sent.
Frequently Asked Questions
Learn more
Base64 Explained: What It Is, When to Use It, and When Not To
Base64 shows up in data URIs, JWTs and APIs everywhere. Here is what it actually does — and the one mistake developers keep making with it.
Read the guide