Base64 is the bridge between binary data and plain text — it turns images, files and special characters into a safe ASCII string you can paste into JSON, data URLs, CSS, or API payloads. Our free Base64 Encoder / Decoder handles both directions in your browser: encode any text with full UTF-8 support (emojis and non-Latin scripts included), or paste Base64 back to get the original text. You can even pick a file from your computer and get its Base64 encoding without uploading it anywhere. Free, no signup.
The decoder validates your input first and tells you plainly when it is not valid Base64 — “Invalid Base64 input, check for typos” — instead of failing silently. Developers use it to inspect JWT tokens and data URLs, designers use it to embed small images directly in stylesheets, and testers use it to move binary fixtures through text-only channels.
Because files are read locally with the FileReader API, even sensitive documents stay on your machine. Copy the output with one click and drop it wherever Base64 is expected.
Base64 Encoder/Decoder
Encode text or files to Base64 and decode Base64 back to text.
The file is read in your browser only — nothing is uploaded.
How to use
- Choose Encode or Decode at the top.
- For encoding, type or paste text into the box and click Encode to Base64.
- For decoding, paste the Base64 string and click Decode from Base64.
- To encode a file, choose it under “Or encode a file” and click Encode File.
- Click Copy Output to copy the result.
- Use Clear to reset everything.
FAQs
Does it handle emojis and non-English text?
Yes. Encoding goes through UTF-8 (TextEncoder), so Urdu, Arabic, Chinese, emojis — everything — round-trips correctly. Decoding uses TextDecoder for the same reason. Many naive Base64 tools corrupt non-ASCII text; this one does not.
Why does it say my Base64 is invalid?
Valid Base64 uses only A–Z, a–z, 0–9, + and / with up to two trailing = signs, and the length must be a multiple of 4. The usual culprits are typos, missing padding characters, or line breaks copied from an email — the validator ignores whitespace, so check the characters themselves.
Is my file uploaded when I encode it?
No. The file is read locally in your browser with the FileReader API and converted to a data URL on your machine. Nothing is sent to any server, so it is safe for private documents.