How to Add Sonic to MetaMask in 2026 – Network Setup Guide

If you want to explore the Sonic ecosystem from your MetaMask wallet, the first thing you need to do is add the Sonic network to MetaMask. Sonic is an EVM-compatible Layer 1 blockchain, so MetaMask can connect to it the same way it connects to Ethereum, Arbitrum, or Polygon — but only if you enter the correct network details.

In this guide, you will learn what Sonic is, the verified network parameters you need, how to add Sonic to MetaMask step by step, how to fund your wallet with S tokens, how to send and receive on Sonic, and how to spot the fake-network scams that target new chains.

id=”what-is-sonic”>What Is Sonic?

Sonic is an EVM-compatible Layer 1 blockchain built by Sonic Labs, the team that previously ran the Fantom network. Sonic launched its mainnet in December 2024 as the successor to Fantom, and its native token is S, which replaced the old FTM token at a 1:1 ratio.

Because Sonic is EVM-compatible, it runs the same kind of smart contracts as Ethereum. That means MetaMask, which is built around the EVM, can connect to Sonic once you give it the right network parameters. You do not need a special wallet — the MetaMask you already use works fine.

Here is the key thing to understand before you continue: MetaMask does not “know” about Sonic out of the box. The wallet only stores network connections for a handful of popular chains. For every other EVM chain, including Sonic, you add the network manually. The process takes a couple of minutes and is fully reversible — if you add a network and later change your mind, you can remove it without touching your funds or your seed phrase.

Before You Start: What You Need

Adding a network to MetaMask requires nothing except the wallet itself and a few minutes of your time. But a short checklist will save you from mistakes.

• MetaMask installed. Use the official MetaMask browser extension or the official MetaMask mobile app. If you have not installed MetaMask from its official source, do that first — a wallet downloaded from a fake site is one of the most common ways beginners lose funds.
• A funded account or a plan to fund one. Adding the network is free. Sending transactions on Sonic, however, requires S tokens to pay for gas. You can add the network first and fund it later.
• The verified Sonic network details. I verified the following parameters through multiple independent technical sources:
  • Network name: Sonic
  • New RPC URL: https://rpc.soniclabs.com
  • Chain ID: 146
  • Currency symbol: S
  • Block explorer URL: https://sonicscan.org
• Your seed phrase nowhere near this process. Adding a network never requires your seed phrase or private key. If any site asks for either while “adding a network,” close it immediately.

One caveat: RPC endpoints can change over time, and third-party RPC providers come and go. The parameters above are the widely documented Sonic Labs values as of 2026. Before pasting anything, it is good practice to double-check the current values on the official Sonic Labs documentation — type the address yourself rather than clicking a link in a search ad or a social media post.

How to Add Sonic to MetaMask in 4 Steps

Step 1: Open the network selector

Click the MetaMask extension icon to open your wallet, then click the network dropdown at the top-left of the wallet window (it usually says “Ethereum Mainnet” or whatever network you last used). This opens a menu of your saved networks.

Step 2: Click “Add network”

At the bottom of the network list, click “Add network”. MetaMask will open a new browser tab with a list of popular networks. If Sonic happens to be listed there, you can add it with one click — but do not rely on this; listings change, and fake entries have occasionally appeared in aggregator lists.

At the bottom of that page, click “Add a network manually.” This opens a form with five fields: Network name, New RPC URL, Chain ID, Currency symbol, and Block explorer URL.

Step 3: Enter the Sonic network details

Fill in the form exactly as follows:

• Network name: Sonic
• New RPC URL: https://rpc.soniclabs.com
• Chain ID: 146
• Currency symbol: S
• Block explorer URL: https://sonicscan.org

Double-check the Chain ID especially. The chain ID is what tells MetaMask which blockchain you are talking to — 146 means Sonic. If you mistype it, MetaMask will either reject the network or, worse, connect you to the wrong chain. Take thirty seconds to compare what you typed against the values above.

Step 4: Save and switch

Click “Save.” MetaMask validates the details, adds Sonic to your network list, and usually switches you to Sonic automatically. You will see your balance displayed as S instead of ETH. If the wallet does not switch on its own, use the network dropdown and select Sonic yourself.

How to Verify You Added the Real Network

After adding Sonic, spend one minute confirming you are actually connected to the real chain:

1. Check the chain ID. Open Settings > Networks, select Sonic, and confirm the chain ID reads 146.
2. Check the block explorer link. Click the explorer link MetaMask offers for Sonic. It should take you to sonicscan.org, the Sonic block explorer. If the explorer shows a completely different chain, you entered the wrong parameters.
3. Check the currency symbol. Your Sonic balance should display as S, not ETH or anything else.
4. Send a tiny test transaction first. Before moving meaningful funds, fund the wallet with a small amount of S (see the next section) and send a fraction of a token to yourself or a known address. If it confirms on the explorer, your setup is correct.

How to Get S Tokens on Sonic

You need S tokens to pay for gas on Sonic, and for anything you want to do in the ecosystem. There are three common routes:

