Base64 Encoder - Encode Text to Base64 Online Free

What Is Base64 Encoding?

Base64 encoding is a method of converting binary data or text into a safe ASCII string representation using a character set of 64 printable characters: uppercase letters (A-Z), lowercase letters (a-z), digits (0-9), plus (+), and forward slash (/). An equals sign (=) is used as padding at the end of the encoded string when the input length is not a multiple of 3 bytes.

Base64 encoding works by taking every 3 bytes of input data and converting them into 4 ASCII characters. Each group of 6 bits from the input is mapped to one of the 64 characters in the Base64 alphabet. This process is fully reversible — anyone can decode a Base64 string back to its original content without any key or password.

It is important to understand that Base64 is not encryption. It provides no security, confidentiality, or integrity. It is simply an encoding scheme designed to represent binary data as text, making it safe to transmit through text-based systems like email, URLs, HTTP headers, and configuration files.

The Four Base64 Output Formats

This tool provides four distinct Base64 output formats, each designed for specific use cases:

• Standard Base64 — The classic format using the character set A-Z, a-z, 0-9, +, / with = padding. This is the default output of PHP's base64_encode() and is used in most general-purpose encoding scenarios including HTTP headers, JSON payloads, and data storage.
• URL Safe Base64 (RFC 4648) — A variant that replaces the + and / characters with - (hyphen) and _ (underscore) respectively. This format is essential when embedding Base64 data in URLs, file names, or any context where the standard + and / characters would be misinterpreted or cause parsing errors. This is also the format used in JWT (JSON Web Token) signatures.
• MIME Base64 (76-character line breaks) — Follows the RFC 2045 standard for email transmission. The encoded output is split into lines of 76 characters each, which is required by the MIME specification for encoding binary attachments in email messages. If you are sending binary data via email or SMTP, use this format.
• Data URI — Wraps the Base64-encoded content in a data: URI scheme (e.g., data:image/png;base64,iVBOR...). This allows you to embed images, fonts, scripts, and other small files directly inline in HTML, CSS, or JavaScript, reducing HTTP requests and improving initial page load performance.

How Base64 Encoding Works

Base64 encoding operates on the principle of converting 3 bytes (24 bits) of binary data into 4 characters of ASCII text. Here is the step-by-step process:

1. Group bytes in threes — The input data is processed in chunks of 3 bytes. Each chunk produces 4 Base64 characters.
2. Split into 6-bit groups — The 24 bits from 3 bytes are divided into four 6-bit segments. Each 6-bit value (0–63) maps to one character in the Base64 alphabet.
3. Map to characters — Each 6-bit value is mapped to A-Z (0–25), a-z (26–51), 0–9 (52–61), + (62), or / (63).
4. Add padding — If the final group has fewer than 3 bytes, equals signs (=) are appended to pad the output to a multiple of 4 characters.

The tool also auto-detects the type of your input text and labels the output accordingly. It identifies Plain Text, JSON, XML, HTML, CSV, URLs, and email addresses, giving you insight into what you are encoding.

When Should You Use Base64 Encoding?

Base64 encoding is essential in several common scenarios:

• Email attachments — Email was designed to transmit text only. Binary files (images, PDFs, documents) must be Base64-encoded before inclusion in MIME-formatted email messages. Use the MIME format with 76-character line breaks for email compatibility.
• Data URIs for inline embedding — Embed small images, fonts, icons, and scripts directly in HTML or CSS using data: URIs. This eliminates extra HTTP requests and can improve initial page load times for small assets.
• HTTP Basic Authentication — The Authorization: Basic header in HTTP requests contains the Base64-encoded representation of the username:password pair. This is the standard authentication method for many REST APIs and web services.
• URL parameters — When binary data or data containing special characters must be passed through a URL query string, Base64 encoding ensures it remains URL-safe (especially when using the URL Safe format).
• JWT tokens — JSON Web Tokens use Base64URL encoding (RFC 4648 URL Safe variant) for the header, payload, and signature segments.
• Data storage and transfer — Store binary data as ASCII text in databases, configuration files, and text-based systems that do not support raw binary input.

