Base64 / URL / HTML Encoder & Decoder
Instant results as you type.
Fill in the values — results appear instantly.
Base64, URL and HTML encoding are the three conversions developers reach for daily — embedding data in configs, making text safe inside links, and displaying code in web pages without it executing. This one page does all six directions: pick the operation, paste your text, and the result appears instantly with a copy button. Everything runs in your browser, so tokens, config fragments and snippets you paste here never travel over the network.
How to use it
- Pick the operation — Base64, URL or HTML entities, encode or decode.
- Paste or type your text; the result updates as you type.
- Copy the result with one click. Input and output lengths are shown below it.
Examples
- Base64: Hello → SGVsbG8=
- URL: a b&c=d → a%20b%26c%3Dd
- HTML: <b>bold</b> → <b>bold</b>
Frequently asked questions
- Does this work with emoji and non-English text?
- Yes. Text is converted through UTF-8 bytes, the web standard, so emoji, Punjabi, Hindi, Chinese and every other script encode and decode correctly. Tools built on the browser's older Latin-1 functions fail on such text — this one does not.
- Why did Base64 decoding fail on my string?
- Either the string contains characters outside the Base64 alphabet (letters, digits, +, / and trailing =), or it is truncated, or it is valid Base64 that encodes binary data such as an image rather than text. The tool tells you rather than producing garbage.
- What is the difference between URL encoding and Base64?
- URL encoding escapes only the characters that would break a URL (spaces, &, =, and so on) and keeps the rest readable — use it for query parameters. Base64 re-encodes the entire text into a uniform alphabet, growing it by about a third — use it when a system needs plain ASCII, such as data URIs or basic auth headers.
- Is my text sent to a server?
- No. The conversion happens in your browser as you type — nothing is transmitted, logged or stored. That matters for this tool in particular, because encoded strings often contain tokens or credentials.