Encode
Turns plain text into Base64. Works with any characters, including emoji and accented letters, because the text is read as UTF-8 first.
HelloAfterSGVsbG8=Convert text to Base64 and back in one place. Pick a direction, type or paste your text, and click Encode or Decode to see the result. It handles emoji and accented characters, and everything runs in your browser so your text stays on your device.
Base64 rewrites any text or data using only 64 plain text characters. It is the standard way to carry content through systems that expect plain text, like email attachments, data URLs, and JSON fields. This tool encodes your text to Base64 or decodes it back with one click. It is an encoding, not encryption, so anyone can decode it. Use it to move and store data as plain text, not to keep it secret.
Turns plain text into Base64. Works with any characters, including emoji and accented letters, because the text is read as UTF-8 first.
HelloAfterSGVsbG8=Turns Base64 back into plain text. Extra spaces and line breaks are ignored, and both standard and URL-safe Base64 are accepted.
SGVsbG8=AfterHelloSwaps the + and / characters for - and _ and drops the trailing = padding, so the result is safe to drop into a URL or filename.
a?b>cAfterYT9iPmMBreaks long output into 76-character lines. This matches the MIME format used in email headers and PEM files. Leave it off for a single unbroken string.
long input...After76 chars↵
per lineBase64 reads your data 3 bytes at a time. Those 24 bits are split into four groups of 6 bits, and each group becomes one of 64 characters: A to Z, a to z, 0 to 9, + and /. So every 3 bytes of input become 4 characters of output.
| Input | Base64 | Why |
|---|---|---|
Man | TWFu | 3 bytes become exactly 4 characters |
Ma | TWE= | 2 bytes, so one = is added as padding |
M | TQ== | 1 byte, so two = signs are added |
Because 3 bytes turn into 4 characters, Base64 is about 33% larger than the original. A 300 KB image becomes about 400 KB of text. That is fine for small icons and tokens, but it is why large files are better sent as normal files.
Anyone can decode Base64 with a tool like this one, in one click and with no key. It hides nothing. Never use it to protect passwords, API keys, or personal data.
This matters in places where Base64 looks like a secret. A Basic Auth header or a JWT is only Base64, so anyone who sees it can read what is inside. Keep them private and only send them over HTTPS.
Base64 comes up whenever data needs to travel or be stored as plain text. Here are the most common reasons people encode and decode it: