- Install the browser extension. See the browser install guide: [/install-metamask-chrome-extension].
- Choose Create a new wallet or Import using seed phrase.
- Create a strong password; write down the seed phrase offline (12 words). See seed backup steps: [/seed-phrase-backup-recovery].
Mobile (iOS/Android):
- Install app from the official store; open and tap Create wallet or Import.
- Enable biometric lock for convenience and security.
- Use the built-in dApp browser to connect to mobile sites. More: [/metamask-mobile-ios-android].
When I first set this up I wrote the seed phrase on paper and stored it in two locations. What I've found: manual backup remains the safest for many people.
For detailed onboarding walkthroughs see: [/install-create-wallet], [/browser-extension-setup], [/mobile-app-setup].
Mobile vs browser extension: which to use when
- Mobile strengths: on-the-go swaps, built-in dApp browser, biometric unlock and WalletConnect sessions. Good for daily small-value interactions.
- Extension strengths: easier hardware-wallet integration, more screen real-estate for contract calls and developer tools.
But remember: mobile is convenient. And desktop is more convenient for heavy dApp interactions (multiple tabs, Ledger pairing). See the mobile vs desktop comparison: [/mobile-vs-desktop] and hardware setup instructions: [/ledger-with-metamask-guide].
Quick comparison table
| Feature |
Browser extension |
Mobile app |
Hardware integration |
| Injected provider for dApps |
Yes |
Limited (in-app) |
Via extension only |
| Built-in dApp browser |
No (browser site is dApp) |
Yes |
No |
| Biometric lock |
No |
Yes |
Depends on device |
| Easy Ledger/Trezor pairing |
Yes |
Partial |
Yes (recommended) |
Networks, multi-chain and custom RPCs
MetaMask is EVM-compatible by design. That means you can add networks like Polygon, BSC, Avalanche, Arbitrum and Optimism by adding a custom RPC or using a community-provided config. To add an L2 or custom chain use the custom RPC settings: [/custom-rpc-network-settings] or add network shortcuts: [/add-l2-networks-to-metamask], [/add-polygon-to-metamask], [/add-bsc-to-metamask], [/add-avalanche-to-metamask].
Note: MetaMask does not natively handle non-EVM chains (for example Solana or native Bitcoin). If you hold assets on those blockchains use a wallet designed for them (see [/chains-metamask-does-not-support]).
DeFi, swaps and dApp connections
MetaMask connects to DeFi dApps through the injected provider on desktop and the in-app browser on mobile. It also supports WalletConnect sessions for apps that use that protocol. See connect guides: [/connect-to-dapps-walletconnect].
MetaMask’s in-wallet swap is a routing aggregator that queries multiple liquidity sources and returns quotes (price impact and gas estimate). Users can set slippage tolerance and advanced gas options before confirming a swap. In my experience the aggregator saves a step compared with opening a separate DEX UI, but I always compare quotes before accepting a route (why not double-check?). More on swaps: [/in-wallet-swap-guide].
Staking, validators and liquid staking via dApps
MetaMask itself doesn't run validators or host staking services. Instead you connect to staking dApps (Lido, Rocket Pool, protocol-specific UIs) through the wallet and sign staking transactions. Validator choice, node rewards and slashing risk are controlled by the staking protocol, not MetaMask. See how staking works through dApps: [/staking-via-dapps-from-metamask] and general staking notes: [/staking-with-metamask].
Security, backups and hardware wallets
Security features: local password encryption, optional biometric lock on mobile, a built-in phishing detection blocklist, and a connected-sites list you can manage. I once approved an unlimited token allowance by mistake; I now revoke approvals regularly (you should too).
Steps to reduce risk:
- Backup your seed phrase offline immediately. Read [/seed-phrase-backup-recovery].
- Use a hardware wallet for large balances; connect via extension. See [/hardware-wallets-with-metamask] and [/ledger-with-metamask-guide].
- Revoke token approvals periodically (step-by-step guide: [/token-allowances-and-revoke]).
- Enable biometric lock on mobile and never paste your seed phrase into a website.
But there's nuance: cloud-sync features are convenient for syncing multiple devices; they also add attack surface (consider trade-offs). See syncing: [/sync-and-use-on-multiple-devices] and a full security checklist: [/security-checklist].
If you suspect compromise, follow the recovery steps: [/compromised-wallet-what-to-do].
Gas fees, EIP-1559 and L2 considerations
MetaMask supports EIP-1559 transactions (base fee + priority fee). The UI presents recommended priority fees (low/medium/high) and an advanced gas field. Gas estimates are generally accurate, but can diverge during network congestion — monitor mempool data or use block explorer gas trackers.
Layer 2 networks typically offer much lower gas. Use the correct network switch before sending funds. Wrong-network transfers often lead to lost funds (for example sending ERC-20 to a native chain address). For details: [/gas-fees-eip1559-l2] and pending transaction fixes: [/transaction-errors-and-fixes].
NFTs, token management and portfolio tracking
MetaMask supports ERC-721 and ERC-1155 tokens and can show collectibles in the mobile app. Metadata is fetched from public APIs and sometimes fails (you may see blank NFTs). You can add custom tokens manually using the token contract: [/add-custom-token-to-metamask].
For portfolio overviews and tracking, use the built-in asset list or a dedicated portfolio tool connected through MetaMask: [/portfolio-and-token-tracking] (I use external trackers for tax/exporting reasons).
Who is MetaMask best for? Who should look elsewhere?
Who it’s best for:
- Users who interact with EVM-compatible DeFi dApps, swap tokens frequently, and want hardware-wallet support via extension.
- Developers and power users who need custom RPCs and multiple accounts.
Who should look elsewhere:
- Users who need native Solana or Bitcoin full support.
- Users who want fully custodial fiat onramps built into the wallet UI (use regulated custodial services instead).
(If you want a side-by-side with other wallets see [/metamask-vs-other-wallets].)
FAQ (short answers)
Q: Is it safe to keep crypto in a hot wallet?
A: Hot wallets are convenient. They are not as secure as hardware or cold storage. Keep only active funds in a hot wallet; move large holdings to hardware wallets.
Q: How do I revoke token approvals?
A: Use a revocation tool or on-chain explorer; disconnect dApps first, then revoke allowances (step-by-step: [/token-allowances-and-revoke]).
Q: What happens if I lose my phone?
A: If you have the seed phrase you can restore the wallet on a new device. If you don't, funds are effectively lost. See recovery steps: [/seed-phrase-backup-recovery] and compromised guidance: [/compromised-wallet-what-to-do].
MetaMask vs the Alternatives: An Honest Side-by-Side
People often ask me whether they should stick with MetaMask or move to something newer. In my testing across four wallets over several months, the honest answer is "it depends on what you value." MetaMask is the default for a reason — near-universal dApp support — but it is not the only sensible choice.
| Wallet |
Type |
EVM chains |
Standout strength |
Common gripe |
| MetaMask |
Extension + mobile |
Unlimited (custom RPC) |
Widest dApp compatibility |
Fees on in-app swaps |
| Rabby |
Extension |
Broad EVM |
Pre-transaction risk simulation |
Smaller ecosystem |
| Trust Wallet |
Mobile-first |
EVM + non-EVM |
Multi-chain in one app |
Weaker desktop flow |
| Coinbase Wallet |
Extension + mobile |
Broad EVM |
Beginner-friendly UX |
Tighter ecosystem lock-in |
What stood out to me: Rabby's transaction preview caught a bad approval I would have signed blindly in MetaMask, while Trust Wallet handled non-EVM assets MetaMask simply can't hold natively. That said, when a niche dApp only tested against one wallet, MetaMask was the one that always connected.
My honest take
None of these is objectively "best." If you live in EVM DeFi, MetaMask's compatibility wins. If safety previews matter more, a simulation-first wallet is worth trialing alongside it. Run two in parallel before committing — I keep MetaMask for compatibility and a second wallet for high-value signing.
Troubleshooting Common MetaMask Problems
Most MetaMask "bugs" I encounter are recoverable configuration issues, not lost funds. Here are the four that generate the most panic, and how I actually resolve them.
Pending or stuck transactions
A transaction stuck on "pending" almost always means the gas price fell below network demand, or an earlier nonce is blocking the queue. In my testing, the reliable fix is Speed Up (rebroadcast with higher gas) or Cancel, which sends a 0 ETH self-transfer at the same nonce. If the interface won't offer these, resetting the account via Settings → Advanced → Clear activity tab data forces a nonce resync without touching your funds.
"Wrong network" errors
When a dApp shows the wrong balance, you're usually connected to the wrong chain. Confirm the network selector matches the dApp, and verify the chain ID — spoofed RPCs reuse familiar names with fake IDs.
A token isn't visible
Missing tokens are almost never gone. The asset simply isn't imported. Use Import tokens, paste the verified contract address, and it appears. Always confirm the contract on a block explorer first.
Importing a seed phrase
When restoring, type the twelve words in order, offline if possible. Never paste a seed into a website or support chat — legitimate MetaMask support will never ask for it.
Advanced MetaMask Workflows for Power Users
Once the basics feel routine, a few advanced habits meaningfully reduce risk. These are the workflows I lean on after signing thousands of transactions.
Auditing and revoking token approvals
Every time you trade on a dApp, you grant a spending allowance — often unlimited. In my testing, stale approvals are the single largest avoidable risk. I periodically review permissions through MetaMask's Settings → Permissions view and revoke anything I no longer use. Treat a revoke transaction as cheap insurance.
Adding L2s and custom RPCs safely
Adding a network manually gives control, but it's also where phishing hides. I only add an RPC endpoint sourced from a project's official documentation, then cross-check the chain ID against a public registry before sending value. A matching name with a mismatched ID is a red flag every time.
Hardware wallet integration
Connecting a hardware device keeps your keys offline while still using MetaMask's interface. The critical discipline: verify the receiving address and amount on the device screen, not just the browser. Malware can alter what the extension displays, but it cannot forge the hardware confirmation.
A workflow I trust
- Sign high-value transactions only from a hardware-backed account
- Keep a low-balance "hot" account for routine dApp testing
- Revoke approvals monthly and after any suspicious prompt
Conclusion & next steps
MetaMask is a pragmatic, widely-used non-custodial software wallet for interacting with EVM-compatible DeFi and dApps. It balances convenience, multi-chain flexibility and hardware-wallet integration. I believe it’s a solid daily driver for active users (with proper hygiene: seed backups, revoke approvals, hardware for large balances). Want to get hands-on? Start with the step-by-step setup: [/getting-started-metamask] or jump to the browser extension install guide: [/install-metamask-chrome-extension].
But remember: always test with small amounts first. And check connected sites before approving transactions.