Remove UTM parameters from a URL
Strip campaign tracking parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) from a URL while keeping the parameters your app actually needs.
Opens URL Parser with this example preloaded. Everything runs locally in your browser.
The problem
Shared links often carry UTM tracking that is noise at best and privacy-leaking at worst. Parse the URL, drop the utm_* keys, and keep functional parameters like id or page intact.
Sample input
https://example.com/pricing?utm_source=newsletter&utm_medium=email&utm_campaign=spring&id=123Expected output
https://example.com/pricing?id=123All five utm_* parameters are removed; the functional id=123 parameter is preserved.
How to do it
- Paste the URL.
- Identify the tracking parameters in the query string.
- Remove
utm_source,utm_medium,utm_campaign,utm_term, andutm_content. - Keep the business parameters the page needs.
- Copy the cleaned URL.
Common mistakes
- Removing important non-UTM parameters by accident.
- Breaking an encoded redirect URL nested in a parameter.
- Dropping the fragment when you only meant to drop tracking.
- Missing duplicate parameters.
- Sharing URLs that still carry unnecessary tracking data.
Related tools
Related guides
FAQ
What are UTM parameters?
Query parameters beginning with utm_ that analytics tools use to attribute traffic to a campaign, source, and medium.
Is it safe to remove UTM parameters?
Usually yes. UTM parameters are for analytics and normally do not affect what the page renders, so removing them is safe for sharing.
Which UTM parameters can I remove?
The standard set: utm_source, utm_medium, utm_campaign, utm_term, and utm_content.
Will removing UTM parameters change the page?
In almost all cases no — they are tracking only. Verify if a specific app reads them for something functional.
Can I keep some query parameters?
Yes. Remove only the utm_ keys and keep any parameters the page actually uses.
Cleaning the URL happens locally in your browser. The link is never uploaded.
Practical example and expected result
Strip campaign tracking parameters ( utm_source , utm_medium , utm_campaign , utm_term , utm_content ) from a URL while keeping the parameters your app actually needs. In practice, this is most useful when you need a quick, repeatable check on a URL or query string before adding it to a ticket, pull request, test fixture, or support note.
A realistic input for this workflow is https://example.com/pricing?utm_source=newsletter&utm_medium=email&utm_campaign=spring&id=123. The expected result should resemble https://example.com/pricing?id=123, with the same important values preserved.
Troubleshooting checklist
- Confirm you copied the complete URL or query string and not only a partial line or truncated preview.
- Run the local tool once with a safe sample, then repeat with the real data only if your team policy allows it.
- Check quoting, escaping, whitespace, encoding, timestamps, and environment-specific values before trusting the result.
- Before sharing output, remove secrets, tokens, cookies, customer data, and production hostnames that are not needed for the review.
Next useful steps
- Remove UTM parameters from this URL → for a related validation or follow-up step.
- Encode and decode URL components for a related validation or follow-up step.
- Convert cURL commands for a related validation or follow-up step.
- Use Magic Box when you are not sure which tool should handle the next artifact.
Review checklist before sharing the result
For Remove UTM parameters from a URL, the safest workflow is to test with a small sample, confirm the output shape, then repeat with the real artifact only when needed. Keep the original input open until you verify that no value was dropped, decoded twice, sorted unexpectedly, or changed from text into a different type.
Before copying the result into a pull request, issue, chat thread, or support ticket, scan for private values. Replace real IDs, bearer tokens, session cookies, email addresses, internal hostnames, and customer data with placeholders. If another tool is listed above, use it as the second pass rather than manually editing complex output.
- Keep one line of context explaining why the transformation was needed.
- Preserve enough sample structure for a reviewer to reproduce the result locally.
- Note any assumptions about encoding, timezone, delimiter, schema version, or runtime environment.