Base64 Encoder & Decoder

How to Use the Base64 Encoder & Decoder

Paste your text into the input area and click Encode to convert it to Base64 format, or paste Base64-encoded text and click Decode to restore the original content. The tool processes your text instantly and displays the result in the output area. The statistics grid shows character lengths and byte sizes for both input and output, making it easy to see the size overhead introduced by encoding. Use the Copy button to copy the output to your clipboard with one click.

This tool is ideal for developers who need to quickly encode strings for API requests, decode Base64 tokens for debugging, or verify that encoded data round-trips correctly. It handles UTF-8 text seamlessly, so multibyte characters such as accented letters, emoji, and CJK ideographs are encoded and decoded without corruption.

What Is Base64 Encoding and How Does It Work?

Base64 is a binary-to-text encoding scheme that represents arbitrary binary data using a set of 64 printable ASCII characters: the uppercase letters A through Z, the lowercase letters a through z, the digits 0 through 9, and the two symbols + and /. A padding character = is used when the input length is not a multiple of three bytes. The encoding process takes every three bytes of input (24 bits) and splits them into four groups of six bits, each of which maps to one of the 64 characters. This produces four output characters for every three input bytes.

The scheme was originally defined for MIME email encoding and is now specified in RFC 4648. It is one of the most widely used encoding schemes on the web because it turns any binary payload into a string that is safe for inclusion in text-based protocols and formats.

Common Use Cases

Base64 encoding appears throughout modern web development. Data URIs use Base64 to embed images, fonts, and other binary assets directly in HTML and CSS, eliminating extra HTTP requests. HTTP Basic Authentication encodes the username and password pair as a Base64 string in the Authorization header. JSON Web Tokens (JWT) use Base64url encoding for the header and payload segments. Email attachments are encoded with Base64 through the MIME standard. API payloads that need to carry binary data, such as file uploads sent as JSON, rely on Base64 to serialize the file contents into a text-safe string.

Standard vs URL-Safe Base64

Standard Base64 uses + and / as the 63rd and 64th characters, but these characters have special meanings in URLs and filenames. URL-safe Base64 (also called Base64url, defined in RFC 4648 Section 5) replaces + with - and / with _ to avoid conflicts. The padding character = can also be omitted in URL-safe variants because the original length can be inferred from the encoded length. JWT tokens, for example, use Base64url without padding. When working with web APIs, always check whether the endpoint expects standard or URL-safe encoding.

Size Overhead Explained

Because Base64 maps every 3 bytes of input to 4 characters of output, the encoded data is always approximately 33% larger than the original. For a 1 KB file, the Base64 representation is about 1.37 KB. For a 1 MB image embedded as a data URI, the encoded string is roughly 1.33 MB. This overhead is the trade-off for text-safe representation. When bandwidth or storage is a concern, consider whether Base64 is truly necessary or whether a binary transport like multipart form data would be more efficient.

Frequently Asked Questions

What is Base64 encoding?

Base64 is a binary-to-text scheme using 64 ASCII characters (A-Z, a-z, 0-9, +, /). It embeds binary data safely in text formats like JSON, XML, HTML, and email.

Why does Base64 increase the data size?

It uses 4 characters for every 3 input bytes, causing roughly 33% size growth. The trade-off is accepted because the output is safe for text-only channels.

What is URL-safe Base64?

URL-safe Base64 replaces + with - and / with _, making encoded strings safe for URLs and filenames without percent-encoding. Padding may also be omitted.

When should I use Base64 encoding?

For data URIs, JSON API binary payloads, HTTP Basic Auth headers, JWT tokens, email attachments, and storing binary data in text-only configuration files.

Can Base64 be used for encryption?

No. Base64 is an encoding scheme, not encryption. It is trivially reversible without a key. Use proper encryption like AES first, then optionally Base64-encode the ciphertext.