If you want to send FTM to MetaMask, the address is the easy part. The network is the part that decides whether your funds arrive cleanly, show up on the wrong chain, or sit in a support ticket for weeks.
MetaMask can use Fantom because Fantom Opera is EVM-compatible. That means your MetaMask account uses the same 0x... address format you see on Ethereum, BNB Smart Chain, Polygon, Avalanche C-Chain, and many other EVM networks.
But the same address does not mean the same network.
FTM can exist as:
- native FTM on Fantom Opera
- wrapped or bridged FTM on Ethereum
- wrapped FTM on BNB Smart Chain
- exchange balances that may or may not support native Fantom withdrawals
- migrated or related assets under Sonic branding, depending on the platform
For most users, the correct destination is Fantom Opera, chain ID 250. Add that network to MetaMask first, then withdraw or transfer FTM using the Fantom network from the sending platform.
What has to be true before FTM can arrive in MetaMask?
Three things need to match:
- Your wallet address
- The destination network
- The asset type
If one of these is wrong, the transfer may still be recorded on-chain, but not where you expected.
MetaMask address: same account, different chains
Your MetaMask account address is usually the same across EVM networks. For example, the same address can receive assets on Ethereum, Fantom Opera, Arbitrum, Base, BNB Smart Chain, and Polygon.
That is convenient, but it causes a common mistake.
If you copy your MetaMask address while viewing Ethereum and then withdraw native FTM over Fantom Opera, the FTM can still arrive at that same address on Fantom. You just need to switch MetaMask to Fantom Opera to see it.
If you withdraw ERC-20 FTM over Ethereum, however, it arrives on Ethereum — not Fantom.
Same address. Different ledger.
Network: the part exchanges and bridges care about
On centralized exchanges, the withdrawal screen usually asks for a network. This choice matters more than the copied address.
| Withdrawal network shown by sender | Where the funds arrive | Gas token needed later | Correct for native FTM in MetaMask? | Typical issue |
|---|---|---|---|---|
| Fantom / Fantom Opera / FTM | Fantom Opera | FTM | Yes | Usually correct |
| Ethereum / ERC-20 | Ethereum mainnet | ETH | No, unless you wanted ERC-20 FTM | High gas, not usable as native Fantom gas |
| BNB Smart Chain / BEP-20 | BNB Smart Chain | BNB | No, unless you wanted wrapped FTM on BSC | Asset appears on BSC, not Fantom |
| Sonic / S | Sonic network | S | Not the same as Fantom Opera FTM | Confusion after Fantom-to-Sonic migration support |
| Polygon / Avalanche / Arbitrum | That selected chain | MATIC / AVAX / ETH | No | Wrapped or bridged representation, not native FTM |
The safest rule: if your goal is native FTM in MetaMask on Fantom, the withdrawal network must say Fantom, Fantom Opera, or FTM network.
Do not assume “FTM” as an asset name automatically means the Fantom network is being used.
Asset type: native FTM is not an ERC-20 token on Fantom
Native FTM on Fantom Opera is the gas coin. It behaves like ETH on Ethereum or BNB on BNB Smart Chain.
That means:
- you do not need a token contract to see native FTM
- it appears as the primary balance after switching to Fantom Opera
- it is used to pay transaction fees on Fantom
- you need a small amount of it to swap, bridge, stake, or send tokens on Fantom
If someone tells you to “add the FTM token contract” to see native FTM on Fantom, they are probably confusing native FTM with a wrapped token.
How do you add Fantom Opera to MetaMask?
MetaMask does not always show Fantom Opera by default. You can add it manually as a custom network.
Use the details below, but always verify network settings against a trusted source if MetaMask, Fantom documentation, or your exchange displays updated information.
| Field | Fantom Opera setting |
|---|---|
| Network name | Fantom Opera |
| RPC URL | https://rpc.ftm.tools/ |
| Chain ID | 250 |
| Currency symbol | FTM |
| Block explorer | https://ftmscan.com/ |
Manual setup in MetaMask
- Open MetaMask.
- Click the network selector at the top.
- Choose Add network.
- Select Add a network manually if Fantom is not listed.
- Enter the Fantom Opera details.
- Save the network.
- Switch MetaMask to Fantom Opera.
- Confirm that the native currency symbol is FTM.
Once the network is added, your MetaMask account can receive native FTM on Fantom Opera.
If the balance does not load
A zero balance does not always mean funds are missing.
Check these first:
- Are you on Fantom Opera, not Ethereum?
- Did the sender use the Fantom network, not ERC-20 or BEP-20?
- Is the transaction confirmed on FTMScan?
- Is the RPC endpoint responding?
- Are you viewing the correct MetaMask account?
Public RPC endpoints can become slow or temporarily unreliable. If FTMScan shows the funds at your address but MetaMask does not update, the issue is usually display or RPC-related, not a failed transfer.
How do you send FTM from an exchange to MetaMask safely?
The most common path is a centralized exchange withdrawal: buy FTM, copy your MetaMask address, select the Fantom network, and withdraw.
That sounds simple. The risk is that exchanges often list several networks for the same asset.
Step-by-step exchange withdrawal checklist
Before submitting the withdrawal:
- Add Fantom Opera to MetaMask.
- Switch MetaMask to Fantom Opera.
- Copy your MetaMask
0x...address. - On the exchange, select FTM as the asset.
- Choose the withdrawal network as Fantom, Fantom Opera, or equivalent.
- Confirm the network fee and minimum withdrawal.
- Send a small test amount if the transfer is large or if it is your first time.
- Wait for confirmations.
- Check the transaction on FTMScan if the exchange provides a hash.
For a first transfer, a test withdrawal is not paranoia. It is cheap insurance.
If you plan to send $2,000 worth of FTM, sending $5–$20 first can confirm that the exchange network label, MetaMask setup, and destination address are all correct.
Exchange withdrawal pros and cons
| Method | Pros | Cons | Best for |
|---|---|---|---|
| Centralized exchange withdrawal to Fantom | Simple, often cheaper than Ethereum, no bridge complexity | Network labels vary; withdrawals can be paused; custody risk before withdrawal | Users buying FTM on an exchange |
| Wallet-to-wallet transfer on Fantom | Fast, direct, low complexity | Requires sender to already hold native FTM on Fantom | Moving FTM between self-custody wallets |
| Bridge from another chain | Useful if funds are already on Ethereum, BSC, Arbitrum, etc. | Bridge risk, route complexity, may need gas on source chain | Users moving value cross-chain |
| Cross-chain swap route | Can convert one asset on one chain into FTM on Fantom | Price impact, bridge fees, route risk, destination gas considerations | Users who do not already hold FTM |
Real example: withdrawing 100 FTM from an exchange
Suppose you buy 100 FTM on an exchange and want it in MetaMask.
The exchange asks for:
- address
- network
- amount
Your MetaMask address is:
0x1234...abcd
You select Fantom as the withdrawal network.
What happens:
- The exchange sends native FTM on Fantom Opera.
- The transaction appears on FTMScan.
- Your MetaMask balance updates after switching to Fantom Opera.
- You now have FTM available for gas and transfers on Fantom.
If you accidentally selected Ethereum instead, the exchange would send ERC-20 FTM to the same 0x1234...abcd address on Ethereum. You would need ETH gas to move or swap it, and it would not function as Fantom gas.
How do you send FTM from another wallet to MetaMask?
A wallet-to-wallet transfer is straightforward if the sending wallet already holds native FTM on Fantom Opera.
The sending wallet must be connected to Fantom Opera, not Ethereum or another chain.
Wallet-to-wallet checklist
Before sending:
- Confirm the sender wallet is on Fantom Opera.
- Confirm the balance is native FTM, not wrapped FTM on another network.
- Copy your MetaMask address.
- Paste the address into the sending wallet.
- Leave enough FTM in the sender wallet for gas.
- Send a small test transaction if the amount is meaningful.
- Verify the transaction on FTMScan.
Real example: moving FTM from a hardware wallet account
You have 500 FTM in a hardware wallet connected to MetaMask, and you want to move 100 FTM to a new MetaMask hot wallet.
Both addresses are EVM addresses.
If the hardware wallet account is on Fantom Opera, sending 100 FTM to the new MetaMask address transfers native FTM on Fantom. The recipient sees it after switching to Fantom Opera.
If the hardware wallet account is on Ethereum and holds ERC-20 FTM, a normal transfer sends ERC-20 FTM on Ethereum. It does not bridge the asset to Fantom.
A send transaction is not a bridge.
What if your FTM is on Ethereum, BNB Smart Chain, or another network?
If your FTM is not already on Fantom Opera, you have two choices:
- Send it to an exchange that supports deposits on that network, then withdraw native FTM to Fantom.
- Use a bridge or cross-chain swap route to move value to Fantom.
The right option depends on fees, size, risk tolerance, and available liquidity.
Comparing exchange withdrawals, bridges, and cross-chain swaps
| Route | Fees | Liquidity | Execution quality | Gas cost | Speed | Security trade-off | Ease of use |
|---|---|---|---|---|---|---|---|
| Exchange deposit then Fantom withdrawal | Exchange fees + withdrawal fee | Usually strong for major assets | Fixed by exchange order book and withdrawal terms | Source-chain deposit gas may apply | Medium; depends on deposit/withdrawal processing | Custodial risk while funds are on exchange | Easy if networks are supported |
| Direct bridge | Bridge fee + source/destination gas | Depends on bridge liquidity | Good for supported assets, weaker for thin routes | Can be high on Ethereum | Fast to medium | Smart contract and bridge risk | Moderate |
| Cross-chain swap aggregator | Route fee + swap spread + bridge/gas costs | Depends on connected liquidity sources | Can be better if routing across multiple DEXs/bridges | Varies by route | Fast to medium | Aggregator route inherits bridge/DEX risks | Often easier than manual bridging |
| Manual multi-step route | Multiple swap and bridge fees | User controls venue selection | Can be optimized by experienced users | Often inefficient for small transfers | Slow | More chances for user error | Harder |
Platforms such as switchfi.app can compare multiple liquidity and bridge routes before selecting an execution path, but users should still review the source chain, destination chain, received asset, estimated fees, and slippage before signing.
Real example: you have $100 USDT on BNB Smart Chain and want FTM in MetaMask
You do not actually have FTM yet. You have USDT on BNB Smart Chain.
A normal transfer to your MetaMask address keeps the USDT on BNB Smart Chain. It does not become FTM on Fantom.
A workable path could be:
- Use a cross-chain swap or bridge route from BNB Smart Chain to Fantom.
- Swap USDT or another bridged asset into FTM on Fantom.
- Make sure the route delivers native FTM or leaves you with enough FTM for gas.
The key problem for small transfers is fee drag. If the route costs $4–$8 in bridge fees, gas, and slippage, that is material on a $100 transfer.
For small amounts, an exchange withdrawal may be cheaper and simpler if the exchange supports both the deposit network and native Fantom withdrawals.
Real example: you have $10,000 worth of FTM exposure on Ethereum
With larger transfers, execution quality matters more.
If you hold ERC-20 FTM on Ethereum and want native FTM on Fantom, Ethereum gas might not be your biggest cost. Slippage, bridge liquidity, route reliability, and withdrawal limits can matter more.
For a $10,000 transfer, compare:
- exchange deposit and withdrawal fees
- bridge liquidity
- expected received amount
- slippage tolerance
- whether the route delivers native FTM or a wrapped token
- how long finality and confirmations take
- counterparty or smart contract risk
A route that is “cheapest” by displayed fee can still be worse if it has poor liquidity or large price impact.
How can you verify that the transfer worked?
Do not rely only on MetaMask’s displayed balance.
Use the block explorer.
For Fantom Opera, that means FTMScan.
How to check your transaction on FTMScan
You can verify by searching:
- your MetaMask address
- the transaction hash
- the sender address
- the contract address, if dealing with a token
For native FTM transfers, the account page should show the FTM balance and the transaction under native transfers.
If the exchange says the withdrawal is complete but you see nothing on FTMScan, one of these is likely true:
- the exchange has not actually broadcast the transaction yet
- the transaction hash is for another network
- the selected withdrawal network was not Fantom
- the exchange is showing internal status rather than on-chain status
What confirmations mean
A transaction can be:
- submitted by the sender
- pending in the network
- confirmed on-chain
- indexed by a block explorer
- displayed by MetaMask
Those are separate events.
If FTMScan shows the transfer confirmed to your address, the funds are on Fantom. If MetaMask does not show them, troubleshoot MetaMask, RPC, or account selection.
If FTMScan does not show the transfer, ask the sender or exchange for the exact network and transaction hash.
What should you do if FTM was sent on the wrong network?
The answer depends on where it was sent and who controls the receiving address.
If you sent to your own MetaMask address
This is often recoverable because MetaMask can access many EVM networks with the same private key.
| Mistake | What likely happened | Recovery path |
|---|---|---|
| Sent ERC-20 FTM to MetaMask | Funds arrived on Ethereum | Switch to Ethereum, add the token if needed, use ETH for gas |
| Sent BEP-20 FTM to MetaMask | Funds arrived on BNB Smart Chain | Add/switch to BNB Smart Chain, add token if needed, use BNB for gas |
| Sent native FTM but cannot see it | Funds may be on Fantom but MetaMask is on another network | Add/switch to Fantom Opera and check FTMScan |
| Sent to wrong MetaMask account | Funds are at another address you control | Switch accounts or import the correct wallet |
| Used a non-EVM network | Address compatibility may not apply | Recovery depends on the network and sender support |
If the funds went to an EVM network controlled by your MetaMask seed phrase or hardware wallet, they may not be lost. You need to view the correct network and have that network’s gas token to move them.
If you sent to an exchange using the wrong network
This is much harder.
If you deposited FTM to an exchange address on a network the exchange does not support for that asset, the exchange controls the private keys. You cannot recover it yourself.
Possible outcomes:
- the exchange automatically credits it if the network is supported
- support manually recovers it for a fee
- recovery is delayed for weeks
- recovery is refused due to unsupported network policy
This is why exchange deposit pages show warnings. They are not just legal boilerplate.
If the receiving platform says “deposit only via Fantom network,” do not send ERC-20 or BEP-20 FTM to that address unless the platform explicitly supports it.
If you sent to a smart contract address
Sending native FTM or tokens to a contract address can be unrecoverable unless the contract has a withdrawal function controlled by someone.
Examples of risky recipients:
- token contract addresses
- bridge contract addresses copied manually
- DEX router addresses
- staking contract addresses outside the official interface
- old deposit addresses from closed services
A wallet address and a contract address can look similar. Both can start with 0x.
Before sending a large amount, verify that the destination is a wallet or a deposit address provided by the platform’s official interface.
What fees should you expect when sending FTM?
Fantom transactions are usually inexpensive compared with Ethereum mainnet, but the full cost depends on the route.
Fee types to understand
| Fee type | Applies when | Paid in | Who controls it |
|---|---|---|---|
| Fantom gas fee | Sending or using apps on Fantom | FTM | Network conditions |
| Exchange withdrawal fee | Withdrawing from a centralized exchange | Usually deducted from withdrawal asset | Exchange |
| Source-chain gas | Bridging or swapping from another chain | ETH, BNB, AVAX, etc. | Source network |
| Bridge fee | Cross-chain transfer | Varies | Bridge or route |
| Swap fee | Swapping assets | Input/output token | DEX or aggregator route |
| Slippage / price impact | Swapping with limited liquidity | Embedded in execution price | Market liquidity |
Keep some FTM after receiving
Do not send your entire FTM balance away unless you are done using Fantom.
You need FTM for:
- swaps
- token transfers
- approvals
- bridging
- staking actions
- NFT transactions
- contract interactions
For light use, keeping a small buffer may be enough. Active DeFi users should keep more. Running out of gas is one of the most common reasons users get “stuck” after successfully receiving funds.
Which transfer method should you choose?
There is no universally best route. Use the route that matches where your funds are now.
Decision framework
| Your starting point | Best practical route | Why |
|---|---|---|
| You bought FTM on an exchange that supports Fantom withdrawals | Withdraw directly to MetaMask over Fantom | Simple and usually clean |
| You already hold native FTM in another Fantom wallet | Send wallet-to-wallet on Fantom | Direct and low complexity |
| You hold ERC-20 FTM on Ethereum | Compare bridge vs exchange route | Ethereum gas and liquidity can change the best choice |
| You hold USDT/USDC/ETH on another chain | Use exchange route or cross-chain swap | You need both chain movement and asset conversion |
| You are transferring a large amount | Test first, compare routes, verify liquidity | Mistakes and price impact become expensive |
| You are transferring a small amount | Avoid multi-step routes with high fixed fees | Fees can consume too much of the transfer |
Expert tip: optimize for certainty before cost
A route that saves $1 but introduces bridge risk, unsupported assets, or unclear routing is usually not worth it for a first-time transfer.
For beginners, the best route is often:
- Buy FTM on an exchange.
- Withdraw using the Fantom network.
- Confirm on FTMScan.
- Use MetaMask on Fantom Opera.
For advanced users, bridges and aggregators can make sense when they improve execution quality or avoid centralized custody. But they require more careful review.
What are the most common mistakes when sending FTM to MetaMask?
Most failed or confusing FTM transfers come from network assumptions.
Mistake 1: Choosing ERC-20 because MetaMask is an Ethereum wallet
MetaMask started as an Ethereum wallet, but it supports many EVM networks.
If you want native FTM on Fantom, do not choose ERC-20 unless you specifically want FTM on Ethereum.
ERC-20 FTM will not pay gas on Fantom.
Mistake 2: Thinking the address determines the network
The address does not route the transfer. The sending network does.
Your 0x... address can receive assets on many chains. The withdrawal network decides which chain records the transaction.
Mistake 3: Not adding Fantom before withdrawing
You can technically receive FTM before adding Fantom Opera to MetaMask, but adding the network first reduces anxiety and makes verification easier.
If you withdraw first and only see a zero balance on Ethereum, you may think the transfer failed even though it arrived correctly on Fantom.
Mistake 4: Sending the full balance and leaving no gas
If you receive FTM and immediately swap or bridge all of it, you may not have enough left for the next transaction.
Keep a gas buffer.
Mistake 5: Trusting token symbols without checking networks
Symbols are not unique.
“FTM” on one platform may represent native FTM. On another, it may represent a wrapped token. On another, Fantom-related assets may appear alongside Sonic migration options.
Read the network label, not just the ticker.
Mistake 6: Using an old deposit address without checking support
Exchanges change supported networks, pause withdrawals, update wallet infrastructure, or migrate assets.
Before sending to an exchange, generate a fresh deposit address from the current deposit page and confirm the network is supported.
Mistake 7: Ignoring withdrawal pauses
If an exchange has paused Fantom withdrawals, do not try to force the transfer through another network unless you understand the consequences.
Withdrawing ERC-20 FTM because Fantom withdrawals are unavailable may leave you with a more expensive and less useful asset for your intended purpose.
What should you check before pressing send?
Use this as a final pre-flight check.
FTM to MetaMask pre-send checklist
- MetaMask is installed and backed up securely.
- You are using the correct MetaMask account.
- Fantom Opera is added to MetaMask.
- Chain ID is
250. - Native currency symbol is
FTM. - The sending platform supports withdrawals on Fantom Opera.
- The selected withdrawal network is Fantom / Fantom Opera / FTM.
- The destination address is your MetaMask
0x...address. - You checked the minimum withdrawal and fee.
- You are not confusing Fantom Opera with Ethereum, BNB Smart Chain, or Sonic.
- You sent a test transaction if the amount is large.
- You know how to check the transfer on FTMScan.
For larger transfers, add two more steps:
- Confirm the destination address using a saved address book or hardware wallet screen.
- Wait for the test transfer to arrive before sending the rest.
FAQ
What network do I use to send FTM to MetaMask?
Use Fantom Opera if you want native FTM in MetaMask. The key network details are chain ID 250, currency symbol FTM, and block explorer FTMScan.
If an exchange asks for the withdrawal network, choose Fantom, Fantom Opera, or the platform’s equivalent label for native FTM withdrawals.
Is Fantom Opera the same as Ethereum?
No. Fantom Opera is EVM-compatible, so it uses Ethereum-style addresses and works with MetaMask, but it is a separate blockchain.
A transaction on Ethereum does not appear on Fantom unless you use a bridge or cross-chain route.
Can I send FTM to my MetaMask Ethereum address?
Yes, if by “Ethereum address” you mean your MetaMask 0x... account address. The same address can receive native FTM on Fantom Opera.
But the withdrawal network must be Fantom. If you choose Ethereum/ERC-20, the FTM arrives on Ethereum instead.
Why is my FTM not showing in MetaMask?
The most common reasons are:
- MetaMask is on the wrong network.
- Fantom Opera has not been added.
- The exchange sent FTM on Ethereum, BNB Smart Chain, or another network.
- The transaction has not been broadcast yet.
- MetaMask RPC data is lagging.
- You are viewing the wrong account.
Check your address or transaction hash on FTMScan. If FTMScan shows the funds, the issue is usually MetaMask display or network selection.
Do I need to add a token contract for FTM on Fantom?
No for native FTM. Native FTM is the gas coin on Fantom Opera and should appear as the main balance after adding the network.
You may need token contracts for other Fantom tokens, but not for native FTM.
What happens if I send ERC-20 FTM to MetaMask?
It arrives on Ethereum at your MetaMask address, assuming the transaction is valid. You will need to switch MetaMask to Ethereum and may need to add the ERC-20 token to view it.
To move or swap it, you need ETH for gas.
It will not become native FTM on Fantom automatically.
What happens if I send BEP-20 FTM to MetaMask?
It arrives on BNB Smart Chain, not Fantom. Add BNB Smart Chain to MetaMask, switch networks, and add the relevant token if it does not appear.
You will need BNB for gas to move or swap it.
Can I recover FTM sent on the wrong network?
If it was sent to your own MetaMask address on another EVM chain, usually yes. Add the correct network and use that chain’s gas token.
If it was sent to an exchange on an unsupported network, only the exchange can help. Recovery is not guaranteed.
Do I need FTM for gas on Fantom?
Yes. FTM is the native gas token of Fantom Opera. You need it to send tokens, swap, approve contracts, bridge, or interact with apps on Fantom.
Can I send FTM from Binance, OKX, KuCoin, or another exchange to MetaMask?
Usually, if the exchange supports native Fantom withdrawals at that time. Support can change, and withdrawals can be paused.
Check the exchange withdrawal page and select the Fantom network. Do not rely on old tutorials or screenshots.
Is Sonic the same as Fantom Opera?
No. Sonic-related assets and networks can appear alongside Fantom-related options on some platforms due to ecosystem migration and rebranding. Do not assume a Sonic withdrawal is the same as a Fantom Opera withdrawal.
If your goal is native FTM on Fantom Opera, use the Fantom Opera network details and chain ID 250.
Is it safe to add Fantom to MetaMask manually?
Yes, if you use correct network details from trusted sources. The main risk is entering a malicious or unreliable RPC URL.
A bad RPC cannot directly take funds from your wallet by itself, but it can mislead you about balances or transactions. Always verify important transfers on FTMScan.
Should I send a test transaction?
For meaningful amounts, yes.
A small test transfer confirms:
- the destination address is correct
- the withdrawal network is correct
- MetaMask is set up properly
- the exchange is processing withdrawals normally
The extra fee is usually worth it for larger transfers.
Key takeaways
- To send FTM to MetaMask as native Fantom funds, use Fantom Opera, not Ethereum/ERC-20 or BNB Smart Chain/BEP-20.
- Fantom Opera’s chain ID is
250, and the native currency symbol isFTM. - Your MetaMask address can be the same across many EVM networks, but the selected sending network determines where funds arrive.
- Native FTM does not require a token contract in MetaMask.
- FTMScan is the best place to verify Fantom Opera transactions.
- Wrong-network transfers to your own MetaMask address are often recoverable; wrong-network deposits to exchanges may not be.
- Always keep some FTM for gas after receiving funds.
- For larger transfers, send a small test transaction before moving the full amount.
Final verdict
Sending FTM to MetaMask is simple only after the network question is settled.
If you want native FTM for Fantom apps, gas, swaps, or transfers, add Fantom Opera to MetaMask and withdraw using the Fantom network from the sender. The copied address is not enough; the withdrawal network must match the chain you intend to use.
For most users, the safest workflow is:
- Add Fantom Opera to MetaMask.
- Confirm chain ID
250. - Copy your MetaMask address.
- Select Fantom as the withdrawal network.
- Send a small test amount.
- Verify on FTMScan.
- Send the rest.
That one network check prevents most failed, hidden, or stranded FTM transfers.
