How it works
This page has two independent encoders. Base64 turns any text — including accented characters and emoji — into a compact ASCII string made of letters, numbers, and a few symbols, commonly used for embedding data in JSON, data URIs, or config files; decoding reverses it back to the original text exactly. URL encoding escapes characters that have special meaning in a URL (spaces, &, ?, /, and more) into a %-prefixed safe form, so text can be safely placed in a query string or path; decoding reverses it. Neither is encryption — both are fully reversible with no key, and both run entirely in your browser.
Base64 & URL Encoder/Decoder
Encode or decode text instantly — nothing leaves your browser.
Base64
URL encoding
FAQ
What is Base64 encoding used for?
Base64 converts binary or text data into a plain ASCII string so it can be safely embedded in places that only support text, like JSON payloads, data URIs, email attachments, or config files.
Is Base64 encryption?
No. Base64 is an encoding, not encryption — anyone can decode it back to the original text with no key required. Don't use it to protect sensitive data.
When should I use URL encoding instead of Base64?
Use URL encoding when putting text into a URL's query string or path — it escapes characters like spaces, &, and ? that have special meaning in a URL. Use Base64 when you need a compact, URL-unsafe-character-free representation of arbitrary text or binary data for something like an API token or file embed.
Does this handle emoji and non-English text?
Yes. The Base64 encoder correctly handles full Unicode text, including accented characters and emoji, by encoding the UTF-8 bytes rather than raw character codes.
Related tools
Word / Character Counter · Case Converter ·Password Generator · Timestamp Converter