Most "my 2FA code is not working" problems are the same problem in different clothes: a clock, or a secret that does not match. Authy is the exception worth writing separately, because its most common failures are not about the code at all. They are about the account the codes live inside, a desktop app that no longer exists, and a password that nobody — including Twilio — can reset for you.
If your codes are being refused everywhere and you have never touched the Authy desktop app, start with 2FA code not working: causes and fixes, in order, which is the general guide. If your situation involves an empty app, a phone number prompt or a dead desktop install, you are in the right place. The equivalents for the other two big apps are Google Authenticator code not working and Microsoft Authenticator code not working.
The short answer
Work out which of three things has happened, because they have nothing in common:
- The codes are gone rather than refused. Almost always the desktop app, which was retired, or a reinstall on a device that was never linked.
- The app wants a phone number and will not go further. Authy identifies you by the number you originally registered with, country code included.
- The codes are present and refused. Now it is the ordinary problem: clock first, then the entry.
If the codes vanished rather than failed: the desktop app is gone
Twilio announced in January 2024 that the Authy desktop apps for Windows, macOS and Linux would reach end of life on 19 March 2024, and they were discontinued that August, with users logged out and locked out of the desktop app for good (Twilio Help Center, BleepingComputer).
The consequence is specific and it is still catching people out years later: if your tokens were only ever on a desktop install, and that install was never synced to a mobile device, there is nothing left to open. The app will not sign you back in, and the tokens it was showing are not recoverable from it. If they were synced to a phone, they are on the phone, and installing Authy there is the whole fix.
For a replacement that actually runs on a computer, an Authy desktop alternative goes through the options, including what each one gives up.
Multi-device is the setting everything else hinges on
Authy's multi-device setting is what allows a new install to join your account at all. Twilio describes where it lives — "You can find it under 'Settings,' then 'Devices,' then 'Allow Multi-Device'" — and how the trust works: "An already trusted device can extend this trust to another device. This means that you can authorize any other device to access your accounts, and the new device can further extend trust to other devices" (Twilio).
Twilio also recommends switching multi-device off once your devices are set up, on the reasonable grounds that every extra device is another way in. That advice has a sharp edge, and it is worth saying plainly: with multi-device off and only one device, a new install has no trusted device to inherit from. That is the state a lot of people discover they are in on the day their phone breaks, which is exactly the wrong day to discover it.
If the phone still works, the move is ordinary: turn multi-device on, install Authy on the new device, verify, then turn it off again. Moving Authy to a new phone has the full sequence, including which phone number Authy expects.
When the code itself is refused
If Authy opens, shows your tokens, and a service rejects them, Authy is not special and the normal order applies.
Turn on automatic date and time on the phone, then use a fresh code rather than one with a few seconds left. If the clock was already automatic, the cause is the entry rather than the time: an account enrolled a second time at some point, leaving a retired entry that still counts down and still produces well-formed digits; two accounts at one provider with near-identical labels; or a verifier with a tighter acceptance window than you assumed. The causes that survive a correct clock works through each one.
One Authy-specific note on that last point. A code's length is a property of the account, not of the app: Twilio's own description of Authy one-time passwords says it "allows you to choose a token length between 6, 7 or 8 numbers" (Twilio). So if the field in front of you expects six digits and the row you are reading shows seven, you are reading the wrong row rather than hitting a bug.
The backup password, and the one thing Twilio cannot do
Authy's backups are encrypted with a backup password that Twilio never receives, which means Twilio cannot recover or reset it. That is a sound design and a hard limit at the same time: with no working device and no backup password, there is no route back through Authy at all. The route back is each service's own account recovery, and then adding the token again.
If you still have a working Authy install, this is the moment to make sure you know that password, not the day after you need it.
There is no export, so plan around it rather than for it
Authy has never shipped an export. The community scripts that used to read secrets out of the desktop app went with the desktop app, and nothing official replaced them. How to export Authy codes in 2026 (and why you cannot) is the long version, with what still works and what does not.
What that means for a sign-in problem is unglamorous but important: if the answer to your situation is "move to another app", moving is re-enrolment, one account at a time, with Authy kept installed until the last one is verified. Authy alternative lays out that route in order, starting with the email account that controls the others.
Where KeyNesta fits, and what it cannot do
KeyNesta cannot read anything out of Authy. Nobody can: there is no export, so there is no file to import, and any page claiming otherwise is describing the retired desktop scripts. Coming across means re-enrolling each account at its own service.
Two differences are relevant to the failures above rather than to a feature list. KeyNesta has no phone number in it at all, so there is no number to verify against and no device-trust chain that has to be switched on before a new install can join; the vault opens with your passphrase. And it runs in a browser as well as on a phone, which is the gap the retired Authy desktop app left — an Authy desktop alternative covers that comparison properly.
What it cannot do is recover anything for you. Sync is zero-knowledge, so the server holds ciphertext and no key that opens it, and a forgotten passphrase is the same dead end an unknown Authy backup password is. That is the trade, and what zero-knowledge costs you is the honest version of it.
Frequently asked questions
Why does Authy ask for a phone number before it will show my codes?
Authy identifies an account by the phone number it was registered with, so a fresh install asks for that number including its country code, then verifies the new device against a device you already trust. A different number starts an empty new account rather than reopening your old one.
Did my Authy tokens disappear when the desktop app shut down?
If they only ever existed in the desktop app and were never synced to a mobile device, effectively yes: the desktop apps reached end of life in March 2024 and were discontinued that August, and there is no way back into them. Tokens that had synced to a phone are still on the phone.
Can I still install Authy on a computer?
Not as a supported desktop app. The Windows, macOS and Linux apps were retired and Twilio moved Authy to mobile only. If you need codes on a computer, that is a reason to move to an app that supports one, rather than a problem to troubleshoot.
Why is my Authy code refused when the app looks completely normal?
Because a countdown ring proves the maths is running, not that the secret behind it is still live. A retired entry from an earlier enrolment keeps producing well-formed digits for ever. If every service refuses your codes, suspect the clock; if exactly one does, suspect that one entry.
Should I leave Authy multi-device switched on?
Twilio recommends switching it off once your devices are set up, because every trusted device is another way in. The cost of that advice is that a new install cannot join without an existing trusted device, so if you keep it off, keep a second trusted device or a current set of each service's backup codes.
Takeaway
Separate the three failures before you start fixing anything. Codes that vanished point at the retired desktop app or a device that was never linked. An app stuck on a phone number prompt points at the registered number and the multi-device setting. Codes that are present and refused are the ordinary problem, and the ordinary order applies: clock, then entry. And whichever one you are in, the absence of an export means the safe move is always re-enrolment with the old app still installed, never deletion first.