URL & Query String Encoder, Decoder & Inspector
High-precision client-side URL encoder and decoder. Seamlessly toggles between full URI and component encoding, recursively resolves multi-encoded parameters, and breaks down query strings into structured key-value tables.
| Parameter Key | Decoded Value |
|---|
Comprehensive Guide: Understanding URL Encoding, Percent-Encoding & Deep Decoding
Uniform Resource Identifiers (URIs) demand strict syntax conformance across internet routers, proxies, and web gateways. Master character encoding and avoid corrupted network requests with client-side validation.
encodeURIComponent vs. encodeURI: When to Use Which?
encodeURI() is designed for entire URLs, preserving protocol schemes (https://), domain names, path slashes (/), and query delimiters (? & =). In contrast, encodeURIComponent() encodes every reserved character, making it ideal for individual query parameter values (such as nested redirect URLs, JSON payloads, or search terms).
Solving the "Double-Encoding" Problem (%2520)
When data passes through multiple backend layers, reverse proxies (Nginx), or client libraries, percent characters (%) often get re-encoded into %25. A space (" ") initially encoded as %20 becomes %2520. Our Recursive Deep Decode engine detects these multi-tier artifacts and automatically resolves them down to the true source text in a single client-side pass.
RFC 3986 Standards vs. Form URL-Encoded (+)
RFC 3986 specifies %20 as the canonical representation for spaces in URI paths. However, legacy HTML forms and application/x-www-form-urlencoded POST bodies historically substitute spaces with plus signs (+). OmniTools allows you to toggle space formatting dynamically to match your target API specification.
Frequently Asked Questions (FAQ)
Why does my decoded URL still look encoded (e.g. %20)?
Your URL was likely double-encoded (%2520). Enable the "Recursive Deep Decode" checkbox in the options bar above. The engine will loop through encoded layers until the original text is completely restored.
What characters are considered reserved in URLs?
Characters with defined structural purposes include : / ? # [ ] @ ! $ & ' ( ) * + , ; =. If used as raw data inside query values, they must be percent-encoded to prevent URL truncation or parser confusion.
Is my URL or query payload sent to any backend servers?
Never. OmniTools operates entirely in your browser memory using native JavaScript Web APIs. Zero network requests, analytics trackers, or server logs are generated.