- Why This Happens More Than You'd Think
- Can You Message Them At All?
- Check Your Internet Connection First
- Update The App Or Refresh The Browser
- Clear The App Cache
- Check If You've Been Restricted
- Check If The Other Person Has Restricted Their DMs
- Look For A Wider X Outage
- When To Just Start A New Conversation
- Frequently asked questions
An X (formerly Twitter) DM usually won't send because the other person can't receive messages from you, you've hit X's daily limit on message requests, or something on your side is glitching: a poor connection, an outdated app or a full cache. Check whether they follow you or accept messages from anyone first, then restart the app, check your internet, update to the latest version and clear the cache. If none of that works, the problem may be on X's end or your account may be restricted.
Why This Happens More Than You'd Think
I get asked about this a lot. Someone sends a direct message on X (formerly Twitter), it just sits there spinning, or it never shows up on the other end at all. It's annoying, especially if you're relying on DMs for business or client work.
The good news is that most of the causes are ordinary and fixable. The bad news is that a few causes are out of your hands. I'll walk through both.
Can You Message Them At All?
Start here, because no app fix will help if X won't let the message through. X's Direct Messages help page says you can start a conversation with anyone who follows you. Someone you don't follow back can only be messaged if:
- they've opted in to receive messages from anyone
- they're Verified and have opted in to messages from Verified users, and you're Verified too
- you've messaged them before
If none of those apply and they have a closed inbox, X shows you that their inbox is closed and asks for their X Number. X's help page on Chat says you can't send the message unless they follow you, you already have a Chat with them, or you enter their enabled X Number. The prompt alone doesn't mean you need a number: if their inbox accepts message requests, you can send without one and it lands in their requests.
Check Your Internet Connection First
Before you blame the app, check your connection. DMs need a stable connection to send, and a weak signal or patchy wifi is one of the most common reasons messages fail.
Try switching from wifi to mobile data, or the other way round. If one works and the other doesn't, you've found your answer.
- Turn off wifi and try sending on mobile data
- Turn off mobile data and try sending on wifi
- Restart your router if both are slow
Hit The Daily Message Request Limit?
If messages to people you already talk to send fine but first messages to new people fail, you've probably hit the request cap. X's help page on Chat limits how many message requests you can send in a 24-hour period, by subscription tier:
- Free: 7
- Premium: 35
- Premium Plus: 75
- Premium Business: 500
Here's how that plays out. You're on a free account, and after a networking event you send first messages to seven new contacts before lunch. All seven count as requests, so the eighth, to someone who doesn't follow you, won't go, while your reply to an existing client sends straight away. Messages to people you already talk to working while new ones fail is the giveaway, and the account stays stuck until the 24-hour period rolls on. The fix is to wait, reply in threads that already exist, or ask the person to message you first. Upgrading raises the cap, but for occasional outreach waiting a day is the better call.
Update The App Or Refresh The Browser
X updates its app often, and older versions sometimes have bugs that affect messaging. If you haven't updated in a while, that could be your problem.
Go to your app store, check for updates, and install the latest version. If you're using X on a browser, a hard refresh or clearing the browser cache can sort out similar issues.
I'd also suggest closing the app completely rather than just minimising it, then reopening it. Force-close it, reopen it, then try the message again before you change any settings.
Clear The App Cache
Over time, the X app builds up cached data that can slow things down or cause messages to stick. Clearing it won't delete your account or your messages, it just clears temporary files.
- On Android, go to Settings, then Apps, find X, tap Storage, then Clear Cache
- On iPhone, there's no direct cache clear option. Apple's route is Settings, General, iPhone Storage, then tap X and choose Offload App, which Apple says frees up the storage the app uses but keeps its documents and data. Reinstall X from the App Store afterwards, and if that doesn't help, delete the app and reinstall it
- Reopen the app and try sending the DM again
If you're on desktop, clearing your browser cache and cookies does the same job.
Check If You've Been Restricted
X places limits on accounts that look like they're sending too many messages too quickly, or that have been reported. If you've hit a limit, your messages may not send, or may send but not deliver.
This is more common on newer accounts or accounts that have recently followed a lot of people or sent a lot of DMs in a short space of time.
The message request caps above are published, but the wider spam restrictions aren't. I can't tell you the exact thresholds because X doesn't publish them, and they change. If you suspect this is the issue, slow down your activity for a day or two and try again.
Check If The Other Person Has Restricted Their DMs
Sometimes it's not your account at all, and the rules in the first section decide whether you can reach them. The useful question here is a different one: did your message fail, or has it simply not been answered? From your side the two can look the same.
A request that went out has been sent. X keeps it in the other person's requests until they accept it, ignore the conversation or block you, and it doesn't tell you which they chose. A closed inbox is the one case X flags, by asking you for their X Number. X's help pages don't describe what a failed send looks like in the thread, so test it instead: send a short message to someone who already talks to you. If that one goes through and the new contact's doesn't, the block is their settings or your request limit, not your app or connection.
If it's a business contact, try reaching them another way to confirm.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Look For A Wider X Outage
Sometimes the problem isn't you, it's X. Server issues and outages happen, and when they do, DMs are often one of the first things affected.
Check a site status tracker or search on another platform to see if other people are reporting the same issue. If it's widespread, there's nothing to fix on your end, you just wait it out.
I'd avoid spending ages troubleshooting your settings if it turns out half of X is down anyway.
For anyone who wants the background, see our guide to whether you can delete X messages for both people.
When To Just Start A New Conversation
If a specific thread keeps failing but everything else on the app works fine, the thread itself might be stuck. Try starting a fresh conversation with the same person instead of continuing the old one.
This isn't a guaranteed fix, but I've seen it work when nothing else did. It's a quick thing to try before you assume something bigger is wrong.
If messages still won't send after all of this, it's worth contacting X support directly and explaining what you've already tried.
Message Requests And Encryption
X now runs DMs through Chat, its encrypted messaging feature, and that changes what you see when a message goes out. A message request to someone who doesn't follow you is kept separate from their other messages until they accept it, and X says requests stay unencrypted until accepted. The recipient can accept, ignore the conversation or block you, so a request that's been sent but never answered isn't a sending fault. If the person hasn't registered for Chat, X sends the message unencrypted and shows an unlock icon next to the send button. That icon is normal, not an error, and the message still sends.
For a related read, see my post on getting a suspended X account back. There's more on what to do when X is not working in a separate post of mine.
If the whole app is misbehaving rather than just DMs, this guide covers how do i restart the x app step by step.
Frequently asked questions
Who can I message on X?
Anyone who follows you, anyone who has opted in to messages from anyone, Verified users who opted in to messages from Verified users (if you're Verified), or someone you've messaged before.
Why does X ask for an X Number?
The person has a closed inbox. You can only message them if they follow you, you already have a Chat with them, or you enter their enabled X Number.
How many message requests can I send a day on X?
X sets the limit per 24-hour period by tier: Free 7, Premium 35, Premium Plus 75 and Premium Business 500. Replies in existing conversations aren't message requests.
How do I know if X is down rather than my app?
Check a site status tracker or search another platform for reports. If others are having the same issue, it's a wider problem and you'll just need to wait.
More X and Twitter fixes: the X help guide.
Run a business, a brand or a blog? I feature tools, products and expert guest posts for an audience of 15,000. See how it works


