``

Nearly a year after rolling out direct messaging to every Threads user on mobile, Meta is finally bringing Threads web DMs to the browser. This long-awaited feature addresses a major user demand: the ability to pivot from a scrolling feed to a sidebar conversation without shifting context to a mobile device.
For power users and developers who prefer the precision of keyboard input and screen real estate, this shift validates Threads as a productive tool, not just a social feed.
Meta has confirmed that direct messaging on Threads is entering a broader testing phase on the web. This isn't just a UI tweak; it represents a strategic pivot for the app toward "Desk-First" productivity.
According to Connor Hayes, Head of Instagram and Threads, the reasoning is simple: engagement.
"Our most engaged people spend time on web because theyโre at their desks, tapped in, using Threads for longer sessions."
The current capabilities include:
The "one-click" fix isn't enough.
Don't expect Threads to kill Facebook Messenger just by cloning the UI on the web. The mistake Meta is making (a common trap in tech) is treating the "Desktop" experience as a scaled-down version of "Mobile."
Mobile users are scrolling for dopamine hits. Desktop users want utility. If Threads web DMs don't offer a fast text-input mode, keyboard shortcuts, and API integrations, it will remain a feature, not a replacement. The Web version needs to feel like Slack, not Instagram.
The delay (nearly a year) was likely due to backend synchronization. Threads runs on the same Rally architecture that powers Instagram. Integrating a separate, ephemeral communication layer (DMs) requires tighter coupling between the message queue and the notification system.
For developers, this means the API will likely see a surge in "get_conversation_history" and "update_message_timestamp" endpoints.
Previously, the web feed was clean but isolating. The addition of the "DM" tab creates a split-vision interface. This mirrors competitor X (Twitter), which utilizes sidebar navigation for tweets and DMs simultaneously.
This shift increases platform stickiness. Itโs harder to leave a chat window open than it is to just close a tab.
If you are building against the Threads API, this feature rollout signals an expectation for higher data frequency.
1. Real-Time Updates
2. State Persistence
What should you do right now?
threads.net.| Feature | Threads Web DM | X (Twitter) Web DM | Threads (Mobile) |
|---|---|---|---|
| Integration | Dedicated Sidebar Tab | Requires "More" menu click | Native Tab |
| Group Chats | Coming to Web | Standard | Available |
| Animation | Minimalist | High Energy (Confetti) | Standard |
Winner: Threads wins on integration speed (tab vs menu), though X wins on feature parity for group management.
We expect Meta to roll out Group chat management controls next. Currently, you can delete messages, but moderating a group of 10+ friends (removing a disruptive user, pinning topics) on the web is likely the next priority feature after the basic DM interface stabilizes.
Q: When are Threads DMs fully launching to everyone? A: Meta states they are "testing" it now and will make the feature available to more people "soon."
Q: Can I use Threads DMs on mobile and web at the same time? A: Yes, messages are synced to the cloud. You can reply on your phone and see the reply on your desktop.
Q: Do I need to be logged into Instagram to use Threads DMs on the web? A: Threads is a standalone platform, but it uses your account credentials. You generally do not need to be active on Instagram simultaneously, but they share the same data base.
Q: Can I delete a DM on the web like on mobile? A: Yes, message options including deletion are expected to mirror the mobile experience as the test expands.
Q: Is video calling coming to Threads web DMs? A: No indication of video calling in the immediate roadmap mentioned in the beta release.
The rollout of Threads web DMs is a significant milestone. It moves Threads from a mere publishing platform to a communication utility. For the average user, it closes the gap between the app's stationary nature and its mobile-first design.
Subscribe to BitAI for more deep dives into the technology behind your favorite social apps.