X (Twitter) DM Issues: 2026 Troubleshooting Guide for Direct Messages

Quick answer: Most "I can't DM them" and "they can't message me" problems are not bugs. They come from the recipient's who can message you setting, from the daily DM send limit that X places on unverified accounts, or from a block. If your message shows "not sent" or "message failed to send," work through these in order: confirm the recipient allows messages from accounts like yours, confirm you have not hit your daily send cap, rule out a block, then rule out network and app issues.

The one detail that explains the majority of "they can't message me" cases: since 2023, X defaults many inboxes to message requests from Verified users and people you follow only, which silently drops requests from unverified accounts you do not follow. Combined with the per-day DM cap on unverified accounts, that covers most delivery failures before you touch any technical fix.

Create content, post everywhere

Create captions, images, and videos with AI. Schedule to 9 platforms in seconds.

Start your free trial

Jump to:

• Quick diagnosis
• Who can message you on X
• The unverified DM send limit
• Why your DM failed to send
• Fixing specific DM error messages
• Encrypted DMs and XChat
• Blocked, muted, and message requests
• App and network fixes
• When to contact X support
• FAQ

Quick diagnosis

Run through this before trying any technical fix. It sorts almost every DM problem into the right cause.

1. Can you open the DM composer at all? If the message button is greyed out or missing, the recipient's settings do not allow messages from your account, or one of you has blocked the other.
2. Does the message send to a mutual follower? If a DM to someone who follows you back works, the problem is specific to the other person's settings, not your account.
3. Have you sent a lot of DMs today? If sends started failing after a burst of messages, you have likely hit the unverified daily send limit or a spam rate limit.
4. Is it happening everywhere? If DMs fail on both mobile and desktop, it is an account or recipient issue. If it fails on one only, it is an app or browser issue.

Who can message you on X

X gives every account a single setting that controls who can start a conversation with you. You reach it at Settings and privacy, then Privacy and safety, then Direct Messages, then Allow message requests from. The options in 2026 are:

• Everyone: anyone can send you a message request, even people you do not follow.
• Verified users and people you follow: you receive requests from accounts you follow and from Verified (paid) accounts only. Requests from unverified accounts you do not follow are dropped. This is the default many accounts sit on, and it is the single most common reason someone says "I messaged you but you never got it."
• No one: you receive no new message requests. Existing conversations still work.

What this means in practice:

• If you cannot message someone, their setting probably excludes accounts like yours. If you are unverified and do not follow each other, a recipient on "Verified users and people you follow" will never see your request.
• If people cannot message you, open that same setting and loosen it. Moving from "Verified users and people you follow" to "Everyone" is what fixes most "your DMs are closed" complaints.
• Following the person, or getting them to follow you, moves you inside the "people you follow" allowance and usually restores messaging regardless of verification.

If you want your account reachable by the public, also confirm your account is not protected. A private or locked account changes who can interact with you. See how to make your Twitter account public, and if your account is restricted, how to fix a locked X account.

The unverified DM send limit

This is the cause people miss most, because it looks like a random glitch. X caps how many direct messages an unverified account can send in a day. Once you reach that cap, new DMs fail to send until it resets, even to people who allow your messages. A separate short-term rate limit also kicks in if you send many messages very quickly, which the system reads as spam behavior.

X does not publish an exact, guaranteed number, and the cap has changed over time, so treat any specific figure you see quoted elsewhere as an estimate rather than an official value. What is consistent is the shape of the policy: unverified accounts get a limited daily allowance of sent DMs, and a Premium subscription raises that allowance substantially. The send limit is one of the levers X uses to push heavy messagers toward paying for Premium.

How to tell the send limit is your problem:

• DMs worked earlier today and started failing after you sent a batch.
• Sends fail across multiple different recipients at once, including people you have messaged before.
• The failure clears on its own after some hours.

What to do:

• Wait it out. The daily cap resets, and normal messaging returns.
• Slow down. Space messages out instead of firing many in a row to avoid the anti-spam rate limit.
• Verify (subscribe to Premium) if you legitimately need higher volume. This is X's intended workaround and it raises the cap.
• Do not mass-send identical DMs. Duplicate outreach is the fastest way to trip both the rate limit and spam enforcement. If you run outreach at scale, read our X automation guide for what stays within the rules.

Why your DM failed to send

When a message shows "not sent," "message failed to send," or sticks on "sending," it is one of these, roughly in order of likelihood:

• The recipient's settings exclude you. They allow "Verified users and people you follow" and you are neither. The request is dropped.
• You hit your daily send cap or a rate limit. Common after sending many DMs, especially on an unverified account.
• One of you blocked the other. Blocks stop messaging in both directions.
• The recipient deactivated or was suspended. If the account is gone, the conversation cannot be delivered. Learn to tell whether you are blocked or they deactivated.
• Your account is limited or locked. Restrictions from policy enforcement can suspend messaging. See how to fix a locked X account.
• A network or app problem. Weak connection, an outdated app, or a client-side glitch can stall a send.
• Unsupported or oversized media. A large video or an unsupported file can fail while text would go through. Try sending the text alone first.

