Mastodon users have long awaited direct interoperability with Threads, Meta’s Twitter-like platform built on the ActivityPub protocol. As of early 2025, the connection status between Mastodon instances and Threads remains partial and asymmetric. This article explains exactly what federates between the two networks, what does not work, and how to verify your current federation status.
Meta officially enabled limited ActivityPub support for Threads in late 2024, allowing Mastodon users to follow certain Threads profiles and see their public posts in their home timeline. However, Threads does not fully implement the Mastodon federation model. Replies, direct messages, and most interactive features remain one-way or blocked. This article covers the current capabilities, configuration steps, and known limitations.
Key Takeaways: Mastodon and Threads Federation Status
- Public profile federation via ActivityPub: Mastodon users can follow Threads profiles that have enabled federation and see their public posts
- One-way replies only: Mastodon users can reply to Threads posts, but Threads users cannot see or respond to those replies in their own timeline
- No DMs or private posts: Direct messages and followers-only posts from Mastodon are not delivered to Threads at all
What Federation Between Mastodon and Threads Actually Means
Federation in the ActivityPub ecosystem means that different servers can exchange messages, follow relationships, and content. Mastodon uses the full ActivityPub protocol, including inbox and outbox delivery for public and private posts. Threads implements a subset of ActivityPub called “limited federation.” This means Threads can send public posts to Mastodon instances and accept follow requests from Mastodon users, but it does not process incoming ActivityPub messages beyond basic acknowledgement.
The key difference lies in how each platform handles replies. On Mastodon, a reply to a post is delivered to the original author’s server, which then fans it out to everyone who follows that thread. On Threads, replies from external servers are received but never redistributed to Threads users. The Threads user who posted the original content can see the Mastodon reply in their Threads notifications panel, but their followers will not see it in their timeline. This creates an asymmetric experience where Mastodon users can see Threads content, but Threads users cannot see Mastodon content in their main feed.
Another critical limitation is that Threads does not support the Mastodon-style “boost” (retweet) or “favorite” actions as ActivityPub activities. When a Mastodon user boosts a Threads post, that action is not sent to Threads. The boost only appears on the Mastodon user’s own instance. Similarly, favoriting a Threads post from Mastodon does not increment the like count on Threads.
How to Connect Mastodon With Threads
Connecting your Mastodon account to Threads requires two preconditions: the Threads profile you want to follow must have federation enabled, and your Mastodon instance must not block Threads domains. As of early 2025, many large Mastodon instances still block threads.net due to privacy concerns. Verify your instance’s federation policy before attempting to follow a Threads account.
Step 1: Find a Threads Profile With Federation Enabled
- Open the Threads profile in a browser
Go to threads.net/@username and look for a small ActivityPub icon near the profile name. This icon indicates federation is enabled for that account. - Copy the profile URL
Copy the full URL from the address bar. It should look like https://www.threads.net/@username.
Step 2: Search for the Profile in Mastodon
- Open your Mastodon search bar
Click the search icon or press Ctrl+F on Windows or Cmd+F on Mac. - Paste the Threads URL
Paste the full Threads profile URL into the search field and press Enter. Mastodon will attempt to resolve the remote profile. - Verify the resolved profile
If federation is working, Mastodon will display the Threads profile with a note that it is from threads.net. Click the profile name to open it.
Step 3: Follow the Threads Profile
- Click the Follow button
On the Threads profile page in Mastodon, click the Follow button. The button will change to Following. - Wait for posts to appear
Public posts from that Threads profile will now appear in your home timeline. Note that only posts made after federation was enabled will appear. Older posts are not backfilled.
What Works and What Does Not
The table below summarizes the current federation capabilities between Mastodon and Threads as of early 2025.
Mastodon Users Can See Threads Public Posts
If a Threads user has federation enabled, their public posts appear in the Mastodon home timeline of anyone who follows them. The posts include text and images. Videos and links are also supported.
Mastodon Users Cannot See Threads Replies or Quote Posts
Threads does not federate replies or quote posts from its own users. If a Threads user replies to another Threads user, that reply does not appear on Mastodon. Only top-level posts are sent to the fediverse.
Threads Users Cannot Reply in Mastodon Timelines
When a Mastodon user replies to a Threads post, the reply is sent to Threads and appears in the Threads user’s notifications. However, that reply is not visible to other Threads users in their timeline. The Mastodon reply is effectively invisible to the Threads community.
No Direct Messages or Private Posts
Threads does not support ActivityPub’s direct message or private post types. Any Mastodon post with visibility set to “followers only” or “direct” will not be delivered to Threads. Only public posts federate.
Boosts and Favorites Do Not Sync
A boost or favorite from Mastodon does not affect the Threads post. The engagement metrics on Threads remain unchanged. Mastodon users see the boost only on their own instance.
| Item | Mastodon to Threads | Threads to Mastodon |
|---|---|---|
| Public posts | Delivered to Threads | Delivered to Mastodon |
| Replies | Delivered to Threads notifications only | Not delivered |
| Direct messages | Not supported | Not supported |
| Boosts / Favorites | Not synced | Not synced |
Common Misconceptions and Limitations
Threads Federation Is Optional for Users
Not every Threads profile has federation enabled. Users must manually turn it on in their Threads settings under Account > Federation. Profiles without this setting enabled are invisible to Mastodon. You cannot follow them or see their posts.
Instances Can Block Threads Entirely
Many Mastodon instance administrators have added threads.net to their domain blocks due to data privacy concerns and Meta’s tracking policies. If your instance blocks threads.net, you cannot follow any Threads profile. Check your instance’s federation status by searching for threads.net in the instance’s domain blocks list.
Threads Does Not Support Fediverse Discovery
Mastodon users cannot search for Threads profiles by username alone. You must use the full threads.net URL. Threads does not appear in Mastodon’s global search results or directory features.
As of early 2025, federation between Mastodon and Threads is functional but limited. Mastodon users can follow public Threads profiles and read their posts. Replies and engagement remain one-way. Direct messages and private content do not cross over. If you rely on full two-way interaction, you should continue using Mastodon-native accounts for those conversations. For reading public content from Threads users who have enabled federation, the current setup works reliably.