Base64 Encoder / Decoder

What Is the Base64 Encoder / Decoder?

Base64 is a binary-to-text encoding scheme that takes raw binary data and converts it into a string of printable ASCII characters. The name comes from the fact that it uses a 64-character alphabet, made up of uppercase letters, lowercase letters, digits, and the two symbols + and /. The full specification is set out in RFC 4648, which also covers URL-safe variants that swap out + and / for - and _. In practice, you come across Base64 constantly in web development, whether that is data URIs for images, JWT tokens, or MIME email attachments.

The encoder on this page works entirely in your browser. No data is sent to a server, which matters when you are dealing with credentials, private keys, or any other sensitive payload that you need to encode quickly without passing it through an external service.

How to Use the Base64 Encoder / Decoder

1. Paste your text or binary string into the input area on the left.
2. Choose whether you want to encode (plain text to Base64) or decode (Base64 back to plain text) using the toggle above the field.
3. The output appears instantly in the right panel. Click the copy button to pull it into your clipboard.
4. If you need a URL-safe variant, tick the URL-safe option. This swaps + for - and / for _, and strips trailing padding characters as required by many JWT libraries.
5. For binary files, use the file upload option to drop the file in and get the encoded string without having to run a command-line tool.

Technical Background

Base64 works by breaking input bytes into groups of three. Each group of 24 bits is then split into four 6-bit chunks, and each chunk is mapped to one of the 64 characters in the alphabet. Because you are packing three bytes into four characters, every Base64-encoded string is roughly one-third larger than the original. That overhead is the trade-off you make for being able to pass arbitrary binary data through text-based protocols like HTTP headers or JSON payloads.

When the input length is not divisible by three, padding characters (=) are added to fill out the final group. MDN's Base64 reference is a solid place to look through the mechanics if you want to understand how padding works in detail or how the URL-safe alphabet differs from the standard one.

On top of that, it is worth knowing that Base64 is an encoding scheme, not encryption. Anyone who comes across a Base64 string can decode it instantly. If you need to protect the underlying data, you have to encrypt it first and then encode it, not the other way around.

Common Use Cases

• Data URIs: Embedding small images directly into CSS or HTML without a separate HTTP request. You encode the image bytes, prefix the string with the appropriate MIME type, and plug it into a src or background-image value.
• JWT tokens: The header and payload sections of a JSON Web Token are Base64url-encoded. If you come across a JWT and want to look through its claims without setting up a dedicated tool, paste the middle section here and decode it.
• API authentication: HTTP Basic Auth encodes username:password as Base64 and passes it in an Authorization header. This encoder lets you build or check those strings quickly.
• Email attachments: MIME attachments in email are Base64-encoded so that binary files can pass through text-based mail servers. If you ever need to decode an attachment that has come through raw, this tool handles it.
• Environment variables: Teams sometimes encode multiline config values or private keys in Base64 before storing them in environment variables to avoid newline issues.

For related encoding tasks, you might also want to look at the URL Encoder / Decoder for percent-encoding, or the MD5 Hash Generator if you need a one-way fingerprint rather than a reversible encoding.

Limitations to Know

Given that Base64 increases output size by about 33 percent, it is not a good fit for large binary files where bandwidth or storage matters. In practice, most teams use it for small payloads like tokens, credentials, and small images, and pass larger files as raw binary instead.

That said, this tool operates on text in the browser's memory. Very large inputs, say files over a few megabytes, may cause the interface to slow down. For those cases, a command-line utility like base64 on Linux/macOS or the equivalent PowerShell cmdlet on Windows will handle the job more efficiently.

What is more, if you are working with binary files that contain non-UTF-8 bytes, you should use the file upload path rather than pasting raw bytes as text. Pasting binary data as text can introduce encoding errors that corrupt the output.

Conclusion

The Base64 Encoder / Decoder is one of those tools you reach for regularly once you start working with APIs, tokens, and binary data in web development. It converts binary data into portable text and back again, with support for both the standard and URL-safe alphabets. Because everything runs in the browser, sensitive payloads stay on your machine. For a deeper look at the standard, the authoritative reference is RFC 4648.