Quick overview
This guide explains how to connect MetaMask on mobile and how to connect MetaMask app to browser sites, covering both the wallet's in-app dApp browser and external connection flows (WalletConnect and deep links). I use MetaMask mobile daily for small swaps and dApp testing, so these are practical, hands-on notes rather than theory. And yes, I've accidentally clicked a questionable "connect" prompt before — and learned the hard way to check allowances.
How mobile dApp connections work (short primer)
There are three common ways a mobile dApp talks to your software wallet:
- In-app browser (the wallet opens the dApp inside the app and injects a provider).
- WalletConnect (an open protocol that opens your wallet to approve a session between the site and your app).
- Deep link / universal link (the site opens the wallet app directly to handle a connection or signature request).
Which is used depends on the site and the mobile browser you're on. On desktop the extension injects a provider (window.ethereum). On mobile, regular browsers rarely support extension injection, so WalletConnect and the wallet's own browser are the usual options.
Step-by-step: How to connect MetaMask on mobile (in-app browser)
If you want the smoothest experience with an injected provider, use the wallet's built-in browser.
- Open the MetaMask mobile app.
- Tap the Browser (or DApps) tab.
- Enter the dApp URL (for example, the official site you intend to use).
- When the site prompts "Connect Wallet" tap it.
- A connection modal will appear inside the wallet. Choose the account(s) you want to expose and tap Connect.
- Confirm any signature or transaction requests that follow. Read the destination and data — if the prompt asks to approve a token allowance, check the amount and consider setting a custom limit.
Short, focused sessions work best inside the in-app browser. If you regularly swap tokens, this keeps the flow in one place (no copy-paste of addresses), and chain switching behaves like changing tabs in a browser — seamless in my experience.
Step-by-step: How to connect MetaMask app to browser (mobile browser & WalletConnect)
What if you're in Chrome or Safari and the site doesn't run inside MetaMask? Use WalletConnect (or a deep link if the site supports it).
- Open the dApp in your mobile browser.
- Tap Connect Wallet on the site.
- Choose WalletConnect (or select "MetaMask" if the site lists it and provides a deep-link option).
- If WalletConnect appears, the site will present a modal with wallets; select MetaMask (or scan a QR if you are using a desktop site).
- MetaMask will open and show a session request. Check the site domain, requested chains, and the metadata the dApp wants to read. Approve the connection.
- Return to your browser. The dApp should now show your connected account.
How to connect MetaMask in mobile browser often comes down to whether the dApp supports WalletConnect or deep links. If it doesn't, open the site inside the wallet's browser instead.
Example: Connect MetaMask mobile to Uniswap app
Want to connect MetaMask mobile to Uniswap app (or another DEX)? The steps are the same as above:
- Open app.uniswap.org in your mobile browser.
- Tap Connect Wallet → WalletConnect.
- Select MetaMask. The MetaMask app opens and asks to approve the session.
- Approve, then return to the Uniswap page.
Uniswap and other major DEXes generally support WalletConnect. If you prefer to stay fully inside the wallet, open Uniswap inside the MetaMask browser instead. But if you use browser extensions on desktop, WalletConnect will let your phone pair to the desktop session (more on that on the /mobile-desktop-sync page).
Connection methods compared (table)
| Method |
How it works |
Pros |
Cons |
Best for |
| In-app dApp browser |
dApp runs inside the wallet; provider injected |
Fast, single-app flow; injected provider |
Some dApps behave differently in in-app browsers |
Daily swaps and quick dApp tests |
| WalletConnect |
Protocol-based session between site and wallet |
Works from any mobile browser; widely supported |
Extra step to switch apps; session persistence (careful) |
Mobile browser users and desktop-to-phone pairing |
| Deep link |
Site triggers wallet app directly |
Quick jump to wallet for auth |
Requires site support; sometimes flaky |
Single actions or sites with dedicated mobile integration |
Common connection issues and troubleshooting
- Site doesn't list MetaMask on mobile: try WalletConnect or open the site in the wallet's browser.
- Connection hangs after approving: close and reopen the browser tab (or revoke session and reconnect).
- Wrong network requested by dApp: switch networks in the wallet or add a custom network (see /add-custom-network).
If problems persist consult /troubleshooting-dapp-connections or /connect-button-troubleshoot for step-by-step fixes.
Security & permission checklist before you approve
Always review the connection details. Short checklist:
- Confirm the domain matches the official site (phishing sites are common).
- Check whether the dApp requests only to view your address or also to sign transactions.
- If asked to approve a token allowance, prefer a specific amount over "infinite" allowance. (I once granted an unlimited allowance by mistake; I revoked it immediately.)
- Use biometric lock on mobile for an extra layer of protection.
After you connect, periodically audit active approvals and connected sites — see /token-approvals-revoke for how to remove unwanted allowances.
Practical tips for daily DeFi use
- For frequent swaps, the in-app swap UI saves time, but compare prices with an aggregator if you paste trade details into a separate tool.
- Adjust slippage only when you understand slippage dynamics. Low slippage may cause failed transactions; high slippage can be costly.
- Watch gas fees and EIP-1559 fields: the wallet suggests priority fees, but you can customize if a transaction is time-sensitive.
- Disconnect dApps when you finish a session, especially on public or shared devices.
Who this flow is for — and who should look elsewhere
Who this helps:
- Mobile-first DeFi users who want quick access to DEX UI and dApps.
- People who prefer not to juggle desktop extensions and a phone.
Who should look elsewhere:
- Users holding very large balances should consider combining hardware wallets with desktop flows (see /hardware-wallets-overview).
- Developers needing injected providers for local testing may prefer desktop extension workflows (see /connect-ganache-local and /connect-remix).
FAQ
Q: Is it safe to keep crypto in a hot wallet on my phone?
A: Hot wallets are convenient but carry more risk than cold storage. For everyday amounts and active DeFi use, hot wallets are practical. For large holdings keep most funds offline and transfer small amounts for activity. See /security-best-practices and /backup-recovery-seed for backup options.
Q: How do I revoke token approvals?
A: Use the wallet's approval manager or a reputable revoke UI. The /token-approvals-revoke article walks through steps and shows how to revoke an unlimited allowance.
Q: What happens if I lose my phone?
A: Your seed phrase is the key. If you have the seed phrase or another recovery method, you can restore accounts on a new device (see /backup-recovery). If you lose the seed phrase and the phone, funds are likely unrecoverable.
Conclusion & next steps
Connecting MetaMask on mobile can be quick and safe when you understand the different flows: the in-app dApp browser for injected sessions, WalletConnect for external browsers, and deep links for one-off actions. Which should you use? It depends on whether you value speed (in-app browser) or browser flexibility (WalletConnect). But always check permissions before you hit "Approve".
If you haven't installed the app yet, start with the Install MetaMask Mobile App guide. For detailed help with dApps, see Connect dApps and for WalletConnect-specific pairing instructions see WalletConnect mobile linking.
Want hands-on troubleshooting? Visit /troubleshooting-dapp-connections. Safe transacting.
