You will meet Base64 in data URLs, email attachments, API tokens and configuration files. It looks scrambled, but it hides nothing.
What it does
Base64 represents binary data using 64 safe characters: A to Z, a to z, 0 to 9, plus and slash, with equals signs as padding. Every three bytes become four characters, so the output is about a third larger than the input.
In the Base64 Encoder/Decoder, “Hello” encodes to SGVsbG8= and decodes back again. Text with non-English characters works too, because it is converted as UTF-8 first: “Hello, 世界” becomes SGVsbG8sIOS4lueVjA==.
Using the tool
- Choose encode or decode.
- Paste your text, then convert.
- Copy or download the result.
When decoding, the input must be valid Base64 and must decode to valid UTF-8 text. Otherwise the tool says so. Decoding a binary file, such as an image, will not give readable text; use the image to Base64 tool for pictures.
It is not encryption
Base64 offers no secrecy at all. Anyone can decode it in a second, so never use it to protect a password or private data. If you see credentials “hidden” in Base64, treat them as exposed.
Where it is useful
- Embedding small images directly in HTML or CSS as data URLs.
- Sending binary data through systems that only accept text, such as JSON.
- Reading the parts of a token or an email header.
Frequently asked questions
What do the equals signs at the end mean?
They are padding that makes the length a multiple of four. One or two may appear, or none.
What is the difference between Base64 and Base32?
Base32 uses a smaller alphabet that is easier to read aloud and avoids case problems, at the cost of longer output. See Base64 vs Base32.