Base64 Encode

Encode any text to Base64 — full UTF-8 support, with optional URL-safe output.

Encoders & DecodersRuns in your browserFree, no sign-up

Options

URL-safe alphabet

RFC 4648 base64url: - and _ instead of + and /, no padding.

Wrap at (0 = no wrap)

MIME email bodies require wrapping at 76 characters.

Plain text

Base64

Output appears here as you type.

Ctrl + Enter to run

About the Base64 Encode

Base64 represents arbitrary bytes using 64 printable ASCII characters, so binary data can travel through channels that only accept text: a JSON string field, an email body, a data URL. Output is about a third larger than the input, which is the price of the transport safety.

It is an encoding, not encryption. There is no key and decoding is one click, so a Base64 string in a config file or a cookie is plaintext to anyone who looks at it. Text is encoded as UTF-8 here, which is what makes emoji and non-Latin scripts survive a round trip intact.

Frequently asked questions

Does this handle emoji and non-English text?

Yes. This is where most online Base64 encoders break: the browser's built-in btoa() throws an error on any character above U+00FF, so it fails on the first emoji, accented letter or CJK character. This tool encodes the text to UTF-8 bytes first, so any Unicode input works correctly.

Is Base64 encryption?

No, and this matters. Base64 is an encoding, not a cipher — anyone can decode it instantly with no key. It exists to carry binary data through text-only channels, not to hide anything. Never use it to protect a password, token or personal data.

When should I use the URL-safe alphabet?

When the result goes into a URL path, query string or filename. Standard Base64 uses + and /, which have reserved meanings in URLs and would need percent-encoding. base64url (RFC 4648 §5) substitutes - and _ and drops the = padding. JWTs use it for exactly this reason.