How to Transfer Google Authenticator Codes to Your Computer (2026 Guide)

Short answer: Google doesn't make a desktop version of Google Authenticator — but you can still get every one of your 2FA codes onto your computer. You export your accounts from the phone app as QR codes, then import those QR codes into a Chrome authenticator extension such as OTPSync. The whole process takes about five minutes and doesn't disturb the codes on your phone.

This guide walks through the exact steps, what the export actually contains, and how to verify everything works before you rely on it.

Why there's no official Google Authenticator for PC

Google Authenticator exists only as an Android and iOS app. When you sign in on your laptop and the site asks for a 6-digit code, you're forced to grab your phone — every single time. A browser-based authenticator solves this by generating the same time-based one-time passwords (TOTP) directly in Chrome.

That's possible because TOTP is an open standard (RFC 6238). The 6-digit codes are derived from a shared secret plus the current time — any compliant app that holds the same secret produces the same codes. Moving to desktop is really just moving those secrets, safely.

Step 1 — Export your accounts from Google Authenticator

1. Open Google Authenticator on your phone.
2. Tap the menu (☰ or ⋮) and choose Transfer accounts.
3. Select Export accounts and confirm with your device unlock.
4. Pick the accounts you want to move (or select all).
5. The app displays one or more QR codes. Each QR code holds up to 10 accounts — if you have more, swipe through and capture each one.

Take a screenshot of each QR code, or keep the phone screen visible if you plan to scan it directly with your computer's camera or from the screen.

Step 2 — Import into your browser with OTPSync

1. Install OTPSync from the Chrome Web Store (free).
2. Open the extension and tap the + button, then choose Upload QR image.
3. Select the screenshot(s) you exported. OTPSync decodes Google's otpauth-migration:// format natively — a single image with 10 accounts imports all 10 at once.
4. Repeat for each QR code if your export spanned several.

Prefer not to use screenshots? OTPSync can also scan the current tab for a QR code shown on screen, accept a pasted otpauth:// link, or take a manual secret-key entry — whichever the site or app gives you.

Step 3 — Verify before you trust it

1. Open OTPSync and your phone's Google Authenticator side by side.
2. Pick two or three accounts and confirm both apps show the same 6-digit code at the same moment.
3. Sign in to one low-stakes account using the code from OTPSync to prove the end-to-end flow.

If a code doesn't match, your computer's clock is usually the culprit — TOTP depends on accurate time, so make sure the system clock is set to sync automatically.

Should you delete the accounts from your phone?

Not necessarily. Exporting copies the secrets; the phone app keeps working. Many people run both: phone for mobile logins, browser for desktop work. If you do retire the phone app, first make sure your new vault is backed up — OTPSync encrypts your vault locally (AES-256-GCM with a key derived from your Master Passcode via PBKDF2) and can back it up to your own Google Drive and OTPSync Cloud, so a lost machine doesn't mean lost accounts.

Common problems and fixes

• "QR code not recognized" — make sure the screenshot is sharp and uncropped; the entire square must be visible.
• More than 10 accounts — Google splits the export across multiple QR codes; import every image, not just the first.
• Codes off by one step — fix the computer clock (enable automatic time sync) and try again.
• A site that only offers SMS — you can't import SMS-based 2FA; check the site's security settings for an "authenticator app" option and enroll it fresh.

FAQ

Does this work on Windows, Mac, and Linux?

Yes — anywhere Chrome (or a Chromium browser like Edge or Brave) runs, the extension works the same way.

Is it safe to have 2FA codes in the browser?

It is when the vault is properly encrypted. OTPSync never stores plaintext secrets at rest: the vault is encrypted locally, the Master Passcode never leaves your browser, and the server only ever sees ciphertext. Read more in our zero-knowledge encryption explainer.

Can I use 2FA with no phone at all?

Yes — see the companion guide: How to Use 2FA Without a Phone.