TOOL · DEV
Encode and decode Base64 and URL
Paste the text, pick the direction and the result appears live — Base64 with real UTF-8 (accents and emoji work) and URL encoding in the same place.
The conversion happens in your browser — nothing you paste is sent.
Processed in your browser — your files never leave your computer.
How it works
-
Pick the tab and direction
Base64 or URL, encode or decode — four combinations, the buttons show which one is active.
-
Paste the text
The result comes out instantly, no convert button. On Base64 decode, spaces and the base64url variant (with - and _) are accepted just fine.
-
Copy the result
One click on "copy result". If the input is broken, the message says exactly what is wrong — a character outside the alphabet, a stray %…
Frequently asked questions
What is Base64?
A way to represent any byte sequence using only 64 printable characters (letters, digits, + and /). It is used to embed data in JSON, email and URLs — places that only accept text. The price: the result is ~33% bigger than the original.
Is Base64 encryption?
No — and confusing the two is dangerous. Base64 is just a representation: anyone decodes it in a second, with no key. Never use Base64 to "hide" passwords or sensitive data. To protect data, the answer is real encryption.
Do accents and emoji work?
Yes. The tool encodes to UTF-8 before turning into Base64 (instead of raw btoa, which breaks on any non-ASCII character), so "ção" and "🎉" go in and come out intact.
What is URL encoding (percent encoding)?
The escaping that makes text safe inside a URL: a space becomes %20, "ç" becomes %C3%A7, "&" becomes %26. Use it when passing a value with special characters in a URL parameter — otherwise the server reads something else.
I decoded and got a bunch of "�" — now what?
The Base64 was valid, but the content is not UTF-8 text — it is probably binary: an image, a zip, a PDF. The tool warns you when that happens. For binary, decode into the right destination (a file), not a text box.
Is what I paste here sent to any server?
No. Encoding and decoding run in your browser, with its native functions. Tokens, API payloads, config secrets — nothing leaves your machine.