URL Query Remover

Remove tracking and other query parameters from a URL and report what changed.

  • Runs locally in your browser
  • No upload required

Try it

Cleaned URL
https://example.com/?q=1
Removed
utm_source, fbclid
Kept
q

Supported formats

Input
text, select
Output
number, text

Privacy

Runs entirely in your browser. Your input is never uploaded, stored, or sent to a third party.

Processing
In your browser
Privacy level
Browser only

Removed 2 parameter(s); 1 kept.

How it works

  • Parsed the URL and enumerated its query parameters.
  • Removed the parameters matching the selected set (known campaign tags, your custom list, or all).
  • Re-serialised the URL with the remaining parameters.
  • The tracking preset covers common campaign and click identifiers (utm_*, gclid, fbclid, mc_*, and similar).
  • Removal preserves the order of the parameters that remain and does not touch the path, fragment or other URL components.

Methodology

  1. Parse the URL with the standard URL parser.
  2. Select the parameters to remove: the tracking preset, a custom list, or all.
  3. Re-serialise the URL and report the removed and kept parameters.

Usage

  1. Paste a URL.
  2. Choose the tracking preset, a custom list, or all parameters.
  3. Copy the cleaned URL and review what was removed.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

Tracking tags

jsonSelect to copy
{
  "url": "https://devplace.example/?utm_source=news&q=1&fbclid=abc",
  "params": "",
  "mode": "tracking"
}

Custom parameters

jsonSelect to copy
{
  "url": "https://devplace.example/?q=1&page=2&session=1",
  "params": "session, page",
  "mode": "custom"
}

Strip everything

jsonSelect to copy
{
  "url": "https://devplace.example/path?a=1&b=2#frag",
  "params": "",
  "mode": "all"
}

Limitations

Why clean a link

Campaign parameters such as `utm_*`, `gclid` and `fbclid` are added by marketing tools so analytics can attribute a visit. They are harmless to the destination but leak how you arrived and make links long and ugly to share.

Removing them before sharing gives a short, private URL. Use the custom mode when a site relies on a query parameter for state.

Frequently asked questions

Does it change the path or fragment?
No. Only query parameters are removed; the scheme, host, path and fragment are preserved.
Are tracking parameters always safe to remove?
Almost always for sharing links, but some sites use query parameters for required state. Use the custom mode when in doubt.

Sources

  1. WHATWG URL Standard — WHATWG
  2. MDN Web Docs: URLSearchParams — MDN