Facebook Login Code Not Received? How to Get Back In

Codes are time-limited, and a new request can make older ones stop working. Asking for codes repeatedly can also trigger a temporary limit.

1. After requesting a code, wait a few minutes before asking again.
2. Delete or ignore older Facebook texts and emails so you don’t enter the wrong one.
3. Type the newest code carefully, with no spaces, and do it promptly.
4. If your phone offers to autofill the code from a text, check it matches the latest message.

Most SMS problems are on the receiving end: signal, blocked senders, message filters, or a full message inbox.

Some mobile plans, such as some prepaid, business or child-safe plans, may block texts from short-code numbers. If nothing at all arrives, your carrier’s support can tell you whether short-code messages are allowed on your line. Warning sign: if your phone suddenly loses all signal and codes stop at the same time, contact your carrier at once — that can be a sign someone has moved your number to their SIM (a “SIM swap”).

Email providers often filter security messages. And if the account uses an old address, the email is arriving, just not where you’re looking.

1. Search your mailbox for “Facebook” and check Spam, Junk, Promotions, Updates and All mail.
2. Compare the partly hidden address on Facebook’s screen with the inboxes you actually use.
3. If your inbox is full, delete some messages so new mail can arrive.
4. Mark the Facebook email as “not spam” once you find it, so the next one lands in your inbox.
5. Be cautious: before using any link, check the email is genuinely from Facebook. Meta has a help page on how to tell (linked below). Typing the code into Facebook yourself is safer than clicking links.

If you set Facebook up with an authenticator app (such as Google Authenticator, Microsoft Authenticator or a password manager), it generates codes on your phone with no text message needed, even without signal.

1. On the code screen, look for an option such as Try another way and choose the authentication app if it’s offered.
2. Open your authenticator app and find the Facebook entry.
3. Enter the current six-digit code before it changes.
4. If codes are always rejected, check your phone’s date and time are set automatically: authenticator codes depend on an accurate clock.

Meta says that if you’re already logged in to Facebook on a different browser, phone or tablet, you may see a prompt there to approve the new login attempt without needing a code.

1. Find any device where you’re still logged in to Facebook — an old phone, a tablet, a work or family computer.
2. Open Facebook there and check your notifications.
3. If you see a prompt about the new login attempt, confirm it was you to approve it.
4. Go back to the device you’re logging in on; it should continue without a code.

Facebook lets people with two-factor authentication create login recovery codes, one-time backup codes for exactly this situation. Meta has a help page on setting them up.

1. Look for wherever you stored them: a printout, a password manager, a notes file, or a photo you saved when you turned on two-factor authentication.
2. On the code screen, choose Try another way (or similar) and pick the option to use a recovery or backup code.
3. Enter one recovery code in place of the two-factor code. Meta says each recovery code can only be used once, so cross it off afterwards.
4. Once you’re in, set up two-factor authentication again on your new phone and create fresh recovery codes.

If you can’t get a code, can’t approve from another device and have no recovery codes, Meta says you can ask Facebook to confirm your identity so you can regain access. The help link has a different name on each device.

1. Try to log in and continue until you reach the screen asking for your two-factor code.
2. Find the help link on that screen (see your device below).
3. Confirm your identity. Meta says this may involve uploading a photo of a government-issued ID (such as a driving licence or passport), answering security questions about your account, or confirming through trusted contacts you set up earlier — the options depend on what you set up.
4. Submit, then wait. Meta says you’ll receive instructions typically within 1–2 working days, by the email or phone number on your account.
5. Do this on a device you’ve logged in on before if you can, and only inside Facebook’s own screens — never through a link someone sends you.

No access to your phone at all? Meta says to look for I don’t have my phone on the authentication screen, then Contact us. Using Facebook Lite? Meta says identity confirmation isn’t available in Facebook Lite — use the full Facebook app for Android or facebook.com in a browser.

When you’re abroad, texts may not reach a home SIM that isn’t roaming, and a local SIM has a different number. Logging in from a new country can also trigger extra security checks.

1. Check your home SIM has roaming turned on and can receive texts abroad (some plans can’t, or charge for it).
2. If you switched to a local SIM, codes will still go to your home number. Put the home SIM back in temporarily if you can.
3. Prefer an authenticator app or recovery codes while travelling: they work without signal or roaming.
4. If you log in with a phone number, include the correct country code (for example +44 for the UK, +1 for the US and Canada, +61 for Australia).
5. Expect possible extra checks when you log in from a new country, and try from the device you normally use.

Before your next trip: add an authenticator app and save recovery codes, so a SIM swap or no-signal situation can’t lock you out.

This is a temporary security limit. Every new request or attempt can extend it, so waiting is the fix.

1. Stop requesting and entering codes. Facebook doesn’t publish how long the limit lasts, so give it a good while before trying again.
2. When you return, use a familiar device and network.
3. Request one code, wait for it, and enter it carefully, or use your authenticator or a recovery code.