Runs entirely on your device — nothing is uploaded, logged or stored. Safe for config blobs, tokens and certificates.
Text Input
No file chosen
Base64 Output
Runs on your deviceWorks offlineUTF-8 safe
No watermark, no account, no limits
Free foreverNo sign upNothing uploaded
Decode a Base64 string back to text, or encode text and files into Base64. Both directions, in your browser, instantly.
Runs entirely on your device — nothing is uploaded, logged or stored. Safe for config blobs, tokens and certificates.
Text Input
Base64 Output
Runs on your deviceWorks offlineUTF-8 safe
No account. No rate limit. No "sign in to copy your result."
Paste it, read it, move on. Three things this handles that a console one-liner doesn't.
Decode a string back to text, or encode text the other way. One toggle, same box — no hunting for a second tool when you guess the direction wrong.
Paste data:image/png;base64,… whole. The prefix is read for the MIME type and stripped for you, so you never have to hand-trim the string before decoding it.
The encode, the decode and the file read all happen locally. Nothing is uploaded or logged, which is why it's safe to paste a certificate or a config blob.
Three steps, no account, about ten seconds.
Encode turns text or a file into Base64. Decode turns a Base64 string back into readable text.
Paste into the input box, or upload any file — an image, a PDF, a font, a certificate.
Copy it to the clipboard or download it as a text file. Decoded images preview in place.
The jobs this actually gets used for.
It's an encoding — reversible by anyone in one step, including this page. Never hide a secret in it.
Fair question. Here's the honest version.
Switch to Decode, paste the string into the input box and click Decode from Base64. The plain text appears on the right, ready to copy or download. Whitespace and line breaks in the pasted string are ignored, so a Base64 blob wrapped across many lines works without cleaning it up first.
Switch to Encode, type or paste your text and click Encode to Base64. The encoder is UTF-8 safe, so accented characters, emoji and non-Latin scripts survive the round trip intact — something a naive btoa() call in the console will fail at.
You can paste a full data URI such as data:image/png;base64,iVBORw0… and the prefix is read and stripped for you. What comes back is the raw decoded data, so an SVG will come out as readable markup. A PNG or JPEG is binary rather than text, so it won't display as characters — to view one of those, paste the whole data URI straight into your browser address bar.
Yes. Click Upload file and pick anything — an image, a PDF, a font, a certificate. The file is read in your browser and encoded to Base64, which you can copy or download as a text file. This is how you inline a small asset into CSS, a data URI or a JSON payload.
No, and this matters. Base64 is an encoding, not encryption — anyone can reverse it in one step, exactly as this page does. It exists to move binary data safely through channels that expect text, such as email or JSON. Never use it to hide a password, a token or an API key.
Usually one of three things: it has been URL-encoded, so + became a space or - and _ were swapped in; it is truncated, since valid Base64 length is a multiple of four; or the padding = characters at the end were stripped. Paste the original untouched string and it will normally decode first time.
No. Everything runs in your browser — the encode, the decode and the file read. Nothing is uploaded, logged or stored. You can check it yourself: load the page, turn off your network, and it still works. That's why it's safe to paste a config blob or a certificate here.
There's no limit we impose, only what your browser tab can hold in memory. Strings of a few megabytes are fine. Very large files will make the page sluggish while it works, because Base64 output is about a third larger than the input it came from.
Same rules on every one: free, no sign up, no watermark.
Reference: MDN on Base64 and RFC 4648, the spec itself.