Home › Blog › Base64 Encoding Guide

What Is Base64 Encoding? A Complete Developer's Guide

May 7, 2026 • 8 min read • Try the free Base64 Encoder →

If you've worked with APIs, email attachments, or data URIs, you've encountered Base64 encoding. It appears in HTTP Authorization headers, JWT tokens, embedded images in HTML, and countless configuration files. Understanding how it works — and when to use it — is a fundamental skill for any developer.

What Is Base64?

Base64 is a binary-to-text encoding scheme that converts arbitrary binary data into a string of printable ASCII characters. It uses a fixed alphabet of 64 characters: uppercase letters (A–Z), lowercase letters (a–z), digits (0–9), and two symbols — typically + and /. A 65th character, =, is used as padding.

The name "Base64" comes from the fact that the encoding uses 64 distinct characters — exactly 6 bits of information per character (2⁶ = 64).

Why Does Base64 Exist?

Many text-based protocols — SMTP (email), HTTP headers, HTML — were designed to carry text and may corrupt or reject binary data. For example:

• Binary data may contain null bytes (0x00) that terminate C strings
• Line breaks in different formats (CR, LF, CRLF) can corrupt binary data in transit
• Some protocols only support 7-bit ASCII, stripping the high bit from bytes above 127

Base64 solves all of these by transforming binary data into a safe, portable representation using only printable ASCII characters that all text-based protocols handle correctly.

How Does Base64 Encoding Work?

Base64 processes input 3 bytes at a time and converts them to 4 characters:

1. Take 3 bytes (24 bits) of input
2. Split them into four 6-bit groups
3. Map each 6-bit value (0–63) to its corresponding Base64 character

Example: encoding the string Man:

Combined: 010011010110000101101110 → split into 6-bit groups: 010011 010110 000101 101110 → decimal values 19, 22, 5, 46 → Base64 characters TWFu.

When the input length isn't a multiple of 3, padding (=) is added:

• 1 remaining byte → 2 Base64 chars + ==
• 2 remaining bytes → 3 Base64 chars + =

Base64 in Practice: Common Use Cases

1. Embedding Images in HTML/CSS

<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAA...">

Data URIs let you embed images directly in HTML or CSS, eliminating an HTTP request. Useful for small icons and critical above-the-fold images.

2. HTTP Basic Authentication

Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=

The value is username:password encoded in Base64. Note: this is NOT secure without HTTPS — Base64 is trivially reversible.

3. Storing Binary Data in JSON

JSON only supports text strings. When you need to include binary data (images, files, certificates) in a JSON payload, Base64 is the standard approach:

{
  "filename": "report.pdf",
  "content": "JVBERi0xLjQKJeLjz9MKN..."
}

4. JWT Tokens

JSON Web Tokens use Base64URL encoding (a variant of Base64 that replaces + with - and / with _, and omits padding) for the header and payload sections. See our JWT Decoder to inspect any JWT token.

Base64 in Code

JavaScript (Browser)

// Encode
const encoded = btoa('Hello, World!');
console.log(encoded); // SGVsbG8sIFdvcmxkIQ==

// Decode
const decoded = atob('SGVsbG8sIFdvcmxkIQ==');
console.log(decoded); // Hello, World!

JavaScript (Node.js)

// Encode
const encoded = Buffer.from('Hello, World!').toString('base64');

// Decode
const decoded = Buffer.from('SGVsbG8sIFdvcmxkIQ==', 'base64').toString('utf8');

Python

import base64

# Encode
encoded = base64.b64encode(b'Hello, World!').decode('utf-8')
print(encoded)  # SGVsbG8sIFdvcmxkIQ==

# Decode
decoded = base64.b64decode('SGVsbG8sIFdvcmxkIQ==').decode('utf-8')
print(decoded)  # Hello, World!

Base64 vs Base64URL

Standard Base64 uses + and / which have special meaning in URLs and query strings. Base64URL is a variant that replaces them with - and _ respectively, and typically omits the = padding. Use Base64URL when encoding data that will appear in a URL (JWT tokens, for example).

Performance Considerations

Base64 encoding increases data size by approximately 33% (every 3 bytes becomes 4 characters). For large binary files transmitted over a network, this overhead is significant. In performance-sensitive contexts, prefer sending binary data directly using multipart/form-data or binary WebSocket frames rather than Base64-encoding it.

Frequently Asked Questions

Related Guides

• How to Use Bcrypt Generator: Practical Guide and Best Practices
• How to Use Cron Parser: Practical Guide and Best Practices
• How to Use CSS Minifier: Practical Guide and Best Practices