The text-and-file gap beside the numeric base converter and the image tool: encode text to Base64 and back with multi-byte characters intact — conversion always runs through UTF-8 bytes, never btoa on raw code units, the classic mojibake mistake the help copy explains. Toggle the URL-safe alphabet (-_ for +/) and padding; decoding tolerates whitespace and line breaks, accepts both alphabets, and names the offending character and position when the input is not Base64. A small local file (up to 10 MB) encodes to a Base64 string or a data: URI, and a Base64 string decodes to a downloadable file — with the caution that the declared content type is not verified against the bytes.
| Data acquired | None. |
|---|---|
| Libraries used | Lit 3 — bundled into the tool file itself. |
| Data stored | None. Files are read in memory only and never uploaded or stored. |
| Data transmitted | None. |