Many 2FA and MFA apps use the same TOTP setup standard behind their QR codes and manual setup keys. This guide explains when this local generator can read those keys, what parameters matter, and which sign-in methods are outside the scope of a TOTP code generator.
Compatible means the service provides a standard TOTP setup secret, usually as a Base32 manual setup key or an otpauth://totp/ URI. The app brand is less important than the shared secret, algorithm, digit count, and time period.
Google Authenticator compatible setups usually use a Base32 secret, SHA-1, 6 digits, and a 30-second period. If the QR code contains an otpauth://totp/ link, this tool can read the secret and supported parameters from that link.
Microsoft Authenticator can store standard TOTP codes for many third-party services. This generator can handle those TOTP setup keys, but it cannot create Microsoft push approvals, number matching prompts, passwordless sign-ins, or account-specific cloud authentication.
1Password, Bitwarden, 2FAS, FreeOTP, Authy-style setup keys, and similar apps can be compatible when they expose the same TOTP secret or otpauth URI. App-specific encrypted exports may need to be opened in the original app before a usable setup key is available.
The tool cannot extract secrets from another authenticator app, recover a lost 2FA setup, create SMS or email OTPs, approve push prompts, generate passkey responses, or bypass an account provider's recovery process.
For temporary compatibility tests, use a fragment shortcut such as #secret=YOUR_BASE32_SECRET. Fragments remain in the browser and are not sent in the HTTP request, while path and query shortcuts are server-visible and marked noindex.
This table separates standard TOTP setup keys from app-specific sign-in features. The local generator works when the app or service exposes a Base32 secret or otpauth://totp/ URI.
| App or flow | Compatible input | Works locally | Outside this tool |
|---|---|---|---|
| Google Authenticator | Base32 setup key or otpauth://totp/ URI | Standard TOTP codes, commonly SHA-1, 6 digits, and 30 seconds | Google account sync, official app storage, or app-specific account features |
| Microsoft Authenticator | Third-party TOTP setup key or otpauth://totp/ URI | Authenticator codes for accounts that use standard TOTP secrets | Push approvals, number matching, passwordless Microsoft sign-ins, or cloud prompts |
| 1Password and Bitwarden | Visible TOTP secret, copied setup key, or otpauth URI | Matching TOTP codes when the secret, algorithm, digits, and period are the same | Encrypted vault export/import, account storage, or password manager sync |
| 2FAS and FreeOTP | Standard TOTP QR data or manual setup key | Browser-local code generation for compatible TOTP profiles | App backup restore, device transfer, or app-specific migration files |
| Authy-style TOTP | Base32 secret or otpauth URI when the setup value is visible | Codes for standard TOTP setup secrets | Authy cloud sync, recovery, backups, or proprietary exports |
| SMS, email, push, passkey, and hardware-key flows | Not a TOTP setup secret | Not handled by this local TOTP generator | SMS codes, email OTPs, push login approvals, passkeys, WebAuthn, or hardware challenge responses |
No. It is an independent local TOTP generator that can calculate standard authenticator codes from compatible setup keys. It is not affiliated with Google, Microsoft, Authy, 1Password, Bitwarden, 2FAS, or FreeOTP.
No. SHA-1, 6 digits, and 30 seconds are common defaults, but some services use 8 digits, SHA-256, SHA-512, or a different period. otpauth links can include those parameters.
Only if the export includes a readable Base32 secret or otpauth://totp/ URI. Many app backups are encrypted or use app-specific formats, so they must be opened with the original app or converted before this generator can use them.
Users often search by app name, but the technical requirement is the same TOTP setup secret. Mentioning app names clarifies compatibility while keeping the boundary clear: this page generates local TOTP codes, not app-specific login approvals.