Encode and decode Base64, privately
Convert text to Base64 and back, right in your browser. Everything runs on your device (0 uploads, works offline), so whatever you paste — tokens, keys, config or notes — never touches a server.
How to use it
- Paste or type your text (to encode) or a Base64 string (to decode) into the box.
- Pick the direction: Encode (text → Base64) or Decode (Base64 → text).
- The result updates live. Copy it, or edit the input to convert more.
- Decoding ignores spaces and line breaks, so wrapped or MIME-style Base64 pastes cleanly.
FAQ
How do I Base64 encode text online for free?
Type or paste your text on this page and choose Encode — the Base64 result appears instantly, built entirely in your browser with local JavaScript, so nothing is uploaded and there's no sign-up. It uses standard RFC 4648 Base64 (A–Z, a–z, 0–9, + and /) with = padding, and it still works with your Wi-Fi off.
How do I decode a Base64 string back to text?
Paste the Base64 and choose Decode — it's converted back to UTF-8 text on your device, with surrounding spaces and line breaks ignored so wrapped or MIME-style Base64 pastes cleanly. If the input isn't valid Base64, you get a clear typed error instead of a crash.
Is my text or key uploaded when I encode it here?
No. Encoding and decoding both happen locally in your browser and nothing is stored or logged — that's the point, since Base64 is often used for tokens, keys and other secrets you don't want to paste into a site that uploads them.
Does this handle emoji and non-English characters?
Yes. Text is encoded as UTF-8 first, so emoji (🙏), Devanagari (नमस्ते), accents and any other Unicode round-trip exactly — encode then decode returns precisely what you started with.
Is Base64 the same as encryption?
No — Base64 is encoding, not encryption. It simply represents bytes using 64 printable characters so binary data survives text-only channels like email, JSON and URLs; anyone can decode it, so never treat Base64 as a way to hide or protect a secret.
Limits
Handles standard RFC 4648 Base64 with = padding — encoding UTF-8 text and decoding it back. It does not use the Base64URL variant (the - and _ alphabet used inside JWTs — reach for the JWT decoder there), and it works on text rather than arbitrary binary files.
Related
For developer work alongside this, the JWT decoder and JSON formatter pair naturally with Base64 once they're live.
Bookmark this page (Ctrl+D, or ⌘D on Mac) or install the app — it works offline the next time you need it.