Q-TOTP Autofill
Automatically generate and fill TOTP codes for configured sites.
As of June 2026, Q-TOTP Autofill has 8 users in the Productivity category.
Usersno change0%
8
8
Ratingno change0%
—
— reviews
Reviewsno change0%
—
Version
1.4.21
Manifest V3
History
7 snapshotsTracking since Apr 22, 2026.
View as table
| Date | Users | Rating | Reviews | Version |
|---|---|---|---|---|
| Apr 22, 2026 | — | — | — | 1.4.21 |
| Apr 26, 2026 | — | — | — | 1.4.21 |
| May 9, 2026 | 3 | — | — | 1.4.21 |
| May 21, 2026 | 2 | — | — | 1.4.21 |
| May 27, 2026 | 5 | — | — | 1.4.21 |
| Jun 3, 2026 | 10 | — | — | 1.4.21 |
| Jun 9, 2026 | 9 | — | — | 1.4.21 |
| Now | 8 | — | — | 1.4.21 |
Permissions & access
- Permissions
- storagescriptingtabs
- Host access
- None declared
Screenshots
About
Q-TOTP Autofill helps users generate and autofill TOTP codes on websites they explicitly configure. The extension is designed for teams and individuals who want a focused OTP autofill workflow without broad default site access. Users add a site URL, Base32 secret key, and optionally a CSS selector for the OTP field. When a configured site is opened, the extension can generate the current TOTP code and autofill it into the page. Key features: Generate RFC 6238 compatible TOTP codes from configured Base32 secrets Autofill OTP codes only for websites the user has configured Request host permissions only for configured sites instead of broad default access Prefer smart OTP field detection on the page Fall back to a configured CSS selector when needed Support manual “Fill now” from the popup Support Vietnamese and English UI Encrypt stored secrets in local browser storage before persistence How it works: The user opens the extension settings page and adds a site configuration Each configuration includes a target URL and a Base32 secret key The extension generates the active TOTP code locally in the browser On matching configured pages, the extension detects the OTP input and fills the code If the page layout is unusual, the user can provide a CSS selector as a reliable fallback Privacy and security: Secrets are stored locally in Chrome storage and are not sent to third-party servers by the extension The extension does not provide a cloud sync service for secrets Site access is limited to user-configured origins The extension focuses on OTP generation and autofill only Important note: Users are responsible for configuring the correct site URL, secret key, and optional selector for each website they want to use with the extension.
Technical
- Version
- 1.4.21
- Manifest
- V3
- Size
- 72.89KiB
- Min Chrome
- 116
- Languages
- 2
- Featured
- No
Metadata
- ID
- clihffefnebbkcihblbdmbolhmllkffa
- Developer ID
- ude7b28b7e7ab7f2b24411e5362465485
- Developer Email
- [email protected]
- Created
- Apr 21, 2026
- Last Updated (Store)
- Apr 21, 2026
- Last Scraped
- Jun 9, 2026
- Website
- —
- Support URL
- —
Data sourced from the Chrome Web Store · last verified Jun 9, 2026.