Binance authenticator won't bind or scan? Work through it in this order

When binding an authenticator to Binance stalls, it's rarely a broken account — it's one of a few specific, fixable causes. Either the QR code won't scan, or you bind it and Binance keeps saying the code is wrong. The two have different roots: one is stuck at the scan, the other at entering the code. Below splits the checks into those two stages and hands you an order to follow, so you don't rush off to the recovery flow.

Work out which stage you're stuck at

Placing yourself in the right bucket first saves half the effort. Bind failures fall into two common types, with different roots:

• Stuck at the scan: the QR code just won't go in, or you get an "unable to read" message, and no entry ever gets added — usually a scanning-method or camera-permission problem.
• Stuck at the code: the entry is added and a code rotates every 30 seconds, but typing it into Binance returns "code is wrong" — nine times out of ten that's a clock out of sync, or a small slip while entering the code.

When the QR code won't scan or read

1. Switch to entering the key by hand: the page showing the QR code usually also lists a string of letters and numbers — the secret key. In your authenticator, choose "enter a setup key" and type it in; it's equivalent to scanning and sidesteps camera-reading trouble entirely.
2. Don't scan one screen with another phone: screenshotting the QR onto phone A and scanning A's screen with phone B often fails — glare and scaling get in the way. Enter the key by hand on the same phone, or scan the original screen directly.
3. Check camera permission and app version: with no camera permission the scan box stays black or won't catch, so turn it on in system settings; a very old app can fail to scan too, so update and try again.
4. The QR code expires: linger too long on the binding page and the code goes stale — step back, generate a fresh one on Binance's current screen, and scan that, or copy the key printed beneath it.

"Code is wrong" after binding: check the time first

The entry is added, the code is rotating, yet it's always rejected — the most common culprit here is your phone's clock being out of sync.

An authenticator runs on TOTP (a time-based one-time password): from "secret seed + the current time" it computes a code locally every 30 seconds, with no network and no SMS. Binance's servers verify with the same seed and algorithm against their own time — when the two clocks don't line up, the codes don't match.

So even a phone clock that's a minute or two off produces a code that won't match, giving "code is wrong" every time. The fix is simple: set the system time to automatic / network-synced (don't hand-tune the clock to try to match). Some authenticator apps also carry their own "time correction" you tap once — where exactly it lives may change, so go by your app's current settings screen.

Time's right and it still fails — check these

Once the clock is fixed and it still won't take, it's usually one of these small details:

• An old entry left behind alongside the new scan: after unbinding and re-binding, your authenticator may hold two Binance entries at once, old and new, nearly identical — only the new one is valid. Delete the old, keep just the one you've bound.
• A space copied along with the code: authenticators often show the six digits as "123 456"; typing it out is fine, but copy-paste tends to drag the space in, and Binance reads that as wrong. Before submitting, check it's six plain digits.
• Landing right on the 30-second turnover: the code changes every 30 seconds, and by the time you see it there may be two or three seconds left, so it expires mid-entry — if it's about to flip, wait for the fresh one.
• The app or OS was just updated: a big version update can throw the odd compatibility hiccup; restart the app, and the phone if need be, then try again.

A tick-through troubleshooting order

From simplest to most involved — if it won't bind, work down the list:

1. First sort out: does the code refuse to scan, or does it say the code is wrong after binding?
2. Won't scan → switch to entering the key by hand, and don't screenshot-and-scan; still nothing, check camera permission, update the app, regenerate the code.
3. Code is wrong → set the phone's time to auto-sync first, then retry.
4. Still wrong → delete the void old Binance entry and confirm you're reading the new one.
5. Still wrong → check whether the copied code carried a space, and wait for a fresh code rather than catching the 30-second edge.
6. Still locked out → only then use Binance's official account-recovery / 2FA-reset flow; that's the fallback, not the first step.

Once it binds, do two things straight away

1. Copy the recovery codes down offline: at binding time Binance gives you a string of recovery codes (or the secret seed itself). Copy it onto paper there and then, or into an offline password manager — don't just screenshot it into your photo library, or it vanishes with the phone. For moving 2FA across when you switch, see moving your Binance 2FA to a new phone.
2. Log out and back in once, right away: while it's fresh, sign out and log back in with the new authenticator to confirm the whole route works; if a code is rejected again, go back up and keep checking, so you don't discover it when you actually need it.

Not sure a phone switch will go smoothly? Tick through the phone-switch 2FA migration checklist first.

Common questions