Base64 & URL Tool
Encode · decode · percent-escape — offline
Base64 is NOT encryption. Anyone can decode it. Never store passwords or secrets in Base64 — use it only for binary-data transport.
Output
Waiting…
0
Input chars
0
Output chars
—
Size change
Unicode done right
JavaScript's native btoa() breaks on emoji & non-ASCII. This tool first UTF-8 encodes, so Hindi (नमस्ते), Chinese (你好) and emoji (🎉) round-trip perfectly.
Related tools
Common use cases
- Base64: embed small images in HTML/CSS, send binary over JSON APIs, Basic auth headers.
- URL-encode: put user search terms into query strings safely —
?,&,+, spaces all become safe percent-escapes. - URL-decode: read what a server actually received when debugging webhooks.
- WhatsApp / SMS templates frequently need URL-encoded body text — this does it in one tap.
Decoding sanity check: if the decoded output looks like garbage characters, the input wasn't actually Base64 — most errors come from mixing in whitespace or an invalid character.
Frequently asked questions
Is Base64 safe for passwords?
Absolutely not. Base64 is reversible by anyone without any key. It's an encoding — like writing in a different alphabet — not encryption. For password hashing use bcrypt/argon2.
Why is the output about 33% longer?
Base64 packs every 3 bytes into 4 printable characters. That 1.33× markup is the price paid to move binary data through text-only channels like JSON or email.
Difference between Base64 and Base64URL?
Base64URL replaces + with - and / with _ and drops trailing = padding so the result can safely appear inside a URL without additional percent-encoding.