Utilore

Base64 Encode and Decode

Paste text to get Base64, or paste Base64 to get the text back. Cyrillic, Chinese and emoji all survive the trip — the string is read as UTF-8, not as bytes of one language.

How to use

Good to know

Why Base64 exists at all

Some channels only carry plain text: email headers, JSON fields, URLs, configuration files. Base64 turns any bytes into 64 safe characters so they pass through untouched. The price is size — the result is about a third larger than the original.

Two alphabets, one standard

The classic alphabet uses + and /, which have their own meaning inside a URL. The URL-safe variant replaces them with - and _ and drops the padding, so a token stays intact in a link. Decoding here accepts both without asking.

Frequently asked questions

Is Base64 encryption?

No. It is a way of writing bytes as text, and anyone can decode it in a second. Never use it to hide a password.

Is my text sent anywhere?

No. Encoding and decoding happen in your browser — safe for tokens and private data.

Why does my Cyrillic break in other tools?

Because they call btoa on the raw string, and it only understands single-byte characters. Here the text is converted to UTF-8 first, so any alphabet works.

How large a file can I encode?

Up to 5 MB. Larger files make a string the browser struggles to display, not just to compute.

Related tools