Base64 Encoder & Decoder — UTF-8 Safe

Base64 Is Not Encryption

Base64 is a way to write any bytes using only 64 safe printable characters: A–Z, a–z, 0–9, plus, slash, and padding equals signs. It exists because some channels — email bodies, JSON fields, HTTP headers, data URIs — were built to carry text only. Base64 lets you encode arbitrary data so it survives those channels intact, with no transformation.

It is not encryption. Anyone can decode base64 in seconds, with no key. Storing a password, API key, or secret in base64 in a config file, .env, or URL hides it from zero people. If you need secrecy, encrypt first—then base64 the ciphertext if the channel demands it.

It is not compression. Base64 makes data larger, not smaller. Every 3 input bytes become 4 base64 characters — a 33% size increase. Use it only when you must, and only because the channel requires text.

UTF-8 Works, Even with Emoji and Accents

The browser's built-in btoa() fails on any character outside Latin-1: emoji, accented letters, Arabic, Hindi, Chinese text. Most online base64 tools break the moment you paste them.

This encoder uses the UTF-8 workaround: it converts your input to percent-encoded UTF-8, encodes that safely with base64, then reverses it on decode. So you can encode "résumé", "你好", "مرحبا", "🎉" without errors. On decode, you get the original text back exactly.

If a base64 string came from a UTF-8-aware encoder elsewhere, this decoder will read it. If it came from naive btoa(), it may have been mangled or may fail—but the error message will tell you so.

How to Use It

Paste text in the left panel, pick Encode. The right side shows the base64 output; click Copy to grab it. To reverse, paste base64 in the right panel, pick Decode, and the left panel shows the original. Use Swap ↔ to flip modes and re-use the output from your last operation.

If you paste invalid base64 to decode, you'll see a clear error message. This tool runs entirely in your browser—no server upload, no privacy concerns.

When Base64 Matters in Development

Base64 is standard for embedding images in HTML or CSS as data: URIs, for encoding binary attachments in email, for the Authorization header in HTTP Basic authentication (which is exactly why Basic auth needs HTTPS — the credentials are encoded, not protected), and for packing data into URLs or headers. You'll encounter it constantly in web development.

If you need to inspect what's hidden in a base64 string—verifying a JWT payload, checking a data URL, or preparing binary for a REST API—this tool decodes it instantly. For related tools, see the URL encoder and JWT decoder.

Limitation: This tool uses standard base64 (with +, /, and =). It does not yet support URL-safe base64 (which uses - and _). For most use cases, standard base64 is correct.