What is Base64 Encoding? A Practical Guide

Base64 encoding converts binary data to text so it can travel safely through text-based systems. Learn when to use it, how it works, and its limitations.

Base64 is a binary-to-text encoding scheme that converts arbitrary binary data into a sequence of printable ASCII characters. You encounter it constantly in web development — in data URLs, JWT tokens, email attachments and API responses — often without realising it.

Why Base64 Exists

Many protocols and systems are designed to handle text, not raw binary data. Email (SMTP), HTML, CSS, JSON and HTTP headers all have restrictions on which characters are safe. Base64 solves this by encoding binary data using only 64 safe characters: A–Z, a–z, 0–9, + and /. This makes any binary data safe to embed in text-based systems.

Common Uses of Base64

Embedding images directly in HTML or CSS as data URLs (data:image/png;base64,...) avoids an extra HTTP request. Email attachments are Base64-encoded for MIME compatibility. JSON Web Tokens (JWTs) use Base64URL encoding for their header and payload sections. Many APIs return binary data (like generated images) as Base64 strings.

The Trade-off: Size Overhead

Base64 increases data size by approximately 33%. Three bytes of binary data become four Base64 characters. For small embedded assets this is often acceptable, but for large files it adds meaningful overhead. This is why Base64 images in CSS are generally only recommended for very small icons or sprites.

Base64 is Not Encryption

Base64 is purely an encoding scheme — it provides zero security. Any Base64 string can be decoded without a key in seconds. Never use it to "hide" passwords, API keys or sensitive data. It is safe for transmission but not for protection. For security, use proper encryption algorithms like AES.

Our Base64 encoder and decoder works entirely in your browser, handling standard Base64 and URL-safe Base64 (which replaces + with - and / with _ for use in URLs and filenames).