URL Parser
Break a URL into its parts and detect UTM campaign parameters
Enter a URL to parse
Last updated: 2026-10-11
About this tool
A URL is actually made up of seven component parts, and troubleshooting usually needs only one of them. This tool takes a URL apart and lists each piece: protocol, username and password, hostname, port, path, query string and fragment. Query parameters are parsed into a table showing the raw and decoded values side by side. If you work on growth or marketing, it also automatically spots utm_source, utm_medium and utm_campaign so you do not have to scan for them by eye. Parsing happens locally, so URLs with internal hostnames or auth parameters are safe to paste.
Features
Full structural breakdown
Splits the URL into protocol, username, password, hostname, port, path, query string and fragment. Missing parts are explicitly marked as "None" rather than left blank.
Query parameters as a table
The query string becomes a table with the parameter name, raw value and decoded value shown together, so percent-encoded values are obvious.
UTM detection
Automatically surfaces utm_source, utm_medium, utm_campaign, utm_term, utm_content and utm_id with an explanation of each — handy for attribution work.
Default port notice
When no port is specified it says "the protocol default applies" instead of leaving you to guess.
Fragment pitfall warning
If the fragment contains something query-like (common with hash routing), it warns that those parameters are never received by the server.
How to use
- 1
Paste a URL
Paste the full address; results update as you type.
- 2
Inspect the structure
The URL structure section lists each component; missing ones are marked "None".
- 3
Check the parameters
Use the query parameters table to compare raw and decoded values.
- 4
Detect campaign tags
If UTM parameters are present, they are listed with their meanings.
Options
- URL
- The full address to parse. Include the scheme (https://), otherwise the hostname cannot be determined.
Common use cases
- Debugging why a link redirects unexpectedly, by checking the path and parameters
- Verifying that a campaign link has all the required UTM parameters
- Quickly extracting a specific field from a URL with auth parameters
- Confirming whether a fragment is sent to the server (usually it is not)
FAQ
Questions you may have about this tool
Is my URL uploaded?
No. Parsing uses the browser built-in URL API and runs entirely locally with no network requests. Links with internal hostnames or secret parameters are safe to paste.
Why does it say some URLs cannot be parsed?
The most common cause is a missing scheme. A browser address bar will auto-complete something like example.com/path, but a parser needs an explicit https:// to determine the protocol and hostname. Add the scheme and it will work.
What is %E4%B8%AD in a query parameter?
That is the percent-encoding of UTF-8 bytes, which decodes to the Chinese character "中". The query table shows both the raw and decoded value, so you do not have to work it out yourself.
What are UTM parameters for?
They are the campaign attribution parameters agreed on by tools like Google Analytics. utm_source records the source (e.g. newsletter), utm_medium the medium (e.g. email) and utm_campaign the campaign name — used to analyse where traffic comes from and which campaign performs best.
Why can the server not see parameters in the fragment?
Per the HTTP spec, everything after # (the DOM fragment) is used only by the browser and never appears in the request sent to the server. So with hash routing like example.com/#/user?id=1, only the front end can read those parameters.
What does "the protocol default applies" mean for the port?
When a URL omits the port, the browser fills it in by protocol: 80 for http and 443 for https. This tool states that explicitly instead of leaving it blank.
Can it parse IP-based URLs?
Yes. Addresses like http://192.168.1.1:8080/admin are broken down into hostname, port and path normally.
How is this different from the URL encoder tool?
The URL encoder converts between plain text and percent-encoding; this tool splits a URL into structured parts and parses its parameters. One transforms, the other analyses — they are often used together.