Moving your Binance 2FA to a new phone — or after losing one

The thing that gives you a cold sweat is switching phones and finding that the Binance entry in your authenticator no longer produces codes. This guide separates three cases: a planned switch, a lost phone with a setup key, and every old verification method being unavailable. It also maps Binance's current Manage / Edit and official reset routes.

Why switching phones goes wrong so easily

Authenticator apps use TOTP (a time-based one-time password). When you bind one, Binance displays a setup key (Secret Key) and matching QR code. The app stores that seed and calculates rotating codes from “seed + time”. Anyone who gets the setup key may be able to clone the codes, so it is both recovery material and a highly sensitive credential.

Moving phones means carrying that TOTP entry safely to the new device. You can use a trusted app migration, rebuild it with the setup key, or change the authenticator through Binance's current interface. A setup key is not a separate one-time recovery code, and it is not the only path back into Binance: an official 2FA reset remains available when migration fails. See the setup-key guide for storage details and the complete 2FA guide for method choices.

Switching phones with a plan

This is the easiest case — the old phone is still in your hands. Choose the route that fits:

1. Trusted app migration: if your authenticator supports a trusted export/import, import the Binance entry on the new device and test it. If you use cloud sync, secure that platform account too.
2. Rebuild with the setup key: enter the saved setup key in the new authenticator; both devices then calculate codes from the same TOTP seed.
3. Change it in Binance: go to Security → Authenticator App → Manage / Edit, follow the current prompts, and save the new setup key. Binance says withdrawals and P2P are disabled for 24 hours after the change.

Whichever route you use, make the new device generate valid codes and pass a test before wiping or selling the old phone. Do not delete the old app before testing, and do not send the setup key or QR code through chat.

A lost or broken phone

With the old phone out of action, check whether you saved the setup key or still have a security key, Passkey, or another verification method.

If you have the setup key, enter it manually in an authenticator on the new device to rebuild the same Binance TOTP entry. After signing in, remove the lost phone's session in device management. If the setup key may have leaked with the phone, use Manage / Edit to change the authenticator and invalidate the old seed.

If your backup 2FA is a security key or passkey, it's simpler still: log in with the backup one, then re-bind the new phone's authenticator once you're in. This is exactly why we keep advising you to keep a second method that doesn't depend on a single phone — lose one device and you're not sunk. For how to use a security key or passkey and what to do if you lose one, see how to use security keys and passkeys.

When every old verification method is unavailable

If the phone, setup key, app migration and other verification methods are all unavailable, use Binance's official 2FA reset. On the login verification screen, choose Security verification unavailable?, select the method you cannot use and complete the identity checks shown.

Binance currently says review may take up to 24 hours. After reset, withdrawals, P2P selling, internal transfers and payment services may be unavailable for up to 48 hours. The exact notice can vary by account and region, so follow the live screen. Never trust a third party offering to bypass or fast-track review.

Once access is restored, bind an authenticator again, keep the new setup key offline, and add a backup method that does not depend on the same phone.

The hidden trap of changing your number

Plenty of people change their phone number too when they switch phones, and there's an easily missed trap here.

If your backup 2FA is SMS, changing the number kills that backup — a code sent to the old number never reaches the new one. Then some day the main method (your authenticator) plays up, you reach for the SMS backup to save the day, and find the backup is gone too. So before you change numbers, either update the bound phone number to the new one in Binance, or make sure you still have a method that doesn't depend on a phone number, such as an authenticator or a security key.

Going a step further: SMS is already the weakest of the 2FA methods, vulnerable to SIM swapping. A number change is a good prompt to stop treating SMS as your only verification — demote it to a backup and hand the main role to an authenticator or a security key. For why SMS is fragile and how SIM swapping works, see the piece on SMS verification and SIM swapping.

The pre-switch checklist

Boiling all of the above into a list you can tick off before switching:

1. The new device's authenticator is bound and has passed a test login (done while the old phone is still around).
2. The current setup key is stored offline in two separate places only you can access.
3. If you've changed numbers, you've updated the bound phone number in Binance, or confirmed a backup method that doesn't rely on a number.
4. The old device's login sessions are ended; if the setup key may be exposed, the authenticator has also been changed through Manage / Edit.
5. You still have at least one working backup 2FA — not every method riding on a single device.

Too tedious to check item by item? Use the phone-switch 2FA migration checklist — a few ticks and it tells you what's still missing. A phone switch is also a good moment to review your whole set of defences, so run through the others against the account-security checklist while you're at it.

Common questions