Base64 Encoder & Decoder

Base64 is one of those technologies that most developers encounter regularly but few deeply understand. It appears in email headers, API authentication, JWT tokens, data URIs, and countless other contexts. Knowing what Base64 actually does — and more importantly, what it does not do — is essential for using it correctly and avoiding common misconceptions.

What Base64 Encoding Does

Base64 is a binary-to-text encoding scheme that represents arbitrary binary data using a set of 64 printable ASCII characters: uppercase A–Z (0–25), lowercase a–z (26–51), digits 0–9 (52–61), plus the plus sign (+ for 62) and forward slash (/ for 63). An equals sign (=) is used as padding when the input length is not a multiple of three bytes.

The encoding process works in groups of three input bytes (24 bits), which are split into four 6-bit groups. Each 6-bit group maps to one of the 64 characters in the Base64 alphabet. This means every 3 bytes of binary data becomes 4 bytes of Base64 text — an overhead of approximately 33%.

The purpose of Base64 is not security or compression — it is compatibility. Many systems were designed to handle only ASCII text (email protocols, URL parameters, JSON values, HTML attributes), but needed to transmit binary data like images, encrypted content, or serialized objects. Base64 provides a safe way to embed binary data in text-only contexts without corruption from character encoding conversions, line-ending transformations, or other text processing.

Common Use Cases

Data URIs are one of the most visible uses of Base64. When you embed an image directly in an HTML file or CSS stylesheet using a data: URL, the image data is Base64-encoded and included inline. This eliminates a network request but increases the file size by about 33% — a worthwhile trade-off for small icons and decorative elements, but impractical for large images.

HTTP Basic Authentication sends credentials as Authorization: Basic base64(username:password). The server decodes the Base64 string to extract the credentials. While Base64 is not encryption, the Basic scheme is typically used over HTTPS, which provides the actual security through TLS encryption.

JWT (JSON Web Tokens) use Base64URL — a URL-safe variant that replaces + with -, / with _, and omits padding — to encode the header and payload segments. The signature is also Base64URL-encoded, producing the three-part token format that API developers work with daily.

Email attachments (MIME) encode binary files as Base64 text within email messages, allowing images, PDFs, and other binary content to be transmitted through text-based email protocols like SMTP.

Storing binary data in JSON is another practical use case. When an API needs to return binary data (like a generated file or image) as part of a JSON response, Base64 encoding allows the binary content to be included as a string value.

Base64 Is Not Encryption

This is the most important misconception to address: Base64 encoding provides absolutely no security. Anyone can decode a Base64 string instantly using any Base64 decoder, including this tool. Base64 does not use a key, does not involve a mathematical transformation designed for secrecy, and was never intended for security purposes.

Never store passwords, API keys, or sensitive data in Base64 thinking it provides protection. If you need to encrypt data, use established algorithms like AES-256, RSA, or ChaCha20. Base64 is purely an encoding format for data transmission compatibility.

Unicode and UTF-8 Considerations

When encoding text that contains Unicode characters (accented letters, Chinese characters, emoji), the text must first be converted to UTF-8 bytes before Base64 encoding. The standard btoa() function in JavaScript only works with Latin-1 characters, so encoding Unicode text requires using TextEncoder to produce UTF-8 bytes first. ForgePlug's Base64 tool handles this automatically, supporting the full range of Unicode characters including emoji.

Size Impact

Base64 increases data size by approximately 33%. For every 3 bytes of input, 4 bytes of output are produced. This overhead is the inherent cost of representing 8-bit binary data using only 6 bits per character. For large files, this can be significant — a 1MB image becomes approximately 1.33MB when Base64-encoded. When size matters, consider whether Base64 is the right choice or whether binary transfer would be more appropriate.