• Buy on an exchange and withdraw directly. Some exchanges list S and support withdrawals to the Sonic network. If yours does, withdraw a small test amount to your MetaMask address with Sonic selected.
• Bridge from another chain. Bridge aggregators and native bridges can move assets from Ethereum or other networks to Sonic. Expect the bridged asset to arrive as S or a wrapped version, and always start with a small test transfer.
• Receive from another wallet. If you already hold S elsewhere, send a small amount to the MetaMask address you use for Sonic. Your address is the same on every EVM chain — only the network selection in MetaMask changes.

If you are new to adding new chains to MetaMask, the flow is the same as for other EVM networks. The pattern — add the network, verify the details, then fund with a small test transfer — is identical whether you are following this guide, our Ink Chain to MetaMask guide, or our Arbitrum to MetaMask guide.

Sending and Receiving on Sonic

Once Sonic is added and funded, sending and receiving work exactly like they do on Ethereum:

1. Confirm you are on the Sonic network. Glance at the network dropdown. The number-one cause of “lost” transactions is sending from the wrong network — if MetaMask still shows Ethereum Mainnet, your transaction will go to Ethereum, not Sonic.
2. Copy your address. Click your account name to copy your address. It is identical across all EVM networks.
3. To receive: Share that address with the sender and tell them to send on the Sonic network. Then paste the transaction hash into sonicscan.org to confirm it arrived.
4. To send: Click Send, paste the recipient’s address, enter the amount of S (or a token), review the gas fee, and confirm. Sonic fees are typically much lower than Ethereum mainnet, but always check the fee estimate before confirming.

MetaMask may not automatically detect every token you receive on Sonic. If a balance does not appear, use “Import tokens” at the bottom of the assets list and paste the token’s contract address — but only one you obtained from the official project documentation or the block explorer, never from a DM or a comment section.

Sonic vs Other EVM Chains

Adding a network follows the same steps everywhere, but the parameters and the funding assets differ. Here is how Sonic compares with other EVM chains you may already use:

Two things to note. First, the RPC URLs and explorer addresses in this table are shown as bold plain text, not links — that is deliberate. Phishing sites live on lookalike domains, so always type addresses yourself instead of clicking through. Second, Polygon’s gas token has migrated from MATIC to POL; if a tutorial still says MATIC, it is simply outdated. Details like that are a good reminder to cross-check parameters against current official documentation, including our Polygon to MetaMask guide, before relying on any single source.

Troubleshooting Common Problems

MetaMask says the chain ID is already in use. This usually means Sonic is already added — perhaps under a slightly different name. Search your network list for “Sonic” before adding it again.

“Could not fetch chain ID” error. MetaMask cannot reach the RPC endpoint. Check your internet connection, confirm you typed https://rpc.soniclabs.com exactly (including https://), and try again. Public RPC endpoints occasionally have downtime; if the problem persists, wait and retry rather than grabbing a random RPC URL from a forum.

Balance shows zero after funding. First, confirm you are on the Sonic network, not Ethereum. Second, confirm the sender actually sent on Sonic — ask for the transaction hash and look it up on sonicscan.org. If the transaction is confirmed on the explorer, the funds are at your address even if MetaMask is not displaying them; try importing the token.

Transactions fail or stay pending. This is usually a gas issue. Sonic fees are low, but a wallet that underestimates gas can still get stuck. Try speeding up or cancelling the transaction in MetaMask’s activity tab, and make sure you hold enough S for gas.

MetaMask is slow or unresponsive. A misbehaving RPC endpoint can make the whole wallet feel broken. Switch back to Ethereum Mainnet — if MetaMask becomes responsive again, the Sonic RPC was the problem, and your funds are safe.

Fake-Network and RPC Scams to Avoid

Adding a network manually is safe, but the process is also a favorite target for scammers. The most common attacks:

• Fake “add network” buttons. Phishing sites imitate a dapp and show a convincing “Add Sonic to MetaMask” button. The button actually adds a network with the attacker’s RPC URL. Once you use it, the attacker can see and potentially manipulate the transaction data your wallet sends. Only add networks manually with parameters you verified yourself.
• Lookalike RPC and explorer domains. Domains that are one letter off from rpc.soniclabs.com or sonicscan.org host phishing pages designed to harvest seed phrases. Type addresses yourself; never click them from search ads, emails, or social media.
• Seed-phrase requests during setup. No legitimate network addition, bridge, or explorer will ever ask for your seed phrase or private key. Any site that does is a scam, full stop.
• Fake S tokens. Scammers create tokens named “S” or “Sonic” on other chains and trick people into buying them. Verify any token contract on the real Sonic explorer before interacting with it.
• Airdrop and “claim” pages. Sites promising free S for connecting your wallet are almost always drainers. There is no official MetaMask or Sonic “claim page” that requires you to connect and sign.

FAQs

The Bottom Line

Adding Sonic to MetaMask is a quick, free, two-minute task: open the network selector, add a network manually, enter the verified details (chain ID 146, S as the currency symbol, the Sonic Labs RPC and explorer), and save. After that, verify you are connected to the real chain, fund the wallet with a small test amount of S, and you are ready to use Sonic.

The main risks are not in the setup itself but around it — fake “add network” buttons, lookalike RPC domains, and counterfeit S tokens. Add networks manually, type addresses yourself, and never share your seed phrase. Do those three things and Sonic becomes just another network in your MetaMask dropdown.

This guide is for education only — not financial advice.