Unicode URL Percent-Encoder & Query Studio
Percent-encode strings for safe URL inclusion and query strings, or decode percent-encoded URLs back into human-readable Unicode text under RFC 3986.
Parsed URL Query Parameters (4 Key-Value Pairs)
| Parameter Key | Decoded Parameter Value |
|---|---|
| q | Unicode 16.0 |
| Symbols 🚀 | |
| category | web-dev |
| price | €99.99 |
URL Percent-Encoding (RFC 3986) Ready to Run
Using standard urllib.parse in Python.
The Networking Architecture of RFC 3986 Percent-Encoding
The Uniform Resource Identifier (URI) specification was standardized under RFC 3986. By design, valid URI components are strictly restricted to a small subset of 7-bit US-ASCII characters. Any character outside this reserved and unreserved range must be percent-encoded:
A-Z, a-z), digits (0-9), and four safe symbols: hyphen -, underscore _, dot ., and tilde ~.:, /, ?, #, [, ], @, !, $, &, ', (, ), *, +, ,, ;, =.How Multi-Byte UTF-8 Characters are Percent-Encoded
When international scripts (like Arabic, Urdu, Devanagari, or Emojis) are included in a URL, they are first converted into their UTF-8 binary bytes:
A (Unchanged)%20 (or + in forms)%C3%A9%F0%9F%9A%80Frequently Asked Questions (FAQs)
How do I decode double-encoded URLs (e.g. %2520)?+
Paste your string into the input and select "Decode". If the string was double-encoded, decode it twice to revert %2520 to %20 and then to a normal space.
Why should I use encodeURIComponent for query parameters?+
If a query parameter value contains characters like "&" or "=", not encoding them will cause the web server to misinterpret them as delimiters separating new parameters.
Is this URL encoding safe for private API keys and tokens?+
Yes! All encoding and decoding operations run 100% locally in your web browser without sending your URLs across the network.