What is TOTP QR Code Generator?
TOTP QR Code Generator — A TOTP QR Code Generator creates an otpauth:// setup URI and QR code that authenticator apps can scan to enroll a time-based one-time password secret.
Loading your tools...
Create a standard otpauth:// TOTP setup QR code for authenticator apps, then verify the live 6-digit code with the same secret.
TOTP QR Code Generator: Enter an issuer, account name, and secret, or generate a new Base32 secret. The tool creates a scannable TOTP QR code and live OTP code for Google Authenticator, Authy, 1Password, Bitwarden, and other RFC 6238 apps.
Generate and validate time-based OTP (one time password) for multi-factor authentication. totp generator, totp qr code generator.
Secret in hexadecimal
9f46f04e3d53f4877017
Epoch
1780449015
Iteration — Count
59348300
Padded hex
000000000389954c
TOTP QR Code Generator — A TOTP QR Code Generator creates an otpauth:// setup URI and QR code that authenticator apps can scan to enroll a time-based one-time password secret.
Enter the issuer or app name that should appear in the authenticator app.
Enter the account label, such as a username or email address.
Generate a Base32 secret or paste an existing test secret.
Scan the generated QR code with Google Authenticator, Authy, 1Password, Bitwarden, or another TOTP app.
Compare the live OTP code and countdown to confirm the setup works.
Testing 2FA enrollment screens during app development
Creating a QR code from an existing Base32 TOTP secret
Debugging authenticator app setup issues
Validating issuer, label, period, digit count, and algorithm settings
QA testing login flows that require rotating OTP codes
The QR code contains an otpauth URI, usually in this format: otpauth://totp/Issuer:account?secret=BASE32SECRET&issuer=Issuer&algorithm=SHA1&digits=6&period=30. Authenticator apps read that URI and store the secret locally.
Use generated test secrets for development and QA. Do not paste production 2FA secrets from real accounts into online tools unless your security policy explicitly allows it. For production apps, generate secrets server-side and show the QR only to the enrolled user.
If codes do not match, check device time sync first. Then verify the Base32 secret, issuer/account label, algorithm, digit count, and period. Most consumer authenticator apps expect SHA-1, 6 digits, and 30-second windows.