Base64 Encode & Decode Tool — Complete Guide for Developers

Understand Base64 encoding from the ground up, and convert text or files instantly with our free browser-based tool.

What Is Base64 Encoding?

Base64 is a binary-to-text encoding scheme that represents binary data using 64 printable ASCII characters. It converts every 3 bytes of binary data into 4 ASCII characters, making binary data safe to transmit through text-based systems like email, JSON, XML, and URLs.

The 64 characters used are: A-Z, a-z, 0-9, +, and /, with = used for padding. This character set is safe for virtually every text-based protocol.

For example, the text "Hello, World!" encodes to:

SGVsbG8sIFdvcmxkIQ==

And decoding SGVsbG8sIFdvcmxkIQ== gives you back "Hello, World!" exactly. The encoding is fully reversible — no data is lost.

Why Does Base64 Exist?

Base64 solves a fundamental problem in computing: many protocols and systems are designed to handle text, not arbitrary binary data. Email (SMTP), for instance, was originally designed for 7-bit ASCII text. If you tried to send a binary file directly through email, certain bytes would be interpreted as control characters and corrupt the data.

Base64 encoding transforms any binary data — images, PDFs, encrypted content, compressed files — into safe ASCII text that survives transmission through text-only systems.

Common Use Cases for Base64

1. Email Attachments (MIME)

Every email attachment you've ever sent was Base64-encoded. The MIME standard uses Base64 to embed binary files within the text-based email format. Your email client handles the encoding/decoding transparently.

2. Data URIs in HTML and CSS

You can embed images, fonts, and other assets directly in HTML or CSS using Base64 data URIs:

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

This eliminates an HTTP request for the resource, which can improve performance for small assets. For a detailed guide on image encoding specifically, check out our complete Base64 image encoding tutorial.

3. API Authentication

HTTP Basic Authentication encodes the username:password pair in Base64. The Authorization header looks like:

Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=

Important: Base64 is encoding, not encryption. The credentials above decode to username:password. Always use HTTPS with Basic Auth.

4. JSON Payloads with Binary Data

JSON only supports text. When you need to include binary data (like a file upload) in a JSON API request, Base64 encoding is the standard approach:

{
  "filename": "document.pdf",
  "content": "JVBERi0xLjQKMSAw..."
}

5. JWTs (JSON Web Tokens)

JWTs use Base64URL encoding (a URL-safe variant) for their header and payload segments. Every JWT you've worked with contains Base64-encoded JSON. If you need to decode JWTs, try our JWT decoder tool and guide.

Base64 Variants You Should Know

• Standard Base64 (RFC 4648): Uses + and / with = padding. The most common variant.
• Base64URL: Replaces + with - and / with _. Safe for URLs and filenames. Used in JWTs.
• MIME Base64: Same as standard but adds line breaks every 76 characters. Used in email.

The Size Overhead

Base64 encoding increases data size by approximately 33%. Every 3 bytes of input become 4 bytes of output. This is an inherent tradeoff — you gain compatibility at the cost of size.

For small assets (icons, thumbnails, small config blobs), the overhead is negligible. For large files, it becomes significant. A 1MB image becomes ~1.33MB when Base64-encoded. This is why you generally shouldn't Base64-encode large images for web embedding — use regular file URLs instead.

Base64 in Every Language

// JavaScript
btoa("Hello")           // "SGVsbG8="
atob("SGVsbG8=")        // "Hello"

# Python
import base64
base64.b64encode(b"Hello")  # b'SGVsbG8='
base64.b64decode(b"SGVsbG8=")  # b'Hello'

// Java
Base64.getEncoder().encodeToString("Hello".getBytes());
new String(Base64.getDecoder().decode("SGVsbG8="));

# CLI
echo -n "Hello" | base64        # SGVsbG8=
echo "SGVsbG8=" | base64 -d     # Hello

Common Mistakes with Base64

• Treating it as encryption: Base64 provides zero security. Anyone can decode it. It's encoding, not encryption.
• Encoding already-encoded data: Double-encoding produces garbage. If you see U0dWc2JHOD0=, someone Base64-encoded an already Base64-encoded string.
• Ignoring character encoding: When encoding text, the result depends on the text encoding (UTF-8, ASCII, etc.). Always be explicit about character encoding.
• Using standard Base64 in URLs: The + and / characters have special meaning in URLs. Use Base64URL for URL-safe encoding.

When NOT to Use Base64

• Large file storage: Store files as binary and serve them directly. Base64 wastes 33% storage.
• Security/encryption: Use actual encryption (AES, RSA) instead.
• Large images on web pages: Use optimized image formats (WebP, AVIF) served as files.
• When binary transport is available: If your protocol supports binary (WebSocket binary frames, gRPC), use it directly.

For more practical examples and use cases, read our comprehensive guide on what Base64 encoding is used for in real-world development.