Made for email
Base64 landed in the early ’90s for MIME email so binary attachments could survive 7-bit mail relays without mangling.
Tip: Ctrl/Cmd + K focuses the input. Ctrl/Cmd + Enter repeats last action.
Understands raw Base64 or data:[mime];base64,....
Base64 is an encoding that turns arbitrary binary data into ASCII text. It’s commonly used in email (MIME), data URLs (e.g., embedding small images), JSON/API payloads, and anywhere binary needs to travel over text-only channels.
URL-safe Base64 follows RFC 4648: it replaces + with - and / with _
so the string can appear in URLs and filenames without escaping. Some systems also drop the trailing = padding.
No. All encoding/decoding happens locally in your browser. If you use file features, files are processed in-memory; nothing is sent to a server.
=?= characters are padding so the output length is a multiple of 4 characters. Many parsers accept
unpadded Base64, but some require padding—use the “Omit padding” toggle only if your target system allows it.
Encoding (Base64) is reversible and not a security measure—it just re-formats data. Encryption protects data and requires keys. Don’t use Base64 for secrecy.
Yes. The tool uses UTF-8 via TextEncoder/TextDecoder, so Unicode text (e.g., emojis, CJK) round-trips correctly.
Use the file picker or drag-and-drop. “File → Base64” produces the Base64 payload (suitable for data URIs or JSON). To recover a file, paste its Base64, then click “Base64 → File” to download.
Some legacy encoders wrap lines at 76 characters (MIME). This tool doesn’t insert line breaks. If your input has them, it will still decode successfully.
There’s no fixed limit, but browser memory is finite. Very large files (hundreds of MB) may be slow or fail. For huge data, prefer streaming or server-side tooling.
Prepend the MIME type and the base64 flag, e.g. data:image/png;base64,AAAA….
You can get the MIME type from the selected file when using the file encoder.
Strict mode rejects characters outside the Base64 alphabet. Enable “URL-safe” if your input uses - and _,
or disable strict validation to attempt a best-effort decode.
Base64 landed in the early ’90s for MIME email so binary attachments could survive 7-bit mail relays without mangling.
Each 24-bit chunk splits into four 6-bit values. Those map to 64 symbols; padding just fills the final quartet.
RFC 4648 replaces +// with -/_ so Base64 can live in URLs and filenames without escaping.
Base64 is reversible formatting, not security. Anyone can decode it with one line—use real encryption for secrecy.
data: URLs store the MIME type plus Base64 so tiny images or fonts ride inside HTML/CSS with zero extra requests.