How to parse a URL
- Paste a full URL, or just a query string such as
?id=7&sort=asc. - The URL is split into protocol, username, host, port, path, query, fragment and origin, each shown on its own row.
- Every query parameter appears in a table with its value fully decoded. Repeated keys are listed separately.
- Copy the parameters as JSON for use in code or tests, or copy a clean version of the URL with tracking parameters removed.
Why parse URLs?
Long marketing and app links are hard to read. A parser shows at a glance which campaign tags are attached, which redirect target is hidden in a ?url= parameter, which port a service runs on, or whether a value is double-encoded. It is also a quick way to turn a query string into a JSON object for a test fixture or API call.
The tracking tag marks common analytics parameters such as utm_source, utm_medium, utm_campaign, gclid, fbclid, msclkid and Mailchimp and HubSpot IDs. Removing them before you share a link keeps it short and avoids passing on information about where you clicked.
Parsing uses the browser's standard URL API, so results match what your JavaScript code sees. Nothing you paste leaves your browser.
FAQ
What is the difference between host and origin?
The host is the domain name and port. The origin adds the protocol, as in https://example.com:8080, and is what browsers use for security rules like CORS.
How are repeated parameters handled?
Each occurrence is shown in the table. In the JSON copy, repeated keys become arrays, for example {"tag": ["a", "b"]}.
Is removing UTM parameters safe?
Yes, for normal links. UTM parameters are only read by analytics tools and do not change the page you see.