How to Unsend a Message on Threads (and What They Still See)

Open Threads, tap Messages at the bottom, then select the conversation and go to the message you want to unsend. Tap and hold that message, then tap Unsend. Those steps are on the official help page for Android and iOS, and they apply to a message you sent, not to one someone else sent you.

Once you unsend a message, it will no longer be visible to others. The help page also notes that your Data Download file doesn't include messages you've unsent from your Threads profile. It does not say the message is erased from a screenshot, a report, or the moment someone already read it.

The part people get wrong is the timing: unsending has no time limit. The official help page describes no cutoff, so a message you sent an hour ago or yesterday can still be unsent. The 15-minute window you may have heard about belongs to editing, a different button that only works right after you send.

Unsend and edit are not the same button. Unsend is for a message that should leave the conversation. Edit is for a small fix, and it only works within 15 minutes. Neither one deletes the chat from your inbox or removes a public post. The tap-and-hold steps are the ones on the official help page.

On the web, the official steps are short. Click Messages on the left, click the conversation, and go to the message. Hover over the message, click More, then click Unsend. Meta documents that same hover path for a computer and for a mobile browser.

The result matches the app exactly. The message will no longer be visible to others, and the same lack of a time limit applies. The steps do differ: a computer and a mobile browser use hover and More, while the Android and iOS apps use tap and hold.

One difference does exist on desktop, just not for unsend. Deleting an entire conversation is an Android and iOS feature only; Threads says it isn't available on computers. So from a browser, unsend is the removal tool you have, and it's usually the one you want anyway since it works on both sides of the chat.

The browser route is handy when your phone isn't around or you'd rather work with a mouse. The sequence comes straight from the official help page, so if Threads ever shifts a menu label, that page is the place to recheck. Until then, hover, More, Unsend is the whole flow.

Unsend has honest limits, and Threads says so itself. The help page warns that the people you sent the message to may have already seen it. Unsending changes what the conversation shows from that moment on, and it doesn't reach back into the seconds the message spent on their screen.

Screenshots are the other gap. Nothing stops someone from capturing your message before you unsend it, and no button reaches their camera roll or wherever they paste it afterward. That isn't a Threads weakness; it applies to any messaging app.

Does the other person get notified? Meta's unsend help page does not document a notification when you unsend a message. The only documented outcome is that the message will no longer be visible to others.

Two quieter details are on the help pages. Unsent messages could be included in a report if the entire conversation or a surrounding message is reported. And if you request a copy of your data from your Threads profile, the download won't include the messages you unsent. If the bigger problem is who can message you at all, set up a quieter inbox before the next regret.

Threads spreads removal across four buttons, and each does a distinct job. Unsend makes a message you sent no longer visible to others, in the app and on the web. Edit swaps in corrected text within 15 minutes. Delete conversation removes the whole chat from your inbox only; it will still appear in the inbox of other people, and that control is on Android and iOS, not on computers. Delete post removes a public post from your profile and does not touch your messages.

The rule of thumb is straightforward. Unsend when the message shouldn't exist at all, edit when the fix is small and you're inside 15 minutes, and delete the conversation when the goal is a tidier inbox, not privacy, since the other person keeps the full history on their side. Delete a post when the regret sits on your profile rather than in a chat.

Only unsend removes the message from their view. Edit still leaves a message they can read, delete conversation only tidies your own inbox, and delete post lives outside messaging entirely. When privacy is the goal, unsend is the only one of the four that helps. For public cleanup rather than chats, the same care applies when you delete Threads posts. Deleting a conversation isn't available on computers.

Sometimes the message doesn't need to disappear; it needs one correction. Threads lets you edit the messages you send to a chat, within 15 minutes of sending. The same 15-minute window applies to editing posts, but a post past that window is deleted, not unsent. After the edit window closes, unsend is still available for a message you sent, because the unsend help page sets no time limit.

Edit is usually the better call for typos, broken details, or the wrong link. The conversation keeps its flow, nothing vanishes mid-read, and the corrected text simply takes over. Reserve unsend for messages where no wording fixes the problem.

The 15-minute rule covers group chats as well, and that's where it earns its keep. Group chats on Threads can include up to 50 people, so a garbled message there has a far bigger audience than a one-to-one DM. Editing quickly fixes the text for everyone in the chat.

Editing applies to the messages you send, which matches how unsend works: both act on your own output, never on what someone else wrote. If the message bothering you came from the other side, your options are reporting it or letting it sit, not rewriting it.

A successful unsend doesn't erase every copy, and the clearest case is a report. Unsent messages could be included in a report if the entire conversation or a surrounding message is reported. Unsending doesn't scrub that process.

Everything off the platform is out of reach too. A screenshot taken before you unsend, a line quoted into another app, or the plain fact that someone already read it: none of that responds to anything in Threads. Unsend is a cleanup tool, not a time machine, so it repairs what the conversation shows going forward and nothing before that moment.

That's the limitation worth sitting with. If the message carried something genuinely sensitive, removing it is step one, not the whole fix. A short follow-up, or an actual conversation, does more good than any button. And if the person is the problem rather than the message, the restrict or block decision has its own guide.

The best unsend is the one you never need. A few boring habits prevent most panic sends, and none of them depend on platform features.

Draft first. For anything emotional or sensitive, write it somewhere outside the chat and give it a minute before it goes anywhere. Most messages that feel urgent late at night read differently in the morning, and a draft you never send costs nothing.

Pause before personal details. A one-second check catches a lot: do you actually want a reply to this, and would you still want it in a screenshot?

If panic sends cluster around one person, the real fix isn't a faster unsend. It's less exposure: fewer channels, more distance, or a conversation about what's making you regret what you type. JoltSage does not unsend messages or manage your inbox. If you also publish public Threads posts, it is a scheduler for those posts, not a cleanup button for chats.