Utility #12RFC 4648 Engine

Base64 Encoder & Decoder

Convert text, files, and images to and from Base64. Features URL-safe encoding, live image previews, HTML/CSS Data URI generators, and instant local execution.

0 bytes

Base64 Output

// Encoded or decoded output will appear here...

Input: 0 BOutput: 0 B

100% In-Browser Sandbox (0 Bytes Uploaded to Servers)

Two-Way Conversion

Instantly toggle between encoding text/files into Base64 and decoding raw Base64 strings back to their original format.

Live Image & Media Preview

Decode images (.png, .jpg, .svg, .webp) with instant visual thumbnail rendering and copyable HTML/CSS embed tags.

100% In-Browser Privacy

Files and confidential authentication headers never touch a server. All processing runs inside your browser sandbox.

Understanding Base64: Radix Math, URL-Safe Encoding & Best Practices

Base64 is one of the most widely used encoding algorithms in modern web development, network authentication (HTTP Basic Auth), and data serialization. Here is how it works under the hood.

Choose Mode & Input

Select Encode to transform plain text or files to Base64, or Decode to convert Base64 back into human-readable text or images.

Toggle URL-Safe (Optional)

If embedding inside query parameters or JSON Web Tokens (JWT), enable the URL-Safe toggle to replace `+` and `/` with `-` and `_`.

Copy or Download

Copy the output with 1 click, copy the HTML `<img>` tag for images, or download the result directly as a local file.

Standard Base64 vs. URL-Safe Base64 (RFC 4648)

Depending on where your encoded data is transmitted, choosing the wrong dialect can corrupt query parameters or break HTTP headers:

Specification	Character 62	Character 63	Padding Character	Primary Use Cases
Standard Base64 (RFC 4648 §4)	+ (plus)	/ (slash)	= (equals)	Email MIME attachments, Basic Auth headers, Data URIs.
URL-Safe Base64 (RFC 4648 §5)	- (minus)	_ (underscore)	Stripped or =	JWT tokens, URL query params, filenames, OAuth2 states.

The 6-Bit Radix Mathematics

Modern computers operate in 8-bit bytes (octets). However, legacy networking equipment and text protocols were historically designed for 7-bit ASCII. Base64 bridges this gap:

24-Bit Block Alignment: 3 bytes of input (3 x 8 = 24 bits) are grouped together and divided into 4 chunks of 6 bits each (4 x 6 = 24 bits).
64-Character Alphabet: Each 6-bit value (ranging from 0 to 63) indexes directly into the Base64 alphabet table (`A-Z`, `a-z`, `0-9`, `+`, `/`).
Padding (`=`): When the input length is not a multiple of 3 bytes, padding characters (`=`) are added to complete the 4-character output block.

Common Developer Applications

Base64 is essential across multiple layers of the modern web stack:

HTTP Basic Authentication: Credentials are sent in the header as `Authorization: Basic [base64(user:password)]`.
Inline Image Data URIs: Small icons can be embedded directly in CSS or HTML as `data:image/png;base64,...` to eliminate separate HTTP roundtrips.
JSON Web Tokens (JWT): The header and payload of every JWT are serialized as URL-safe Base64 strings separated by periods (`header.payload.signature`).

Frequently Asked Questions About Base64

Technical answers regarding encoding, overhead, safety, and image handling.

Base64 is a binary-to-text encoding scheme that translates arbitrary binary data (including images, compiled files, and cryptographic hashes) into a set of 64 standard ASCII characters (A-Z, a-z, 0-9, +, and /). It prevents byte alteration when transmitting data through protocols historically designed only for ASCII text, such as SMTP email MIME attachments and HTTP headers.