How it works
Pick a format and a direction, then type or paste. Text is treated as UTF-8, so Korean, Chinese, Japanese and emoji round-trip correctly. The swap button moves the result back into the input and flips the direction, so you can check that decoding gives back exactly what you started with.
"Hi" → Base64 "SGk=" · URL "Hi" · HEX "48 69"
Which format to use
- Base64: embed data in emails, JSON or data URLs.
- Base64URL: the URL-safe variant used in JWT tokens and links (no + / =).
- URL: percent-encode query parameters and non-ASCII paths.
- HTML: escape < > & and quotes so text shows safely in a web page.
- HEX: see the raw UTF-8 bytes of any text.
- Unicode: \u escapes for JavaScript, JSON and Java source code.
Tips
- Base64 is an encoding, not encryption — anyone can decode it.
- Decoding ignores spaces and line breaks in Base64 and HEX input.
- Everything runs in your browser; nothing is uploaded.
Standards and sources
- Base64 and Base64URL follow RFC 4648
- URL percent-encoding follows RFC 3986
- Text is encoded as UTF-8 (RFC 3629)
Last reviewed October 7, 2026
Frequently asked questions
How do I decode a Base64 string?
Choose Base64, set the direction to Decode and paste the string. Spaces and line breaks are ignored.
What is Base64URL?
A URL-safe version of Base64 that uses - and _ instead of + and / and drops the = padding. It is used in JWT tokens and web links.
Why does decoding fail?
The input may be in a different format, cut off, or not valid UTF-8 text. Check that the format and direction match the data.
Is Base64 encryption?
No. Base64 only changes how data is written. Anyone can decode it, so never use it to protect secrets.
Does it handle emoji and non-Latin text?
Yes. Text is converted to UTF-8 bytes first, so every language and emoji round-trips exactly.