URL Parser — Break a URL into Its Parts

Paste a URL to see every component and decoded query parameter — then edit, add or remove parameters and copy the rebuilt URL.

Runs in your browserUpdated

Query parameters

Your data never leaves your computer. All processing happens 100% locally in your browser.

How to use the URL Parser

  1. Paste a URL — the scheme is optional.
  2. Read the components: protocol, host, port, path, query and fragment.
  3. Edit, add or remove query parameters; the rebuilt URL updates instantly.
  4. Remove UTM and click-ID tracking with one click, then copy the clean URL.

Anatomy of a URL

https://user@shop.example.com:8443/en/products?sort=price&q=keyboard#reviews
└─┬─┘   └┬─┘ └──────┬───────┘ └┬─┘└─────┬────┘ └────────┬───────────┘ └──┬──┘
scheme  user      host       port    path            query           fragment
PartNotes
Schemehttps:, http:, ftp:, mailto:…
HostDomain or IP; internationalised domains are shown in Punycode (xn--…)
PortOmitted when it is the default (443 for HTTPS, 80 for HTTP)
PathCase-sensitive on most servers
Querykey=value pairs joined by &; keys can repeat
FragmentAfter #; never sent to the server

Encoding

Spaces and special characters in query values are percent-encoded (%20) or, in form encoding, written as +. The parameter table shows the decoded values; the rebuilt URL re-encodes them correctly, so you can edit values in plain text. For encoding single strings, use the URL encoder.

Cleaning tracking parameters

Marketing links often carry utm_*, gclid, fbclid or mc_eid parameters. They do not change the page content, so remove them before sharing links or using them as canonical URLs. To create tracked links on purpose, use the UTM builder.

Credentials in URLs (user:password@host) are deprecated and visible in logs and browser history — avoid them.

Tools that pair well with the URL Parser

  • Redirect Checker — Follow a URL hop by hop to see every redirect, its status code and timing, and check that the http, https, www and non-www versions of your domain all end at one canonical address.
  • HTTP Header Checker — Fetch any URL and see exactly what the server sends back — status code, redirect chain and every response header, with a plain-English explanation of the ones that matter for SEO, caching and security.
  • Slug Generator — Convert any title into a clean, lowercase URL slug — with proper transliteration of accents, umlauts and Cyrillic, optional stop-word removal and a bulk mode for whole lists.
  • MIME Type Lookup — Search 200+ file extensions and MIME types — .webp, .woff2, .webmanifest, application/wasm … — or drop a file to detect its real type from its first bytes.

Frequently asked questions

Is the fragment (#) sent to the server?
No. Browsers keep everything after # on the client; servers never see it.
Can a query parameter appear twice?
Yes, for example ?tag=a&tag=b. Each occurrence appears as its own row and is kept when rebuilding.
Is my URL sent anywhere?
No. Parsing uses the browser’s built-in URL API.

Related tools