Base64 Encode & Decode Online
Encode text into Base64 format or decode Base64 back to plain text. Full Unicode support ensures characters and emojis are processed correctly.
Drag & drop an image here, or click to upload
In digital communications, data must travel across diverse networks, mail transfer agents, and API gateways. Many of these legacy infrastructures were built to transmit 7-bit ASCII text. When binary files—like images, zipped folders, or encrypted payloads—are sent through these channels directly, network devices can misinterpret bytes as control characters, leading to corrupted data. Base64 encoding resolves this by converting any binary stream into a set of 64 standard ASCII characters, guaranteeing safe transit across any network.
The Math Behind Base64
The name Base64 comes from the fact that it uses a 64-character alphabet. This alphabet includes uppercase letters A-Z, lowercase letters a-z, numbers 0-9, and the symbols + and /. During encoding, the engine takes three bytes (24 bits) of data and splits them into four 6-bit chunks. Each 6-bit chunk has a value between 0 and 63. This value is mapped to a character in the Base64 alphabet. Since four characters are used to represent three bytes of data, Base64 increases file size by about 33%.
Solving the Unicode and Emoji Challenge
The native JavaScript functions for Base64, btoa() and atob(), were designed for 8-bit binary strings. If you pass a string containing Unicode characters outside the Latin-1 range (such as emojis or non-English alphabets), the parser throws an exception: "The string to be encoded contains characters outside of the Latin1 range." To prevent this, our encoding engine uses a UTF-8 escape routine. It converts multi-byte characters into percent-encoded bytes, which are then converted into safe binary values before encoding. This ensures that non-English text and emojis are processed correctly.
Worked Example: Unicode Base64 Encoding
Let's look at a text string containing a Unicode emoji: Hello World! 👋. A standard encoder will fail. Our Unicode-safe engine first encodes the emoji to UTF-8 bytes, and then produces the correct Base64 string:
SGVsbG8gV29ybGQhIPCfkYI=
Decoding this string reverses the process, translating the bytes back into the original UTF-8 structure and rendering the text and emoji accurately.
frequently asked questions
Base64 encoding is used to convert binary data (such as images, files, or non-ASCII characters) into a set of 64 safe ASCII characters. This allows binary payloads to be transmitted over text-based networks (like email or JSON APIs) without data corruption from character-set transformations.
Yes, our encoder uses a Unicode-safe conversion method. A standard JavaScript btoa() function throws errors when parsing non-latin characters. Our engine escapes string sequences into UTF-8 prior to Base64 compilation, ensuring emojis and non-English scripts decode correctly.
Base64 groups binary data into blocks of 24 bits, representing them as four 6-bit characters. If the input text is not a multiple of 3 bytes, the final block will have empty spaces. Base64 uses equals signs (=) as padding characters at the end of the string to complete the 4-character block.
Yes, completely. All encoding and decoding actions run within your browser using client-side JavaScript. No data is transmitted to our server, keeping passwords, keys, and tokens safe.
This usually occurs when you try to decode a Base64 string that was originally compiled using a different character encoding (like UTF-16) or when the input string is a binary file (such as a PDF or image) rather than plain text.