Short answer: yes — MetaMask mobile supports WalletConnect as a connector, so you can connect the MetaMask app to dApps that offer WalletConnect (QR code or link). The desktop/browser MetaMask extension does not need WalletConnect because it injects an Ethereum provider (window.ethereum) directly into the browser; that difference matters depending on whether you're connecting from a phone or from a desktop site.
If you're wondering "does metamask support walletconnect" because a website only shows a QR or a deep link, MetaMask mobile is the intended client to complete that connection. For mobile setup details see the MetaMask Mobile: iOS & Android guide. In my experience the QR-scan route is the most reliable on a modern phone (scan to connect in a few seconds). And yes, copy/paste links are a good fallback when deep links misbehave.
WalletConnect is a protocol that creates an encrypted session between a dApp and a remote software wallet. When you accept the connection in MetaMask mobile, the app and the dApp exchange a session key via a relay and sign messages locally on your device — private keys never leave your phone. The process is usually: dApp shows a QR or creates a wc: deep link -> MetaMask scans or opens that link -> handshake and session establishment -> dApp can request signatures or transactions, which you approve inside the app.
What I've found useful: WalletConnect avoids installing an in-app browser extension on mobile, while still enabling full DeFi flows (swaps, staking, NFTs) without exposing private keys externally.
Tip: if the dApp supports both WalletConnect and an injected provider, a desktop browser with the MetaMask extension will connect via injection (no QR required). For more about connecting dApps via WalletConnect see Connect to dApps: WalletConnect.
Problem: the dApp attempts a mobile deep link and you see messages like "deep link not supported metamask opensea" or search queries like "deeplink not supported metamask ios". Why does this happen? Several causes are common:
Quick fixes:
Example: OpenSea mobile sometimes tries to open MetaMask via a deep link that fails when the OS hasn't registered the current app build, which results in a generic "deep link not supported metamask opensea" error. The fastest workaround is scanning the QR shown on OpenSea desktop or using the WalletConnect option inside MetaMask to paste the link.
But if deep links still fail after updates, try deleting the dApp's cached session and reconnecting (steps below).
Best practice: end sessions you no longer use. Active WalletConnect sessions remain valid until you disconnect.
How to disconnect:
If a session is stuck (dApp shows connected but MetaMask doesn't), force-terminate the session from MetaMask and refresh the dApp. If that fails, a reinstall or account reset can clear stale session data (see reset-delete-and-reinstall).
And remember: WalletConnect secures private keys but social engineering can still trick you into signing malicious transactions. Pause and read the transaction payload before approving.
| Error message | Likely cause | Quick fix |
|---|---|---|
| "Deep link not supported" / "deeplink not supported metamask ios" | Universal link or app association mismatch | Update MetaMask, use QR / paste link, open site in Safari |
| Connection timeout | QR expired or network issue | Refresh QR on desktop, rescan, check phone network |
| "Request rejected" shown on dApp | You declined signature on phone | Re-check request details; try again if legitimate |
| Wrong network / chain ID | dApp expects different chain | Add or switch the network in MetaMask (or use custom RPC) |
| Stale session (dApp shows connected but no actions) | Session metadata mismatch | Disconnect in MetaMask and reconnect |
For transaction-specific errors see transaction-errors-and-fixes.
Q: Is it safe to keep crypto in a hot wallet connected via WalletConnect? A: Hot wallets are practical for daily DeFi and small balances, but self-custody has trade-offs. Use hardware wallets for large holdings and follow the security-checklist.
Q: How do I revoke token approvals after connecting via WalletConnect? A: Disconnect the WalletConnect session, then use a revocation tool or Token allowances and revoke walkthrough to remove approvals on-chain. I recommend doing this after a suspicious session.
Q: What happens if I lose my phone? A: If you have a secure seed phrase you can restore your wallet on a new device; however, any active WalletConnect sessions may still be valid until explicitly disconnected. Revoke approvals after restoring (or from another device) and rotate keys if needed. See Seed phrase backup & recovery.
Q: Why does OpenSea show "deep link not supported metamask opensea"? A: Often the OpenSea mobile site uses a deep link that your OS or app won't accept due to app version or association; switch to QR or copy/paste the WalletConnect link into MetaMask.
MetaMask mobile works well with WalletConnect for most DeFi and NFT flows, but deep-link behavior can be brittle across different OS versions and dApps. If you run into issues: try the QR flow, update the app, clear the session, and revoke allowances if anything looks suspicious.
Want focused walkthroughs? Check the connect-to-dapps-walletconnect page for more examples, or read the MetaMask Mobile: iOS & Android setup guide next.
If you need help tracing a specific error message, try the troubleshooting table above, or consult the deep-link-errors and disconnect-connected-sites pages for step-by-step fixes. But above all: keep your seed phrase offline, and pause before signing.