Lost your phone, accidentally deleted Google Authenticator, or got a new phone without exporting? These situations happen every week, but as long as you wrote down the 16-digit backup key or the 8 backup codes, recovery only takes 5 minutes. This article outlines three rescue paths, ranked from fastest to slowest. Once you are ready, log in to the Binance Official Website to enter the recovery process, or use the Binance Official App on a backup device. Apple users should refer to the iOS Installation Guide.
Three Paths: Try in Order
- Fastest (5 minutes): Use the 16-digit backup key to restore the Authenticator on a new phone.
- Faster (10 minutes): Use one of the 8 backup codes to bypass 2FA for a single login.
- Slowest (3-7 days): Appeal to manual customer service to reset your 2FA.
Remember one rule: If you can resolve it yourself, don't contact customer service. Customer service reviews are slow, require many documents, and the process is cumbersome.
Path 1: Restore Using the 16-Digit Backup Key
This is the most recommended method. The prerequisite is that you wrote down the 16-digit backup key when you first enabled 2FA.
What is the 16-Digit Backup Key?
When enabling Google Authenticator binding, Binance displays a 16-character string that looks like ABCD EFGH IJKL MNOP. This is the seed key, and all 6-digit dynamic codes are calculated from this seed.
As long as you have this key string, you can restore your 2FA on any device.
Restoration Steps
- Download Google Authenticator (or Authy, Microsoft Authenticator, FreeOTP) on your new phone.
- Open the APP → Click the "+" at the bottom right.
- Select "Enter a setup key".
- Enter "Binance" as the account name.
- In the Key field, enter the 16-digit backup key you wrote down (spaces can be omitted).
- Select "Time based" for the key type.
- Click "Add".
- The APP immediately starts generating 6-digit dynamic codes.
- Go back to Binance and log in using the dynamic code.
As long as the key is correct, the 6-digit code will be exactly the same as the one on your old phone. This is because they use the same algorithm, based on time and the same seed.
Confirm Validity
Immediately use the newly generated 6-digit code to log in to Binance once. Successful login = restoration complete. You can use it normally.
Path 2: Bypass 2FA Using Backup Codes
Backup codes are the 8 sets of 8-digit numbers that Binance displays after 2FA is successfully enabled. Each code can only be used once and automatically expires after use.
The Purpose of Backup Codes
Backup Code = One-time 2FA token. When you do not have the 6-digit code generated by Google Authenticator, you can use a backup code as a substitute to log in.
Usage Steps
- Open the Binance login page.
- Enter your account and password.
- When you reach the interface asking for 2FA, click "Security verification unavailable?" or "Use backup code".
- Select "Enter backup code".
- Enter an 8-digit backup code.
- Submit.
- Login successful.
What to Do Immediately After Successful Login
A backup code only lets you log in once; it does not solve the 2FA issue. After successfully logging in, you must immediately:
- Go to "Security Center" → "Google Authenticator".
- Click "Disable".
- Re-enable it.
- Scan the new QR code to bind it to your new phone.
- This time, make absolutely sure you write down the new 16-digit backup key and the 8 new backup codes.
Disabling + re-enabling is the key. Otherwise, your next login will still be stuck on 2FA.
What If I Run Out of Backup Codes?
When you have used up or are about to use up the 8 backup codes, you can generate a new set of 8 in the "Security Center". Once generated, the old ones automatically expire.
Path 3: Manual Customer Service Appeal
If you have neither the backup key nor the backup codes, this is the only path left.
Appeal Entrance
- Open the Binance webpage → Go to "Help Center" at the bottom → "Submit a Ticket".
- Select "Account Security & Identity Verification" for the ticket category.
- Select "Reset 2FA / Google Authenticator" as the sub-category.
Required Materials to Submit
- Registered email address
- Registered phone number
- KYC Name
- ID number
- Photos of the front and back of your ID (clear and unobstructed)
- Real-time selfie: Holding your ID + a piece of paper with "Binance Reset 2FA + Today's Date" written on it.
- Video Verification (Customer service will send a link): Turn your head, blink, and read specific numbers as instructed.
- Account-related evidence: The amount of a recent transaction, approximate registration date, recent deposit records, etc.
Review Time
- Initial Review: 24-48 hours
- Secondary Review: 3-7 business days
- Once Approved: Customer service sends a 2FA reset link to your registered email. Click it and complete the reset within 24 hours.
Notes During the Review Period
- Your account will be temporarily frozen to prevent hackers from appealing as well.
- Do not submit duplicate tickets, as it will be flagged as spamming.
- Keep your email accessible, as customer service may request additional materials.
- Never trust "expedited services"; Binance customer service does not charge any fees.
The Phone Is Still There, But Authenticator Was Deleted
This is the best-case scenario. If you didn't lose the phone itself but just accidentally deleted Google Authenticator:
Solution A: iCloud / Google Backup Restore
- iOS: Connect your Apple ID → Re-download Google Authenticator → Log in to your Google Account → If cloud sync was enabled, it will automatically restore.
- Android: If cloud sync for Google Authenticator was enabled (a feature added in 2023), logging back into your Google Account will automatically sync it.
Solution B: Use the 16-Digit Backup Key
This is Path 1.
Solution C: Authy Migration
If you originally used Authy, it has a built-in cloud sync + multi-device feature. You can see your 2FA on any device where you log into your Authy account. It's more convenient than Google Authenticator.
The Correct Approach Before Getting a New Phone
Planning ahead is 100 times easier than fixing things afterward. Before switching to a new phone:
Step 1: Install an Authenticator on the New Phone Too
Do not uninstall the one on your old phone yet.
Step 2: Re-enable 2FA on Binance
- "Security Center" → "Google Authenticator" → "Disable".
- Enter the 6-digit code generated by the old phone to complete the disablement.
- Click "Enable".
- Use the new phone to scan the code and bind.
- Write down the new 16-digit backup key and 8 backup codes.
- Confirm that the new phone can log in normally.
Step 3: The Old Phone's Authenticator Can Be Deleted
Or keep it for a while as a backup.
Common Mistakes and Pitfalls
Mistake 1: Only Taking a Screenshot of the QR Code
If the screenshot of the QR code is lost or corrupted, you have no key to restore it. Hand-copying the 16-character string is the only safe way.
Mistake 2: Saving Backup Codes to the Phone's Photo Album
Phone lost → Photo album lost → Backup codes lost together. Write them down with pen and paper and keep them in a safe or a hidden place at home.
Mistake 3: Saving the Key to Cloud Notes
If the cloud account is hacked, your Binance 2FA is exposed along with it. Never use cloud storage for this.
Mistake 4: Treating a Screenshot of the 6-Digit Code as a Backup
The 6-digit code changes every 30 seconds, making a screenshot completely meaningless. Restoration must use the 16-digit key, not the 6-digit code.
Frequently Asked Questions (FAQ)
Q: Can backup codes be used multiple times?
A: No. Each backup code can only be used once and becomes invalid afterward. Binance marks used backup codes.
Q: Where can I regenerate backup codes?
A: After logging in, go to "Security Center" → "Google Authenticator" → "View backup codes" or "Generate new backup codes". Generating new ones will invalidate all the old ones.
Q: What if I have neither, and I lost my ID card too?
A: This is the most troublesome situation. You need to first go to your local registry to replace your ID card, and then go through the customer service appeal process. Your ID card is Binance's final proof to verify your identity.
Q: Will a customer service appeal definitely pass?
A: Not necessarily. If your KYC information is incomplete, or the evidence provided does not match your KYC, the appeal may be rejected. The more complete and authentic your information was during KYC certification, the higher the success rate of your appeal.