How to Move Google Authenticator to a New Phone? 3 Ways to Keep Your Binance 2FA
How do you move your Binance 2FA from Google Authenticator to a new phone? This guide covers three cases: old phone still available, still able to log in, and old phone lost, with steps for QR export, re-binding and reset.
When you switch to a new phone, the Binance verification codes stored in Google Authenticator are the part most likely to go wrong, because you need them every time you log in to the Binance Official Site or open the Official Binance App; iPhone users can read the iOS installation tutorial on this site first. The short answer to the title question: if the old phone is still with you, use the "Transfer accounts" feature built into Google Authenticator and scan the exported QR code; if the old phone is gone but you can still log in to Binance, unbind the old authenticator and bind it again on the new phone; if the old phone is lost and you cannot log in, you need to go through Binance's security verification reset process. BiabaApp is an independent third-party tutorial site, not Binance itself, so menu names and procedures shown on the official Binance pages and in the app always take precedence.
First, Work Out Which Situation You Are In
A: The right method depends on two conditions: whether you still have the old phone, and whether you can still log in to your Binance account. These two conditions decide which path to follow, how long it takes and how risky it is. The table below puts the three common cases side by side.
| Case | Old phone status | Can you log in to Binance? | Suggested method | Difficulty |
|---|---|---|---|---|
| Case 1 | Still in hand, authenticator opens | Yes | "Transfer accounts" QR scan inside the authenticator | Low |
| Case 2 | Gone, or authenticator wiped | Yes (using another verification method) | Unbind in Binance, then bind again | Medium |
| Case 3 | Lost, broken or reset | No | Binance security verification reset process | High |
If you cannot tell which case applies, the safest approach is to keep Google Authenticator installed on the old phone and avoid a factory reset until the new phone is confirmed to generate working Binance codes.
What to Prepare Before Switching Phones
A: The most important preparation is to confirm that the authenticator on the old phone still works and that your Binance account has other verification methods available. Many people only discover on the day of the switch that the old phone has already been traded in, and by then the options are much narrower. Work through the checks below before you start.
- Confirm that the Binance entry is visible in Google Authenticator on the old phone and that the 6-digit code refreshes normally.
- Confirm that the email address and phone number linked to the Binance account are still usable. If you are changing phone numbers, update the number in Binance first.
- Check whether you saved the setup key from the original binding. When Binance first binds Google Authenticator it shows a text key, and if you wrote it down at that time, it is the most direct recovery credential.
- Do not log out of Binance yet. Keeping the Binance app signed in on the old phone helps, because some operations need the old device.
- Install Google Authenticator on the new phone from a legitimate source such as Apple's App Store or Google Play, and never from an unknown installer file.
The Chinese-language article on this site about setting up Binance 2FA with Google Authenticator describes the full first-time binding process and can be used to check that your backups are complete.
Method 1: The Old Phone Is Still Available, Use "Transfer Accounts"
A: Google Authenticator has a built-in "Transfer accounts" feature that lets the new phone scan a QR code generated on the old phone and copy every entry across. This is the simplest method, and the Binance entry moves together with the authenticator entries of other websites, with no changes needed in the Binance back end.
Step 1: Install Google Authenticator on the new phone
Install Google Authenticator on the new phone from the App Store or Google Play, open it once and stay on the main screen. Android users whose region cannot access Google Play need a trustworthy overseas app store, and should check that the developer is Google LLC after downloading.
Step 2: Generate the export QR code on the old phone
Open Google Authenticator on the old phone, go to the menu, choose "Transfer accounts", then "Export accounts", select the entries to move (including Binance) and tap "Next". The screen will show one or more QR codes. Menu wording can differ slightly between versions, so follow what the app currently displays.
Step 3: Scan and import on the new phone
In Google Authenticator on the new phone, open "Transfer accounts", choose "Import accounts" and scan the QR code on the old phone's screen. If several QR codes were exported, scan them one by one. When the import finishes, the new phone shows the same entries as the old one.
Step 4: Check that the new phone's codes work
Return to Binance and test the 6-digit code from the new phone, either on the Binance login page or in any operation that requires two-factor verification. Once the code is accepted, you can clean up the entries on the old phone.
Note: An export QR code is equivalent to a complete verification key. Screenshots or photos leave the key in your photo library, so delete them as soon as the transfer is done, and make sure nobody else or no camera can see the screen while you work.
Method 2: The Old Phone Is Gone, but You Can Still Log In to Binance
A: If you can still log in to your Binance account, unbind the old Google Authenticator inside Binance and bind it again with the new phone; the old code is not required. The condition is that the account has another working verification method, such as SMS verification on a bound phone number, email verification or a passkey.
Step 1: Log in and open Security settings
Log in to Binance using email verification, phone verification or another method that still works, then open the "Security" page under your account or profile and find the Google Authenticator entry (some versions label it "Authenticator App").
Step 2: Unbind the old authenticator
Choose "Change" or "Unbind" for that entry, and Binance will ask you to confirm your identity with another verification method. In some cases, changing a verification method triggers a temporary restriction on sensitive actions such as withdrawals. This is part of Binance's risk control, and how long it lasts follows what the Binance page shows.
Step 3: Bind again on the new phone
After unbinding, follow the on-screen prompts to bind Google Authenticator, scan the QR code on the new phone or type in the key shown on the page, and enter the 6-digit code generated by the new phone. The page shows a setup key again at this stage, and you should copy it down by hand.
Step 4: Check the features that depend on it
After binding, check login, withdrawal whitelist, API management and any other feature that relies on two-factor verification, and confirm that each accepts the new code.
Method 3: The Old Phone Is Lost and You Cannot Log In
A: If the old phone is lost, the authenticator cannot be recovered and no other verification method is available, you need to reset 2FA through Binance's account security verification process. This is the slowest case and usually involves face recognition, identity checks and a review period.
- On the Official Binance App or on the web login page, choose "Verification code unavailable" or a similar entry; the exact name follows what Binance currently shows.
- Follow the prompts to pick the verification item to reset, upload your ID document and complete face recognition. The document should match the information used for the account's identity verification.
- Wait for the review after submitting. Processing time is not fixed and follows what the Binance page and notifications say, and withdrawals may be restricted in the meantime.
- Once approved, follow the instructions to bind Google Authenticator again on the new phone and save the new setup key.
If the account has not completed identity verification, fewer documents are available for the check, and the process becomes harder. This is one reason new users are advised to complete identity verification and create backups early.
Comparison of the Three Methods
A: In terms of speed and safety, "Transfer accounts" is the fastest, re-binding sits in the middle and the security verification reset is the slowest. The table below summarizes time, prerequisites and main risks.
| Item | Transfer accounts scan | Unbind and re-bind | Security verification reset |
|---|---|---|---|
| Old phone needed | Yes | No | No |
| Binance login needed | No | Yes | No |
| Changes Binance settings | No | Yes | Yes |
| Withdrawals may be restricted | Usually not | Possibly | Possibly |
| Main risk | QR code leaked by a screenshot | Weaker protection while unbound | Review time is uncertain |
| Other websites' authenticators affected | Moved together | Must be moved separately | Must be moved separately |
Checklist After the Migration
A: After the migration, confirm on the new phone that each code works before you deal with the old phone. The table below lists what to verify.
| Check | How to do it | Pass condition |
|---|---|---|
| Login verification | Log out of Binance and log in again | The new code is accepted |
| Sensitive action verification | Try changing one security setting | The new code is accepted |
| Setup key backup | Write it down and store it safely | The paper copy is legible |
| Old phone entries | Delete only after the new phone is confirmed | Old entries removed |
| Other websites' authenticators | Test them one by one | All generate codes normally |
| Time sync | Check that the new phone's time is set automatically | Codes are not rejected |
Risks and Security Notes
A: The core risks when migrating 2FA are a leaked verification key and clearing the old device too early. The points below deserve special attention in practice.
- Never send the QR code or setup key to anyone. Binance support does not ask users for Google Authenticator codes or keys, and anyone who asks should be treated as a scammer.
- Do not store the setup key in plain text in chat apps or cloud notes. A paper copy kept in a safe place at home is harder to steal remotely than an electronic backup.
- Watch out for fake pages. Reset 2FA only through the official Binance website or the official Binance app, and use the Binance Verify tool to check whether a link or email really comes from Binance.
- Do not sell, trade in or reset the old phone before the migration is complete.
- Mind the time sync. The 6-digit codes in Google Authenticator depend on the phone's system time, and if automatic time is turned off on the new phone, codes may keep being rejected.
- Users in mainland China must follow local laws and regulations. Cryptocurrency trading carries price and policy risk, so judge for yourself and bear the risk.
FAQ
Q: Do Binance codes sync automatically when I change phones with Google Authenticator? A: Google Authenticator can now sync entries after you sign in to a Google account, but whether sync is turned on depends on your own settings. To be safe, use the "Transfer accounts" feature or keep a handwritten copy of the setup key as a backup, and do not rely on cloud sync alone.
Q: The old phone has been factory reset. Can the authenticator entries still be recovered? A: If Google account sync was not turned on and no setup key was saved, the entries cannot be recovered locally, and you need to bind again or reset inside Binance following Method 2 or Method 3.
Q: Will my account be restricted from withdrawing after I unbind Google Authenticator? A: After a security verification method is changed, Binance may restrict sensitive actions such as withdrawals for a period to protect the account. The exact length and scope follow what the Binance page shows.
Q: Why does the new phone keep showing wrong codes after scanning? A: The most common cause is an inaccurate clock on the new phone. Turn on automatic time in the system settings and generate the code again. If the error continues, consider binding again.
Q: Can I keep the same Binance authenticator on two phones at once? A: Technically yes, because two phones scanning the same QR code produce identical codes, but this raises the risk of a leaked key. After the migration, deleting the entry on the old phone is recommended.
Q: Can I switch to SMS or email verification and stop using Google Authenticator? A: Binance supports several verification methods, and the currently available options are listed on the security page. The methods differ in strength, and an authenticator app is generally considered harder to intercept than SMS, but the actual options follow what the Binance page shows.
Q: How long does a 2FA reset usually take? A: There is no fixed figure; it depends on the review queue and whether your documents are complete. Follow the status messages in the Binance app and the email notifications.
Summary
To move Binance 2FA to a new phone, first decide whether the old phone is still available and whether the account can be logged in to, then choose one of three paths: "Transfer accounts" scan, unbind and re-bind, or a security verification reset. Saving the setup key in advance, and dealing with the old phone only after the migration has been completed and tested, is the key to avoiding being locked out. If you need to install or update the client, you can get it through the Official Binance App entry and check that the source is legitimate.