Overview
This guide covers extension updates and the most common extension issues for the MetaMask browser extension on Chrome, Firefox, and Edge. If you landed here after seeing messages like "this item has been disabled in chrome" or wondering how to update metamask chrome, you’ll find practical troubleshooting steps and safe recovery advice.
I use the extension daily and have walked through several updates and a couple of painful reinstalls. What I've found helps most is a short checklist before any uninstall: backup first, then update.
How browser extension updates work (short technical primer)
Browsers usually auto-update extensions via their official add‑on store. Chrome pulls signed extension packages (CRX) from the Web Store. Firefox uses its add‑ons server. Edge follows Chromium mechanics but can also allow other stores. Updates are applied in the background and should keep your extension data (accounts, settings) intact. Short sentence. But when a major manifest or permission change occurs the browser may require you to accept new permissions or it may temporarily disable the extension.
Under the hood the extension runs content scripts and a background service (or worker). When an update changes that code, the browser swaps the files and restarts the service worker. That can briefly interrupt dApp connections.
Step-by-step: Update MetaMask on Chrome
- Start with a backup. Export or write down your seed phrase and ensure it's stored offline. (Do this even if you don't plan to reinstall.)
- Open the extensions page (type chrome://extensions into the address bar).
- Toggle Developer mode on (top-right). Click the "Update" button to force-check updates for all extensions.
- If Chrome reports "this item has been disabled in chrome," click the extension card for details and then check the Web Store listing. The store page will often show whether the item was removed or flagged.
- If the extension won't update or is missing, update Chrome itself, restart, and try again.
If those steps fail, uninstall and reinstall from the Chrome Web Store only after confirming your seed phrase. Removing the extension usually wipes local extension storage.
(If you can’t download MetaMask on Chrome because you’re on a phone: Chrome mobile doesn’t support extensions — use the mobile app instead: /install-metamask-mobile-app.)
Step-by-step: Update MetaMask on Firefox
- Back up your seed phrase first.
- Open the Add-ons Manager (about:addons) and click the gear icon.
- Choose "Check for Updates" to force Firefox to fetch the latest version.
- If the extension is disabled, the Add-ons page usually shows the reason (signed, blocked, or incompatible).
- If needed, remove and reinstall from the official Firefox add-ons site and restore using your seed phrase.
Note: Firefox may block an extension if it’s unsigned or flagged. Keep your browser updated.
Step-by-step: Update MetaMask on Edge
- Backup seed phrase first.
- Go to edge://extensions and enable Developer mode to reveal an "Update" button.
- Force an update and restart the browser.
- If Edge shows the extension disabled, verify whether Edge is allowing extensions from the Chrome Web Store (toggle in settings) or install from Edge's store.
Edge closely follows Chrome behavior because it's Chromium-based, so many Chrome troubleshooting steps apply.
Common errors and how to fix them
"This item has been disabled in Chrome": This can mean the extension was removed from the store, a new policy blocked it, or local browser policy (enterprise) disabled it. Check chrome://policy to see managed policies, and check the store listing. And don’t panic — your accounts are recoverable with your seed phrase.
"Why can't I download MetaMask on Chrome?": Often due to using a mobile Chrome build (no extensions), an outdated browser, or corporate restrictions. Update the browser, or use the desktop version.
Extension crashes or won’t open: Disable other extensions that inject scripts (ad blockers, privacy add-ons) and retry. Try a fresh browser profile to isolate conflicts.
Permissions prompt after update: Grant only what you expect. New permissions may be legitimate for new features; evaluate them before agreeing.
Resolving "metamask this session is already connected" and connection hiccups
Why does that message appear? Usually because a previous connection session remains active between the dApp and your extension (localStorage/session tokens, or a background worker). Here are fixes I use:
- Disconnect the site from the extension: open the extension → Settings → Connected Sites (or Connected Sites / Permissions) and remove the site.
- On the dApp, look for a "Disconnect" or "Logout" button. Then hard refresh the page (Ctrl+Shift+R).
- Clear the site's local storage via DevTools Application tab (advanced).
- If the problem persists, try a private window or a different browser profile.
See also the guides on connecting to dApps and troubleshooting connections: /connect-dapps and /connect-uniswap.
Safe reinstall & backup checklist
- Seed phrase backed up offline? Yes.
- Exported any hardware-wallet linked accounts? Consider that separately.
- Note custom networks and RPC endpoints (copy them from Settings → Networks).
Uninstalling will remove the extension. Reinstalling requires the seed phrase to restore your accounts. If you manage funds on-chain, do the seed phrase backup step twice. I learned that the hard way after a reinstall that required a restore.
For more on backups and restoring: /backup-recovery-seed and /create-restore-wallet.
Browser comparison: update routes and quick fixes
| Browser |
Force update path |
Common disable causes |
Quick fix |
| Chrome |
chrome://extensions → Developer mode → Update |
Store removal, policy, manifest changes |
Check chrome://policy, update browser, reinstall |
| Firefox |
about:addons → Gear → Check for Updates |
Unsigned add-on, compatibility |
Update Firefox, reinstall from addons site |
| Edge |
edge://extensions → Developer mode → Update |
Store permissions, Chromium policy |
Enable "Allow extensions from other stores", reinstall |
Who the extension is for — and who should look elsewhere
Best for: daily DeFi users, token swappers, and dApp interactors who need a flexible, non-custodial browser extension that supports EVM-compatible chains and WalletConnect flows.
Look elsewhere if: you hold very large balances and prefer hardware or cold storage for signing transactions, or if your workflow requires a mobile-only solution (see /install-metamask-mobile-app) or enterprise-managed browser where extensions are blocked.
FAQ
Q: Is it safe to keep crypto in a hot wallet extension?
A: Hot wallets are convenient. They are non-custodial but remain online, so use small daily funds in the extension and move large holdings to hardware or cold storage. See /hardware-wallets-overview for alternatives.
Q: How do I revoke token approvals after an update or reinstall?
A: Use the revoke approvals tools and double-check connected sites. See /token-approvals-revoke for step-by-step instructions.
Q: What happens if I lose my phone or browser profile with the extension installed?
A: Your funds aren’t gone if you have the seed phrase. Restore on a new device via /create-restore-wallet or /backup-recovery-seed.
Conclusion & next steps
Extension updates are usually automatic, but problems do occur — from store removals to corporate policy blocks. Start with a backup, try the browser-specific force-update steps, and only reinstall once you have your seed phrase saved offline. I've been using extensions daily for months and can say that a careful backup habit saves time and stress.
If you want step-by-step install or restore walkthroughs, check the install guide (/install-metamask-extension) and our maintenance notes (/update-maintenance). If connection problems continue, see the troubleshooting guide (/troubleshooting-connect).
And if you need hands-on help, follow the safe reinstall checklist above before making changes.
