Which parameters are removed?

The utm_* family plus known click identifiers: fbclid, gclid, gbraid, wbraid, msclkid, mc_eid, igshid, twclid and similar. Content-bearing parameters are left untouched.

Will cleaning break the link?

Almost never — tracking parameters are ignored by the page itself. Test after cleaning if the site is one you know behaves unusually.

Does this stop the site from tracking me?

No. It removes the identifier carried in the URL. Cookies, fingerprinting and server-side logging are unaffected.

Should I strip tracking from my own campaign links?

No — those parameters are how you measure the campaign. Clean links you share personally or publish in documentation, not links inside the campaign itself.

URL & Links🔒 Browser (client-side)API available📴 Works offlinebeginner

URL Tracking Cleaner

Strips tracking parameters, affiliate tokens, and invasive marketing queries from URLs to create clean, canonical links.

Data stays in your browser

Ready to runInstant execution

All tools →

Result

—

What does this tool do?

Strips tracking parameters, affiliate tokens, and invasive marketing queries from URLs to create clean, canonical links.

Why would I use it?

You want to share clean links without cluttering them with utm_*, fbclid, or gclid tracking tokens.
You are archiving bookmarks or indexing canonical web destinations.
You want to protect user privacy by eliminating cross-site tracking fingerprints.

Real-life example

Input

https://example.com/product?utm_source=newsletter&fbclid=IwAR3x&id=42

Output

https://example.com/product?id=42 (Removed: utm_source, fbclid)

Preserves functional application parameters (like id=42) while stripping trackers.

Input → Process → Output → Next

Input: Paste any URL containing tracking query parameters.
Process: Parses URL query keys and strips known tracking tokens (utm_*, fbclid, gclid, mc_eid, etc.).
Output: Clean URL and a summary list of removed tracking parameters.
Next action: Copy the clean link or shorten it into a branded short URL on YAS.SH.

Common mistakes

Assuming all query parameters are trackers (some parameters are required for page state).
Modifying URL encoded path characters.
Forgetting to verify the destination after cleaning.

What the result means

A privacy-first, normalized URL stripped of surveillance and tracking telemetry.

Privacy & security

Your input is processed entirely in your browser and never sent to a YAS server.

API

Endpoint

POST https://yas.sh/api/v1/tools/url-cleaner

Request Header

Content-Type: application/json

cURL

curl -X POST "https://yas.sh/api/v1/tools/url-cleaner" \
  -H "Content-Type: application/json" \
  -d '{"input":"https://example.com/page?utm_source=twitter&fbclid=123"}'

JavaScript

const res = await fetch("https://yas.sh/api/v1/tools/url-cleaner", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
  "input": "https://example.com/page?utm_source=twitter&fbclid=123"
}),
});
const data = await res.json();

Python

import requests

r = requests.post("https://yas.sh/api/v1/tools/url-cleaner", json={"input":"https://example.com/page?utm_source=twitter&fbclid=123"})
data = r.json()

Field	Type	Required	Description
input	string	Yes	URL with tracking params

Success response

{ "slug": "url-cleaner", "cleanedUrl": "https://example.com/page", "removedParams": ["utm_source", "fbclid"] }

Strip marketing tracking parameters from URLs.

Error responses

400 VALIDATION_ERROR — invalid input or unsupported option.
413 PAYLOAD_TOO_LARGE — input exceeds the 64 KB limit.
429 RATE_LIMIT_EXCEEDED — rate limit exceeded (60 req/min).

Limits

Maximum input: 64 KB per request.
Rate limit: 60 requests/min per IP address.
Authenticated accounts benefit from higher tier quotas.

How URL Tracking Cleaner works

Cleaning removes query parameters that exist for attribution rather than for content: the utm_* family, Facebook's fbclid, Google's gclid and gbraid/wbraid, Microsoft's msclkid, mc_eid from Mailchimp, and a long tail of platform-specific identifiers. Each is matched by exact name or by a known prefix pattern, and the remaining parameters are re-serialized in their original order.

The distinction that matters is between parameters that identify the click and parameters that select the content. Removing utm_source changes nothing about the page returned; removing an id or q parameter changes what you get, or breaks the URL entirely. That is why cleaning works from a known list of tracking names rather than from a heuristic about which parameters look unnecessary.

When to use it: real-world scenarios

Sharing a link without passing on an identifier

A URL copied from an email or social feed carries a click identifier tied to you. Cleaning it before sharing prevents that identifier from being attributed to everyone who clicks.

Canonicalising URLs for analytics or storage

The same page arriving with dozens of parameter combinations fragments reporting. Normalising on the clean URL consolidates it.

Preparing links for documentation

Tracking parameters in a wiki or README persist for years and attribute future traffic to a campaign that ended long ago.

Deduplicating a crawl or bookmark list

Stripping tracking parameters collapses hundreds of apparent URLs to the handful of distinct pages they actually represent.

Pro tips

Verify the page still loads after cleaning. A minority of sites incorrectly depend on a parameter you would assume is tracking.
Clean URLs before setting canonical tags or adding them to a sitemap, so search engines are not offered parameter variants.
Removing gclid breaks Google Ads conversion attribution for that click — do not clean links inside your own ad campaigns, only links you share.
Fragments can carry tracking too. Check anything after # as well as the query string.

Limitations and edge cases

What this tool deliberately does not do, and where it will disagree with other implementations.

Only known tracking parameter names are removed; a platform's newly introduced identifier is not recognised until the list is updated.
Some sites route on parameters that resemble tracking, so cleaning can occasionally alter behaviour.
Server-side tracking, redirect-based attribution and pixels are unaffected — this only cleans the URL string.
It does not follow redirects, so a shortener that adds tracking downstream is not addressed.

Frequently asked questions

Which parameters are removed?: The utm_* family plus known click identifiers: fbclid, gclid, gbraid, wbraid, msclkid, mc_eid, igshid, twclid and similar. Content-bearing parameters are left untouched.
Will cleaning break the link?: Almost never — tracking parameters are ignored by the page itself. Test after cleaning if the site is one you know behaves unusually.
Does this stop the site from tracking me?: No. It removes the identifier carried in the URL. Cookies, fingerprinting and server-side logging are unaffected.
Should I strip tracking from my own campaign links?: No — those parameters are how you measure the campaign. Clean links you share personally or publish in documentation, not links inside the campaign itself.