Independent review. This site is not the official website and is not affiliated with, endorsed by, or operated by the wallet vendor reviewed here. Never enter your seed phrase or private keys on any third-party site.

Add Fantom to MetaMask — RPC & Chain ID

Try Tangem secure wallet →

Add Fantom to MetaMask — RPC & Chain ID


Quick overview

This guide shows how to connect Fantom to MetaMask by adding the network manually (RPC URL, Chain ID, currency symbol and block explorer). If you prefer, there are also automated ways to add networks in some wallets, but here I walk through the manual, explicit method so you can verify each value before you save it. Short and practical. I've added Fantom to MetaMask many times while testing DeFi flows; I’ll share what to watch for.

Why add Fantom to MetaMask?

Fantom is an EVM-compatible chain used by a number of DeFi protocols and dApps. Adding Fantom to a software wallet like MetaMask lets you:

  • Send and receive native FTM and Fantom-based tokens.
  • Connect directly to Fantom dApps (instead of always using Ethereum mainnet or L2s).
  • Use Fantom-focused bridges, swaps, and staking interfaces.

Why not just use a bridge UI in a browser? Because switching networks in MetaMask is faster for daily swaps and for approving contracts (one fewer step). And yes — there are trade-offs: a hot wallet is convenient but has different security trade-offs compared with a hardware wallet.

Network settings (what to enter)

Below are the core fields MetaMask asks for when you add Fantom. Copy them exactly into the Add Network form in MetaMask.

Try Tangem secure wallet →
Field Typical value
Network Name Fantom Opera
New RPC URL https://rpcapi.fantom.network (public RPC)
Chain ID 250
Currency Symbol FTM
Block Explorer URL https://ftmscan.com

(Image placeholder: screenshot of MetaMask "Add Network" screen)
Alt text: MetaMask add custom network form (placeholder)

A few notes: Chain ID is how wallets and dApps identify the blockchain (250 identifies Fantom mainnet). The RPC URL points your MetaMask to an RPC node that serves chain data. If a public RPC is slow, try an alternative public endpoint or a paid provider — or run your own node if you need maximum privacy and reliability.

Step-by-step: Desktop (MetaMask extension)

  1. Open your MetaMask extension and unlock your wallet.
  2. Click the network dropdown at the top (it usually says "Ethereum Mainnet").
  3. Choose "Add Network" or "Add a network manually" (depending on your MetaMask version).
  4. Paste the values from the table above into the form and click Save.
  5. Switch to Fantom Opera in the network dropdown. Your account address is the same across chains (EVM-compatible).

If you need a refresher on installing the extension first, see the install guide: Install MetaMask extension.

Step-by-step: Mobile (MetaMask mobile app)

  1. Open the MetaMask mobile app and unlock.
  2. Tap the menu (three lines), then Settings > Networks > Add Network.
  3. Enter the RPC, Chain ID (250), symbol and explorer URL.
  4. Save and switch to Fantom Opera.

To connect Fantom from mobile dApps, the in-app browser will use the active network. If you prefer a direct install, read the mobile installation steps here: Install MetaMask mobile app.

But if a dApp offers an automatic "Add network" button, double-check the values before accepting.

Adding tokens and NFTs on Fantom

MetaMask won’t automatically show every token on Fantom. To add a token:

  • Find the token contract on a block explorer (e.g., ftmscan.com).
  • In MetaMask, open the account on Fantom and choose "Import tokens." Paste the contract address, and the token symbol and decimals usually populate automatically.

For NFTs, the wallet will show ERC-721 and ERC-1155 assets if the dApp metadata is available. Spam NFTs can clutter your list — hide them or use specialized NFT managers. For token management workflows and approval cleanup, see token-approvals-revoke.

Connecting Fantom dApps, swaps and staking

Most Fantom dApps expect an injected provider (MetaMask) or WalletConnect. After switching MetaMask to Fantom Opera (Chain ID 250), the dApp should detect the network. If it asks to switch, confirm in MetaMask.

Built-in swap features in wallets vary. If you plan to swap often on Fantom, check the wallet’s aggregator routing and slippage controls before hitting Confirm. For staking, some apps let you stake native FTM directly or use liquid staking; always confirm validator reputations and smart contract audits (link to a staking guide: staking-via-metamask).

Security notes and best practices

  • Verify RPC sources. A malicious RPC could misreport balances or serve misleading data. I prefer official or well-known public RPCs, and sometimes a paid provider for frequent testing.
  • Keep your seed phrase offline and backed up. If you lose your phone, restore with your seed phrase on another device (see backup-recovery-seed and lost-phone-recovery).
  • Check smart contract approvals before confirming. I once approved an unlimited allowance by mistake; I learned the hard way to limit approvals and to use approval revocation tools.
  • Consider using a hardware wallet for larger balances. MetaMask supports hardware integrations (see hardware-wallets-overview).

And always double-check contract addresses and UX prompts. Phishing dApps and fake RPC endpoints are real risks.

Troubleshooting common issues

  • "RPC endpoint not responding": try an alternate RPC URL and restart MetaMask.
  • Balances not showing: make sure you switched to Fantom Opera and added the specific token contract if needed.
  • Transactions stuck or low priority: raise gas fees (priority fee) or use the speed up/cancel option in MetaMask.
  • Sent tokens to the wrong network: this happens. It’s recoverable only if you control the receiving address private keys on the destination chain; otherwise funds may be lost.

If your issue is persistent, check the general network troubleshooting page: troubleshooting-dapp-connections and troubleshooting-connect.

Who this guide is for (and who should look elsewhere)

Who this guide is for:

  • MetaMask users who want to interact with Fantom dApps, swap tokens, or stake FTM.
  • Beginners who prefer a step-by-step manual setup.

Who should look elsewhere:

  • Users who keep all funds on hardware wallets and don’t use software wallets for Web3 interactions (see hardware wallet guides linked above).
  • Developers wanting programmatic RPC access — see developer docs and developers-connect.

FAQ

Q: Is it safe to keep crypto in a hot wallet?
A: Hot wallets balance convenience and security. For day-to-day DeFi interactions they’re practical, but for larger sums consider using a hardware wallet or multisig. See security-best-practices.

Q: How do I revoke token approvals on Fantom?
A: Use a reputable approval-revoke tool or a wallet feature that lists allowances. Revoke unlimited allowances and re-approve with a limited amount when needed. See token-approvals-revoke.

Q: What happens if I lose my phone?
A: If you have your seed phrase backed up, you can restore the wallet on another device. Without the seed phrase, recovery is unlikely. Read backup-recovery-seed and lost-phone-recovery.

Conclusion & next steps

Connecting Fantom to MetaMask is a small setup step that opens access to Fantom-based DeFi and dApps. Add the network by entering the RPC URL and Chain ID (250), then import any tokens you use. I recommend testing with a small transfer first to confirm everything works as expected. In my experience, that extra test transfer saves headaches.

Ready to add more networks? Check other guides for Add Polygon and Add BSC network, or follow the full MetaMask setup series: create-restore-wallet and install-setup.

If you want hands-on troubleshooting or a screenshot walkthrough, see the troubleshooting and installation sections linked above. But first — try adding Fantom manually so you know exactly what each field means.

Try Tangem secure wallet →