How to Use a Base64 Encoder Decoder – Encode & Decode Data Online

Base64 encoding increases data size by exactly 33.3% (4/3 ratio). Every 3 bytes of binary input produce 4 bytes of Base64 output. A 150 KB image becomes a 200 KB Base64 string. For files over 100 KB, the size penalty nearly always outweighs the convenience of embedding—use a regular file URL instead of a data URI.

Base64 is encoding, not encryption. Anyone who sees a Base64 string can decode it instantly—there is no key, password, or secret involved. Never use Base64 to protect passwords, API keys, or sensitive user data. If security matters, use AES-256-GCM or a similar authenticated encryption algorithm, then optionally Base64-encode the encrypted binary output for text-safe storage or transmission.

For JWT (JSON Web Tokens), each segment (header, payload, signature) is Base64URL-encoded independently. The format is header.payload.signature, with each part separated by a dot. Paste the middle segment into our decoder to inspect the token's claims (user ID, expiration time, issuer, scopes) without needing a JWT library.

When embedding images in HTML or CSS as data URIs, always specify the correct MIME type: data:image/png;base64, for PNG images, data:image/jpeg;base64, for JPEGs, or data:image/svg+xml;base64, for SVG. An incorrect MIME type causes the browser to misinterpret the binary data and display a broken image. For SVG, consider using the text-based data:image/svg+xml, format instead of Base64—it is smaller and human-readable.

URL-safe Base64 replaces the + character with - and / with _ to make the encoded string safe for use in URLs, query string parameters, and filenames without percent-encoding. Standard + and / have special meanings in URL contexts (+ represents a space in query strings, / is the path separator). Always use URL-safe Base64 when embedding encoded data in a URL.

Do not Base64-encode files larger than 1 MB. Beyond that threshold, the 33% size increase plus browser memory overhead makes encoding slow and produces unwieldy strings hundreds of thousands of characters long. For large files, use multipart/form-data uploads, direct file URLs, or cloud storage object URLs instead.

Hex encoding (Base16) is an alternative to Base64 that uses 16 characters (0-9, A-F) and doubles the data size (100% overhead vs Base64's 33%). Use Base64 when you need compact text representation of binary data. Use hex when you need byte-level readability for debugging—each byte becomes exactly two hex characters, making it easy to inspect individual bytes.

The = padding characters at the end of a Base64 string indicate how many bytes of the final 3-byte block were missing in the original data. One = means 2 bytes of padding (input was 1 byte short of a full block). Two == means 4 bytes of padding (input was 2 bytes short). A Base64 string with no = has an input length that was exactly divisible by 3. The padding is mathematically required for decoding but can be omitted in URL-safe contexts if the decoder infers the correct length.

In email systems, Base64 is used by the MIME (Multipurpose Internet Mail Extensions) standard to encode binary attachments within the text-based email format. When you attach an image or PDF to an email, your email client Base64-encodes the file and wraps it in MIME headers that tell the recipient's client what the original file type was and how to decode it. This is the same Base64 encoding you see in raw email source with Content-Transfer-Encoding: base64 headers.