URL parser

Paste a long link to see its parts and every query parameter, decoded. Edit the parameters and copy the new URL.

ParameterValueRemove

This free URL decoder and query string builder works in your browser. All inputs and calculations run locally on your device without server uploads; details on browser processing and storage are set out in the privacy policy.

The parts of a URL

PartExample
Protocolhttps:
Host nameshop.example.com
Port:8080, usually left out
Path/products/shoes
Query string?size=9&colour=red
Fragment#reviews, never sent to the server

Marketing links carry parameters such as utm_source, utm_medium, fbclid and gclid. Remove them with the × buttons and copy the rebuilt URL to share a clean link. Values are decoded for reading and encoded again when the URL is rebuilt.

Worked example: Dissecting a port-mapped URL and stripping UTM/ad-click tracking parameters

Paste this marketing link into the URL Parser to inspect its RFC 3986 components and clean its query string:

https://shop.example.co.uk:8443/catalog/shoes?color=navy%20blue&size=9&utm_source=newsletter&fbclid=IwAR19x#reviews
  • Scheme (Protocol): https:
  • Hostname & Port: Host = shop.example.co.uk, Port = 8443 (Origin = https://shop.example.co.uk:8443).
  • Path: /catalog/shoes
  • Decoded query parameters (4 keys): color = "navy blue" (%20 decoded), size = "9", utm_source = "newsletter", and fbclid = "IwAR19x".
  • Fragment (Hash): #reviews
  • After clicking Remove tracking parameters: Strips utm_*, fbclid, gclid, and msclkid while keeping functional product filters (color and size), producing: https://shop.example.co.uk:8443/catalog/shoes?color=navy+blue&size=9#reviews.

Limits and what this tool cannot do

  • Does not follow shortlinks (bit.ly, t.co, lnkd.in) over the network: Because this page makes zero external network requests, it parses the literal URL string you paste. To strip tracking parameters from a shortened link, open or expand the shortlink first and paste the destination URL.
  • Requires a scheme (https:// or http://) or valid URL structure: Relative paths like /catalog/shoes?size=9 have no protocol or host unless resolved against a base origin.
  • Hash-router query strings (/#/page?id=1): In single-page apps that place ?id=1 *after* the # symbol, standard WHATWG new URL() parsers treat everything after # as part of url.hash rather than url.search.

Questions

Why is a parameter shown twice?

A URL can repeat the same name, for example ?tag=a&tag=b. Both are kept.

Do I need to type https://?

No. It is added if missing.

Is the URL visited?

No. It is only parsed in your browser.

Is the #hash fragment ever sent to the web server in an HTTP request?

No. Browsers strip the #fragment before sending the HTTP request over the network; the fragment is processed strictly on the client side to scroll to an element ID or route a single-page application.

Which tracking parameters are removed by the clean button?

It removes Google Analytics (utm_source, utm_medium, utm_campaign, utm_term, utm_content, _ga, _gl), Google Ads (gclid, gclsrc), Meta/Facebook (fbclid), Microsoft (msclkid), Mailchimp (mc_cid, mc_eid), and HubSpot (_hsenc, _hsmi) tracking keys.

What happens if a URL has the same query parameter key twice (like ?tag=js&tag=web)?

Both occurrences are valid under the WHATWG URL standard (searchParams.getAll('tag')) and are listed as separate rows in the parameter editor.

Last reviewed .

Related converters and guides