How to Switch Networks in MetaMask: Desktop and Mobile Guide 2026

A network in MetaMask is the blockchain your wallet is talking to at a given moment. Ethereum mainnet is the default. Other networks, such as Layer 2 rollups and sidechains, run their own ledgers, have their own native gas token and keep their own record of balances and contract deployments.

The important point is that one MetaMask account can hold a balance on several networks. The address you see is the same everywhere, but the ETH or token balance under that address is tracked separately on each chain. If you select a different network, the wallet shows you what that chain holds for your address, not what you hold on another chain.

This is why switching networks matters. A transaction is only valid on the chain that your wallet is connected to at the time you sign it. If a dApp expects Polygon and you are connected to Ethereum mainnet, the transaction will be rejected or sent to the wrong place. Knowing which network you are on is the first habit to build.

Before you change networks, check three things so you do not end up confused or paying fees you did not expect.

• Which network holds your funds. Look at the transaction history or the block explorer for the chain where you received the tokens.
• Which network the dApp needs. Most sites name the chain in their interface or documentation.
• Whether you have enough of the gas token. Each network charges fees in its own native token, so you need a small amount of that token on the chain where you plan to transact, even if your main balance is elsewhere.

It also helps to write down the network name and chain ID you intend to use. Chain IDs are numbers that identify each network, and they are a more reliable check than a name alone, because some networks have similar names or unofficial copies.

On the desktop browser extension, the network selector sits near the top of the MetaMask window, usually beside the account icon. It shows the name of the network you are currently using. The exact layout can change between versions, so if you cannot find it, look for the network name at the top of the home screen.

To switch networks:

1. Open the MetaMask extension from your browser toolbar and unlock it.
2. Click the network selector at the top of the window.
3. Pick the network from the list. Networks you have already added appear here.
4. Confirm that the network name at the top has changed.
5. Check your balance again, because the displayed tokens now belong to the new network.

If the network you need is not in the list, you will need to add it. Test networks are hidden by default in some versions. If you are working with a test network, look for the option to show test networks in the settings, then select it from the same menu.

Older versions of the extension placed the Networks option inside the main menu. If the selector is not visible, open the menu from the top right and look for Networks.

The mobile app works in a similar way, though the layout is different. On the home screen, tap the network name near the top of the screen. A list of available networks opens. Choose the network you want, then return to the home screen and confirm the name has changed.

Steps on mobile:

1. Open the MetaMask app and sign in with your password or biometric check.
2. Tap the network name shown at the top of the home screen.
3. Select the network from the list.
4. Check that your balance and token list now match the network you expect.

If you use the app in the in-app browser to open a dApp, the site may ask to switch chains. You will see a prompt asking you to approve the change. Read the network name in the prompt before you approve it. Mobile screens are small, so it is easy to miss a mismatch. If anything looks wrong, reject the request and switch manually from the home screen.

Most common networks are included by default, but not all of them. If a network is missing, you can add it by hand. The usual fields are:

• Network name. A label you choose to recognise it.
• RPC URL. The address of the node your wallet uses to read and send data on that chain.
• Chain ID. A number that identifies the network.
• Currency symbol. The name of the native gas token.
• Block explorer URL. Optional, but useful for checking transactions.

Always copy these values from the network's official documentation or from the project's own announcement. A wrong RPC URL or chain ID can point your wallet at a service you do not trust, or make it show the wrong balances. Do not add a network because a stranger sent you a link or a message in a chat.

To add a network on desktop, open the network selector, choose the option to add a network, and enter the fields. On mobile, the path is in the network list and the same fields apply. After saving, switch to the new network and check the chain ID shown in the details before you use it.

Switching networks changes the view and the chain your wallet signs for. It does not move tokens between chains. If you received USDC on one network, it stays on that network until you transfer it. Switching to another network will show you a zero balance for that token, and this can look like a loss when it is not.

The balance you see for a network can also be wrong if the token list is missing an entry. Many tokens are not shown automatically on every chain. You can add a token manually by entering its contract address for that network. Get the contract address from the official source for the token or the block explorer, and check it carefully, because similar-looking fake tokens exist.

If the balance still does not appear, look up your address on the block explorer for that chain. The explorer shows transactions and token transfers even when your wallet does not display them.

To move assets from one network to another, you usually use a bridge or a cross-chain swap. A bridge locks or burns tokens on the source chain and releases or mints them on the destination chain. Some bridges are operated by the network itself, which are often called canonical bridges. Others are third-party services that connect many chains.

Before you use any bridge, take these steps:

1. Confirm the bridge address or website from the network's official documentation rather than a search result or an advert.
2. Start with a small amount to see how long the transfer takes and what fees apply.
3. Make sure you hold the gas token for the destination chain if the transfer needs a final transaction there.
4. Read the approval prompts. Approving a token spend lets a contract move that token, so only approve what you need.
5. Keep the transaction hash so you can track the transfer on both block explorers.

Bridges carry smart contract risk and operational risk. Transfers can be slow, fees can change, and some routes are paused. Treat any bridge as a tool with its own rules, not as a guaranteed service.

Websites use a standard wallet request to ask MetaMask to change networks. When this happens, you will see a prompt naming the network. Approving it switches your wallet to that chain. Declining it leaves your current network unchanged.

A prompt is a request, not an instruction you must follow. Before you approve, ask yourself whether you expected to use that network on this site, whether the network name matches the one in the site's documentation, and whether you are about to sign anything after the switch. If the site asks you to add a network you do not recognise, reject it and check the project's official channels.

If you are unsure, reject the request, select the network yourself from the wallet, and then reload the dApp. Keeping the switch under your own control is the safest habit, especially on sites you do not use often.

Be alert to lookalike sites. Phishing pages copy the design of popular dApps and may send network prompts that lead to fake chains. Type or bookmark addresses you trust, and do not sign requests that appear after you clicked an unexpected link.

Most switching problems come from one of a few causes.

• The wrong network is selected. Check the name at the top of the wallet before you sign anything. If a transaction fails, this is the first thing to check.
• The token is not added on that network. Add it by contract address from an official source, or view the balance on the block explorer.
• You have no gas token on the current chain. Fees are paid in the native token of the network you are using. Buy or bridge a small amount of that token there, then try again.
• A transaction is stuck or pending. Look it up on the block explorer for that chain. Do not send a second identical transaction without checking the first one, because you may pay twice.
• The network is unreachable. This can be a temporary RPC problem. Try a different reputable RPC endpoint from the official documentation, or wait and retry.
• Test networks are hidden. Enable them in the settings if you need them, and remember that test tokens have no real value.

If the problem continues, consult the network's official support channels and the MetaMask support pages. Never share your recovery phrase or private key with anyone who offers help, including people who contact you first in a chat or direct message.