URL Tracking Param Cleaner
Strip utm_*, fbclid, gclid and 30+ other tracking params from a URL — paste, get a clean shareable link back.
https://example.com/article?id=42
- utm_source=newsletter
- utm_medium=email
- fbclid=abc123
Cleaning happens entirely in the browser. Useful before sharing in Slack, email, or anywhere you don't want the recipient to look like they came from your campaign.
How to use
- Paste the cluttered URL into the input.
- Pick a preset or edit the param list — append
*to a name for a prefix match (e.g.utm_*). - Copy the clean URL and share without the tracking tail.
About this tool
ShowHide
Strips the analytics, ad-click and share parameters that platforms staple onto a link before you pass it on. It knows the whole UTM family, Google's gclid, gbraid, wbraid and dclid, Facebook's fbclid, Microsoft's msclkid, Yandex's yclid, Mailchimp's mc_eid and mc_cid, TikTok's ttclid, Twitter's twclid, Instagram's igshid, HubSpot's _hsenc, Marketo's mkt_tok, Pinterest's epik, Matomo's pk_* set and more, with three presets running from "strip everything" to ads only or analytics only, and an editable list for anything your own stack adds.
These parameters are appended by the sharing surface rather than the destination, which is why a link copied out of an app is longer than the same link typed by hand. The identifiers are opaque and per-click: fbclid ties a visit to the specific impression it came from, and two people sharing "the same" article are actually passing round two different URLs. That is also why stripping them almost never breaks anything — the destination page ignores parameters it did not put there, and the site's own routing lives in the path.
Almost never is not never, and the exception is worth knowing. A few sites do read utm_source to vary content or attribute a signup, and some booking and checkout flows carry state in parameters that look tracker-ish but are not. If a cleaned link lands somewhere unexpected, try the original before assuming the site is broken.
What this does not do is make a link private. Tracking survives in several places a query string cannot reach: the Referer header tells the destination where you came from regardless, a shortened or wrapped link resolves through a redirector that logs the click before handing over a clean URL, and some platforms have moved identifiers into the path or the fragment where they look like part of the address. Cleaning a URL stops the parameter travelling onward when you paste it into a group chat, which is a real and worthwhile effect, and it is not the same thing as not being tracked.
Frequently asked questions
Does it preserve regular query params?
Yes. Only the params you list are removed. ?id=42&utm_source=x becomes ?id=42 — the substantive part of the URL is untouched.
What's the wildcard for?
Add utm_* to remove every parameter that starts with utm_. Useful when a platform adds new UTM-family names (utm_id, utm_marketing_tactic) faster than you can enumerate them.
Is it always safe to strip these before sharing a link?
For the person receiving it, almost always: tracking parameters exist to attribute the click, not to decide what the page shows. The exception is a link where something that looks like tracking actually carries state — some campaign landing pages, referral programmes and email links encode an identity, a discount or a session in a parameter. If the destination is a form or an offer, open the cleaned link once before sending it.
Does removing them protect my own privacy?
Only partly. It stops that particular link from carrying an identifier onward to whoever you send it to, which is the main benefit. The destination site still sees your address and its own cookies when you visit, and a shortened link can put the tracking back during the redirect. Treat it as a courtesy to the recipient rather than as a shield for yourself.
Related tools
Relative URL Resolver (RFC 3986)
Resolve a relative reference against a base URI by RFC 3986, with the dot-segment trace and the browser’s answer beside it.
Network
URL Query Builder
Build URLs by combining a base address with editable key-value query parameters — each pair toggleable, properly percent-encoded.
Network
URI Template Expander (RFC 6570)
Expand RFC 6570 URI templates with your own variables — all four levels, with path, query, fragment and label operators and explode modifiers.
Network
OAuth 2.0 PKCE Generator
Generate code_verifier + S256/plain code_challenge for OAuth 2.0 PKCE (RFC 7636).
Network
mailto: Link Builder
Build a mailto: URL with To, Cc, Bcc, subject, and body — RFC 6068 percent-encoded, ready to drop into an <a> tag.
Network
HTTP Status Code Reference
Searchable list of every HTTP status code (1xx-5xx) with summary, RFC, when to use, and common pitfalls.
Network