What is Base64 encoding and decoding?

Base64 is a binary-to-text encoding standard defined in RFC 4648. It translates raw binary data into a set of 64 printable ASCII characters (A-Z, a-z, 0-9, +, /). Encoding converts binary or text into Base64 ASCII, while decoding reverses Base64 back into original text or binary files.

What is the Data URI format in Base64?

A Data URI formats Base64 encoded binary data into an inline web resource using the syntax 'data:[mediatype];base64,[data]'. For example, 'data:image/png;base64,iVBOR...' allows images or fonts to be embedded directly into HTML or CSS stylesheets without separate HTTP requests.

How does URL-Safe Base64 differ from standard Base64?

Standard Base64 uses '+' and '/' characters, which have reserved meanings in URL query parameters and web paths. URL-safe Base64 replaces '+' with '-' (hyphen) and '/' with '_' (underscore), making the string safe for URLs, filenames, and JSON Web Tokens (JWT).

Why does Base64 encoding increase data size by 33%?

Base64 takes 3 bytes of binary data (24 bits) and splits them into 4 separate 6-bit chunks, representing each with an 8-bit ASCII character. Because 4 bytes are required to transmit what was originally 3 bytes, data size increases by exactly 33.3%.

Can I encode images, audio, or PDF files into Base64?

Yes. You can upload any binary file (PNG, JPG, PDF, MP3, ZIP) directly into our tool. In Encode mode, it produces a clean Base64 string or ready-to-use Data URI. In Decode mode, it reconstructs and downloads the original binary file.

Does this tool support Unicode and non-English characters?

Yes. Our tool uses modern browser TextEncoder and TextDecoder APIs supporting full UTF-8. Accented European characters, Arabic, Urdu, Chinese, Japanese, and Emojis are encoded and decoded without data corruption or mojibake.

What is line wrapping / chunking in Base64?

Line wrapping splits long continuous Base64 strings into fixed-width lines. Email MIME standards (RFC 2045) require lines to be wrapped at 76 characters, while PEM cryptographic certificates and SSH keys require 64-character line wrapping.

Is my data private when using this Base64 tool?

Yes, 100% private. All conversions, file reads, and rendering occur entirely on your local machine within your web browser. No text, credentials, or files are ever uploaded to our servers.

Base64 Encode Decode – Free Online Developer Tools

The Complete Technical Guide to Base64 Encoding and Decoding (RFC 4648)

Base64 is a binary-to-text encoding standard specified under IETF RFC 4648 designed to represent arbitrary binary data in an ASCII string format. Modern computer networks, protocols, and file formats—including email transfers (SMTP/MIME), HTTP headers, HTML Data URIs, and JSON Web Tokens (JWT)—frequently encounter channels designed strictly for 7-bit ASCII characters. Base64 bridges this architectural gap by converting raw bytes into a safe alphabet of 64 printable characters.

3:4 Expansion Ratio

Every 3 bytes of raw binary data (24 bits) produce exactly 4 Base64 ASCII characters, resulting in a consistent 33.3% size overhead.

URL-Safe Variant

Replaces + and / with - and _ to prevent parameter conflicts in URLs, web endpoints, and cryptographic JWTs.

Data URI Scheme

Embeds images, fonts, and documents directly into HTML <img> tags or CSS stylesheets via data:[mime];base64,[data].

How the Base64 Mathematical Algorithm Works

To understand Base64 encoding, consider the conversion of binary bits into characters:

The encoder takes 3 consecutive 8-bit bytes (totaling 24 bits: 3 × 8 = 24).
These 24 bits are split into 4 separate 6-bit groups (24 ÷ 6 = 4).
Each 6-bit group represents a number from 0 to 63 (since 2⁶ = 64).
Each number is looked up in the RFC 4648 Base64 Index Table to yield an ASCII character.
If the input length is not divisible by 3, one or two padding characters (=) are appended to complete the 4-character block.

Encoding Step-by-Step Example: "Cat"

Input Text	Char 1 ('C')	Char 2 ('a')	Char 3 ('t')
ASCII Value	67	97	116
8-Bit Binary	01000011	01100001	01110100
24-Bit Stream	010000110110000101110100
Re-grouped into 6-Bit Chunks	010000 (Index 16 = 'Q')	110110 (Index 54 = '2')	000101 (Index 5 = 'F') 110100 (Index 52 = '0')
Base64 Encoded Result	Q2F0

The RFC 4648 Alphabet Reference Table

Index Range	Characters	Binary Value	Usage
0 – 25	A – Z	000000 – 011001	Uppercase Latin alphabet
26 – 51	a – z	011010 – 110011	Lowercase Latin alphabet
52 – 61	0 – 9	110100 – 111101	Decimal digits
62	+ (Standard) / - (URL-Safe)	111110	Symbol 62
63	/ (Standard) / _ (URL-Safe)	111111	Symbol 63
Padding	=	Special	Aligns 4-character boundaries