Fixing specific DM error messages

"You can't send messages to this person"

Causes: the recipient's message setting excludes your account, you do not follow each other and you are unverified, or you have been blocked.

Fixes:

1. Follow them, or get them to follow you, to land inside the "people you follow" allowance.
2. If you are unverified and they only accept Verified users and follows, a Premium subscription or a mutual follow is the only route in.
3. Rule out a block by trying to view their profile and posts while logged in.
4. Reply to one of their posts publicly to open contact if DMs are closed to you.

"Message failed to send" or stuck on "sending"

Fixes:

1. Check your connection and retry. Switch between Wi-Fi and mobile data.
2. Send the text without any attached photo or video to isolate a media problem.
3. If you have sent many DMs today, stop and wait. You have likely hit the daily cap or rate limit.
4. Update the app, or log out and back in.

"Something went wrong"

Fixes:

1. Clear your browser cache and cookies on desktop, or force-close and reopen the app on mobile.
2. Disable browser extensions, especially ad and script blockers, or try a private window.
3. Switch between the mobile app and the desktop site to see if the issue is client-specific.

"You are not verified" style rejection

Some accounts restrict certain actions, such as sending videos in DMs, to Verified accounts or to people you both follow. If a specific message type is rejected while plain text works, a verification or mutual-follow requirement is usually the reason.

Encrypted DMs and XChat

X has moved its private messaging onto an encrypted system branded XChat. It launched first for Premium subscribers, then rolled out more broadly to all users during late 2025, and it supports end-to-end encrypted chats, file sharing, editing and deleting messages, disappearing messages, and screenshot blocking, alongside standard DMs.

Caveats worth knowing before you rely on it:

• It is not a drop-in replacement for a dedicated secure messenger. Security researchers have publicly questioned how X implements its encryption, so do not treat XChat as equivalent to a fully audited app like Signal for sensitive material.
• Encryption applies to the newer XChat experience, not necessarily to older message threads. Do not assume every historical DM is end-to-end encrypted.
• Features and availability keep shifting. X has paused, rebuilt, and re-released this system more than once, so exactly which controls you see can vary by account and app version.

If an encrypted conversation misbehaves, update the app first. New messaging features are the most likely to break on an outdated client.

Blocked, muted, and message requests

Blocking stops all messaging between two accounts in both directions. Neither of you can send the other a DM, and the message button disappears. If you suspect a block rather than a settings issue, confirm it with our guide on telling if you are blocked or they deactivated.

Muting is different. A muted account can still send you DMs and you can still send them messages. Muting only hides their content and notifications from you, so it never causes a send failure. If you want to quiet specific accounts or terms without cutting off messaging, see how to mute words on X.

Message requests are where messages from people you do not follow land when your settings allow them. They sit in a separate requests inbox until you accept. If someone insists they messaged you and you never saw it, check the message requests folder before assuming the DM never arrived. Accepting a request moves the conversation into your main inbox; declining it removes the request.

App and network fixes

If DMs fail on only one device or client, the problem is local, not with your account.

Network:

• Switch between Wi-Fi and mobile data and retry.
• Test another app or site to confirm the connection itself works.
• On a restrictive network (some workplaces or public Wi-Fi), a firewall may interfere. Try a different network.

Mobile app:

• Force-close and reopen the app.
• Update to the latest version. Messaging features break most often on old builds.
• Clear the app cache, or reinstall if problems persist.
• Restart the device.

Desktop:

• Clear cache and cookies for the site.
• Disable ad blockers and script-blocking extensions, or use a private window.
• Try a different browser to isolate an extension conflict.

If you are troubleshooting with X support and they ask for diagnostic files, here is how to generate a HAR file in Chrome, Firefox, Safari, and Edge.

When to contact X support

Most DM problems are settings, limits, blocks, or client issues you can fix yourself. Escalate to support when the cause is account-level and outside your control:

• Messaging privileges suspended or restricted with no clear reason.
• A platform-wide DM outage affecting all conversations.
• Harassment, impersonation, or security concerns in your DMs.

How to contact support:

1. Open the X Help Center.
2. Choose the option to report a problem or contact support.
3. Select the technical or account issue category that fits.
4. Describe the problem with specifics: the exact error text, when it started, what you have already tried, and your device and app version.
5. Attach screenshots where they help.

Before you escalate, rule out the common causes: your own send limit, the recipient's settings, and a block. Support cannot change another user's privacy settings for you.

Related guides

• Why are my tweets not being seen for reach and visibility limits beyond DMs.
• X automation complete guide for messaging at scale without tripping spam limits.
• Twitter/X API error codes if you build on the API and hit DM-related errors.

FAQ

Most X DM problems come down to three things: who the recipient allows to message them, the daily send limit on unverified accounts, and blocks. Check those first, then rule out app and network issues before contacting support.

Managing X alongside other platforms? SocialRails lets you schedule posts and content across 9 platforms from one dashboard, keeping your accounts active while you sort out messaging issues.