Popout AuthenticatorMoving from Authy Desktop and other apps
Pick your app below. For the original Authenticator extension, see its own guide.
Get Popout Authenticator
Authy
Twilio ended Authy Desktop (Windows, macOS, Linux) on 2024-03-19 — Twilio's end-of-life guide (checked 2026-10-15). Authy does not offer exporting tokens — Export or Import Tokens in the Authy app (checked 2026-10-15).
So you set each account up again:
- For each service, sign in and open its two-factor settings.
- Set up the authenticator app again. The service shows a new QR code.
- Add the new QR code in Popout: + → "Find QR on screen", or + → "Add account" → "QR code" tab.
- Keep Authy until every account works in Popout.
If you already have a JSON list of otpauth:// links from an earlier export, Popout can read it via "Backup file".
Google Authenticator
- On the phone, open the app's Menu → Transfer codes → Export codes (English app labels; see Google's instructions, checked 2026-10-15).
- Unlock, select the accounts, and choose Next. The app shows one or more QR codes.
- In Popout, select + → "Read QR with camera", or + → "Add account" → "QR code" → "Choose QR code images" (you can choose several images at once).
- If there are several QR codes, scan each one.
These QR codes contain your secret keys. Don't share them, and delete any screenshots or photos afterwards.
Other apps
Use an unencrypted export unless the table says otherwise. For encrypted Aegis, 2FAS, and Bitwarden files, Popout tells you to export an unencrypted file from that app instead (for example, "Export an unencrypted file from the Aegis app and use that.").
| App | What to export | Notes |
|---|---|---|
| Aegis | Unencrypted vault export (JSON) | Encrypted export is not supported. |
| 2FAS | 2FAS Backup → Export, without setting a password (2FAS support, checked 2026-10-15) | The file ends in .2fas. If the file picker doesn't let you select it, rename the file to end in .json. From version 1.0.1 the picker also offers .2fas files. |
| Bitwarden Authenticator | Settings → Export → file format .json → Export items (Bitwarden help, checked 2026-10-15) | CSV is not supported. An unencrypted Bitwarden password-manager JSON export also works (TOTP fields are read). |
| FreeOTP+ | Its JSON export, or a text file of otpauth:// links | |
| andOTP | Plain (unencrypted) JSON backup | Encrypted backups are not supported. |
| Raivo | Settings → Export OTPs to ZIP archive (per Bitwarden help, checked 2026-10-15) | Unzip it with the password you chose, then import raivo-otp-export.json. Popout cannot open the ZIP itself. |
| 2FA Authenticator (authenticator.sh) | Its backup file, plain or encrypted | For an encrypted file, Popout asks for the password. |
| Any app | A .txt file with one otpauth:// or otpauth-migration:// link per line | You can also paste links in the "Links" tab. |
Import into Popout
- In Popout, select + → "Add account" → "Backup file" tab → "Choose a backup file." From the toolbar popup, a small window opens for choosing the file.
- For an encrypted backup from 2FA Authenticator, Popout asks: "This backup is encrypted. Enter its password." Type it in "Backup password" and select "OK". If the password is wrong, you see "The password is incorrect."
- A result message shows how many accounts were added. Accounts that already exist (same type and same secret) are skipped. Existing accounts are never overwritten.
If the file is not recognized, Popout shows "Unknown format".
Afterwards
- Compare a code in both apps before you remove anything.
- Delete unencrypted export files. They contain your secret keys.