08 / url-encoder
free online tool
URL Encoder / Decoder
Encode or decode URLs and query strings instantly.
how to use
- 01
Paste your URL or text into the input field.
- 02
Click 'Encode' to percent-encode special characters, or 'Decode' to reverse.
- 03
Copy the result with the Copy button.
about
What is this tool?
URL encoding (percent-encoding) converts characters that are not allowed in URLs into a format that can be transmitted safely. For example, a space becomes %20. This tool handles both encoding and decoding using JavaScript's encodeURIComponent and decodeURIComponent functions.
why use this tool
- -Essential when constructing API query parameters.
- -Decode garbled URLs to understand their contents.
- -Handles the full UTF-8 character set.
- -No server required — works instantly in your browser.
features
- -Encode: converts unsafe characters to percent-encoded format.
- -Decode: reverses percent-encoding to readable text.
- -Handles Unicode and international characters.
- -One-click copy to clipboard.
comparison
URL Encoding Examples
| Original Text | Encoded Output |
|---|---|
| Hello World | Hello%20World |
| user@email.com | user%40email.com |
| price=100&tax=10 | price%3D100%26tax%3D10 |
| path/to/file | path%2Fto%2Ffile |
All processing happens entirely in your browser using JavaScript. No files, text, or data are ever sent to a server. Your data stays on your device.
✦ tip from dragontail
When building Dragontail's API integrations, I ran into a frustrating bug where Korean characters in search queries were breaking URLs. URL-encoding every query parameter before appending it to a URL string fixed it instantly. If you're constructing URLs dynamically in JavaScript, always run user-supplied values through encodeURIComponent — never trust raw input.
faq
What is the difference between encodeURI and encodeURIComponent?
encodeURI encodes a full URL, preserving characters like / and ?. encodeURIComponent encodes individual parameters, encoding those characters too. This tool uses encodeURIComponent.
Why do spaces appear as + or %20?
%20 is standard percent-encoding. Some systems use + for spaces in query strings (application/x-www-form-urlencoded format).
Can I use this for JWT tokens?
JWT uses Base64URL encoding, not percent-encoding. Use the Base64 Encoder tool instead.