Notes on how this works: MetaMask uses the RPC URL to send JSON-RPC requests to a node. The Chain ID prevents replay attacks and ensures transactions sign correctly for BSC instead of Ethereum. If the RPC is down, MetaMask will show errors when loading balances or sending transactions.
If you prefer a single-click method, some dApps can prompt MetaMask to add a network for you. But verify the values first. Blindly accepting a network pushed by a site can connect you to a malicious RPC that logs activity.
For the extension install steps, see /install-metamask-extension and for adding other custom networks see /add-custom-network or /add-bsc-network.
How to connect MetaMask to Binance Smart Chain (mobile) — Step by step
- Open the MetaMask mobile app and unlock the wallet.
- Tap the hamburger menu (top-left) and go to Settings → Networks → Add Network.
- Fill the same fields shown above (network name, RPC, chain ID, symbol, block explorer URL).
- Save and switch to BSC from the network selector.
Mobile includes an in-app browser for BSC dApps. If a site asks to connect, MetaMask will prompt for permission. But be wary of phishing sites — check the URL twice.
If you need help installing the mobile app first, see /install-metamask-mobile-app.
Adding BEP-20 tokens and managing assets
MetaMask won't show every BEP-20 token automatically. To add one manually:
- Switch to BSC network in MetaMask.
- Go to Assets → Import tokens.
- Paste the token contract address. MetaMask will often auto-fill the symbol and decimals.
- Confirm and import.
Example: if you have a token contract address from a project's official docs (always verify), paste it here. (Tip: check the block explorer entry first.)
If a token doesn't show a logo or shows zero balance, verify the contract address on BscScan and confirm your address truly holds that token. For tools to inspect or revoke token allowances see /token-approvals-revoke.
Connecting to BSC dApps and in-wallet swaps
MetaMask on BSC works with dApps that support EVM chains. To connect a dApp, switch MetaMask to BSC and approve the connection when prompted. Want to use a DEX on BSC? The flow is the same as on Ethereum: connect, approve a token if required (this creates a token approval), then swap.
But be cautious: unlimited token approvals are a common attack vector. Approve only what's necessary, and revoke approvals if a dApp is no longer trusted.
For more on connecting dApps and specific marketplaces or DEXes, check /connect-dapps and /connect-pancakeswap. For swaps inside MetaMask see /swaps-in-wallet.
Gas fees and transaction settings on BSC
BSC uses a legacy-style gas price model rather than EIP-1559. That means MetaMask will show Gas Price (Gwei) and Gas Limit fields. Estimates are usually low (BSC is cheap), but during congestion you should increase gas price slightly to avoid stuck transactions.
How gas works here: you pay BNB to validators for block inclusion. If you set gas price too low, the transaction may not be picked up. If you're using a hardware wallet, the device must confirm the gas and nonce before signing.
For more about gas mechanics and Layer 2 differences see /gas-fees-eip1559 and /gas-fees-l2.
Security, backups, and common mistakes
- Never paste your seed phrase into a website. Ever.
- Confirm the network RPC and chain ID before adding (an attacker could provide a fake RPC that mints spoofed balances in your UI).
- Sending tokens to the wrong chain is a frequent mistake. Addresses look identical on EVM chains, but tokens live on each chain separately. If you send Ethereum-only tokens to BSC, recovery can be complex.
- Approve minimally and use revocation tools when you stop using a dApp.
- Consider using a hardware wallet (connected via MetaMask) for larger holdings—see /connect-ledger and /connect-trezor.
What I've found: the most common errors are trusting auto-populated RPC data from unknown sites and approving unlimited token allowances without a second thought. But careful habits reduce most risks.
For backup options see /backup-recovery and for recovery if you lose your phone see /lost-phone-recovery.
Who this wallet setup is best for (and who should look elsewhere)
Who this is for:
- Users who want a flexible hot wallet to interact with BSC dApps and BEP-20 tokens.
- Traders who do frequent small swaps and value convenience across devices.
- Developers testing smart contracts on BSC using MetaMask as an injected provider (see /developers-connect).
Who should look elsewhere:
- Users holding large balances who prefer cold storage: consider a hardware-wallet-first workflow.
- People who need custodial fiat rails or exchange-like services—MetaMask is non-custodial and does not provide custodial custody.
FAQ
Q: Is it safe to keep crypto in a hot wallet like MetaMask?
A: Hot wallets are convenient but inherently exposed. For small, active holdings used in DeFi, they are appropriate. For long-term storage of large amounts, I recommend moving most funds to cold storage and keeping only what you actively use in the hot wallet.
Q: How do I revoke token approvals on BSC?
A: Use a token-approval revocation tool (see /token-approvals-revoke) or inspect allowances on BscScan and submit a 0-approve transaction. Revoking reduces the attack surface after a dApp is no longer trusted.
Q: What happens if I lose my phone?
A: If you have your seed phrase, you can restore the wallet on another device. Without the seed phrase or an exported private key, funds are not recoverable. See /backup-recovery and /lost-phone-recovery.
Q: Why don’t I see my tokens after switching to BSC?
A: Make sure you are on the correct network and have added the BEP-20 token contract address under Assets → Import tokens. Verify the token contract on BscScan first.
Conclusion and next steps
Connecting MetaMask to Binance Smart Chain is a one-time setup that expands the number of DeFi apps and BEP-20 tokens you can use from the same non-custodial account. Follow the step-by-step instructions above, verify RPC details, and practice safe approval habits.
Next steps I suggest: add BSC on both desktop and mobile, import a small test token to confirm balances, and try a low-value swap to experience gas and approval flows. For deeper reads on approvals, backups, and hardware integration, see /token-approvals-revoke, /backup-recovery, and /connect-ledger.
If you want a quick comparison of form factors (extension vs mobile vs hardware through MetaMask), see the table below.
| Form factor |
Best for |
Security trade-off |
| Browser extension |
Daily swaps, dApp interaction |
Convenient but exposed to browser threats |
| Mobile app |
On-the-go trading, mobile-only dApps |
Convenient; phone loss risk |
| Hardware + MetaMask |
Large holdings, high-value signing |
More secure, less convenient for daily micro-transactions |
But remember: no matter which form you use, the seed phrase is the ultimate key. Guard it accordingly.
Ready to add BSC now? Start with /install-metamask-extension or /install-metamask-mobile-app, then follow the desktop or mobile step-by-step above.
