How to delete a DM on X (and what stays visible)

#Quick answer

To delete a DM on X (formerly Twitter), open the conversation, tap and hold the message on iOS or Android, and choose Delete message. On x.com you click the message and select Delete. It vanishes from your inbox at once, and X's own help page states that a deleted Direct Message or conversation is "deleted from your account only" - the other people in the thread still see theirs.

There is now one real exception, and it is the reason most pages on this query are out of date. In an encrypted Chat conversation, X documents an unsend that removes the message from the recipient's inbox too.

Last updated: September 2026

#Delete one message, on each platform

These steps come from X's Direct Messages help page.

On iOS:

1. Open the conversation from your inbox.
2. Tap and hold the message you want gone.
3. Choose Delete message from the menu that pops up.

On Android:

1. Open the conversation.
2. Tap and hold the message.
3. Choose Delete message.

On x.com:

1. Open the conversation.
2. Click the message.
3. Select Delete.

No confirmation delay, no undo. The message leaves your view of the thread and the rest of the conversation closes up around it.

#Delete a whole conversation (and the group-chat trap)

Per-message deletes get tedious fast, so the conversation-level action is the one people actually want.

One warning that belongs in bold, because X states it and almost nobody repeats it: when you delete a group conversation, you leave that group and can no longer participate. That is not a cleanup, it is an exit. The other members keep every message, and you need a new invitation to get back in. If you only want the noise gone, mute the conversation instead, which is the approach we cover in how to mute someone on X.

#Unsend vs delete: what most guides on this query get wrong

Search for deleting DMs from both sides today and you will find pages insisting it cannot be done. One widely-shared post states "Twitter doesn't allow to delete or unsend Twitter DMs once they are send" and calls the opposite claim misinformation. It was last modified in July 2026, and it never mentions Chat.

X's own About Chat page is explicit:

Chat allows users to "unsend" a message, which will remove it from the recipient's inbox. This is only possible for encrypted messages.

Chat is not a side feature. X began rolling it out on 14 November 2025 as the replacement for basic direct messaging, with end-to-end encryption, voice and video calls, message editing, disappearing messages and screenshot notifications (Engadget, 14 November 2025). A standalone Chat app followed in 2026.

So the honest answer to "can I delete a DM from both sides" is: it depends on whether that thread is encrypted. And that is not your choice alone. X lists the conditions for an encrypted conversation:

• Both of you have registered for Chat, in the X app on iOS or Android, on web, or in the X Chat app signed in with your X login.
• The recipient follows or subscribes to you, has messaged you before, has accepted an encrypted Chat message from you before, or is in the same Premium Business or Premium Organization as you.

If the person you are messaging has not registered for Chat, they have no public key, so the message goes out unencrypted. X says the compose screen signals that with an unlock icon next to the send button. No encryption means no unsend, which means the copy in their inbox is permanent.

The delete side of encrypted Chat is worth reading closely too. X says that when you delete an encrypted message or conversation, the data is instantly deleted from your device and soon after from all of your other devices. Then the caveat: "the recipient may still be able to see the encrypted message or conversation you have deleted." Deleting is still one-sided. Unsending is the two-sided action.

#What a delete never reaches

Treat this as the real scope of the button.

Their copy, in a legacy thread. X's wording is that others in the conversation will still be able to see Direct Messages or conversations you have deleted. Nothing you do from your side changes that.

Their data archive. Anyone can download an archive of their X data, and DM history sits inside it. A conversation you cleared from your inbox is still in their export. If you have never looked at what that file holds, how to download your X archive walks through it.

Screenshots and downloaded media. X notes that recipients may download or re-share links to media you send, and that anyone holding the shortened t.co link can view it. A delete does not revoke a link that already left the building.

Anything passed to Grok. This one is new and easy to miss. X's Chat documentation says that when you select a message or image and use Ask Grok, that content is no longer encrypted, even though the original conversation remains so. Either participant can do this. A message can leave the encrypted envelope without you knowing.

Cached data on a device. X states that logging a session out prevents further actions from it but "may not delete data (e.g., Direct Messages) that was previously cached on the device." If your concern is a device you no longer control, deleting messages is the wrong tool; see how to log out of X everywhere.

#Disappearing messages beat deleting

Deleting is retroactive and partial. The setting that actually controls lifespan is disappearing messages, which X documents for encrypted Chat: pick a duration and messages are removed from the device and from X's servers when it expires. You set it from the conversation info screen, under the Disappearing messages menu.

For anything sensitive, that is the better habit. Decide the retention before you send, not after you regret. The same logic applies to read state: if you would rather not broadcast when you opened something, turning off read receipts on X is a single account-wide switch.

#Bulk deleting, and the tools that offer it

X does not document a bulk delete for DMs. There is no "clear all conversations" button, which is why an industry of erasers exists.

Be clear-eyed about what those tools are. They log into your account, or hold an authorised token, and click through your inbox for you. That means handing a third party access to your private messages, and the job still stops at your own copy, because no external tool can reach the other person's inbox either. If you are cleaning up after a suspected compromise, the priority order is different: secure the account first, revoke apps you do not recognise, and treat the message history as already read. Our walkthrough of what to do when your X account is hacked covers that sequence.

Two limits from X's Direct Message FAQs are worth knowing if you use DMs at volume: there is an account limit of 500 Direct Messages sent per day, and sending duplicate messages or the same link to multiple accounts can be treated as spam activity, which can cut off your ability to send for a while. That pattern, not the delete button, is what puts accounts at risk. We go into it in what an automated DM actually is.

#Bottom line

Tap and hold, Delete message. Your copy goes, theirs stays, unless the thread is encrypted Chat, in which case unsend removes it from their inbox as well. Deleting a group conversation ejects you from the group. And nothing you press retroactively covers screenshots, archives, downloaded media, or text either of you handed to Grok.

If DMs are part of how you grow rather than how you chat, the gains are on the posting side, not the inbox. X-Autopilot drafts and publishes from your own logged-in browser on your Mac, so your session cookie never leaves the machine - a smaller detection surface than a cloud tool posting from a shared IP pool, though no browser-based automation is sanctioned by X's rules.