URL Parser
Parse a URL into protocol, host, path, query and related components to help inspect links and troubleshoot web addresses.
Your result will appear here.
URL Parser online
Split a URL into its components — scheme, host, port, path, query parameters and fragment — each on its own line, so you can see exactly what a link is made of.
How to use this tool
- Paste a full URL into the input box.
- Click Run Tool. The URL is parsed with the browser's URL parser and its components are listed.
- Inspect the query parameters one by one — tracking tags and malformed values stand out immediately.
Common uses
Untangling a marketing link to see its UTM parameters, debugging a callback or redirect URL that an API rejected, checking a URL from an email before trusting it, and learning URL anatomy from real examples.
How it works
The parser is the browser's own URL implementation — the same rules your code and every link click obey. It separates the scheme, host and port, the path, the query string (broken into individual key/value pairs) and the fragment after #. It also normalises as it parses: a missing port shows as the scheme's default, percent-escapes stay as written in the components, and a URL that cannot be parsed at all is reported rather than repaired.
Worked example
Parse https://shop.example.com:8443/orders/list?status=open&utm_source=email#top and the components read: scheme https, host shop.example.com, port 8443, path /orders/list, parameters status=open and utm_source=email, fragment top. The exercise pays off most on ugly links — a 300-character analytics URL is usually a short real address wearing nine tracking parameters, and the parser lays them out to be deleted one by one.
Privacy and browser processing
Parsing runs in your browser with JavaScript — the URL is inspected locally, never visited or uploaded.
Frequently asked questions
What happens to a URL without a scheme?
It fails to parse — the parser requires an absolute URL with its protocol. Add https:// in front of a bare domain-and-path and it parses. That strictness is shared with browsers: "example.com/page" in an address bar is a search-and-guess, not a URL.
Are the query values decoded for me?
Components are shown as the parser exposes them; percent-encoded values appear encoded, so a value like q=fish%20%26%20chips can be run through the URL Encoder/Decoder here to read it.
Why does the port sometimes not show?
A port equal to the scheme's default (443 for https, 80 for http) is normalised away — https://example.com:443 and https://example.com are the same address, and the parser reports the canonical form.
Can it parse URLs with usernames or non-ASCII hosts?
Yes — credentials in the authority (user:pass@host) are exposed as their own components, and internationalised hostnames are shown in their punycode form (xn--…), which is what DNS actually resolves.
Is the URL I paste sent anywhere?
No. Parsing is done by your browser locally; the URL is inspected, never visited or uploaded.