URL Parser & Query String Inspector
Break any URL into protocol, host, port, path, query parameters, and fragment — then edit any part and copy the rebuilt URL.
Your Data Never Leaves Your Device
Every tool runs entirely in your browser. Nothing you type is uploaded, stored, or logged on our servers.
The URL Parser takes a long, unreadable link and breaks it into its real parts — protocol, credentials, host, port, path, every query parameter, and the fragment. Parameter values are percent-decoded automatically, so %20 reads as a space instead of noise.
Every field is editable. Change a parameter, add one, delete one, or rewrite the path, and the rebuilt URL updates as you go with correct re-encoding. Repeated keys such as ?tag=a&tag=b are preserved rather than collapsed — a common failure in simpler parsers. Analytics and ad-tracking parameters are highlighted, and a single click strips all of them for a clean link to share.
Parsing uses the browser's native URL API and runs entirely on your machine. That is worth knowing here specifically: OAuth redirects, password-reset links, and signed URLs routinely carry secrets in their query strings, and none of it is uploaded anywhere.
FAQ
A URL is scheme://user:password@host:port/path?query#fragment. In https://shop.example.com:443/products?id=7#reviews the scheme is https, the host is shop.example.com, the port is 443, the path is /products, the query string is id=7, and the fragment is reviews. Only the scheme and host are always required.
Paste the URL and the parameter table shows every key with its value already percent-decoded, so %20 appears as a space and %40 as @. Edit any value and the rebuilt URL re-encodes it correctly for you.
The query string (after ?) is sent to the server and typically drives what content is returned. The fragment (after #) is never sent to the server — the browser uses it locally to scroll to an anchor or drive client-side routing.
Yes. Parsing happens entirely in your browser with the native URL API — nothing is uploaded, logged, or stored. That matters here, because OAuth redirect URLs, password-reset links, and signed S3 URLs routinely carry secrets in their query strings.
Analytics and ad-attribution parameters such as utm_source, utm_medium, utm_campaign, gclid, fbclid, msclkid, mc_eid, and similar. These are read by marketing platforms, not by the page itself, so removing them almost always leaves you with a shorter link that loads exactly the same content.
Yes. Parameters are kept as an ordered list rather than collapsed into an object, so duplicate keys are all preserved and survive editing and rebuilding — a common failure in simpler parsers.
The subdomain and domain split is a simple last-two-labels guess. Correctly separating co.uk, com.au, and similar multi-part suffixes requires the Public Suffix List, which is not bundled here. The Host field is always exact — treat the split as a hint.
Yes. If no scheme is present, https:// is assumed so the URL still parses, and the page tells you when that assumption was made.