If you turn off the Fediverse sharing toggle in Threads, your existing public posts that were already shared to the fediverse do not disappear from other servers. This confuses many users who expect a simple on-off switch to erase their content from Mastodon, Pixelfed, and other ActivityPub platforms. The toggle controls only future posting behavior, not the past. This article explains exactly what happens to your already-federated posts, how other servers handle them, and what you can do to remove them if needed.
Key Takeaways: Threads Fediverse Toggle and Existing Posts
- Settings > Account > Fediverse sharing: Turning this off stops new posts from being sent to the fediverse but does not recall already-shared posts.
- Manual deletion on Threads: Deleting the original post on Threads sends a delete request to external servers, which typically remove their copies.
- Third-party server caching: Some servers may keep cached copies for a short time even after a delete request, so removal is not instant everywhere.
How the Fediverse Sharing Toggle Works
The Fediverse sharing toggle in Threads is a simple binary switch located under Settings > Account > Fediverse sharing. When enabled, every new public post you make is automatically broadcast to the wider fediverse using the ActivityPub protocol. This means your post appears not only on Threads but also on compatible servers such as Mastodon, Pleroma, and Pixelfed, where users who follow you can see and interact with it.
When you turn the toggle off, Threads stops sending new public posts to the fediverse. However, it does not send a recall or undo command for posts that were already transmitted. The ActivityPub protocol does not have a standard way to retroactively unsend a post across all servers. Each server that received your post stores its own copy, and those copies remain unless the server receives a specific delete request.
This design is intentional. The fediverse is built on the idea of decentralized content distribution. Once content is shared, each server becomes an independent publisher. The toggle gives you control over future sharing, but the past is governed by the actions you already took.
What Happens to Already-Federated Posts When You Toggle Off
When you disable the Fediverse sharing toggle, the following outcomes occur for your already-federated posts:
- Copies remain on external servers: Every Mastodon, Pixelfed, or other ActivityPub server that received your post retains its copy. Users on those servers can still see, boost, reply to, and favorite your post.
- New interactions still come back to Threads: If a user on Mastodon replies to your old federated post, that reply appears in your Threads notifications. The toggle does not cut off incoming activity for past posts.
- Your Threads profile still shows the post: The original post remains visible on your Threads profile unless you delete it manually. The toggle only affects distribution, not your local copy.
- No automatic deletion: Threads does not send a bulk delete command for all previously federated posts when you toggle off. Each post must be handled individually if you want it removed from external servers.
The key takeaway is that the toggle is forward-looking. It is not a privacy eraser for content you already shared.
Steps to Remove Already-Federated Posts from External Servers
If you want your old posts to disappear from the fediverse after turning the toggle off, you must take manual action. The most reliable method is to delete the original post on Threads. Here is the step-by-step process:
- Open the post on Threads
Go to your profile and find the post you want to remove. Tap the three-dot menu icon in the top-right corner of the post. - Select Delete
From the menu, choose Delete. Threads will ask you to confirm. Tap Delete again. - Wait for the delete request to propagate
Threads sends a delete request to all external servers that received the post. Most servers honor this request within a few minutes and remove their copy. Some servers may take up to 24 hours or cache the post temporarily. - Check for remaining copies
Search for your post on a Mastodon instance using the post URL or your handle. If the post is still visible after 24 hours, contact the server administrator directly to request removal.
Deleting posts one by one is tedious if you have many. Consider deleting posts in bulk by using the Threads web interface, which allows you to select multiple posts at once on desktop.
Common Misconceptions and Limitations
“Turning off the toggle will make my old posts invisible on Mastodon”
This is false. The toggle only affects future posts. Old posts remain visible unless you delete them on Threads.
“I can edit the post on Threads and the fediverse copy will update”
Editing a post on Threads does not send an update to the fediverse. ActivityPub does not support post editing across servers. The external copy remains as it was originally posted. You must delete and repost if you want changes to appear on other servers.
“All servers will delete my post immediately when I delete on Threads”
Most servers comply quickly, but some may have caching delays or ignore the delete request due to configuration. There is no guarantee of instant or universal deletion.
“The toggle also controls fediverse interactions like replies and likes”
No. The toggle only controls outgoing posts. Incoming interactions from the fediverse continue to work for posts that were shared while the toggle was on. You cannot block incoming activity with this toggle.
Threads Fediverse Toggle: On vs Off for Post Distribution
| Item | Toggle On | Toggle Off |
|---|---|---|
| New public posts sent to fediverse | Yes | No |
| Already-federated posts remain on external servers | Yes | Yes |
| Incoming interactions from fediverse | Yes | Yes, for posts shared while toggle was on |
| Ability to delete old posts from fediverse | Manual deletion on Threads | Manual deletion on Threads |
| Control over past posts | None automatically | None automatically |
The table shows that the toggle only changes the behavior for new posts. Past posts are unaffected regardless of the toggle state. To remove past posts, you must delete them individually on Threads.
Understanding this limitation helps you manage your fediverse presence more effectively. If you plan to stop using the fediverse entirely, delete your public posts before turning the toggle off. If you only want to pause future sharing, the toggle alone is sufficient. For complete removal, combine toggle-off with manual deletion. Consider using the Threads web interface for bulk deletion if you have many posts to remove.