Ente Auth: 2FA codes, encrypted backups and device migration

Ente Auth review: mobile, desktop and web access to 2FA codes, offline mode, encrypted exports and a practical recovery plan before changing devices.

What is Ente Auth used for?

Ente Auth generates one-time login codes for accounts that support an authenticator app. It keeps the setup secret for each account and calculates the current code on your device. You can use it locally without an account or sign in to Ente for end-to-end encrypted backup and synchronization.

The useful distinction is between access today and recovery tomorrow. A second device and an encrypted export serve different purposes: synchronization keeps entries available, while an export gives you a separate recovery file.

Ente Auth: key information
ItemDetails
PlatformsAndroid, iOS, Windows, macOS, Linux, Web
TaskPassword managers
Download sourceUse the project’s official page and choose the build for your operating system.
Version and termsPlatform and documentation check: 15 November 2026. Free app with optional encrypted synchronization.

Ente Auth interface and illustrations

The official product illustrations show the code list on mobile and desktop. Each entry identifies the service and account; search, tags and pinned entries help with larger collections. These are developer illustrations, not screenshots from an udarknet test.

Download Ente Auth from the official website

The official page links to Android, iOS, Windows, macOS and Linux builds and the web app. Choose the platform there. Auth is free and open source under AGPL-3.0; an Ente Photos subscription is not required.

Keep the recovery codes issued by each service separately from the authenticator. They provide a different route back into that particular account.

Getting started with Ente Auth

  1. Install the official app and choose an Ente account or Use without backups.
  2. In one service's security settings, enable authenticator-based 2FA. Scan its QR code or enter the setup secret, then confirm with the generated code.
  3. Save that service's recovery codes outside the authenticator. Keep the old login method until the new setup works.
  4. If using synchronization, sign in on another trusted device and check that the required entries appear.
  5. Open Settings → Data → Export, select Encrypted and choose a password for the export. Save the file separately.
  6. Test importing the export before replacing the original phone or reinstalling its operating system.

Where Ente Auth fits

It suits people who want the same authenticator entries on a phone and a computer, and those moving away from a phone-only workflow. Tags and account labels help distinguish personal and work logins. Offline mode suits a device-local collection when you are prepared to maintain your own backups.

Local storage and synchronized codes

Choose how to keep your codes
ModeWhere entries are availableRecovery preparation
OfflineOn this deviceEncrypted export or local backup
Ente accountSigned-in devices through encrypted syncAccount recovery and separate export
Encrypted exportA file you store yourselfExport file and its own password

Before a device reset

Offline storage uses a key protected by the operating system's secure storage. Copying the database or restoring a general device backup may leave that key unavailable. Export from the working app before a reset, migration or major system change.

Organizing accounts and moving from another app

Add a clear account name when a service has several logins. Use tags for groups and pin the entries used most often. Notes can record which account an entry belongs to without putting passwords into its label.

Import, then verify

  • Use the migration instructions for the previous authenticator; available export formats differ.
  • Check the service and account labels after import.
  • Try a login before deleting the old copy.
  • Treat an unencrypted export or setup QR code as the underlying account secret.

Export passwords and ongoing maintenance

An encrypted export has the password chosen when that file was created. It is not automatically your Ente account password, and a later account-password change does not update an older export. Keep the export password in a place available after losing the original device.

Limitations and data protection in Ente Auth

A copied one-time code can still be submitted to a phishing page. Check the service address before entering it; use passkeys or a hardware security key where the service supports them.

Offline mode does not synchronize entries to Ente. Desktop and directly downloaded Android builds may still check for app updates.

Alternatives for related tasks

Aegis is a useful alternative for an Android-focused local vault. Bitwarden and KeePassXC address broader password storage workflows. Ente Auth is the focused choice here when cross-platform authenticator access is the main task.

Documentation and images

Official sources, image credits and review methods

The review was prepared on the project documentation. The installation and independent testing of the distribution within this material was not carried out. The rights to the interface and the names are reserved for the respective rights holders.