Base64
Convert text to Base64 and back. Accents and emoji work: we always go through UTF-8, which is exactly where hastily built tools break.
Your text stays on your device: nothing is uploaded
Result
Paste something on the left: the result appears as you type.
How it works
Base64 exists to carry bytes through places that expect text — inside an email, in a URL, in a config file. The browser’s own functions (btoa and atob) work on single bytes and fail on any character outside the English alphabet: btoa("perché") throws. Here the text is converted to UTF-8 bytes first, which is what any serious program does, so an “é” survives the trip. When decoding we accept both alphabets without asking which one it is, because someone pasting part of a JWT often does not know, and we ignore line breaks, because email Base64 is split into lines. If the decoded bytes are not valid text we tell you, instead of showing a row of question marks and pretending it worked.
What you paste is never uploaded. Anywhere.
Not to a server of ours, not to a third party, never. The text you type stays in your browser’s memory: it is read, processed and shown here, and you copy it. There is no path that takes it elsewhere, because there is no server to send it to. You can paste something confidential.
- Processed locallyThe computation happens on this page, using the browser’s own engine: no request goes out while you type.
- Nothing to upload, nothing to wait forOther services send your file to a server and then send it back to you. Here the file never leaves: there is no upload to wait for.
- No accountNo sign-up, no email, no daily limits to get around by paying.
- Nothing to deleteOthers promise to delete what you paste after an hour. We have nothing to delete: it never reached us.