Proton Authenticator is a free, open-source TOTP app for Android, iOS, Windows, macOS, and Linux. It can keep codes on one device without a Proton account, synchronize them through an end-to-end encrypted Proton account, or use iCloud synchronization across supported Apple devices. Direct imports, exports, offline code generation, and desktop clients make it one of the more flexible account-optional authenticators.
Correction published August 30, 2026: The previous edition incorrectly called Proton Authenticator a 2024 mobile-only product, said a Proton account was required, denied desktop and independent recovery options, used unsupported first-person testing claims, and displayed generated product-interface images. This edition removes those claims and images, distinguishes local storage, Proton sync, iCloud sync, and device backups, and cites Proton’s current documentation for each product statement.
Short verdict: Proton Authenticator is a strong general-purpose choice for people who want both mobile and desktop access without mandatory account creation. Its documented encryption and export paths are meaningful, but the current public security model is still Proton’s own account of the design. TOTP itself is not phishing-resistant, so passkeys or FIDO2 security keys remain preferable where a service supports them.
What Proton Authenticator officially supports
Proton announced the standalone app on July 31, 2025, not in 2024. The launch announcement and current setup guide list iOS, Android, Windows, macOS, and Linux. Proton says every version is free, has no ads or tracking, and can generate configured TOTP codes offline.
An account is optional. A user can add codes and keep them locally on one device without signing in. A Proton account enables encrypted synchronization across different operating systems. Apple users can alternatively synchronize across Apple devices with iCloud. These are separate choices, not one mandatory Proton cloud workflow.
The app accepts a camera-scanned enrollment QR code on mobile or a manually entered secret. It also supports imports, exports, biometrics or a PIN, and automatic backup options. Open-source availability makes implementation review possible, but it does not establish that every released binary, platform integration, or future version is defect-free.
This review checks current official documentation and the published security model. It is not an independent usability evaluation, source-code audit, penetration test, or cryptographic assessment, so it does not assign a numerical score.
Three operating models: local, Proton sync, and iCloud
The most important setup decision is where the authenticator data should live.
| Mode | Account required | Device scope | Recovery responsibility |
|---|---|---|---|
| Local-only | No | One configured device | User-managed export or backup |
| Proton account sync | Proton account | Android, iOS, Windows, macOS, and Linux | Proton account access plus independent recovery material |
| Apple iCloud sync | Apple account and iCloud | Supported Apple devices | Apple account, Keychain availability, and separate export |
Local-only mode minimizes account dependency. The trade-off is that losing or resetting the only device can also remove the only working copy unless a backup or export exists elsewhere.
The Proton sync guide says cross-device sync through Proton requires signing in to a Proton account. The same guide identifies iCloud as another route for Apple devices. Neither choice is needed for ordinary offline TOTP generation after an entry has been configured.
Do not confuse synchronization with backup. Sync can quickly reproduce an accidental deletion or account change across devices. A separately stored encrypted export gives a different recovery path and reduces dependence on one account provider.
What the published encryption model says
Proton’s October 2025 security model says cryptographic operations for synchronized Authenticator data happen locally and the service does not receive plaintext entries or plaintext encryption keys.
For Proton account sync, the document says the client creates a random 32-byte Authenticator Key. That key is encrypted and signed with the account’s User Key, and authenticator entries are encrypted with 256-bit AES-GCM. The account authentication and key-unlocking flow also depends on Proton’s wider account cryptography.
For accountless local storage, the app uses operating-system key facilities. Proton identifies Android Keystore, Apple Keychain, Windows Credential Manager, and a DBUS Secret Service on Linux. On Windows and Linux, the documented fallback can protect the local random key with a password when the normal credential service is unavailable.
These details are useful because they specify the intended key boundaries instead of merely saying data is secure. They remain vendor-published design claims. The same document said independent Authenticator audits would be published when available; the official material reviewed for this update did not expose a product-specific independent audit report. Open source and bug-bounty eligibility improve transparency but are not substitutes for a scoped audit result.
Backups and exports are different recovery tools
Proton documents both platform backup controls and portable export. They solve related but different problems.
The backup guide says Apple devices can periodically save Authenticator data to iCloud. Android users can choose a backup location and update frequency. Proton’s security model separately describes a password-protected local backup whose encryption key is derived with Argon2.
An export is the portability path. Proton says users can export their codes and retain the file in another secure location. An exported authenticator vault contains reusable OTP seeds, not merely the six-digit codes currently displayed. Anyone who obtains readable seeds can generate future codes.
Use a long, unique password for an encrypted backup. Keep at least one copy off the authenticator device, and do not send a plaintext export through ordinary email or cloud notes. Delete temporary migration files after the destination app has been checked.
Recovery should also include the one-time recovery codes issued by each protected website. Store those separately from Proton Authenticator and separately from the Proton account used for sync. That prevents one account or vault failure from blocking every recovery route at once.
Import and migration support
The official import guide currently provides migration instructions for 2FAS, Aegis, Bitwarden Authenticator, Ente Auth, Google Authenticator, LastPass Authenticator, Proton Authenticator, and Proton Pass. It accepts supported CSV data and QR-based transfers.
Support for a named source does not guarantee every record will import. Proprietary formats, malformed labels, unsupported algorithms, duplicate entries, or old exports can still need manual repair. If the source app cannot export a reusable secret, open the protected service’s security settings and enroll Proton Authenticator as a new authenticator instead.
Use a staged migration:
- Export or re-enroll one noncritical account.
- Confirm the issuer and account label are correct.
- Complete a signed-out login with a fresh code from Proton Authenticator.
- Save the service’s newly issued recovery codes.
- Repeat for email, password-manager, registrar, financial, cloud, and developer accounts.
- Keep the old authenticator until all important logins and recovery paths have been verified.
A code appearing in the new list proves only that data was parsed. A successful signed-out login proves the service and app agree on the secret and TOTP parameters.
Desktop access is convenient and expands the trust boundary
Native Windows, macOS, and Linux clients are a practical differentiator. They reduce phone switching during desktop logins and provide a current replacement path for people who previously relied on discontinued desktop authenticators.
That convenience places reusable OTP secrets on more endpoints. A synchronized laptop with malware, a weak operating-system login, an unlocked session, or an exposed remote-desktop service can undermine the separation users expect from a second factor.
Enable full-disk encryption, automatic screen locking, current operating-system updates, and a strong local login on every computer holding the vault. Avoid installing the desktop client on shared, borrowed, or unmanaged systems. Remove old devices from the relevant Proton or Apple account when they are no longer controlled.
Biometric or PIN app lock helps against casual access to an already unlocked device. It does not repair a compromised operating system, prevent all memory inspection, or replace device encryption and service recovery codes.
Proton Authenticator versus Proton Pass
Proton Pass can store passwords and TOTP secrets together and autofill both. Proton Authenticator is a separate application designed to keep TOTP codes outside the password vault. Proton itself frames Pass as the convenience option and Authenticator as the separation option.
The separate app can reduce the consequence of one password-vault compromise when the Authenticator vault and its unlock path are genuinely independent. That benefit becomes smaller if both apps use the same Proton account, remain unlocked on the same device, or rely on the same compromised operating system.
There is also a circular-recovery concern. If a Proton account synchronizes the only copy of the TOTP code needed to sign in to that same Proton account, account recovery becomes unnecessarily fragile. Keep Proton’s own recovery codes outside Authenticator, retain a separate encrypted export, and consider a hardware security key or another independent authenticator for the Proton account itself.
The right choice depends on threat model and recovery discipline. Autofill is easier; separation is more deliberate. Neither architecture can compensate for missing service recovery codes.
How it compares with other authenticator models
Proton Authenticator is best understood by recovery model rather than a broad winner label.
| App | Main operating model | Desktop clients | Built-in cross-device sync | Direct portability |
|---|---|---|---|---|
| Proton Authenticator | Account-optional local or synced vault | Yes | Optional Proton account or Apple iCloud | Import and export |
| Ente Auth | Account sync or separate offline mode | Yes, plus web | E2EE Ente account sync | Encrypted and plaintext exports |
| Aegis | Local Android vault | No | No service-operated sync | Encrypted and plaintext exports |
| Google Authenticator | Local use with optional Google account sync | No | Optional Google account sync | QR transfer/export workflow |
Ente Auth is a close alternative for broad platform access and documented encrypted export. Aegis suits Android users who prefer a local vault and manage backups themselves. Google Authenticator favors a simpler mainstream workflow but has no desktop client.
Proton has a strong feature combination, but it also has a shorter product history than long-established authenticators. Users who value conservative operational history may prefer to migrate gradually and retain verified exports during the product’s early years.
TOTP is not phishing-resistant
Proton Authenticator protects how TOTP seeds are stored and moved. It cannot bind a six-digit code to the legitimate website requesting it.
NIST’s current authenticator guidance says authenticators that require manual entry of an OTP are not phishing-resistant. A fraudulent page can collect a valid code and relay it to the real service before it expires.
Use TOTP when it is the strongest practical method a service offers or when it materially improves on password-only access. Prefer passkeys or FIDO2 security keys for important accounts when available. Check the domain before entering a TOTP code, and do not approve unexpected recovery or device-enrollment prompts.
Encrypted synchronization protects stored data from the sync provider under the documented model. It does not transform TOTP into a phishing-resistant protocol.
Who should choose Proton Authenticator
Proton Authenticator fits people who want codes on phones and computers, prefer an open-source client, and want to choose between accountless local use and encrypted synchronization. It is particularly relevant for users leaving an authenticator without a supported desktop client or practical export path.
It is a weaker fit for a strictly mobile, local-only Android workflow where Aegis already meets the need; for organizations requiring central provisioning, policy enforcement, and administrative recovery; or for users who will enable sync but will not maintain independent recovery material.
The source-verified 2FA authenticator comparison places Proton beside local-first, account-optional, and sync-centered alternatives. Choose based on platform requirements, recovery path, and endpoint security rather than a numerical score.
Setup and recovery checklist
- Choose local-only, Proton account sync, or Apple iCloud sync before migrating critical entries.
- Install only from Proton’s official download links or an official app store listing.
- Protect every phone and computer with device encryption, a strong login, and automatic locking.
- Enable biometric or PIN app lock where appropriate.
- Add one noncritical account and complete a signed-out login.
- Save that service’s one-time recovery codes outside Authenticator.
- Create a password-protected export or backup and keep a copy off the device.
- Test the recovery file before assuming it works.
- If using Proton sync, protect the Proton account with recovery methods outside this vault.
- Avoid making this vault the only holder of the Proton account’s own TOTP secret.
- Keep the previous authenticator until every migrated account has been verified.
- Remove stale synchronized devices and temporary plaintext migration files.
- Review backup freshness after major account changes.
- Prefer passkeys or security keys for high-value services that support them.
Proton Authenticator verdict
Proton Authenticator combines five-platform availability, offline operation, accountless local use, optional end-to-end encrypted synchronization, Apple iCloud support, and direct portability without a subscription. That is a compelling set of documented capabilities.
Its limits are equally important. More synchronized endpoints mean more systems to secure. Proton’s detailed security model is vendor-published, and the official sources reviewed here did not provide an Authenticator-specific independent audit report. TOTP codes remain vulnerable to real-time phishing regardless of storage encryption.
For individuals who keep separate service recovery codes and a tested encrypted export, Proton Authenticator is a defensible cross-platform choice. The evidence supports that conclusion without the fabricated testing narrative, simulated interface images, or blanket security rating used in the earlier edition.
Frequently asked questions
Does Proton Authenticator require a Proton account?
No. It can keep codes locally without an account. A Proton account is needed for Proton-operated cross-platform sync, while supported Apple devices can also use iCloud.
Which platforms are supported?
Proton lists Android, iOS, Windows, macOS, and Linux.
Does Proton Authenticator work offline?
Yes. Configured clients generate TOTP codes locally. Connectivity is needed for account sign-in and synchronization, not ordinary code generation.
Can Proton Authenticator import and export codes?
Yes. Proton documents imports from several popular authenticators and direct export. Treat every export as a collection of reusable authentication secrets.
Are synchronized codes end-to-end encrypted?
Proton says Proton-account synchronization encrypts entries on the client so Proton does not receive plaintext codes or keys. This is a vendor-documented security model, not an independent audit conclusion.
Is Proton Authenticator phishing-resistant?
No. Manually entered TOTP can be relayed by a phishing site. Passkeys and FIDO2 security keys provide stronger phishing resistance when supported.
