Base64 Encoder / Decoder — Quick & Accurate Online Calculator & Guide

How Base64 Encoder / Decoder Works

Base64(text) = 64-char alphabet encoding

Base64 encodes binary and text data into a safe 64-character alphabet (A-Z, a-z, 0-9, +, /) for transmission over text-based protocols that might misinterpret binary data. It works by grouping input bytes into 24-bit chunks (3 bytes), splitting each chunk into four 6-bit values, and mapping each 6-bit value to one of 64 printable ASCII characters. If the input length is not a multiple of 3 bytes, = padding is added to make the output a multiple of 4 characters.

input

Input Text — The text to encode or the Base64 string to decode.

encoded

Encoded Output — Base64-encoded string (about 33% larger than input).

decoded

Decoded Output — Original text recovered from Base64 by reversing the encoding process.

How to Use

1. Select Encode mode to convert text to Base64, or Decode mode to convert Base64 back to plain text.
2. Enter your input text in the text area — supports plain text, numbers, and special characters.
3. The encoded or decoded output appears instantly as you type or paste.
4. Use the Copy button to copy the result to your clipboard for use in code, emails, or configuration files.
5. Character counts show the size difference: the encoded output is roughly 4/3 the size of the original due to Base64 overhead.

Understanding the Result

Base64 is a binary-to-text encoding scheme that represents binary data in an ASCII string format using 64 safe characters (A-Z, a-z, 0-9, +, /), with = used for padding. It is commonly used for embedding images directly in HTML or CSS as data URIs (data:image/png;base64,...), encoding email attachments via MIME, storing binary data in JSON or XML, and transmitting credentials in HTTP Basic Authentication headers. Each 3 bytes of input becomes 4 Base64 characters, adding approximately 33% overhead. Because Base64 uses only safe printable ASCII characters, it is immune to character encoding issues and transmission corruption from control characters that binary data might contain. A common variant, Base64URL, replaces + and / with - and _ and omits padding, making it safe for use in URLs and filenames.

Frequently Asked Questions

Why is Base64 output longer than the input?

Base64 encodes 3 bytes of input (24 bits) into 4 ASCII output characters. Since each output character represents only 6 bits of data (64 possible values = 2^6), 4 characters × 6 bits = 24 bits = 3 bytes. The output is always 4/3 the size of the input — a 33% increase. For example, "Man" (3 bytes) encodes to "TWFu" (4 characters). If the input is only 1 or 2 bytes, padding increases the overhead further.

What is the = padding at the end of Base64?

The = character is padding added when the input length is not a multiple of 3 bytes. One = means 1 byte of padding was needed (2 input bytes became 3 Base64 characters + 1 =), and two == means 2 bytes of padding were needed (1 input byte became 2 Base64 characters + 2 ==). The padding ensures the output length is always a multiple of 4, which simplifies decoding algorithms.

When would I use Base64 encoding in practice?

Common use cases include: embedding small images directly in HTML as data URIs to reduce HTTP requests, encoding email attachments in MIME format (the "Content-Transfer-Encoding: base64" header), storing binary data in JSON web tokens (JWTs), encoding HTTP Basic Authentication credentials, and representing cryptographic keys in PEM format (the base64-encoded content between ---BEGIN CERTIFICATE--- markers).

Is Base64 encryption?

No, absolutely not. Base64 is an encoding scheme, not encryption. Anyone can decode Base64 back to the original data using any of thousands of freely available online tools. Base64 should never be used to protect sensitive information — it only ensures safe transmission through text-based channels. For security, use proper encryption algorithms like AES or RSA.

What is the difference between Base64 and Base64URL?

Standard Base64 uses + and / characters, which have special meaning in URLs (a + becomes a space in query strings, and / is a path separator). Base64URL is a variant that replaces + with - and / with _, and omits the = padding entirely. This makes Base64URL-encoded strings safe in URLs, query parameters, and filenames without additional percent-encoding, and it is commonly used in JSON Web Tokens (JWTs).

Sources

• RFC 4648 - The Base16, Base32, and Base64 Data Encodings
• Wikipedia - Base64