Why Is Messenger Not Working? A Practical Checklist

Messenger can fail in several different ways: the app may not open, chats may not load, a message may stay unsent, or only one conversation may have a problem. The fastest way to troubleshoot is to identify which of those is happening before changing settings. A failed message to one person does not prove they blocked you, and an app that will not open does not prove your account is suspended.

Start with a short check: Can your device load another website? Can Messenger open? Can you read an older conversation? Does the problem affect every chat or just one? Does Facebook show an account notice? Those observations help you choose the right next step. Meta separates app crashes, send failures, message limits, and login problems in its Messenger Help Center for the same reason.

If the app will not open or keeps closing

First close Messenger completely and reopen it. Restart the device if the app still crashes. Check the official app store for an available Messenger update, then make sure your device has enough free storage to run apps normally. Meta lists app updates, device storage and restart steps among its troubleshooting advice for Messenger problems. Do these simple checks before deleting the app or changing your account password.

If the crash began after a device or app update, note the version and the exact action that triggers it. For example, does the app fail immediately, or only when you open a particular chat or attachment? That distinction is useful if you need to report a bug. Try a stable connection, but remember that a pure app crash and a network error are different symptoms. A connection change might not fix a broken local installation.

If you consider reinstalling, check that you know how to sign back into the correct account first. Do not delete locally stored files or clear app data without understanding the possible effect on your device. This page cannot confirm what your particular phone has backed up. A safer order is to check the app update and Meta's Help instructions, then use the device maker's app troubleshooting guidance if the problem persists.

If chats or new messages will not load

Check the connection with another website or app. If everything on the device is offline, reconnect to Wi-Fi or mobile data. If only Messenger is affected, try closing and reopening it, then compare what you can see on another device or the supported Messenger web experience if you already use one. A difference between devices can point toward a local app problem; the same problem everywhere suggests checking the account and service side as well. It is a clue, not a definitive diagnosis.

Look for a loading or error indicator in the conversation. Do not repeatedly send the same sensitive information while the state is uncertain: a delayed message may send later. If the app begins working again, inspect the chat to see what actually sent. For an urgent conversation, use another contact method you already have rather than assuming that a stuck Messenger delivery reached its recipient.

Messenger has separate account and app Help topics. Meta's Messenger account hub includes account switching and deactivated-Facebook options, while its problem hub addresses app and send failures. If you switch between accounts, confirm that the missing chat belongs to the account currently open. An absent thread under the wrong account is not evidence of a data deletion.

If messages will not send to anyone

Try one ordinary message after confirming the connection. If it fails across several unrelated chats, update the app, restart the device, and check storage. Meta's unable-to-send guidance lists network, device or app problems among possible causes. Check for any explicit account message or restriction notice. The error shown to you is more reliable than a guess based on how someone else's profile looks.

Meta also says sending many messages or messages that violate its rules can lead to a temporary messaging limit. That does not mean every send error is a penalty. If a notice identifies a limit, read its terms and any review option offered to your account. Do not use other accounts or bulk-message tools to evade a restriction. If there is no notice and routine troubleshooting fails, use Messenger's Report a problem path described in Meta Help. Include the wording of the error, when it started, and whether every chat is affected; avoid sending a password or private conversation contents to an unofficial support page.

Do not assume that waiting a fixed number of hours will restore sending. An app error, account problem and policy limit have different remedies. The available notice or support flow should guide the next step.

If only one conversation fails

Try another existing chat. If that one works, a general connection failure is less likely. The specific conversation may involve an unavailable account, changed message permissions, blocking, a group membership change, or another restriction. Meta mentions some of those possibilities in its unable-to-send Help, but it does not provide a public tool that tells you why another person's account looks different from yours.

Do not use a missing profile picture as a test for blocking or deactivation. People can change photos, privacy settings and accounts, and the app can display an incomplete state. A message error alone cannot tell you what a person decided. If the relationship and situation warrant it, use another respectful contact method you already have. Do not make multiple new accounts to probe the person; if they have chosen not to be contacted, respect that boundary.

For a group chat, check whether the group is still present and whether you still belong to it. A group message may fail for reasons different from a one-to-one conversation. For Marketplace inquiries, Meta has a separate Marketplace messaging Help page that notes access and regional limits. Keep a Marketplace-specific error in that context rather than assuming all of Messenger is broken.

If you cannot sign in

An inability to log in needs a different path from an unsent message. Check that you are using the intended account and its official sign-in method. Follow the on-screen recovery or verification flow if Meta asks for one. Avoid websites or people who promise to unlock Messenger for a fee or ask for a one-time code. This article cannot bypass account security checks, and it cannot verify a third-party recovery service.

If you recently deactivated Facebook, do not assume that alone explains every Messenger problem. Meta documents ways to use Messenger with a deactivated Facebook account, and some regions offer a separate account choice. The exact sign-in arrangement depends on your account. Use the Help path that matches your own setup and the error you see.

If you have an explicit security or enforcement notice, read it in the official app or Help Center. Save the notice wording and follow any review step it offers. A failed login without a notice should not be labeled a policy suspension just because it feels sudden.

How to report a persistent problem

After the basic checks, write down the symptom in one sentence: “Messenger opens, but messages to all chats remain unsent on Wi-Fi and mobile data,” or “The app closes when I open one chat.” Include the device type, operating system, Messenger app version, approximate start time, and exact error text. Note what you already tried. This helps distinguish a crash, a connection problem and an account-specific failure.

Use the app's official Report a problem option if available or navigate through Meta's Messenger Help Center. Do not send your password, login code, or private chat to a person claiming to be support in a comment or direct message. If an account notice gives a specific review path, use that path rather than filing a generic bug report for a policy decision.

Quick decision guide

The practical answer is to diagnose the particular failure and use the matching Help path. Neither a missing photo nor a generic send error reveals whether someone blocked you. Neither an update nor a restart guarantees a fix. Each step narrows what to check next and makes a support report more useful if the problem continues.

Source review: 2 October 2026. Feature availability and menu labels can vary by account, region, app version and device.