URL Encoder
Safely encode or decode special characters and multilingual text in URLs. Supports query strings and IRI processing.
Integrity Verified
Syntactically valid URL sequence. Data processed successfully.
URL Encoder Use Cases
Frequently Asked Questions
Q. Why do spaces become "+" sometimes and "%20" other times?
"+" is traditionally used in URL query parameters (form data), while "%20" is the standard percent-encoding used in URI paths.
Q. Why does my decoded text look mangled?
This usually happens if the text was encoded using a different character set instead of UTF-8, or if it was double-encoded.
Q. What is IDN and Punycode?
Internationalized Domain Names (IDN) allow domains in local languages. Punycode (e.g., xn--) is how these domains are encoded so DNS servers can understand them.
Q. Should I encode the whole URL or just parameters?
Only encode the parameter values. Encoding the entire URL will break the protocol (http://) and path separators (/).
Q. What is double-encoding?
It occurs when an already encoded string is encoded again (e.g., "%20" becomes "%2520"). Our tool can help detect and reverse this.
URL Reserved Characters
| Char | Encoding | Usage |
|---|---|---|
Space | %20 or + | Word separation |
! | %21 | Reserved |
# | %23 | Fragment identifier |
& | %26 | Query parameter separator |
+ | %2B | Space in queries / Reserved |
/ | %2F | Path separator |
= | %3D | Query parameter value assignment |
? | %3F | Query string indicator |
[ | %5B | IPv6 / Array notation |
Korean/UTF-8 | %XX%XX... | Multilingual text |
These characters have special meaning in URLs and must be encoded when used as data.
Multilingual URL (IRI) Handling
How non-ASCII characters are handled in different parts of a URL.
Domain
Path
β οΈ Older systems may not support IRI.
Key Features
- Full URL vs Value encoding modes
- Automatic double-encoding detection
- Punycode support for IDN
- 100% local browser processing
Professional URL Encoder and Decoder. Safely encode or decode special characters and multilingual text in URLs.