Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsatob() decodes Base64 into bytes, but returns those bytes in a JavaScript string rather than decoding them as UTF-8 text. To get text, convert the result to a byte array and pass it to TextDecoder. If the Base64 represents an image or other binary data, keep it as bytes instead.
What atob() actually returns
The browser’s atob() method reverses Base64 encoding, but its output is a so-called binary string: each character, in the range U+0000 through U+00FF, represents one decoded byte. That is not the same as interpreting those bytes as Unicode text. The HTML Living Standard’s Base64 utility methods define the browser behavior, and MDN’s atob() reference explains the byte-string result.
This distinction causes the familiar “garbled text” problem. A character outside the ASCII range is often encoded in UTF-8 using multiple bytes. Displaying those individual byte values as characters does not reconstruct the original Unicode character; UTF-8 decoding is a separate step.
Decode Base64 to UTF-8 text
Convert each character returned by atob() into its byte value, then decode those bytes as UTF-8:
#1 Best Overall
function base64ToBytes(base64) {
const binary = atob(base64);
return Uint8Array.from(binary, (character) => character.codePointAt(0));
}
function base64ToUtf8(base64) {
return new TextDecoder("utf-8").decode(base64ToBytes(base64));
}Use base64ToUtf8(encoded) when the decoded bytes are valid UTF-8 text. The WHATWG Encoding Standard describes UTF-8, while MDN’s Encoding API reference documents decoding bytes to text with TextDecoder.
Keep binary payloads as bytes
Not every Base64 value represents text. If the decoded content is an image, compressed file, or another binary format, do not run it through a text decoder. Use the resulting Uint8Array with the API or file-handling code that expects bytes. Decoding arbitrary binary as UTF-8 can produce replacement characters or text that has no useful meaning.
Rank #2
Padding and invalid input
Base64 uses = as its conventional padding character, but it is inaccurate to say that padding is always required or never required across all decoders. Browser atob() follows the HTML Standard’s forgiving-Base64 decoding algorithm; it can still throw InvalidCharacterError when the input fails that algorithm. Other libraries may enforce different validation rules, so check the behavior of the specific decoder rather than assuming browser and server-side policies match.
Byte-array alternative
Where the target browser supports it, Uint8Array.fromBase64() returns decoded bytes directly, avoiding the intermediate binary string:
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →const bytes = Uint8Array.fromBase64(base64);
const text = new TextDecoder("utf-8").decode(bytes);MDN recommends considering this byte-oriented alternative. Check compatibility for the browsers and runtimes you support before relying on it; the cited documentation does not establish a complete browser-version matrix.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.The inverse pitfall with btoa()
btoa() is not a general-purpose encoder for arbitrary Unicode strings. It treats each input character as one byte and throws when a character exceeds U+00FF. To Base64-encode Unicode text, first encode the text as UTF-8 bytes, then encode those bytes. See MDN’s btoa() reference for the Unicode limitation and byte-conversion guidance.
Quick Recap
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
