URL Parser
Paste an absolute or supported relative URL to separate its components and inspect encoded query parameters.
How to Use URL Parser
- Paste the complete URL, preserving its encoding and query string.
- Parse it and review the scheme, credentials, hostname, port, path, query entries, and fragment.
- Use the decoded view for understanding values, but preserve correct percent-encoding when rebuilding a production URL.
Understanding URL Components
A URL can include a scheme, authority, optional port, hierarchical path, query, and fragment. Query parameter order and repeated keys can matter to an application, while fragments are handled by the client and are not sent in a normal HTTP request.
Decoded text is easier to read but may not be safe to paste back unchanged. Reserved characters have structural meaning, Unicode hostnames can use Punycode, and relative references need a base URL before they become absolute.
URL Parser Example
Parsing `https://example.com:8443/search?q=red%20shoes&page=2#reviews` separates port 8443, path `/search`, decoded q value `red shoes`, page value `2`, and fragment `reviews`.
Frequently Asked Questions About URL Parser
Is the URL fragment sent to the web server?
No. The fragment after # is normally interpreted by the browser and omitted from the HTTP request.
Can a query parameter appear more than once?
Yes. Repeated keys are valid, and applications can interpret them as a list, first value, or last value.
Why should decoded values be re-encoded before rebuilding a URL?
Spaces, separators, Unicode, and reserved characters need context-appropriate percent-encoding to avoid changing URL structure.