Standard Base64 vs. URL-Safe Base64 (base64url)

In standard Base64, the symbols + and / are valid characters. However, when sending data over HTTP GET requests, URLs, or cookies:

Web servers interpret + as an encoded space character, corrupting the payload.
The / character denotes URI path separators, breaking URL routing.

RFC 4648 Section 5 created base64url by replacing + with - (hyphen) and / with _ (underscore), while optionally omitting the trailing = padding. This variant is mandatory for JSON Web Tokens (JWT) and web safe API tokens.

Line Wrapping: MIME (76 Chars) vs. PEM (64 Chars)

Standard protocols enforce maximum line lengths to avoid buffer overflow in legacy email and security systems:

MIME Email Standard (RFC 2045): Requires Base64 lines to be wrapped at a maximum of 76 characters, terminated with CRLF line breaks.
PEM Security Certificates (RFC 7468): Cryptographic keys (RSA, ECDSA), SSL certificates, and SSH keys format raw DER bytes into 64-character lines surrounded by headers such as -----BEGIN CERTIFICATE-----.

Frequently Asked Questions (FAQ)

Is Base64 considered encryption? ▼

No. Base64 is an encoding format, not encryption. It provides zero security, confidential protection, or scrambling against attackers. Anyone who receives a Base64 string can decode it instantly without a key or password. To protect sensitive information, encrypt it with AES or RSA prior to Base64 encoding.

How do I embed an image directly into HTML using Base64? ▼

Upload your image into our tool with "Data URI Prefix" checked. Copy the resulting code and paste it directly into an image tag: <img src="data:image/png;base64,iVBOR..." alt="Embedded Image">. This eliminates the need for a separate image file on your server.

What causes the "Invalid character" error when decoding? ▼

This error occurs when the input contains characters outside the allowed Base64 alphabet (A–Z, a–z, 0–9, +, /, =), such as stray punctuation, whitespace, or URL-safe characters (- or _) when standard decoding is expected. Our tool automatically cleans whitespace and sanitizes URL-safe characters to prevent errors.

How does Base64 handle international characters and Emojis? ▼

Older tools rely on single-byte Latin-1 decoding, which produces gibberish (mojibake) on non-English text. Our tool uses the browser's native TextEncoder and TextDecoder APIs, ensuring 100% accurate multi-byte UTF-8 handling for Arabic, Urdu, Chinese, Japanese, accented letters, and Emojis.

Can I encode or decode binary files like PDF, ZIP, or Audio? ▼

Yes. In Encode mode, dragging and dropping any binary file will convert it to a Base64 string. In Decode mode, pasting a binary Base64 string will automatically detect its file type (PNG, JPEG, GIF, PDF, ZIP, MP3) and provide a button to download the reconstructed binary file.

What is the purpose of equal signs (=) at the end of a Base64 string? ▼

Equal signs (=) are padding characters. Because Base64 operates in 24-bit (3-byte) blocks, if the original data has 1 byte left over, two padding characters (==) are added. If 2 bytes are left over, one padding character (=) is added. This ensures the total character count is always a multiple of 4.

Why is Base64 output ~33% larger than the input file? ▼

Base64 represents 6 bits of information using an 8-bit ASCII character, meaning 2 bits per byte are unused overhead. Because 3 binary bytes become 4 ASCII characters, the encoded data is exactly 33.3% larger (4/3 = 1.333).

Are my uploaded files or text sent to a remote server? ▼

No. All processing, file reading, and encoding/decoding happen entirely on your computer within your browser's client-side JavaScript engine. Your files, text, and keys never leave your device.

Base64 Encode Decode

Base64 Encoder & Decoder Pro

Input Data / Text

Base64 Encoded Result

The Complete Technical Guide to Base64 Encoding and Decoding (RFC 4648)

How the Base64 Mathematical Algorithm Works

Encoding Step-by-Step Example: "Cat"

The RFC 4648 Alphabet Reference Table

Standard Base64 vs. URL-Safe Base64 (base64url)

Line Wrapping: MIME (76 Chars) vs. PEM (64 Chars)

Frequently Asked Questions (FAQ)

Base64 Encode Decode

Input Data / Text

Base64 Encoded Result

The Complete Technical Guide to Base64 Encoding and Decoding (RFC 4648)

How the Base64 Mathematical Algorithm Works

Encoding Step-by-Step Example: "Cat"

The RFC 4648 Alphabet Reference Table

Standard Base64 vs. URL-Safe Base64 (base64url)

Line Wrapping: MIME (76 Chars) vs. PEM (64 Chars)

Frequently Asked Questions (FAQ)

Related Tools

Base64 Decoder

Base64 Encoder

Box Shadow Generator

Credit Card Validator

Email Validator

Favicon Generator