WalletConnect lets a website (a dApp) control a remote signing session with your MetaMask mobile app so the dApp can request transaction signatures without your private keys leaving your phone. I use it when I want to connect a desktop site to my phone wallet or when a site doesn't work in MetaMask's in-app browser. It adds convenience. It also adds long-lived connections you must manage (so pay attention).
And yes, small mistakes happen — I once left a session open overnight. Don’t do that.
At a technical level WalletConnect is an interoperable protocol that creates a secure JSON-RPC channel between a dApp (the client) and your wallet (the signer). The dApp shows a QR code or deep link. MetaMask mobile either scans that QR or receives the link and establishes a session. A relay/bridge handles message transport; the wallet still signs locally with private keys.
What that means practically: the dApp can propose which blockchain and which account it wants to use, then it will ask your app to sign transactions. You approve or reject. Approvals are explicit, but token allowances are transactions too — they can be subtle and persistent.
Why use WalletConnect? Two common cases:
When the dApp works in MetaMask's in-app browser you get an injected provider and slightly faster UX. But some sites are blocked or incompatible in the in-app browser. So WalletConnect is the fallback and often the better choice for desktop-to-phone flows. (See our guide on WalletConnect and mobile browser for more.)
Below are the safe, repeatable steps I use. Do a test transaction of a few cents first.
Pro tip: If a link doesn't open MetaMask, try copying the WalletConnect URI and pasting it into MetaMask's WalletConnect connection interface (some versions expose a "Paste URI" option).
You should disconnect and periodically clean up sessions. Here's a short checklist:
But don't stop at disconnecting sessions. Disconnecting closes the session, but an unlimited token approval remains on-chain until revoked.
Common failure modes and fixes (real mistakes I've seen):
If the error persists, try the following sequence: force-close MetaMask, clear mobile browser cache, re-open the dApp, then re-initiate WalletConnect. That flow fixed a handful of stubborn sessions for me.
(And yes, sometimes the dApp itself is the problem.)
People search for "walletconnect compatible wallets metamask" when comparing options. MetaMask mobile supports WalletConnect and provides QR scanning, deep-link handling, and session controls. Other popular wallets also support WalletConnect; the feature set varies by app.
| Wallet (example) | Mobile app | QR scanner | Built-in dApp browser | Notes |
|---|---|---|---|---|
| MetaMask (mobile) | Yes | Yes | Yes | WalletConnect session management included |
| Wallet A (example) | Yes | Yes | Varies | Supports WalletConnect; check session UI |
| Wallet B (example) | Yes | Yes | Yes | WalletConnect compatible; confirm version support |
Note: The table shows feature categories, not endorsements. Check each app's documentation for exact behavior and version support. See /alternatives and our comparisons such as /vs-coinbase-wallet for deeper side-by-side reads.
Q: Is it safe to keep crypto in a hot wallet? A: Hot wallets (software wallets) are non-custodial and convenient, but they have higher attack surface than hardware wallets. I use a hot wallet for day-to-day DeFi and move larger holdings to hardware. See /security-best-practices.
Q: How do I revoke token approvals? A: Use MetaMask's permissions panel or a trusted revoke tool. Revocation costs gas. Step-by-step is in /how-to-revoke-approvals.
Q: What happens if I lose my phone? A: If you still have your seed phrase, restore to a new device. If not, funds are likely lost. Immediately restore from seed on a new device and move funds if you can. See /backup-and-recovery-options and /how-to-recover-wallet.
Q: How do I disconnect connected sites MetaMask mobile? A: Open MetaMask mobile → Menu → WalletConnect/Connections → find the site → Disconnect. Then revoke any leftover approvals.
Best for: people who use desktop dApps and want phone-based signing, or those who need to connect dApps that don’t work inside the MetaMask browser. If you swap tokens frequently and want a single secure approval flow, WalletConnect + MetaMask mobile is a practical combo.
Look elsewhere if: you need hardware-level signing for every transaction (move to a hardware wallet flow), or if a dApp only supports browser-injected providers and you can't use QR/deep link flows.
WalletConnect with MetaMask mobile is a practical bridge between browsers and phones. Use it for desktop-to-phone flows, but treat sessions and token approvals like live permissions — disconnect and revoke when done. I recommend a small test transaction the first time you connect.
Read more on setup and troubleshooting: Install mobile, Connect to dApps, and Revoke approvals. Take one safe step today: connect, approve a tiny test swap, then disconnect.