🌐 中文
Developer & Encoders

⚡ Base64 Encoder & Decoder

Encode and decode Base64 text and binary images. Supports multi-byte UTF-8 Unicode characters without garbling, DataURL formats, and file drag-and-drop.

The Engineering Guide to Base64 Encoding, Decoding & Data URLs

Base64 is a binary-to-text encoding scheme standardized under RFC 4648 designed to represent arbitrary binary sequences using a restricted alphabet of 64 printable US-ASCII characters: uppercase letters (A–Z), lowercase letters (a–z), numerals (0–9), and two special symbols (traditionally + and /).

Because legacy network communication channels—such as SMTP electronic mail, XML configuration schemas, and HTML document streams—were strictly engineered to transmit human-readable 7-bit ASCII text, raw binary files (such as PNG images, PDF certificates, and cryptographic keys) would suffer corruption from control character misinterpretation. Base64 safely translates raw bytes into durable, printable ASCII strings that travel unimpeded across any protocol.

Mathematical Mechanics: The 24-Bit to 4-Character Mapping

Every standard binary byte consists of 8 bits. Base64 algorithms operate on groups of 3 bytes (3 × 8 = 24 bits), splitting those 24 bits into 4 separate 6-bit chunks (4 × 6 = 24 bits). Each 6-bit chunk has a numeric value ranging from 0 to 63, which maps directly to one corresponding symbol in the Base64 index table:

  • Indices 0 – 25: Uppercase letters A through Z
  • Indices 26 – 51: Lowercase letters a through z
  • Indices 52 – 61: Arabic digits 0 through 9
  • Index 62: Plus sign + (or hyphen - in Base64URL)
  • Index 63: Slash / (or underscore _ in Base64URL)
  • Padding (=): Appended when the input stream length is not evenly divisible by 3 bytes.

Understanding the Data URL Scheme

In modern frontend engineering, Base64 is frequently paired with the Data URL (Data URI) scheme (RFC 2397). Rather than referencing external assets via remote HTTP links, a Data URL embeds the image payload directly into HTML or CSS code using the syntax: data:[<mediatype>][;base64],<data>. For example: <img src="data:image/png;base64,iVBORw0KGgo..." /> allows instant asset rendering without triggering additional DNS lookups or HTTP requests.

How to Use This Base64 Converter

  1. Select Mode: Choose between Text Base64, File to Base64, or Base64 to Image depending on your workflow.
  2. Input Data: Paste plain text or encoded Base64 strings into the editor, or upload an image file to extract its Data URI representation.
  3. Click Convert: Click Encode Text ➔ to produce ASCII-safe Base64 strings or Decode Base64 ➔ to restore raw text with full UTF-8 support.
  4. Copy or Save: Use the one-click Copy button to copy the encoded string or Data URI directly to your clipboard.

Frequently Asked Questions (FAQ)

Q: Why is Base64 output approximately 33% larger than the original file?

Because 3 bytes (24 bits) are expanded into 4 characters (32 bits of text), the resulting payload is exactly 4/3 the size of the binary input. Therefore, Base64 encoding introduces an inherent ~33.3% bandwidth overhead.

Q: What is the difference between standard Base64 and Base64URL?

Standard Base64 uses '+' and '/', which carry special syntactic meanings in URL paths and query parameters. Base64URL (used in JWTs) replaces '+' with '-' and '/' with '_', and omits trailing '=' padding to guarantee seamless URL transmission without URL percent-encoding.

Q: Is Base64 a form of encryption?

No. Base64 is purely an open encoding format, not cryptography. Anyone can decode a Base64 string back to original plaintext in milliseconds with zero secret keys. Never rely on Base64 to conceal confidential credentials.