Facebook hacked and can’t log in? Start here.

Match the message to the problem

Suspension and account theft are different issues, even when they happen together. A complaint to a public office does not replace an appeal or extend a deadline shown by Facebook.

Use a familiar device for recovery

For suspected hacking, Facebook recommends starting its recovery process on a device you used to log in before. Open the official page directly and work through its prompts. Record the result if you cannot proceed.

A different browser, a video tutorial, or a paid third party cannot guarantee access. Avoid changing several things at once without noting what happened; clear notes make the next attempt easier to assess.

If a code or identity check blocks you

Check whether the destination displayed belongs to you. If it does not, look for an alternative verification option in the official flow. If Facebook displays a waiting period or other instruction, follow it.

Do not share a code with someone offering to “finish the process.” Account Armor never asks for codes, passwords, remote access, or identity documents.

Separate a recovery problem from device risk

If you suspect malicious software, update your security software, scan the device, and address anything found. Follow your email provider’s security guidance too. The FTC’s hacked-account checklist explains this distinction.

Keep a note of the exact login message, date, and official route used. An error screenshot is more useful than “nothing worked,” but redact private information before sharing it anywhere.

When you are still locked out

Move to what to do when Facebook recovery doesn’t work. That page explains how to organize your attempts and explore public complaint channels without treating them as a guaranteed recovery service.

You can use public resources yourself. The optional guide below packages the preparation steps and templates into one document.