Base64 Encode

Base64 represents binary or text data using 64 printable ASCII characters plus padding. It is used to embed data in JSON, data URLs, email attachments and HTML, anywhere raw bytes could be mangled in transit.

No. Base64 is reversible encoding, not encryption. Anyone can decode it straight back to the original text in seconds, so never rely on it to protect passwords, tokens or secrets.

URL-safe mode produces base64url: it replaces the plus sign with a hyphen and the slash with an underscore, then strips the trailing equals-sign padding. That makes the string safe to drop into URLs, filenames and JWT segments without escaping.

Yes. Text is run through a UTF-8 encoder before Base64, so emoji, accents and other multi-byte characters encode correctly. For example cafe with an accented e becomes Y2Fmw6k=, which decodes back to the exact original.

Base64 turns every 3 bytes into 4 characters, so the encoded text is about one third larger than the source, plus a little padding. The character count above the output shows the exact length.

Standard Base64 pads the final group with one or two equals signs so the length is always a multiple of 4. URL-safe mode removes that padding, which is why a URL-safe result can look shorter.

This tool encodes text you type or paste, not uploaded binary files. If you paste the text contents of a file it will encode fine, but picking a binary file such as a PNG is out of scope here.

Run the result through a Base64 decoder to recover the original text. The default output here is standard Base64 that any decoder accepts; for URL-safe output use a decoder that understands base64url.

Yes. Encoding happens entirely in your browser using the built-in encoder, so nothing you type is uploaded to a server and the tool keeps working offline.