Paste long links
01One http or https URL per line, up to 100 at a time. Links copied from Slack, email, or an ads console with utm_source, fbclid, or gclid all work.
Ready to use, no signup. Paste a long link copied from Slack, email, or an ads console. This tab removes tracking parameters such as UTM, fbclid, and gclid. You can also redact phone numbers, ID numbers, and emails. Source text is not uploaded and is not written to analytics. Review the result yourself after cleaning.
A single URL over 8 KB is rejected. The pathname and id= or q= stay.
What to remove
Hit types appear after you click Start redaction. Source text is not listed.
Detection types
No shareable URL yet. Click Clean links to list clean URLs and the query parameters that were removed.
No masked result yet. Click Start redaction for a character-count comparison and hit types. Source text is not echoed back.
One http or https URL per line, up to 100 at a time. Links copied from Slack, email, or an ads console with utm_source, fbclid, or gclid all work.
Standard mode removes UTM, Click ID, and common attribution parameters. If you are unsure, use conservative mode, which only touches UTM and Click ID. The pathname and id= or q= stay.
The result lists Clean Links and removed parameters. To redact a ticket or log, switch to Data redaction. Source text is not uploaded.
Parse http / https and remove utm_* plus click IDs such as fbclid, gclid, gbraid, wbraid, and msclkid. Standard mode also removes _ga / _gl and common marketplace share tokens. The path and required query parameters stay. Conservative mode only touches UTM and click IDs.
Detects international phone numbers, ID numbers (including US SSNs and Chinese mainland ID checksums), 13–19 digit bank cards that pass Luhn, emails, common API keys / tokens, plus IPv4 and common IPv6. A little of the start and end is kept by default so you can check the hit; you can also mask the whole value. Over 512 KB, split into smaller pieces.
Redaction handles fields scattered through tickets and screenshot notes. A whole key, contract, or password should go through Burn-Link: only ciphertext is stored, and the decryption key sits in the link’s hash fragment, so it is not sent to the server with the request.
This page only answers whether you can remove tracking and scattered fields before you share. Where computation happens, the limits, and what it cannot do are written on the page.
URL parsing, parameter removal, and text masking all finish in the browser. Source text does not enter an HTTP request and is not written to analytics. After you close the tab, that input is not left on this device.
Up to 100 links at a time. A single URL over 8 KB is rejected. Copy all or export TXT; the file downloads only to your device.
Split very long text before redacting. The result shows a character-count comparison and hit types. Source text is not sent to any API.
No signup, and cleaning history is not saved. This is a pattern-matching assistive tool. Review important outbound text yourself. This page does not claim GDPR or HIPAA certification.
utm_source. Together with click IDs such as fbclid and gclid, they tell the next person where you clicked from. Remove them before you share: the link is shorter, and it leaks less campaign data.utm_source, fbclid, and gclid, plus other campaign tokens. They mark where you clicked from. Clean the link on this page before you send it. The path and parameters such as id= or q= stay.After scattered fields are cleaned, send a whole secret through one-time sharing. File backups can also stay in the browser. Plaintext, keys, and files are not uploaded by default.