Thousands of users hit this exact roadblock because MetaMask does not include Fantom Opera in its default network list. Furthermore, the recent rebranding from “Fantom” to “Sonic” has left many users unsure if the network details they find online are still valid.

This guide uses official network parameters verified for the 2025 Sonic migration context. Whether you are on desktop or mobile, you can get set up in 2-3 minutes.

We will cover two methods: an automatic setup (recommended for speed) and a manual setup (for control), plus exactly how the Sonic migration affects your wallet.

Fantom (Opera) is EVM-compatible, so MetaMask can use it, you just need to add the network once, then switch to it whenever you use Fantom-based dApps. Fantom’s official docs provide the exact MetaMask settings for both desktop and mobile.

If you want the quick answer, use these Fantom Opera (mainnet) details in MetaMask:

• Network Name: Opera
• RPC URL: https://rpcapi.fantom.network
• Chain ID: 250
• Currency Symbol: FTM
• Block Explorer URL: https://ftmscan.com/
• Optional alternate RPCs (if the primary is slow): Fantom maintains a list of public endpoints; use one at a time. Commonly-used alternatives include https://rpc.ftm.tools (often referenced in older guides), but always prefer an official list when possible.

Last verified: February 4, 2026.

 

Method 1: Add Fantom to MetaMask Automatically (Recommended, Chrome/Brave/Firefox/Edge) #

Time Estimate: 2 minutes

1. Open the MetaMask extension.

   

2. Click the network selector at the top (where it says something like “Ethereum Mainnet”).

   

3. Choose Add network (or Add a custom network).

   

4. Select the option to add a network manually.

5. Fill in the fields using the table above.

   

6. Click Save.

7. Select the network dropdown again and switch to Fantom Opera.

Method 2: Add Fantom to MetaMask automatically with FTMScan #

Time Estimate: 30 Seconds

Method 3: Add Fantom to MetaMask on mobile (iOS/Android) #

Mobile is nearly the same idea—just a different menu layout.

1. Open MetaMask on your phone.

2. Tap the network name at the top (it often shows “Ethereum Mainnet”).

3. Choose Add network → Add network manually.

4. Copy/paste the Fantom Opera settings from the table above.

5. Tap Save.

6. Switch to Fantom Opera from the network list.

Copy/paste trick (mobile): Open this article on a second device (or email it to yourself) so you can copy the RPC URL cleanly—typing it by hand is where most errors happen.

Understanding the Fantom-to-Sonic migration (why this can feel confusing) #

If you’ve seen people say “Fantom is Sonic now,” here’s the practical version:

• In August 2024, Sonic Labs announced plans to transition from the Fantom brand/token toward Sonic.

• Many exchanges later completed migrations where FTM balances were converted to S at a 1:1 rate, and some platforms delisted FTM pairs.

• Fantom’s own documentation notes that Opera migrated to Sonic in December 2024, and points users to migration instructions depending on what they hold.

So what does this mean for this guide?
You’re adding the Fantom Opera network (Chain ID 250) to MetaMask so you can interact with apps and assets that still live on that network. If you’re specifically trying to use Sonic (the newer chain), you may need different network settings, so always match the chain to the dApp you’re trying to use.

Conclusion

Connecting MetaMask to Fantom Opera/Sonic’s blockchain is mostly a one-time setup: add the network (automatic or manual), switch to it, and confirm you’re on the right explorer.

After that, using Fantom dApps feels just like using Ethereum, just with different network settings.

Not financial advice: always verify URLs, confirm network details, and double-check whether a dApp is on Fantom Opera or Sonic before you approve transactions.

FAQs

Does MetaMask support Fantom?

Yes. Fantom Opera is EVM-compatible, so MetaMask can connect to it by adding a custom network (either automatically via a trusted prompt or manually via RPC + Chain ID).

What is the Chain ID for Fantom Opera?

250 (hex 0xfa).

What RPC URL should I use for Fantom?

Start with the official RPC URL: https://rpcapi.fantom.network. If it’s slow or temporarily unavailable, use a known-good public endpoint from Fantom’s published list.

I added Fantom on my laptop—why isn’t it on my phone?

Custom networks do not automatically sync between MetaMask extension and mobile. Add the network separately on each device.

Is it safe to use Chainlist to add Fantom?

It can be convenient, but MetaMask explicitly notes they don’t maintain Chainlist’s network info—so you should verify the details before approving anything.
(And always confirm you’re on the correct domain: chainlist.org.)

My Fantom balance is zero after switching networks—did I lose my funds?

Usually, no. You’re probably just on the wrong network. The same wallet address can hold different balances on different chains. Switch back to the chain where your funds actually live (e.g., Ethereum vs Fantom Opera), and confirm via the correct explorer.

A dApp says “wrong network” even though I’m on Fantom. Why?

Common reasons:

• The dApp is on Sonic, not Fantom Opera (or vice versa)

• You’re on Fantom testnet instead of mainnet

• Your RPC endpoint is failing—try another official public endpoint

Can I remove Fantom from MetaMask later?

Yes. MetaMask lets you delete custom networks/RPC endpoints from settings. (It doesn’t delete your funds; it only removes the connection settings.)