Base64 Encoder and Decoder

Introduction:

Many web and messaging formats still need binary data to travel through text-only channels. Base64 solves that transport problem by spelling bytes with printable characters, so an image fragment, certificate body, token, attachment part, or small inline file can sit inside text without losing the original byte values.

The tradeoff is size and readability. Base64 is usually about one-third longer than the original bytes, and the result is not meant to be read by people. It is useful because the encoded text can be copied, wrapped, embedded, or stored where raw bytes would be damaged by line endings, control characters, or character-set conversion.

Two Base64 strings can represent the same bytes while looking different. One system may keep padding signs, another may strip them. A sender may use standard Base64 for a certificate and base64url for a token. A long encoded block may be folded across lines even though the decoded bytes are unchanged.

Text encoding is a separate choice from Base64. The word café has one byte sequence in UTF-8 and a different one in Latin-1, so the Base64 text changes before the Base64 rules even start. During decode, a garbled text preview may mean the bytes are binary, compressed, encrypted, or being displayed with the wrong character encoding.

Base64 does not encrypt, compress, sign, or prove trust. Anyone with the string and a decoder can recover the bytes, so encoded secrets, credentials, tokens, and private files deserve the same care as the original material.

How to Use This Tool:

Start with the direction, then match the output to the place where the encoded text will be pasted or decoded.

1. Choose Encode for plain text or a file that needs a Base64 form. Choose Decode when the input is already Base64 and you want the recovered text or bytes.
2. Paste text into the main field or select Browse file. For binary files, prefer file input so an editor cannot alter byte values before encoding.
3. For text encoding, keep UTF-8 unless a legacy system specifically expects UTF-16LE, Latin-1, or ASCII. If decoded output looks wrong, switch to Raw bytes preview before treating the payload as readable text.
4. Use URL-safe alphabet when encoding for URLs or filenames. Decode mode accepts both standard and URL-safe symbols, but the setting still helps you document the expected variant in the result fields.
5. Open Advanced for padding, wrapping, line endings, lenient cleanup, and Data URL output. Leave Strip non-Base64 characters off unless pasted labels or separators should be discarded.
6. Review Payload Fields for mode, byte counts, alphabet, wrapping, and padding, then use Byte Breakdown when the decoded text is not clearly human-readable.

Interpreting Results:

The primary result is copy-ready text for the current mode. In encode mode, that means Base64 text, or a complete Data URL when that option is on. In decode mode, it means decoded text or a printable byte preview, depending on the output encoding choice.

Check byte counts when comparing results. Line wrapping, Data URL prefixes, and optional padding can change the visible length while leaving the recovered bytes the same. Payload Fields is useful for confirming the variant choices; Byte Breakdown is the better check when the payload contains control bytes, non-text data, or characters that display as dots or replacement marks.

A successful decode proves only that the input can be read as Base64. It does not prove that the recovered content is safe to open, valid for a protocol, encrypted, compressed, or from a trusted sender. When decoding fails, compare strict cleanup, padding repair, and copied wrapper text before deciding that the payload itself is broken.

Technical Details:

Base64 works on octets, not on letters. A text string must first become bytes through a character encoding, while a selected file already supplies its byte stream. Once the bytes are known, Base64 reads them in 24-bit groups and writes four printable characters for each full group.

The 64-character alphabet carries six bits per output character. Standard Base64 uses letters, digits, +, and /. base64url keeps the same six-bit values but replaces the last two symbols with - and _ so the encoded text is easier to place in URLs and filenames. Padding signs are not data bytes; they mark a short final group.

Formula Core

For N input bytes, padded Base64 length L and padding count P are determined before wrapping, URL-safe symbol replacement, or a Data URL prefix is applied.

Five input bytes need two Base64 groups, so padded output has eight characters. Because 5 mod 3 = 2, the final group carries one padding sign. If a format omits padding, the same bytes display as seven Base64 characters.

Transformation Core

Privacy Notes:

Encoding and decoding run in the browser for the built-in text and file workflow, so selected files are not uploaded to a conversion service during that workflow. The browser still handles the material you enter: copied output can go to the clipboard, opened Data URLs can be handed to a new tab, and form values may appear in the address bar for restore or sharing behavior. Avoid pasting secrets when you do not want them reflected in browser history, copied links, screenshots, or shared URLs.

• Use file input for binary data instead of copying through a text editor.
• Clear sensitive text from the field before sharing the page URL.
• Treat decoded bytes, tokens, and credentials as sensitive even when they arrived as printable Base64 text.

Worked Examples:

Plain text with the standard alphabet

Encoding Man as UTF-8 produces bytes 4D 61 6E and the Base64 text TWFu. Payload Fields should show Mode as Encode, Alphabet as Standard Base64, Input bytes as 3 B, and Output bytes as 4 B.

A short token without padding

Decoding SGVsbG8 with Fix missing padding on recovers Hello. The output should report 7 input characters and 5 decoded bytes. If the same token used - or _, the decoder can still normalize those URL-safe symbols before recovering the bytes.

A pasted block with wrapper text

If decode mode reports non-Base64 characters after you paste a log line or labeled block, remove the label first when possible. Turn on Strip non-Base64 characters only when the extra characters are known wrappers or separators, then inspect Byte Breakdown to make sure the recovered hex and decimal values match the content you expected.

FAQ:

Glossary:

Octet

An eight-bit byte, the unit Base64 encodes and decodes.

Alphabet

The 64 printable symbols used to spell six-bit values.

Padding

Trailing = markers used when the final byte group is short.

base64url

The URL and filename-safe variant that uses - and _.

Data URL

A URL form that places a media type and payload data directly inside the address string.

References:

• RFC 4648: The Base16, Base32, and Base64 Data Encodings, IETF, October 2006.
• RFC 2397: The data URL scheme, IETF, August 1998.