Base64 Encode / Decode
Encode plain text to Base64 or decode Base64 back to readable text.
Encode plain text into Base64 format, or decode a Base64 string back into readable text — useful for embedding data in URLs, JSON, or email attachments.
How Base64 Encode / Decode Works
Base64 encoding represents binary data using only 64 printable ASCII characters (A-Z, a-z, 0-9, +, and /), which makes it safe to embed in places that only support plain text, like JSON fields, URLs, or email bodies, without corrupting the underlying data.
Encoding works by first converting your text to its UTF-8 byte representation (so special characters and emoji are handled correctly), then mapping each group of 3 bytes into 4 Base64 characters. Decoding reverses this process, converting the Base64 characters back into the original bytes and then back into readable text.
Base64 is not encryption — it's a reversible encoding scheme. Anyone can decode a Base64 string instantly, so it should never be relied on to protect sensitive information.
See It In Action
Who Uses Base64 Encode / Decode and Why
- Embedding a small icon or image directly inside HTML or CSS as inline Base64 data to avoid a separate file request.
- Converting binary data (like a file or image) into plain text so it can be safely included in a JSON payload or email attachment.
- Decoding a Base64 string found in an API response, a JWT token segment, or a configuration file to see its actual content.
- Troubleshooting why a piece of data pasted into a text-only field looks like a jumble of letters and digits ending in one or two equals signs.
Mistakes to Avoid
- Treating Base64 as a security or encryption method — it provides zero protection since anyone can decode it instantly; it's purely a format conversion, not a way to hide or secure data.
- Expecting Base64-encoded output to be the same size as the original — encoded text is always roughly a third longer than the source data because of how it repacks 3 bytes into 4 characters.
- Trying to decode text that isn't actually valid Base64 (wrong alphabet, missing padding) and being surprised the result is garbled or errors out.
- Forgetting that Base64 output is case-sensitive and can include +, /, and = characters that may need their own encoding if placed inside a URL.
Tips for Best Results
- If you need to put Base64 data inside a URL, use URL-safe Base64 (or run it through URL encoding afterward) since standard Base64's + and / characters have special meaning in URLs.
- Use Base64 encoding to sanity-check what's inside a token or payload you've been handed — decoding it is often the fastest way to see if it's what you expect before debugging further.
Fixing Common Problems
Decoding fails or produces garbled output. — Check that the input is actually valid Base64 — it should only contain letters, digits, +, /, and possibly trailing = padding characters; stray whitespace or line breaks copied in by accident are a common cause.
The encoded output looks much longer than I expected. — This is expected — Base64 always expands data by roughly 33% because it represents each 3 bytes of input as 4 text characters; it's not a bug, just how the encoding works.
Terms Explained
Encoding: A reversible way of representing data in a different format — unlike encryption, encoding requires no secret key or password to reverse.
Padding: The trailing = or == characters sometimes appended to Base64 output to indicate the final group of encoded characters represents fewer than 3 original bytes.
Binary data: Data (like images, audio, or executable files) that isn't plain text and may contain byte values that break systems expecting only readable characters — the reason Base64 exists.