Convert text to Base64 or turn Base64 back into readable text. UTF-8 is handled properly, so accented letters, Devanagari and emoji all survive the round trip.
Base64 turns arbitrary bytes into 64 printable characters so the result can travel through channels that only tolerate text — an email header, a JSON field, a data URI, a basic-auth credential. It expands data by roughly a third, which is the cost of that portability.
The conversion uses the browser's native btoa and atob. Because those two only accept one byte per character, the page encodes your input to UTF-8 first and decodes the bytes back afterwards. That is what stops café from turning into mojibake.
data: URI for a small image or font.Authorization: Basic header value.There is no key and no secrecy. coodeverse and Y29vZGV2ZXJzZQ== carry identical information. If you need confidentiality you still need real encryption on top; if you need compactness, Base64 makes things bigger rather than smaller.
The other common trap is padding. Standard Base64 pads to a multiple of four with =. Strip the padding and a strict decoder will reject it, so only remove it when the consumer expects the URL-safe form.
Standard Base64 uses + and /. In a query string or a path segment those characters need percent-escaping, and some servers mangle them. The URL-safe variant, defined in RFC 4648, swaps them for - and _ and drops the padding. The decoder here accepts both alphabets, so anything produced with the checkbox on will still decode with it off.
No. It is a reversible encoding with no key. Anyone can decode it.
Yes. UTF-8 encoding happens before conversion, so accents, Devanagari and emoji round-trip intact.
Hyphen and underscore instead of plus and slash, with no padding. It survives URLs unescaped.
No. It never leaves the page.