Riley Chen

Why I built this

I've spent years building web apps — REST APIs, front-ends, data pipelines. Base64 comes up constantly: embedding a small image in a JSON payload, debugging a data:image/... blob in a network log, shipping a config file through a text-only channel.

Every time, I'd open some converter site, paste my data, and worry whether it was being uploaded to a server I don't control. So I built the tool I wanted: everything runs in your browser, your files never leave your device, and it actually handles UTF-8 correctly (most simple converters corrupt Chinese text and emoji).

It's free, it's local, and it respects your privacy. That's the whole product.

Tools on this site

Base64 encode & decode · Image to base64 · Base64 to image · File to base64 · Base64 to file

How it works

No backend. No database. No tracking. Each tool is a static page using the browser's native btoa/atob (wrapped for UTF-8 safety) plus the FileReader API. When you encode an image, the bytes are read and converted entirely in your tab, then discarded when you close the page.