Install MetaMask — Browser extension (Chrome)
What this guide covers
This page shows how to download MetaMask for Google Chrome, complete the initial extension install, and configure basic settings for safe daily use. Expect step-by-step instructions for the Chrome MetaMask extension download and install process, plus troubleshooting tips when brave wont connect to metamask or when you need to chrome update metamask manually. I’ve used browser extensions for daily swaps and dApp connections, so I’ll include practical checks I use before moving real funds.
Who should use the browser extension?
Short answer: people who use DeFi on desktop regularly and want a quick, injected provider in the browser. Longer answer: the browser extension is helpful if you open Uniswap, DEX aggregators, or developer tools from a desktop. It’s convenient for quick swaps, connecting to dApps, and for testing contracts on local networks.
Who this wallet is best for
- Desktop-first DeFi users who want an injected provider for sites.
- Developers testing contracts on local chains or L2s (EVM-compatible only).
- People who pair the extension with a hardware wallet for day-to-day interactions.
Who should look elsewhere
- Users who need Solana or Bitcoin native support (see solana-limitations).
- People who prioritize cold storage only—use a hardware wallet alone.
- Mobile-first users who prefer an in-app dApp browser (see install-metamask-mobile-app).
Step-by-step: download MetaMask Chrome extension and install
- Open Chrome and visit the Chrome Web Store. Search for the extension you want. Want to reduce risk? Only install from the official store.
- Locate the extension listing and check details: publisher name, reviews, and install counts. And always verify the extension publisher before you click "Add to Chrome."
- Click Add to Chrome (or Add extension). Accept the permissions the extension requests (the prompt will list them).
- Pin the extension to the toolbar for quick access. On Chrome, click the puzzle icon and pin the extension.
Tip: If you prefer Firefox, there is a separate workflow—search the add-ons site and follow the browser prompts (see metamask extension install firefox).
Initial setup: create or restore a wallet
After installing the extension you get a short onboarding flow: create a password for the extension, and then either create a new wallet or restore from a seed phrase. Never type your seed phrase into websites. Write the seed phrase down on paper and store it offline.
Steps after install:
- Create a secure extension password (this locks access on the device).
- Back up the seed phrase — this is the only recovery path for private keys in a non-custodial software wallet. See backup-recovery-seed for options.
- If you have hardware devices, connect them via the extension for safer transaction signing (see connect-ledger and connect-trezor).
In my experience the easiest safe pattern is: create an account, back up the seed phrase offline, then test with a very small transaction before using larger sums.
Post-install configuration: networks, privacy, and RPCs
MetaMask (browser extension) is primarily for EVM-compatible blockchains and compatible Layer 2s. To add a custom network you can configure an RPC endpoint, chain ID, and currency symbol in settings. That tells the extension which node to talk to when you switch networks.
Privacy note: some extensions block sites from seeing your accounts until you explicitly connect. Check the extension's privacy/account settings so sites can't read your address without permission.
Troubleshooting: Brave won't connect & Chrome update issues
Why won’t the extension connect to a dApp? Often it’s a permission or provider conflict.
Common fixes
- Confirm the extension is enabled (chrome://extensions).
- Ensure the site has permission to use the extension (click the extension icon and check site access).
- Disable other wallet extensions or built-in wallets that inject a provider. But sometimes Brave's built-in wallet takes precedence; try disabling it (update Brave if you don't see the option).
- Clear site data and reload the dApp, then open the extension and approve the connection.
If Brave won’t connect to MetaMask (or brave wont connect to metamask 2022), these steps usually help: update Brave to the latest version, check for built-in wallet conflicts, and re-enable the extension. If you still see trouble, reinstall the extension and import your wallet with the seed phrase (only after verifying you have a secure copy of the seed phrase).
Updating the extension (chrome update metamask)
- Chrome auto-updates extensions. To force an update, go to chrome://extensions, enable Developer mode, then click Update.
- Reinstalling from the Chrome Web Store also installs the latest version.
Security checklist after install
- Back up your seed phrase offline and test recovery on a separate profile. See backup-recovery-seed.
- Use a hardware wallet for large balances and enable it via the extension (connect-ledger, connect-trezor).
- Revoke token approvals regularly (see token-approvals-revoke).
- Never enter your seed phrase into a website. Phishing sites mimic the extension UI.
Daily usage tips: dApps, swaps, and gas fees
- When a dApp asks to connect, check the origin URL before approving.
- For swaps inside the extension, compare the quoted routes (some in-wallet swaps use aggregator routing). See in-wallet-swap.
- For gas control, the extension exposes EIP-1559 fields on many networks. If you're swapping frequently, set conservative slippage and test small trades first.
And if you prefer to test before sending funds, do a tiny transaction first. Small habits like that saved me from bigger mistakes.
Quick comparison: Extension vs Mobile vs Hardware
| Feature |
Browser extension (MetaMask) |
Mobile app |
Hardware wallet |
| Form factor |
Desktop/browser-injected provider |
Phone app with dApp browser |
Cold storage device |
| Best for |
Desktop dApp work, dev tools |
Mobile DeFi, on-the-go swaps |
Long-term storage, high-value signing |
| Security |
Hot wallet — convenient but exposed to browser threats |
Hot wallet — mobile-specific risks |
Most secure for private keys |
| Multi-chain |
EVM-compatible chains & L2s |
EVM-compatible; some wallets add extras |
Can sign across chains with bridge/hosts |
| Hardware integration |
Yes (connect via extension) |
Yes, sometimes via USB/Bluetooth |
N/A (it is the secure signer) |
FAQ
Q: Is it safe to keep crypto in a hot wallet extension?
A: Hot wallets are convenient. They trade some security for usability. For everyday small balances and active DeFi use, they work well. For larger holdings, pair with a hardware wallet or move to cold storage. See hardware-wallets-overview.
Q: How do I revoke token approvals?
A: Use the extension’s revoke tools or a trusted on-chain approvals dashboard. Revoke unlimited allowances and re-approve shorter allowances when needed. See token-approvals-revoke for step-by-step instructions.
Q: What happens if I lose my phone?
A: Losing a device does not expose funds if you keep the seed phrase secure. Use your seed phrase to restore on a new device or use a hardware wallet. See lost-phone-recovery.
Q: Why won't Brave connect to MetaMask?
A: Often due to a provider conflict (Brave's native wallet vs the extension). Update Brave, disable the native wallet if present, and confirm extension permissions.
Final notes & next steps
The browser extension is a practical bridge between desktop workflows and DeFi. I use it daily for quick swaps and dApp testing, but I keep larger balances on hardware wallets. If you finished the install, next steps: secure your seed phrase (backup-recovery-seed), create additional accounts (create-restore-wallet), and configure any networks you need (add-custom-network).
But if you want a mobile-first workflow, head to install-metamask-mobile-app to set up the mobile experience.
If you hit a specific error while installing (permission prompts, Chrome blocking the install, or a dApp not detecting the provider), check troubleshooting-connect for targeted fixes.
Happy testing, and keep small safety steps in place when moving real funds.
