Base64
Encode and decode Base64 with full Unicode (UTF-8) support and URL-safe variant. Everything runs in your browser.
About this tool
Base64 is a text encoding that represents arbitrary bytes using 64 printable ASCII characters. It’s commonly used to embed binary data in JSON, HTTP headers, data URIs, email (MIME), and config files.
Use standard Base64 when your target accepts +,
/, and = padding — most common case. Use
URL-safe Base64 when the output goes into a URL or
filename, where + and / would need additional
escaping.
This encoder handles Unicode correctly by first converting your input to UTF-8 bytes and then encoding those bytes. Decoders do the reverse. If you paste Base64 that was produced by a non-UTF-8 encoder, the decoded text may contain replacement characters.
Frequently asked questions
Is my input sent to your servers?
No. Encoding and decoding run entirely in your browser. The text or file you provide never leaves your device.
What is the difference between standard and URL-safe Base64?
Standard Base64 uses + / and trailing = padding, which conflict with URL query-string and path syntax. URL-safe Base64 (RFC 4648 §5) substitutes - for + and _ for /, and typically omits padding.
How is Unicode handled?
Strings are first encoded to UTF-8 bytes, then those bytes are Base64-encoded. For example, "日本語" encodes to "5pel5pys6Kqe". Decoding reverses the process with UTF-8 decoding.
Can I Base64-encode a file?
Not yet in this tool — we are focused on text. For file Base64, use a CLI tool like `base64 file.bin` or a dedicated file encoder. The Base64 output of a large file is typically not useful to read in a browser.
Is Base64 encryption?
No. Base64 is an encoding, not encryption. Anyone can decode it. Never use Base64 alone to "hide" secrets.