Threads Clean Link
2 ratings
)Overview
Right-click cleans Threads share links into post URLs; copying a link on the web resolves short codes and strips tracking params.
Threads Clean Link turns Threads share links and "Copy Link" results into clean, tracker-free post URLs — and now adds a one-click copy button right on each post. THREE FEATURES • Right-click resolve: Right-click a Threads share link (/share/XXXX) and choose "Copy clean Threads post link" to resolve it and copy the clean post URL — works on any site's tab, not just threads.com. • Auto-clean "Copy Link": Threads' official web "Copy Link" button now writes either a /share/ short code or a full URL with tracking parameters. This extension handles both automatically, so what you paste is always clean. • "Copy original link" button on every post: A link icon is added to each Threads post's action row (next to the share button). One click copies that post's clean URL — no tracking parameters, no short code — to your clipboard. It matches the native buttons in appearance (color follows the page, native hover tooltip), and its label follows your interface language. LINE GROUP FUNNEL FLAGS When you open a Threads post, the extension checks on-device whether the thread follows the "long investment story, then add me on LINE" solicitation pattern. A post is flagged on any one of three paths: (1) it carries a LINE add-friend or add-group deep link (line.me, lin.ee, linktr.ee); (2) it shows a LINE account or an "add me on LINE" phrase together with a group-or-join call to action (for example "I'll pull you into the group", "join", "DM me"); (3) it shows a LINE account alongside investment pitch wording (hot stock tips, paid stock picks, managed trading and the like). On a match it flags the post and adds that author to your flagged list, so the same author is flagged on your feed too. The check is plain rule matching, so a legitimate club, study group or shop solicitation can be flagged too — one click unflags it, and it is never flagged automatically again. When the page itself does not carry the author's identifier, one logged-out request is sent for that same post to look it up. The flagged list lives in the History & Settings page (with evidence links). By default it stays on this device only and is never uploaded; if you sign in for Cloud Sync (see below), the flagged list syncs to your other devices along with your account — only the author handle and the evidence posts' links and timestamps, never the post text — and signing out stops it. Either way it is never shared with other users; a single switch turns the whole feature off. POPUP SETTINGS Click the toolbar icon to toggle two settings that take effect instantly: "Auto-clean the share button" (on by default) and "Notify on success" (off by default; failure notifications always show regardless of this setting). HISTORY & SETTINGS PAGE Every successful cleaning can leave a local history entry (searchable, filterable by source, JSON export/import, one-click clear), with totals and a 14-day activity chart. History is stored only on your device (chrome.storage.local) by default and never uploaded unless you separately sign in with Google to enable Cloud Sync on the History & Settings page, capped at 1,000 entries, and can be disabled entirely with the "Keep cleaning history" switch. The UI, notifications and context menu support Traditional Chinese and English — following your browser language by default, switchable manually. CLOUD SYNC (OPTIONAL) Sign in with Google on the History & Settings page to additionally sync your cleaning history to the cloud and across your other devices running the companion app; your LINE group funnel flagged list syncs too (never the post text). If you don't sign in, nothing changes. Once signed in, the settings page loads your Google account avatar to display it (it is not stored on the server). Each history entry also shows which device it came from; devices can be renamed or removed from the same page. HONEST PRIVACY NOTE Whenever either feature has to resolve a /share/ short code, it sends one anonymous GET request (no cookies) to threads.com/threads.net to look up the real destination — that's the only way to resolve a short code, and it's disclosed in full on the project README. This request carries no login credentials, but Threads will still see your source IP and browser fingerprint; if that matters to you, prefer the manual right-click flow or use a VPN. When the content is already a full post URL with only tracking parameters attached, cleaning is pure local string processing with zero network requests. Unless Cloud Sync is enabled, this extension collects no user data. Once enabled and signed in, it syncs only your own cleaning history, your flagged list (author handles plus the evidence posts' links and timestamps — never the post text) and basic Google account identity (email, name, avatar URL) to the developer's own backend — see the README for details. Either way, it never reads existing clipboard contents, contains no remote code, and never requests <all_urls>. Open source (MIT). Source & full details: https://github.com/hunandy14/threads-clean-link
5 out of 52 ratings
Details
- Version0.11.2
- UpdatedSeptember 28, 2026
- Offered bymapio
- Size333KiB
- Languages2 languages
- Developer
Email
mapio1904@gmail.com - Non-traderThis developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.
Privacy
Threads Clean Link has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.
Threads Clean Link handles the following:
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes
Support
For help with questions, suggestions, or problems, visit the developer's support site