How to use Tracking Parameter Stripper
- Paste up to 200 HTTP(S) links, one per line. Unsupported nonblank lines are returned after surrounding whitespace is trimmed, with a note.
- Keep the known tracking list on or turn it off for custom-name-only removal. Enter up to 50 extra names separated by commas/spaces; matching is case-insensitive.
- Inspect the updated cleaned links and removed-name counts. Leave sorting off to retain query-pair order; URL/query encoding can still be normalized.
- Compare destinations before sharing. Known names include some affiliate/referral markers, and a removed value can also control page behavior.
Example: Tracking Parameter Stripper
Remove two UTM parameters and one fbclid while keeping color=black, page=2 and the #sizes fragment.
Options
- The known list
- The list covers the utm_ and pk_ families and the click ids that ad, email and social platforms add, such as gclid, fbclid, msclkid, mc_eid and _hsenc. Switch it off when a link uses one of those names for its own purpose and you would rather keep every parameter you did not name yourself.
- Extra names and sorting
- Extra names are removed alongside the known list, which suits a campaign tag your own team added under a custom name. Sorting rewrites the order of the parameters that stay, so leave it off when the page or a script expects the original order.
- Links, one per line
- Each line is cleaned on its own. Lines that are not http or https links are left as they are.
- Remove the known tracking parameters
- Turn this off to remove only the extra names below.
- Extra parameter names to remove
- Optional. Comma or space separated, for example campaign, source_id.
- Sort the parameters that stay
- Off by default so the order of the parameters you keep does not change.
Supported inputs and limits
- Up to 200 nonblank addresses, 100,000 input characters, 4,096 characters per address and 50 custom names.
- The known policy includes utm_/pk_/_gac prefixes, click IDs and selected affiliate/referral names such as tag and ascsubtag.
- It cannot identify which values are essential to a destination.
- Query values are decoded/reserialized; encoding and URL normalization can change even when order is retained.
- The original # fragment is appended unchanged and is not cleaned.
More details
Unsupported rows remain with notes; surrounding whitespace/line endings can normalize.
No URL is fetched.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
A parameter name does not prove its purpose
A name used for tracking on one site can select a page variant, record a referral or carry a required value on another. The known list deliberately includes some affiliate markers; removing them can change attribution even when the visible page looks the same. Keep the original list, inspect removed names and compare destination behavior before adopting the cleaned copy. Fragment values after # remain outside this tool’s removal policy.
Questions about Tracking Parameter Stripper
Will this remove a filter or page number I still need?
Yes, if the site uses a removed known/custom name for that function. Unlisted color, page or sort pairs remain in order when sorting is off, but query encoding is still normalized. Check the destination after cleaning.
What happens to lines that are not web addresses?
Unsupported nonblank lines are retained with a note after surrounding whitespace is trimmed. Blank rows retain their place, and input line endings are normalized. Only complete supported HTTP(S) links are parsed.
Could the known list remove something useful?
It can, when a site uses one of those names for its own purpose. Names such as trk and _ga are the likeliest to clash. Switch the known list off and type only the names you are sure about if a cleaned link stops behaving.
Is my link list sent anywhere?
No. Every address is parsed and rewritten inside this browser, and the cleaned list stays on your device until you copy it.