Base64 Encoder

Base64 is a way to represent bytes using a limited alphabet (letters, numbers, +, and /, with optional = padding). It is often used when you need to move data through systems that are not friendly to raw bytes or special characters. That includes JSON fields that must be ASCII-safe, HTTP headers, URL parameters in controlled settings, and legacy protocols.

The key point is that Base64 does not hide content. Anyone can decode it. If you are working with sensitive material, protect it with real security controls (transport encryption, access control, and proper secret management). Base64 is best thought of as a compatibility layer that makes data easier to transmit, store, and compare across environments.

Browser APIs like btoa were originally designed around Latin-1 strings, which becomes a problem the moment your text includes emoji, accents, or non-Latin scripts. This page avoids that trap by converting your input into UTF-8 bytes first, then Base64 encoding those bytes. That is the “Unicode-safe” part.

Under the hood, the conversion follows a simple, deterministic pipeline:

• 1) UTF-8 bytes

  The browser's TextEncoder converts your JavaScript string into a UTF-8 byte array. This preserves every character reliably.
• 2) Byte stream → Base64

  Those bytes are converted to a binary string and passed to btoa to produce standard Base64.
• 3) No network calls

  The input and output stay in memory in your browser tab. There is no server round-trip and no background upload.
• 4) Predictable output

  Given the same input text, you get the same Base64 output. This is useful for diffing, snapshots, and reproducible tests.

Because the algorithm is byte-based, it behaves well with mixed text like “Résumé ✅”, Arabic, Japanese, or multi-line notes. You do not need to pre-normalize your text just to encode it. If you upload a file, extraction happens in your browser as well (PDF and DOCX extraction require optional libraries in your app).

After encoding, you can copy the Base64 output directly or download it as a PDF. Copy is explicit: you click Copy, then paste wherever you need the string. That helps avoid the “did the app reformat my content on paste?” problem in strict fields like JSON editors, form inputs, and configuration panels.

Base64 output is often long. Many systems wrap it across lines for readability, but some systems require a single unbroken line. This page keeps your output exactly as produced, without inserting line breaks. If your destination expects wrapped Base64 (for example, MIME-style line lengths), do that wrapping explicitly with a tool designed for that specific format.

You will sometimes see “URL-safe Base64” mentioned in API docs. Standard Base64 uses + and / characters, which can be inconvenient inside URLs or filenames. URL-safe variants swap those characters (usually to - and _) and may remove padding. This page outputs standard Base64 because it is the most widely accepted and the safest default for copy-and-paste workflows.

If your destination explicitly requires the URL-safe alphabet, you can convert the output with a simple deterministic change: replace + with - and / with _. Some systems also expect padding to be removed. Only do that if your target spec says so, because many decoders still rely on padding for strict validation.

Another common surprise is that Base64 makes strings longer. The encoded output is typically about one third larger than the original byte length. That is normal: the encoding trades compactness for compatibility. If you are hitting field limits, consider whether your system supports binary uploads, gzip compression before encoding, or passing a reference instead of embedding the full content.