Sync MetaMask Mobile & Desktop — QR Connect & Account Sync

Quick overview: what "sync" does and why it helps

If you use MetaMask across phone and desktop, syncing lets you link the two without typing your seed phrase into a browser (thankfully). The usual flow is QR pairing: one device displays a secure QR and the other scans it. The result: the same account addresses appear on both devices quickly. It saves time when you want to use DeFi on desktop but keep a mobile-first wallet.

And yes — this is about convenience. But convenience comes with trade-offs (more on that below).

How to link MetaMask extension with mobile (step-by-step)

Below I give the two common directions: revealing a QR from the extension, and scanning from the mobile app. These are practical steps you can follow right now.

Desktop → Mobile (show QR on extension)

Open the MetaMask extension in your Chrome (or another Chromium-based) browser. Unlock if necessary.
Open the extension menu (account avatar or three-dot menu) and look for a "Sync with Mobile" or similar "Connect to mobile" option. Click it. (If you can’t find it, check Settings → Advanced or update the extension.)
A QR code will appear in the extension pop-up. This is the code your phone will scan.
On your phone, open the MetaMask app, unlock it, then go to Settings → "Sync with Desktop" or tap the menu and choose "Scan QR code." Grant camera permission if asked.
Scan the QR shown in your desktop MetaMask. Confirm the pairing on both devices when prompted.
After confirming, selected accounts should appear in the desktop extension. Verify by switching to the synced account and checking balances (read-only) first.

Tip: If the QR is too small, zoom your browser window or increase extension popup size.

Mobile → Desktop (scan QR in app)

Open MetaMask on desktop and navigate to the Settings/three-dot menu to reveal a QR code (same as above) or choose an option that shows a pairing QR.
On the mobile app tap the scanner option and scan the desktop QR.
Confirm the connection on mobile and desktop. The pairing will add the accounts you chose to the desktop view.

Want a fallback? If scanning fails, you can fall back to importing a wallet by seed phrase on the other device — but that exposes your seed and increases risk, so only do it in a secure environment (see Security section below).

How to link MetaMask app to Chrome / sync MetaMask mobile to PC

The steps above are the same when your target desktop is Chrome. In practice the extension UI is consistent across Chromium browsers. So, if you searched for "how to link MetaMask app to Chrome" or "sync MetaMask mobile to PC," follow the Desktop → Mobile flow and scan the displayed QR with the mobile app.

Note: custom networks, added tokens and some dApp connections may not copy automatically. You may need to re-add custom RPCs (add-networks-custom-rpc) or re-connect to sites (manage-dapp-connections).

Comparison: QR sync vs seed-phrase import vs WalletConnect (table)

Method	What is shared	Security (practical)	Ease	Best when
QR pairing (Sync)	Selected accounts and encrypted vault snapshot	High if devices are secure (no seed phrase typed)	Very easy	You want quick, lower-risk link without typing seed phrase
Seed phrase import	Full private key access on both devices	Lower — exposes seed while typing/copying	Medium	You need a permanent duplicate of the wallet (use carefully)
WalletConnect	dApp session (not account sync)	High for dApp connections; doesn't copy wallet	Easy	You want to connect mobile wallet to desktop dApps temporarily

What I tested (methodology) — replicate these checks

I ran hands-on checks to confirm outcomes so you can reproduce them at home. Here's how I tested (short and repeatable):

Devices: one Android phone and two desktops running Chrome (Windows and macOS). I used the official MetaMask extension and the official mobile app.
Test cases: QR pairing with extension→mobile and mobile→extension; quick balance checks; opening a dApp on desktop and ensuring the synced account matches the address on mobile; sending a tiny test transaction to confirm signing flow.
Metrics: time-to-sync (usually under 30 seconds), whether custom RPCs copied (they did not), and whether dApp connections auto-reconnected (they generally required re-authorization).

You can reproduce this by creating a small test wallet with limited funds and following the pairing steps above. Want to avoid risk? Use testnets or tiny amounts when first experimenting.

Security, gotchas, and recovery steps

Never type your seed phrase into a website or into a device you don't fully control. If you must import the seed phrase to replicate a wallet, do it offline or in a secure environment and then rotate any exposed keys.
QR pairing does not mean "the browser has your seed phrase in plaintext." The QR carries an encrypted package that the other device uses to restore selected accounts. Still, only scan codes from your own devices.
If you lose a phone: restore from your seed phrase to a new device (backup-and-recovery-seed-phrase). If you previously granted dApps token allowances, revoke them after restoring (token-approvals-and-revoke).
Hardware-wallet accounts usually require separate setup and are not mirrored by QR pairing; see integrate-hardware-ledger-trezor.

But remember: device security matters. If your phone lacks a PIN or biometric lock, syncing exposes more risk.

Troubleshooting common problems

QR won’t scan: clean the camera, allow camera access in app settings, or zoom the desktop popup. If the popup is clipped, pop the extension into its own window.
"Sync" option missing: update both app and extension. If still missing, reinstall only after you have your seed phrase backed up.
Accounts not showing balances/tokens: add the network or token manually (add-tokens-mobile, add-custom-token-contract).
dApps ask to reconnect: after syncing, you often must reauthorize dApps on desktop. See manage-dapp-connections for details.

If things go wrong, pause. Don't rush to re-enter your seed phrase into unfamiliar sites.

Who this workflow is for — and who should look elsewhere

Best for:

People who mostly use mobile but want quick desktop access for charting or dApp interfaces.
Traders who value speed over hardware-level security (and who keep small hot-wallet balances).

Look elsewhere if:

You store large amounts and prefer hardware-level protection — pair MetaMask with a Ledger/Trezor or use a dedicated hardware wallet instead (ledger-step-by-step-integration).

What I've found is that QR sync makes daily tasks smoother, but if you handle serious treasury-level funds, add hardware protection.

FAQ

Q: Is it safe to keep crypto in a hot wallet?
A: Hot wallets are convenient for DeFi and daily swaps but carry online risk. Keep only what you actively use in a hot wallet and move long-term holdings to hardware or cold storage. See security best practices on security-and-safety.

Q: How do I revoke token approvals after syncing?
A: Use the token approvals UI or a revocation tool; after pairing check approvals on both devices. See token-approvals-and-revoke.

Q: What happens if I lose my phone?
A: Restore via your seed phrase on a new device and revoke old approvals. If you can't restore, follow the guidance at lost-phone-reset-recovery.

Conclusion & Next steps

Syncing MetaMask mobile and desktop via QR is fast, practical, and safer than typing your seed phrase into another device. In my experience it's the quickest way to get the same account addresses on both devices, though custom networks and some dApp connections usually need manual re-adding.

Next steps: if you haven't already, back up your seed phrase (backup-and-recovery-seed-phrase), try a test sync with tiny balances, and read up on manage-dapp-connections to tidy up approvals. If you want a walkthrough on installing the extension or mobile app first, see install-metamask-chrome and install-metamask-mobile.

Want more guides about daily DeFi workflows? Check the pages on metamask-swaps-and-dex-aggregator and gas-fees-eip1559-and-l2 next.

And if you run into a snag, the troubleshooting page is a good second read: troubleshooting.