Overview
Base64 shows up everywhere once you notice it: email attachments, embedded images, auth tokens, config blobs, the mysterious strings in log files. Sometimes you need to read one; sometimes you need to produce one. This page does both, and does them correctly — which mostly means handling text encoding properly, the step where quick scripts fail.
The failure mode is specific: naive encoders treat text as Latin-1 bytes, so anything beyond basic English — an accent, an Arabic sentence, an emoji — gets mangled or throws. This tool converts text to real UTF-8 bytes first and decodes through a strict UTF-8 decoder on return, so every character round-trips intact. A swap button feeds output back as input for instant verification.
What is Base64, really?
Base64 is an encoding that represents arbitrary bytes using only 64 safe text characters: A–Z, a–z, 0–9, plus and slash, with = as padding. It regroups input three bytes (24 bits) at a time into four 6-bit chunks, each mapped to one character. The output runs about a third larger than the input — the price of restricting the alphabet.
Its purpose is transport, not secrecy: it lets binary data travel through systems built for text — email bodies, JSON strings, URLs. The critical misunderstanding is treating it as encryption. Base64 hides nothing; anyone can reverse it instantly, including with this page. Secrets need encryption, never encoding.
Features
- Both directions, one switch — encode or decode without losing your text.
- Real UTF-8 handling — a proper encoder going in, a strict decoder coming back.
- Emoji-safe round trips — accents, scripts and emoji survive intact.
- Swap button — feed output back as input and verify the reversal.
- Tolerant decoder — ignores stray whitespace and accepts the URL-safe alphabet.
- Plain error messages — malformed input explained instead of silently garbled.
- One-click copy — long wrapped results to the clipboard without selecting.
- Entirely local — no server ever sees your strings.
Benefits
- Trust the round trip. What goes in comes back out, in any script.
- Read opaque strings. Tokens and headers become plain language.
- Avoid the classic bug. No Latin-1 mangling, ever.
- Inspect secrets safely. Credentials you check never leave the tab.
Who can use it
Developers building data URIs and auth headers, system administrators reading certificates and mail logs, testers decoding what an application actually sent, and the curious decoding a mysterious string from a log file. Anyone who has watched an emoji turn into a replacement character in a lesser tool will feel the difference.
How to use
- Choose Encode or Decode with the switch.
- Paste or type your text — whitespace is fine when decoding.
- Read the result below; the status line confirms or explains.
- Use Copy for the clipboard, or Swap to reverse the operation.
- To verify, swap and run it back — you should get the original.
Frequently asked questions
Is Base64 encryption?
No — and mistaking it for encryption is a genuine security error. Base64 is a public, reversible change of alphabet; decoding needs no key and no secret. It exists to make data transportable, not confidential. If information must stay secret, encrypt it with a real cipher and treat Base64 as mere packaging.
Why do some tools mangle my emoji?
They feed text straight into the browser's oldest Base64 helper, which only accepts characters fitting in one byte. Anything else — accented letters, non-Latin scripts, emoji — either errors or gets silently damaged. Proper tools convert text to UTF-8 bytes first. This page does, which is why the round trip is exact.
What are the = signs at the end?
Padding. Output comes in groups of four characters, and when the input length is not a multiple of three, one or two = signs fill the final group. They carry no data; decoders — this one included — also cope when padding was trimmed in transit.
What is the URL-safe alphabet?
A variant replacing + and / with - and _, because plus and slash have meanings inside URLs. The decoder here accepts both alphabets, so strings copied from URLs decode without manual fixing.
Is my input uploaded?
No. Encoding and decoding are pure computation in your browser; nothing is transmitted, logged or stored.
Conclusion
Base64 is plumbing — it should be invisible and exact. Encode, decode, and use the swap button to verify the round trip in one click. Trust that every character, in every script and with every emoji, survives the journey intact, and never mistake this convenient encoding for actual encryption.