Change the copy, keep the purpose clear
Remove UTM Parameters from a Sharing Copy
Remove recognized UTM fields when a sharing copy no longer needs those campaign labels. Keep the original measurement record and preserve the query details that still belong to the destination.
Use the URL Cleaner for a browser-based text transformation. This guide focuses on UTM removal across channels, without requiring a platform-specific cleaning rule or connecting an analytics account.
Remove named fields rather than the whole query
To remove UTM parameters, identify the selected query-key names and remove their segments from a copy of the URL. Do not delete everything after the question mark. The same query can also contain a search term, content identifier, language choice, product variant, or page number that the recipient needs. A fragment after # can point to a useful section and should remain too. This cleaner takes the narrower approach: selected known UTM fields can be removed while retained raw segments stay in place. Start by deciding why the new copy should omit those campaign labels instead of treating a shorter address as the goal by itself.
The distinction matters even when the page appears to open without its query. A homepage, default edition, or first search page may look plausible while no longer matching the original reference. The cleaner does not fetch the destination to compare those views, and it cannot infer a server contract from a field name. Keep uncertain parameters rather than guessing. Unknown names are preserved by default, as are reserved destination and affiliate fields. Your task is to remove an agreed attribution layer from a sharing copy, not to invent a minimal address that happens to resemble the one you started with.
This guide uses an original fictional case: an astronomy club converting a seasonal Winter Sky email reading list into an evergreen reference pack. Its editor needs a guide edition, a star-chart catalogue search, and an equipment reference. The email campaign record should remain intact, but the new reference pack does not need selected email campaign labels. A club coordinator approves that separation before cleaning begins. The example is about a plain address handoff to the pack editor. It is not a claim about better privacy, safer domains, improved search or algorithm ranking, or different native URL requirements on any social service.
Inventory the copies before changing the campaign record
List the places where the addresses are used before replacing anything. A reference in a new reading pack is not the same asset as a live email call to action, a partner placement, or a recorded campaign source. Name the copy you intend to change and keep the original in the records kept by the campaign owner. This prevents a helpful cleanup from becoming an unexplained measurement change across several channels. The cleaner does not locate existing placements or update documents for you. It transforms only the supplied text, so the inventory of where that text belongs must come from your own publishing or campaign workflow.
For Winter Sky, the editor creates a three-row resource sheet: guide, chart catalogue, and equipment reference. Beside each title, the sheet records which retained detail matters. The guide needs its edition and finding-orion fragment. The catalogue needs its search term and third results page. The equipment link needs the item code and club reference. Only the URL column is pasted into the cleaner, one full public HTTP or HTTPS address per line. The labels remain in the sheet so the final output can be matched back to its role without asking a URL transformation to understand the resource titles.
Use direct public addresses that are suitable for the eventual audience. A signed member download is not an evergreen public source simply because it contains utm_source as well. Known protected patterns are skipped before removal, including recognized tokens, signatures, access keys, expiry fields, and signed-storage keys. That protection cannot be overridden with Keep keys. Detection is not exhaustive, so do not rely on it to discover every private address in the inventory. Where access is required, obtain an approved public alternative or leave the resource out of the public pack. Do not remove an access field just to make a private source pass the cleaning step.
Make the attribution tradeoff explicit
UTM fields can support campaign attribution when a destination measurement system collects them. Removing those labels from a shared copy can change how the resulting visit is attributed. That may be appropriate for a neutral reference, but it is a decision with a cost rather than a universal improvement. Ask the owner whether the new placement should remain measurable under the old campaign labels, use new labels, or omit selected labels. The cleaner does not inspect analytics configuration or predict the reporting outcome. A parameter-removal count tells you what text changed, not how many future visits a campaign report will gain or lose.
The club coordinator approves an evergreen version without the selected seasonal email UTMs. The original measured sources remain in the email log so the old campaign can still be understood from its actual records. The editor does not overwrite those records with the new neutral versions or assume that cleaning retrospectively erases collected data. If the club later runs another measured promotion, that is a fresh campaign-link task. Use the UTM Campaign Link Builder to prepare reviewed labels where needed, rather than trying to reconstruct them from a cleaned list that deliberately omitted their values.
A mixed handoff may contain addresses whose attribution requirements differ. Split the task by purpose when that makes review clearer, or use Keep keys for a specific selected field that must remain. Preserve affiliate and partner references such as ref, ap_id, c_id, affiliateid, and affiliate_id. They are not automatically UTM fields, and reserved names cannot be added for custom removal. The equipment reference in Winter Sky keeps ref=club even when email labels elsewhere are removed. If a partner needs another key retained, confirm the exact name and leave it in place rather than assuming every source-looking field belongs to the same attribution family.
Choose the UTM family and exact exceptions
Select UTM removal for the defined nine names: utm_source, utm_medium, utm_campaign, utm_id, utm_term, utm_content, utm_source_platform, utm_creative_format, and utm_marketing_tactic. The family is fixed rather than an arbitrary utm_ prefix match. An unknown key such as utm_theme remains unless you explicitly add an eligible exact extra name. Keys are classified case-insensitively after decoding, so a differently cased or percent-encoded spelling of a recognized name can still match. This classification changes neither the spelling nor the values of the segments that are retained. Read the review names to see which selected fields were actually removed from each row.
For a UTM-only task, leave click-ID removal off if those fields are outside the agreed scope. That is a separate removal family, even when a click ID appears beside UTM fields in the same query. Likewise, do not add custom extras merely to force the output to have no query string. Keep keys takes priority over selected removal families and extra names. If utm_id must survive, list that exact name and confirm it in the result. The option preserves all occurrences classified under that name rather than choosing one value from repeated copies. Your retention requirement should therefore be expressed at the key level.
Custom lists accept up to twelve unique names each, using one to forty ASCII letters, digits, or permitted punctuation characters: underscore, period, tilde, and hyphen. Names are trimmed and compared without case, so case-only duplicates are not separate rules. There are no wildcards. Reserved destination or affiliate names and protected names cannot be used as extra removal keys. A platform selector, if used, supplies context only and does not alter this UTM method. Keep the rule set small enough for the next editor to understand, and explain any exception in your own campaign note rather than relying on a platform label to communicate it.
Prepare the right copy for the next placement
Remove selected UTMs and review what remains
Keep the original campaign record, choose the attribution fields to remove, and inspect the retained destination details.
Work through the Winter Sky UTM-only pass
The first fictional address is https://example.com/sky/guide?edition=2027&utm_source=email&utm_medium=newsletter&utm_campaign=winter_pack#finding-orion. With UTM removal selected and click-ID removal off, Clean links removes the three recognized UTM segments. The result is https://example.com/sky/guide?edition=2027#finding-orion. The edition is an unknown retained key, and the fragment stays exact. This copy is suitable for further review against the approved reading-pack requirement; the cleaner has not checked the guide contents. The source email address remains in the campaign log because its original measurement context is still part of that campaign record, even though the evergreen copy has a different purpose.
The second address is https://example.com/catalogue?q=star%20charts&page=3&UTM%5FSOURCE=community&utm_theme=dark. The encoded key decodes to UTM_SOURCE and matches the selected family without regard to case. It is removed, while q=star%20charts, page=3, and utm_theme=dark keep their raw spelling and order. The third address is https://example.com/equipment?sku=ATLAS-7&ref=club&gclid=example. It stays unchanged in this UTM-only pass because gclid belongs to the separate click-ID family. The item code and club reference also remain. All domains and values in this worked batch are fictional and are not recommendations for actual resources or equipment.
The expected result is three eligible outputs: two changed rows, one unchanged row, and four removed parameters. No duplicate is present in this set. Selecting click-ID removal as an additional approved step would remove gclid from the third line, but that is a different rule choice and needs a fresh review. The retained raw segments are not reserialized, so the encoded space in the chart search does not become a plus sign. A fragment is not searched for additional UTM-looking fields, and an inner address inside a redirect value is not unwrapped. These boundaries keep the example about exact selected removals rather than an unrestricted rewriting of every address component.
Resolve skipped rows and exact duplicates deliberately
Changed, unchanged, invalid, and protected describe different outcomes. Changed means the trimmed input differs from its eligible output. Unchanged means the selected removals made no text change. Invalid means the supplied line falls outside the accepted address format; protected means a recognized access-bearing or signed pattern was skipped. Reports identify issues by line, status, and message without echoing raw invalid or protected addresses. The original paste remains in the input. A ready list can therefore be useful without representing every supplied line. Reconcile skipped rows with the resource sheet so the pack editor knows which references still need a public replacement.
Duplicate removal uses exact eligible output strings after cleaning. Two source addresses with different campaign labels can become the same output and share one ready-list entry when duplicate removal is selected. The first eligible occurrence determines its position. Different fragments, encodings, parameter orders, or content identifiers remain distinct even if you suspect they show the same page. The duplicate count records repeats whether or not removal is enabled. Keep duplicate removal off when the receiving worksheet needs one line for each planned placement, and preserve the placement mapping outside the tool. A smaller ready list is not a count of unique pages, campaigns, or resource topics.
Validation also has a bounded input scope: 200 nonempty lines, 256 KiB of text, and 4096 characters per trimmed address. Blank lines are ignored, while original line numbers remain useful for correction. Public-domain HTTP and HTTPS addresses are accepted; local or internal names, IP literals, numeric-only hosts, credentials, and other schemes are excluded. Malformed percent escapes, backslashes, raw interior whitespace, and tabs need correction at the source. No URL is fetched to resolve an uncertainty. If a batch exceeds a limit, split it intentionally rather than assuming the tool processed a hidden first portion and silently left the rest for later.
Distinguish the cleaned list from the saved source
Copy cleaned URLs and Download TXT supply the ready addresses for the new handoff. Download CSV provides structured review data, including selected rules, counts, ready outputs, removed names, and issue information. These formats do not reproduce the raw pasted list or removed parameter values, and invalid or protected addresses are omitted from the report. Retained eligible values remain present. They can still be sensitive, even when the selected UTM fields are gone. Read the actual output before sharing it, especially when unknown keys or partner references survive. Removing a known campaign family does not make the resulting file anonymous or suitable for every audience.
Download PDF is a review document, not the public astronomy reading pack itself. It summarizes the rules and outcomes, shows a bounded ready-URL preview, and includes checks for the handoff. Long previews are labelled as shortened. Full eligible addresses are in attached review JSON and CSV, so attachments must be considered when deciding who can receive the document. The pack editor still needs the approved source sheet with its resource titles and editorial context. Use TXT or the ready values in CSV for complete addresses rather than copying a shortened visual preview and treating it as the final link to publish.
Save project includes all pasted source text and the settings, including any private, invalid, or protected links supplied. That file is for deliberate local resumption, not a limited review handoff. Open project accepts the strict versioned project format up to one MiB; a valid import can repair invalid current form fields, and a refused file preserves the existing draft. Project line endings normalize to LF, while URL encoding and Unicode spelling are not normalized. There is no autosave, hosted link archive, or analytics-account recovery. Store the project according to its full source content, even if the ready list you approved contains only public-looking addresses.
Approve the new reference copy and keep measurement separate
Review the exact outputs against the acceptance conditions before the new pack is assembled. For Winter Sky, the editor confirms the guide edition and section, the star-chart search and page, and the equipment item with its club reference. When appropriate, manually open your own approved copies outside the cleaner to inspect those destinations. The tool never performs that navigation, checks content accuracy, or guarantees equivalent server behavior after removal. Retained raw segments, duplicate keys, order, and fragments help preserve the supplied address details, but the destination can still interpret combinations in ways the cleaner cannot know. Treat the manual content check as its own responsibility.
The coordinator records which neutral copies were approved and leaves active measured placements untouched unless their owners separately approve a change. The new public reference pack can use the evergreen versions without rewriting the historical email log. If a later editor decides that click-ID removal or a Keep keys exception is needed, rerun Clean links and review the fresh output. Editing the input or settings invalidates the current exports; earlier downloads remain earlier versions. Name the accepted file in the production task so the pack editor does not choose an outdated candidate simply because it has the same resource order or a familiar first address.
Return to the URL Cleaner for another approved batch, keeping the purpose narrower than a general tracking-removal promise. Selected UTM removal does not erase data already collected, remove every possible identifier, make a domain trustworthy, change algorithm ranking, or certify platform URL requirements. Its value is an explicit attribution choice and a reviewable sharing copy that retains other destination details. Browse the free tools directory when a different preparation step is needed. For recurring supported account routines after link approval, explore SMTasker separately, with the campaign owner still responsible for measurement and the editor responsible for the final resource handoff.
Questions about Remove UTM Parameters
Does UTM removal delete every key beginning with utm_?
No. It removes a fixed recognized set when selected. Unknown names such as utm_theme remain unless an eligible exact extra removal name is explicitly added.
Can I remove UTMs while keeping click IDs or one UTM key?
Yes. Leave click-ID removal off for a UTM-only pass, and use Keep keys for a selected exact name that must remain. Review the attribution tradeoff and the resulting outputs.
Can the cleaned list restore my original campaign links later?
No. Review outputs omit removed values. Keep the original campaign record separately; Save project includes the full pasted source and should be stored with that broader content in mind.
Continue with another link-cleaning guide
Review supplied links locally in the URL Cleaner & Tracking Parameter Remover, or choose another guide below. Find more practical resources in all free tools.
Keep the handoff and account routine connected
Organize recurring work after link approval
Explore SMTasker for supported account routines while keeping campaign measurement, source records, and final link approval under the control of your team.