Runs locally in your browser. Nothing you enter is uploaded to our servers.
Tips for Base64 encoding
Use Base64 for transport/storage of binary, not for secrecy.
Prefer URL-safe Base64 when putting data in query strings.
Encoding increases size by roughly one third.
Confirm the consumer expects standard or URL-safe alphabet.
Avoid encoding secrets thinking they are hidden.
Bytes to Base64 for transport
Processing stays in your browser — your input is not uploaded to our servers.
Encoding to Base64 makes binary safe for JSON, email, and URLs that expect ASCII. It expands size by about a third.
Pick the standard or URL-safe alphabet to match whatever will decode the string later.
Encode Base64
Enter the source text
Plain text is encoded as UTF-8 bytes unless you are pasting an already-binary dump.
Encode
Copy the full string including padding if the receiver is strict.
Use the matching decoder
URL-safe output will not round-trip in a decoder that only accepts `+/`.
Base64 encode FAQ
Will encoding hide a password?
No. Encoding is reversible without a key. Use a password manager and HTTPS, not Base64.
Why is the output longer?
Every 3 bytes become 4 characters. That overhead is expected.
Is encoding local?
Yes. Nothing is uploaded.