Google Authenticator codes are generated offline, and the binding information exists only on that one phone. Therefore, switching phones is the most common point of failure—many people find they cannot log in after switching devices. Handle it based on your situation:
Situation 1: Old phone still available (most ideal)
- Log in to Binance → In "Security Settings," first disable the old Google Authenticator, then re-enable and bind it on your new phone;
- Alternatively, use the "Transfer Accounts/Export" feature built into the Google Authenticator app to migrate the authenticator to your new phone;
- Only after confirming the migration is successful should you wipe or dispose of the old phone.
Situation 2: Phone lost or reset (authenticator gone)
- On the login page, select "Can't get verification code / Reset two-factor authentication," then follow the prompts to verify your identity using your registered email, SMS, facial recognition, or ID documents. Once verified, you can disable the old 2FA;
- This process usually includes a 24–48 hour security cooldown period, during which withdrawals are restricted—this is a normal risk control measure;
- After recovery, immediately re-bind Google Authenticator, and write down the initial key (the string of letters and numbers) and store it offline. This way, you won't have to worry the next time you switch phones.
For detailed setup and binding steps, see the Google Authenticator Setup Guide. For overall account security, refer to Binance Account Security Settings, and be sure to enable Anti-Phishing Code to prevent fake customer service from tricking you into revealing your verification code.
The above content is for educational and procedural purposes only and does not constitute investment advice.