URL Parser
Frequently Asked Questions
Everything you need to know about URL parsing
What parts make up a URL?
A URL is made up of several parts: the protocol (e.g. https:), the host (domain plus optional port), the path that identifies the resource, the query string with its parameters (after the ?) and the fragment (after the #). This tool separates them all automatically using the browser native URL API.
Why do I need to include the protocol?
The browser URL API requires an absolute, valid URL, so it must include a protocol such as https:// or http://. If you paste only "example.com/page" without a protocol, parsing will fail. Add https:// at the beginning to get the correct result.
Are the query parameters decoded?
Yes. Query string parameter values are automatically decoded from percent-encoding (e.g. %20 becomes a space) thanks to URLSearchParams. This way you see the real, human-readable values without manually decoding %XX sequences.
What parts is a web address made of?
The protocol, the host with its optional port, the path that points at the resource, the query with the parameters after the question mark, and the fragment after the hash.
Why do I have to type the protocol as well?
Because the parsing uses the browser function, and that only accepts absolute addresses. Typing the domain name on its own gets you nowhere: adding https in front is enough.
Are the parameters decoded?
Yes, the values of the query are shown in clear, so the percent sequences become readable again and the code for a space turns back into an actual space.