Mactokio

Mactokio

Native macOS TOTP two-factor authenticator

Description

Everyone uses two-factor codes, but most people keep a single authenticator on their phone — so logging in on a computer means fishing out the phone and typing six digits by hand. Moving the authenticator to a Mac usually means screenshotting the export QR code and emailing or messaging it to yourself, at which point that image — containing every secret key — lives forever in chat history, mail servers and cloud photo backups. That is photographing your house keys and posting them to a group.

Mactokio is a native macOS TOTP/HOTP authenticator that closes that gap: point your Mac's webcam at the export QR on your phone screen and the secrets travel through the air, not the internet — no screenshot, no file transfer, no cloud. Scanning uses confidence-based detection across frames with visual feedback (tracking, then green for success or red for invalid), and secrets are encrypted the instant they are read.

Security is the headline: every secret is AES-256 encrypted, hardware-bound, and never leaves the device — no cloud, no sync, no account, just your codes. It supports standard otpauth:// and Google Authenticator migration format, and beyond the camera can import from a QR image, a file or the clipboard. MIT licensed.

Features



Secure webcam import: scan the export QR from your phone with the Mac's webcam — no network, no file — with multi-frame confidence detection, green/red feedback, and encryption the moment a secret is read.

TOTP / HOTP generation: standard time- and counter-based codes, click to copy, with a countdown ring showing time remaining.

AES-256, hardware-bound: secrets are AES-256 encrypted locally and tied to the device, so copying the store to another machine will not decrypt it.

No cloud, no sync, no account: nothing is uploaded and no sign-up is needed; the codes exist only on your Mac.

Several import paths: besides the camera, import from a QR image, a text file or the clipboard (a screenshot or otpauth:// URI), compatible with Google Authenticator migration.

Reveal on unlock: codes are masked by default and shown only after an explicit unlock (biometric/system auth), so a glance at the screen reveals nothing.