Messenger actually tells you what's wrong — in a language of tiny circles. Next to a message you've sent, one of four icons appears, and each one is a different diagnosis:
- An empty, hollow circle — the message hasn't left your phone yet. Messenger is still trying to hand it to Meta's servers.
- A filled circle with a tick — sent. It reached Meta's servers.
- Their profile picture in miniature — delivered and seen.
- A red triangle or "Couldn't send" label — the send failed outright.
If you're reading this, you're probably staring at the first or the last one: a message typed, sent, and going nowhere — or a photo upload that spins before giving up. The hollow circle is useful evidence: it means the failure happens before your message leaves the phone. The six fixes below start with what that icon tells you, then work through Messenger's own data settings and account checks before the general network tests.
Quick Answer: First, tap the failed message and choose Retry — and check whether it's every chat failing or just one. If it's all of them, turn off Messenger's own Data Saver (☰ menu → Settings → Data Saver) and exempt Messenger from Android's Data Saver too. If it fails for exactly one person, skip to Fix 3: the cause is almost always an account or block setting.
In This Guide:
- Fix 1: Retry the Message — and Test Whether It's One Chat or All of Them
- Fix 2: Turn Off Messenger's Own Data Saver
- Fix 3: Check Blocks, Restrictions, and Your Sign-In
- Fix 4: Force-Stop Messenger and Clear Its Cache
- Fix 5: Swap the Network Underneath It
- Fix 6: Update Messenger — or Reinstall It Cleanly
- When It's Meta, Not You
- Sending Problems, Answered
Fix 1: Retry the Message — and Test Whether It's One Chat or All of Them
A single message can fail for a reason that has already passed: a two-second connection drop at the exact moment you hit send. Messenger doesn't always recover on its own — the message stays failed until you deal with it:
- Tap the failed message (or long-press it) and choose Retry / Resend.
- If it sends, that was a momentary drop, and nothing else in this guide is necessary.
- If it fails again, run the dividing test: send a message in a different chat, to a different person.
- Also try the reverse comparison — a plain text message if the failed one was a photo or video.
Read the results like a map. Everything fails → connection or app, keep going in order. Only one chat fails → jump to Fix 3. Only photos and videos fail while text goes through → that's a bandwidth problem, and Fix 5's network swap is your answer.
Fix 2: Turn Off Messenger's Own Data Saver
Messenger is throttled from two directions, and most people only know about one of them. There's Android's system Data Saver — and then there's a second, separate Data Saver inside Messenger itself, which can interfere with sends, especially media. Check both:
- Open Messenger, tap the ☰ menu, then the Settings ⚙ icon.
- Find Data Saver in the settings list (its exact spot shifts between versions — look under Preferences) and turn it off.
- Now the system level: go to Settings → Network & internet → Data Saver (Samsung: Settings → Connections → Data usage → Data saver; Xiaomi: Settings → Connection & sharing → Data usage) and turn it off while testing — or open Unrestricted data and allow Messenger through it.
- Finally, long-press the Messenger icon → App info → Mobile data & Wi-Fi and confirm Background data is on.
The signature of this fix working: messages fail on mobile data all day, then send instantly once these steps are done — because Wi-Fi was never restricted, the problem seemed to come and go with your location.
Fix 3: Check Blocks, Restrictions, and Your Sign-In
If Fix 1's test showed the failure follows one person, no network fix will help — because the obstacle is in the account layer. Three things to check:
- Your blocked list. In Messenger, go to ☰ menu → Settings ⚙ → Privacy → Blocked accounts. If the person you're messaging is on it — added accidentally or long ago — unblock them; messages to a blocked contact cannot send.
- Their end. If they have blocked or restricted you, your messages will sit unsent to them alone while everyone else receives normally. There's no phone setting that changes this; Fix 1's test is how you recognise it.
- Your own account's standing. Sign into facebook.com in a browser and look for restriction notices. Meta temporarily limits messaging on accounts flagged for spam-like patterns, brand-new accounts, or after security checks — and the limit often appears in Messenger as plain failed sends. Temporary limits lift on their own, usually within hours or a few days; retrying doesn't shorten them.
- Refresh your sign-in. In Messenger, open ☰ menu → Settings ⚙, scroll down, and Log out, then sign back in. This renews the authentication tokens the app sends with every message — stale tokens after a password change are a quiet cause of sends failing while everything looks normal.
One more check while you're here: open Settings → Storage. On a device with almost no free space, Messenger can fail to queue outgoing media at all — free up space and the problem can vanish with it.
Fix 4: Force-Stop Messenger and Clear Its Cache
Now the app itself. Messenger's sending process can wedge — still "working on" a message from an hour ago, with every new send queued behind it. Swiping the app away doesn't reliably kill that process; a force-stop does:
- Long-press the Messenger icon and tap App info.
- Tap Force stop and confirm. (On Samsung (One UI) the same button lives at Settings → Apps → Messenger; on Xiaomi (HyperOS), Settings → Apps → Manage apps → Messenger.)
- From the same screen, open Storage & cache and tap Clear cache. Leave Clear data alone for now — that signs you out and resets the app completely.
- Reopen Messenger and send a test message.
Clearing the cache is safe: your conversations live on Meta's servers, not in the cache, so nothing you've sent or received exists only in the files you just deleted. A cache clear right after a Messenger update is a particularly good bet — that's when corrupted cache data most often starts blocking sends.
Fix 5: Swap the Network Underneath It
Only now — with Messenger's own settings cleared — does the generic network test earn its place, because by this point a failure here genuinely means the network:
- If you're on Wi-Fi, switch it off and send on mobile data. If you're on mobile data, join a Wi-Fi network and send again.
- If sends work on one network and not the other, you've isolated it. On Wi-Fi, restart the router (unplug for 30 seconds) — and if the network is a hotel, office, or campus one, complete its browser sign-in page, which apps can't pass alone.
- If both fail, refresh the phone's data session: turn Airplane mode on for 10 seconds, then off, and retry.
- Turn any VPN fully off for the test as well — rerouted traffic can break Messenger's persistent connection to Meta's servers even when browsing works fine through it.
Sanity check alongside: open a browser or YouTube. If those also struggle, you're fixing a connection, not an app — and the router restart above is the productive next step.
Fix 6: Update Messenger — or Reinstall It Cleanly
The last resort combines the two heaviest app-level moves. Do the update first; it's painless:
- Open the Play Store, tap your profile icon → Manage apps & device → Updates available, and update Messenger if it's listed. Known sending bugs are fixed in updates more often than anywhere else.
- Restart the phone afterwards (hold Power — on Samsung, Side + Volume Down — and tap Restart) and send a test message.
- If sends still fail, reinstall: long-press Messenger → Uninstall, restart the phone, then install it fresh from the Play Store and sign in.
Reinstalling feels risky and isn't, with one exception covered in the questions below: ordinary chats sync back the moment you sign in. What it buys you is a completely clean copy of the app — no wedged process, no corrupted files — which is why it closes this list. Covers Android 10 through 14.
When It's Meta, Not You
If a clean reinstall on a working network still can't send, the remaining explanation is on Meta's side. Check Downdetector for Messenger and Facebook: when the reports graph spikes, thousands of people are watching the same hollow circle, and waiting is the only fix that exists. While you wait, messenger.com in a browser sometimes works when the app doesn't — and if it does, your account and connection are proven fine. One final isolation test, if you have another phone: sign in there. Sends working on a second device point back at your phone's network settings, whose honest last resort is Settings → System → Reset options → Reset Wi-Fi, mobile & Bluetooth — effective, but it erases saved Wi-Fi passwords, so it stays last.
Sending Problems, Answered
Messages arrive fine, but mine won't send. How is that one-way?
Receiving and sending use different paths. Incoming messages ride a lightweight push connection that's hard to break; outgoing messages — especially photos — need a stable upload path. A weak upload signal, Data Saver restricting outgoing data (Fix 2), or an account restriction (Fix 3) can each block sending while receiving carries on.
It's only failing with one person. Everyone else gets my messages.
Then your phone and connection are already proven innocent — the block is specific to that conversation. Either they're on your blocked list, or you've been blocked or restricted at their end (Fix 3). No amount of cache-clearing changes an account-level block, which is why Fix 1's one-chat test exists.
If I reinstall, do I lose my secret conversations?
Ordinary chats, no — they live on Meta's servers and return at sign-in. Secret (end-to-end encrypted) conversations are the exception: they're tied to the device and its keys, and may not reappear after a reinstall. If one matters to you, treat Fix 6's reinstall as a genuine last resort.
Watch: Messenger Not Sending Messages Fixed Step by Step
Prefer a walkthrough? This video covers Messenger failing to send messages step by step:
Video by Trevor Nace — full credit to the creator.
Related Guides:
By Sameer Zehri | App Fix Guru Editor | Last updated: October 2026
