Base64 and URL encoding, decoded live

Frequently asked questions

What's the difference between Base64 and URL encoding?

Base64 turns arbitrary text or binary data into a compact set of letters, digits, +, /, and = — commonly used for embedding data in JSON, JWTs, or data URIs. URL (percent) encoding escapes characters that aren't safe inside a URL, like spaces and &, using %XX sequences — used in query strings and path segments. Hex, Base32, Base58 and quoted-printable are here too.

Is my text sent to a server?

No. Every encode and decode happens entirely in your browser using built-in Web APIs — nothing is uploaded, logged, or stored anywhere.

Does this handle unicode text and emoji?

Yes. Text is encoded as UTF-8 before Base64 or percent-encoding, so accented characters, CJK text, and emoji round-trip correctly.

What happens if I paste invalid Base64 or a malformed percent-encoded string?

Decoding stops with a message that says what is wrong and where, such as the character that doesn't belong. URL-safe Base64, missing or extra padding, line breaks and a data: prefix are all accepted. Valid Base64 that isn't text (an image, say) is not an error: it is shown as a hex view, previewed when it's a picture or PDF, and can be downloaded as the original file.

Is the Base64 & URL encoder/decoder really free?

Yes. There's no account to create, no card to enter, and no trial clock ticking in the background. Encoding and decoding are unlimited in both directions. Pasted text has no fixed limit beyond what your browser can hold; files can be up to 25 MB.

Can I encode a file, such as an image or a PDF?

Yes. Upload or drop any file up to 25 MB and its exact bytes are encoded, so decoding gives back the same file. Decoded data that isn't text downloads with the right file type.

Do I need an account to use it?

No — nothing to register for, nothing to download, and no email address asked for at any point. Paste text and it encodes or decodes live, in whichever direction you picked.