Base64 Decoder & Encoder

A Way to Write Any Data Using Only Safe Characters

Base64 is a method for representing binary data — images, files, encrypted bytes, anything — using only 64 printable characters: A–Z, a–z, 0–9, plus two extra symbols (usually + and /). It doesn't compress or encrypt anything; it exists purely to make data safe to pass through systems that were only ever designed to handle plain text.

That constraint sounds oddly specific, but it's exactly the problem Base64 was built to solve: older email systems, some URLs, and plenty of text-based protocols choke on raw binary data or special characters. Base64 sidesteps the problem entirely by re-encoding that data into a restricted, universally safe alphabet — at the cost of making the encoded version roughly a third larger than the original.

At a glance:
• Base64 is an encoding, not an encryption — it provides zero confidentiality or security
• Every 3 bytes of input become 4 characters of Base64 output
• Output can include trailing "=" padding characters to complete the final group
• Encoded data is always about 33% larger than the original

Base64 Encoder

How Your First Few Bytes Get Regrouped

Base64 Decoder

How the 8-Bit to 6-Bit Conversion Actually Works

Why 6 Bits, Specifically

A regular byte uses 8 bits, giving 256 possible values — far more than the 64 "safe" characters Base64 allows. Six bits, on the other hand, gives exactly 2⁶ = 64 possible values, matching the Base64 alphabet perfectly. So the encoding process takes three 8-bit bytes (24 bits total), and instead of reading them as three 8-bit groups, it re-reads the exact same 24 bits as four 6-bit groups — each one mapped to one of the 64 allowed characters.

Worked Example

Given: The letter "M" (byte value 77, or 01001101 in binary)

Step 1: Three input bytes are needed to form a clean group — "Ma" adds a second byte (97, or 01100001)
Step 2: Combined 16 bits (with a third byte pending) get split into 6-bit chunks: 010011 010110 0001...
Step 3: Each 6-bit chunk is looked up in the Base64 alphabet table and converted to its matching character
Step 4: If the input doesn't divide evenly into groups of 3 bytes, "=" padding characters fill out the final group

The Base64 Alphabet

Every possible 6-bit value (0–63) maps to exactly one character from this fixed table.

Value Ranges

The URL-safe variant of Base64 replaces + and / with - and _ so encoded strings can be used directly inside URLs without extra escaping.

Where Base64 Quietly Shows Up Every Day

Email Attachments: The MIME standard uses Base64 to encode binary attachments (images, PDFs, documents) so they can travel safely through email systems originally designed only for plain text.

Data URIs in Web Pages: Small images and fonts are sometimes embedded directly into HTML or CSS as Base64 strings, avoiding an extra network request at the cost of a larger file size.

JWT Authentication Tokens: JSON Web Tokens, widely used for web authentication, encode their header and payload sections in Base64 (specifically the URL-safe variant) before signing and transmitting them.

API Authentication Headers: HTTP Basic Authentication encodes a username and password combination in Base64 before including it in a request header — a practice worth knowing isn't secure on its own, since Base64 offers no encryption.

Storing Binary Data in Text-Only Fields: Databases, configuration files, and JSON payloads that only support text fields often store binary data (like a small image or a cryptographic key) as a Base64 string instead.

Data URLs for Downloads: Some in-browser tools generate downloadable files entirely client-side by encoding the file content as a Base64 data URL, without ever touching a server.

Common Base64 Pitfalls

✓ Base64 is not encryption: Anyone can decode Base64 instantly with no key or password required — never use it as a way to protect sensitive data, only to make it transportable.

✓ Watch for the URL-safe variant: Standard Base64 uses + and /, both of which have special meaning inside a URL. If a decode fails on a string pulled from a URL, try swapping those characters back from - and _ first.

✓ Padding characters aren't always required: Some systems strip trailing "=" padding entirely, since the decoder can often infer it from the string length — don't assume missing padding means corrupted data.

✓ Expect roughly 33% size growth: Since 3 bytes always become 4 characters, encoded data is reliably about a third larger than the original — factor that in when embedding Base64 data in size-sensitive contexts.

✓ Line breaks in some Base64 output are normal: Certain standards (like classic email MIME encoding) insert line breaks every 76 characters — strip whitespace before decoding if a tool doesn't handle it automatically.

✓ Decoding garbled text usually means wrong input, not a broken decoder: If decoded output looks like nonsense, double-check that the input is valid, complete Base64 — copy-paste errors and truncated strings are the most common cause.

Built to Solve Email's Original Sin

Early Email Couldn't Handle Binary Data: The original SMTP email standard was designed around 7-bit ASCII text, meaning it technically couldn't reliably transmit binary files, non-English characters, or anything outside that narrow character set without corruption.

Uuencode Came First: Before Base64 became standard, an earlier scheme called uuencode (short for "Unix-to-Unix encode") served a similar purpose, converting binary data into text for transmission over Unix systems, though with a less standardized and less efficient encoding scheme.

MIME Standardized It in the Early 1990s: The Multipurpose Internet Mail Extensions (MIME) standard, formalized in the early 1990s, adopted Base64 as one of its standard content-transfer encodings, giving email attachments a reliable, universal way to survive transmission through text-only mail systems.

Outlived Its Original Purpose: Even though modern email and web infrastructure can handle binary data far more gracefully than 1990s-era systems, Base64 never went away — it simply found new uses wherever a text-only format still needs to carry binary content, from tokens to embedded images.

Frequently Asked Questions