Question 1

Does it handle emoji and accented text correctly?

Accepted Answer

Yes. Text is encoded as UTF-8 before Base64, so emoji, accents and non-Latin scripts round-trip perfectly — unlike tools that use raw btoa/atob and corrupt non-ASCII characters.

Question 2

Can I encode and decode files, not just text?

Accepted Answer

Yes — the File tab works both ways. Encode: drop any file to get its Base64 (toggle “data URI” for the data:…;base64, form you can paste into CSS or an <img src>). Decode: paste a Base64 string or a data-URI — or upload a .txt file that contains it, so you don't have to copy huge strings by hand — and download the original file back. We auto-detect the type to suggest a filename (decoded.png, decoded.pdf, decoded.xlsx, …), and you can edit the Output filename to anything you like before downloading, so any format works.

Question 3

What if my Base64 won't decode?

Accepted Answer

We show a clear message rather than failing silently. We also accept URL-safe Base64 (using - and _) and fix missing padding automatically.

Question 4

Are my files or text uploaded?

Accepted Answer

No. Encoding and decoding happen entirely in your browser; nothing leaves your device.

Base64 Encode/Decode

Frequently asked questions

JSON to CSV

JSON Formatter

URL Encode/Decode

Markdown to HTML