URL Encoder & Decoder
Percent-encode special characters for safe URL transmission, or decode encoded URLs back to readable text.
Your result will appear here…
AD 468×60
How to Use
Three encoding modes are available:
- Encode — encodes a component (e.g., a query parameter value). Encodes all characters except
A–Z a–z 0–9 - _ . ! ~ * ' ( ). - Decode — reverses percent-encoding, converting
%20→ space, etc. - Encode Full URL — encodes an entire URL, preserving the structural characters (
: / ? # [ ] @ ! $ & ' ( ) * + , ; =).
What is URL Encoding?
URL encoding (also called percent-encoding) converts characters that are not allowed in URLs into a percent sign followed by two hexadecimal digits. For example, a space becomes %20, and & becomes %26. This ensures special characters don't interfere with URL parsing.
Common Use Cases
- Encoding query string parameter values before appending to a URL
- Decoding URLs received in logs or network traffic for readability
- Encoding form data for submission via HTTP GET
- Debugging API requests with percent-encoded parameters
Frequently Asked Questions
What's the difference between encodeURI and encodeURIComponent?
encodeURIComponent encodes everything except unreserved characters, making it suitable for encoding individual query parameter values. encodeURI additionally preserves characters that have special meaning in a full URL (: / ? # @ etc.), so it's used for encoding complete URLs.Why is a space encoded as %20 sometimes and + other times?
In application/x-www-form-urlencoded format (HTML forms), spaces are encoded as
+. In standard percent-encoding (RFC 3986), spaces are encoded as %20. Both are valid in different contexts; most modern APIs prefer %20.Is my data safe when using this tool?
Yes — all processing happens locally in your browser. Nothing is transmitted to our servers.