How to parse a URL and query string
Split a URL into host, path, hash, and query parameters in your browser with Toolora’s URL Parser.
Why parse a URL
Long tracking links hide useful parts in the query string. Parsing shows protocol, host, path, hash, and each key/value without running the URL.
Steps
1) Open URL Parser at /tools/url-parser. 2) Paste a full URL (include https://). 3) Read protocol, host, path, hash, and query pairs — the article workspace updates as you type when live, otherwise use the run control. 4) Copy the host, path, or query pairs you need. Percent-encoded values can be decoded separately with URL Decode at /tools/url-decode.
Worked example
https://example.com/a/b?x=1&y=two#frag splits into host example.com, path /a/b, query x and y, hash frag. Tracking links with dozens of utm_ parameters become a table instead of a wall of text. The parser does not fetch the URL. Slugify makes a path from a title; this page reads a path that already exists.
Privacy
URLs stay in the browser. Related: /tools/url-encode, /tools/url-decode. Close the tab if the link contains a session token.
Common mistakes
Pasting a URL without https:// may fail or parse oddly — include the scheme. This page does not fetch, redirect, or expand short links. Query decoding is a separate step on URL Decode; the parser shows the raw pairs. Hash fragments never reach a server; they still appear here. Do not click a phishing link “to test” — paste only. Close the tab if the query contains a bearer token.