URL Encoder/Decoder converts special characters to their percent-encoded equivalents and back. URLs can only contain specific ASCII characters — spaces, symbols, and international characters must be encoded. Also parses full URLs into their component parts.
How to use this tool
Paste text or an encoded URL string.
See both encoded and decoded versions simultaneously.
If you paste a full URL, see it broken down into protocol, host, path, and query parameters.
Each query parameter is displayed in a separate row for easy reading.
Copy the result you need.
Frequently asked questions
Why do URLs need encoding?
URLs can only contain ASCII letters, digits, and a few special characters. Spaces become %20, ampersands become %26, and international characters get encoded. Without encoding, URLs break or get misinterpreted.
What's the difference between encodeURI and encodeURIComponent?
encodeURI encodes a full URL but preserves characters like ?, &, =, and / that have meaning in URLs. encodeURIComponent encodes everything including those characters — use it for individual parameter values, not full URLs.
Why are my URLs showing %20 instead of spaces?
That's correct URL encoding. %20 is the encoded form of a space. Some systems use + instead of %20 for spaces in query strings (application/x-www-form-urlencoded format).
How do I encode international characters in URLs?
They're encoded as UTF-8 bytes in percent-encoding. For example, ü becomes %C3%BC. Modern browsers display the decoded version in the address bar but send the encoded version to servers.