URL Parser

Paste a URL and see its protocol, username, host, port, path, query parameters and fragment broken out into separate lines, with path segments and parameters decoded.

Use the tool

Why this tool exists

Long links with tracking parameters, nested redirects and encoded paths are hard to read. When a redirect misbehaves or a campaign link is wrong, you need to see exactly what the browser sees: which host, which port, which parameters, and in which order.

This parser uses the browser's own URL implementation, so it follows the same rules as real links. It lists every component and numbers the query parameters, including repeated keys. If you leave off the scheme, https:// is assumed. Because the parsing runs locally, links with tokens or internal host names are not sent anywhere.

How to use it

  1. Paste the URL into the box. A missing scheme is treated as https://.
  2. Run the parser.
  3. Read the components: protocol, host, port, origin, path, search and hash.
  4. Check the decoded path segments and the numbered query parameters.

Frequently asked questions

Why does the port say "(default)"?

When a URL has no explicit port, or uses the default one for its scheme such as 443 for https, the browser reports an empty port. The tool shows "(default)" in that case.

How are repeated query parameters shown?

Each occurrence is listed in order and numbered, so tag=a&tag=b appears as two lines. To get them as JSON, use the Query String Parser.

Does it follow redirects or fetch the page?

No. It only analyses the text of the link. A web page cannot read other sites' responses, so nothing is requested.

What happens with an invalid URL?

You see an "Invalid URL" error. Common causes are spaces, a missing host or unsupported characters. Percent-encode special characters first and try again.