Standard Base64 vs URL Safe Base64

The two most commonly used Base64 variants differ in their character sets:

• Standard Base64 uses + and / as the 62nd and 63rd characters. These characters have special meaning in URLs (+ is a space delimiter, / is a path separator) and file systems, making Standard Base64 unsuitable for URL parameters or file names.
• URL Safe Base64 (RFC 4648) replaces + with - (hyphen) and / with _ (underscore). These characters are safe in URLs and file names, making this format the correct choice for URL parameters, file names, and JWT tokens.

Always check which format your target system expects. Using Standard Base64 in a URL will break the URL structure because the + and / characters will be misinterpreted by the URL parser.

How MIME Base64 Differs from Standard

The MIME variant of Base64 follows the RFC 2045 standard and adds line breaks every 76 characters. This is required for email transmission because:

• Many email systems and SMTP servers impose line length limits on message headers and bodies.
• The MIME standard mandates a maximum line length of 76 characters for Base64-encoded content parts.
• Without line breaks, encoded email content may be truncated or corrupted by intermediate mail servers.

Use MIME format when encoding data for email attachments. Use Standard or URL Safe format for all other use cases.

Data URIs: Embedding Base64 in HTML and CSS

A Data URI wraps Base64-encoded content in a data: scheme, allowing you to embed files directly in your HTML, CSS, or JavaScript without external file requests. The format is:

data:[mediatype];base64,[encoded-data]

For example, to embed a small PNG image inline:

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

Data URIs are ideal for small assets like icons, logos, and fonts. However, because Base64 increases data size by approximately 33%, avoid using Data URIs for large files like full-size photographs or video clips.

Common Use Cases in Web Development

• Embedding images in CSS — Use Data URIs to embed small background images and icons directly in CSS files, eliminating extra HTTP requests.
• SVG icons in HTML — Encode SVG files as Base64 Data URIs to embed them inline, avoiding CORS and caching issues.
• API authentication headers — Encode credentials as Base64 for HTTP Basic Authentication when calling protected REST API endpoints.
• JWT token generation — Sign and encode JWT tokens using Base64URL for header and payload segments in authentication systems.
• Email via SMTP — Encode binary attachments (PDFs, images, documents) as MIME Base64 before sending via email protocols.
• Configuration files — Store binary secrets, certificates, or keys as Base64 strings in JSON, YAML, or XML configuration files.

Base64 Encoding vs URL Encoding

These two encoding schemes serve different purposes and should not be confused:

• Base64 encodes entire blocks of data into a safe ASCII character set. It converts 3 bytes into 4 characters and is used for embedding and transmitting binary data.
• URL encoding (percent-encoding) encodes individual characters that are unsafe or reserved in URLs. A space becomes %20 and an ampersand becomes %26. It is used for URL query parameters and path segments.

Use Base64 when you need to represent binary data as text. Use URL encoding when you need to safely include special characters in URLs.

How to Use This Tool

1. Enter your text — Paste or type any text into the input textarea. The tool auto-detects the text type (Plain Text, JSON, XML, HTML, CSV, URL, Email).
2. Click Encode — The tool encodes your text to Base64 using PHP's base64_encode() function and detects the text type.
3. Choose output format — Select Standard, URL Safe, MIME, or Data URI depending on your use case.
4. Copy or Download — Use the Copy button to copy the result to your clipboard, or click Download to save it as a text file.

Need to hash your data instead? Try our MD5 Generator for computing checksums of your text and files.

Related Tools

• URL Encode — Encode and decode URLs with special characters to percent-encoded format.
• MD5 Generator — Generate MD5 hash values for text and data integrity verification.

Privacy and Security

Base64 encoding is performed entirely on our servers using PHP's native base64_encode() function. We do not store your input or encoded output. The tool processes your data in memory and discards it immediately after returning the result. No cookies, tracking scripts, or analytics collect your encoded data.