Phone-Free 2FA
digitalhabits.org
What it is
Phone-Free 2FA is a free, open-source browser extension that generates time-based one-time passwords so users can retrieve login codes on a computer. It creates a new six-digit code every 30 seconds and lets users copy it from the browser sidebar. It works with services that use standard TOTP codes, including Microsoft 365, but does not receive push-approval requests. The extension is available for Chrome, Edge, Firefox, and other Chromium browsers. Account details are encrypted and stored locally, and the extension says it sends nothing over the network. On Chrome, secret keys use AES-256-GCM encryption, with a key derived from the master passphrase using PBKDF2 at 600,000 iterations. Users can set it to lock when the sidebar closes or after inactivity; failed unlock attempts trigger longer delays. Encrypted backups and otpauth exports support moving accounts to another authenticator. There is no central passphrase recovery, so accounts cannot be restored through the extension without a usable backup. The project has no cross-device sync or team administration.
Spec sheet
- Purpose
- Phone-Free 2FA generates time-based one-time passwords in a browser so users can get login codes without reaching for a phone.Read 30 Sep 2026 · digitalhabits.org
- Intended users
- The maker says it can help staff who need TOTP codes during computer-based work without keeping a phone beside them.Read 30 Sep 2026 · github.com
- Support
- The maker directs users to the project’s GitHub repository for questions, suggestions, problems, and contributions.Read 30 Sep 2026 · chromewebstore.google.com
- Headquarters
- Oxford, United KingdomRead 28 Sep 2026 · digitalhabits.org
- Founded
- 2019Read 23 Sep 2026 · digitalhabits.org
- Maker
- The product is developed by Centre for Digital Habits with computer scientists at the University of Oxford and Maastricht University.Read 30 Sep 2026 · github.com
- Backups and migration
- Users can export encrypted backups and export standard otpauth records to move accounts to another authenticator.Read 30 Sep 2026 · github.com
- Biometric unlock
- Touch ID is available on supported Chrome and Edge devices; Firefox users unlock with their master passphrase.Read 30 Sep 2026 · github.com
- Browser availability
- The project lists installs for Chrome and other Chromium browsers, including Edge and Brave, and for Firefox.Read 30 Sep 2026 · github.com
- Code generation
- It generates a new six-digit code every 30 seconds and lets users copy it from the browser sidebar.Read 30 Sep 2026 · digitalhabits.org
- Code type
- totpRead 22 Sep 2026 · github.com
- Compatible accounts
- It works with services that provide standard TOTP authenticator codes, such as Microsoft 365, and does not receive push-approval requests.Read 30 Sep 2026 · github.com
- Encrypted backup
- YesRead 22 Sep 2026 · github.com
- Encryption
- The Chrome Web Store listing says secret keys are encrypted with AES-256-GCM using a key derived from the master passphrase with PBKDF2 at 600,000 iterations.Read 30 Sep 2026 · chromewebstore.google.com
- Local storage
- Account details are encrypted and stored locally in the browser, and the extension says it sends nothing over the network.Read 30 Sep 2026 · digitalhabits.org
- Multi-device sync
- NoRead 22 Sep 2026 · github.com
- Organisation limits
- The project has no backend, tenant, administrator account, central recovery, cross-device sync, or administrative view of users’ accounts.Read 30 Sep 2026 · github.com
- Push approvals
- NoRead 22 Sep 2026 · github.com
- Recovery limit
- There is no central passphrase reset or recovery; without a usable backup, stored accounts cannot be recovered through the extension.Read 30 Sep 2026 · github.com
- Supported platforms
- Chrome,Edge,Firefox,and other Chromium browsersRead 22 Sep 2026 · github.com
- Team administration
- NoRead 22 Sep 2026 · github.com
- Unlock protection
- The extension can lock when the sidebar closes or after configurable inactivity, and failed unlock attempts trigger progressively longer delays.Read 30 Sep 2026 · github.com
Plans and prices
Strong points and limits
Strong points
- Generates a fresh six-digit code every 30 seconds.
- Stores encrypted account details locally in the browser.
- Supports encrypted backups and standard otpauth exports.
- Offers configurable locking and progressively longer failed-unlock delays.
Limits
- Does not receive push-approval requests.
- No central passphrase reset or recovery.
- No cross-device sync or team administration.
- Without a usable backup, stored accounts cannot be recovered.
Who it suits
It suits people who need TOTP login codes while working at a computer and do not want to keep a phone beside them. It is not suited to teams needing centralized account administration or recovery.
Verdict
Phone-Free 2FA keeps TOTP code generation in the browser and specifies how it stores and protects account details. Users should plan for their own backups because the extension has no central recovery or synchronization.
Where Specifiction places it
- Authenticator apps#40 of 1118.2