This guide explains how to disconnect MetaMask from a website, both on the browser extension and on mobile (including WalletConnect sessions). I explain practical steps, what disconnecting actually does (and what it doesn't), and how to fully erase a site's connection. What I've found from regular use: disconnecting is fast, but on-chain approvals and browser cookies often remain unless you take extra steps. And yes — disconnecting is something you should do after using unfamiliar dApps.
When you "connect" a site to MetaMask you give that domain the ability to query (and with your permission, request transactions from) one of your accounts. Disconnecting removes the domain-level permission to read which account(s) are exposed to that site in your current browser session.
But disconnecting does NOT automatically cancel any token allowance (token approval) you previously granted to a smart contract. Those approvals are recorded on the blockchain. So: disconnect to remove ongoing site access in your UI, and then revoke approvals separately if you worry about on-chain access.
See how to revoke approvals: token approvals and revoke.
Step-by-step (typical path in modern browser extension UIs):
Quick tip: many dApps include a "Disconnect" button in their UI. That is often the quickest way, but I prefer to verify via MetaMask's Connected sites list afterward.
How to disconnect MetaMask mobile from website (Android/iOS):
If you connected via the in-app browser inside MetaMask, you can also open the browser tab for the site and use the site's wallet menu to disconnect.
And a heads-up: mobile menu labels have changed over time. If the exact label is missing, search Settings for words like "Connected" or "Connections".
Related: connected-sites-mobile explains mobile quirks and screenshots.
WalletConnect creates a persistent session between a dApp and your wallet. Disconnecting requires closing the session on at least one side.
Steps (both desktop dApp using QR and mobile):
After disconnecting, reload the dApp and check whether it asks to initiate a new WalletConnect session (verification).
Disconnect vs erase: disconnect removes the live permission. Erase is broader and may require extra steps.
Warning: uninstalling or reinstalling the wallet does not change on-chain approvals. To remove a contract's token allowance you must revoke it on-chain. See: token approvals and revoke.
But remember: disconnecting is a privacy and convenience step. It reduces the chance a shady front-end can keep polling your account, but it does not remove what you already signed on-chain.
How I tested (so you can replicate):
What I've found: disconnect from MetaMask's UI is immediate. But sometimes the dApp's JavaScript keeps a cached address in local storage; clearing cookies/local storage is the final step to erase every trace.
Q: Is it safe to keep crypto in a hot wallet? A: For small, everyday balances yes, if you practice good security (strong device security, seed phrase backup, revoke approvals periodically). For larger holdings consider a hardware wallet. (I moved large amounts to hardware after a careless approval some months back.)
Q: How do I revoke token approvals? A: Disconnecting does not revoke approvals. Use the in-wallet approvals tool or a reputable approval revocation interface. See: token approvals and revoke.
Q: What happens if I lose my phone? A: If you have your seed phrase (stored securely) you can restore your wallet on another device. For steps: backup and recovery seed phrase and lost-phone-reset-recovery.
Q: My dApp still reads my address after disconnect. Why? A: The dApp might store your address in cookies or local storage (client-side). Clear those for the domain and reload.
Disconnecting MetaMask from a site is a simple privacy step that every active DeFi user should know. It stops the site from reading your account in that browsing session, but it does not undo on-chain token approvals — so always follow up by revoking allowances when needed.
If you want to learn more about connecting safely, start with: connect-metamask-to-dapps, and if you worry about approvals, read: token approvals and revoke. For mobile-specific screenshots and tips check: connected-sites-mobile.
If you want a step-by-step refresher on installation or account recovery before making changes, see: install-metamask-extension and backup-and-recovery-seed-phrase.
Thanks for reading. If you try these steps and something behaves unexpectedly, try the troubleshooting notes above, and you can follow the exact test steps I used to replicate the issue on your own device.