How to Fix 'Failed to execute btoa on Window: character outside Latin1 range'

Why window.btoa Fails on Modern Strings

The name `btoa` stands for "binary to ASCII". Developed in early browser eras, the function assumes that every character in the provided string occupies exactly 1 byte (8 bits, representing the **Latin-1 / ISO-8859-1** character set).

However, modern JavaScript strings use **UTF-16 encoding**. When you pass characters with code points above 255—such as emojis (🚀), em-dashes (—), or non-Latin alphabets (e.g., Chinese, Arabic, Cyrillic)—`btoa` cannot fit the multi-byte code units into Latin-1 bytes and throws: ```text Uncaught DOMException: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range. ```

The Modern, Standards-Compliant Solution Use the standardized **TextEncoder API** to encode the string into an array of UTF-8 bytes, then convert those bytes into a Base64 string:

function utf8ToBase64(str) {
  const bytes = new TextEncoder().encode(str);
  const binString = Array.from(bytes, (byte) => String.fromCharCode(byte)).join("");
  return btoa(binString);

function base64ToUtf8(base64) { const binString = atob(base64); const bytes = Uint8Array.from(binString, (m) => m.charCodeAt(0)); return new TextDecoder().decode(bytes); }

// Example: const encoded = utf8ToBase64("Hello 🌍! Mickytool makes dev tools."); console.log(encoded); // "SGVsbG8g8J+MjfCfkJkhIE1pY2t5dG9vbCBtYWtlcyBkZXYgdG9vbHMu" console.log(base64ToUtf8(encoded)); // Restored with emoji intact! ```

Avoid encoding errors by formatting and validating your Unicode strings in Mickytool's **Base64 Encoder / Decoder**, which handles multi-byte UTF-8 streams out of the box.