A Send Button Does Not Move Crypto to Another Chain
A wallet Send stays on the selected network. Moving value to another chain takes a bridge, exchange, or other supported service, each with its own risks.
A Send Button Does Not Move Crypto to Another Chain
A wallet Send button processes a transfer on the network you selected. It does not place those tokens on a different blockchain. Moving value to another chain takes a separate action: a bridge, a centralized exchange, or another service that supports that route.
MetaMask's guide to custom networks states that assets and transactions are specific to each network, even when the address looks the same. MetaMask also says it cannot track transactions between networks. Ethereum.org says blockchains are built in isolated environments with different rules, so they cannot communicate natively and tokens cannot move freely between them.
What a Send Does
When you tap Send, the wallet submits a transaction on the chain that is currently selected. If the wallet is set to Ethereum and you paste an address you copied from BNB Smart Chain, the transfer still happens on Ethereum.
MetaMask's field guide to bridges uses that mix-up as an example. It says the BNB Smart Chain and Ethereum networks are separate and have no built-in knowledge of each other. A send still goes to the address you entered, but on the network you sent from.
Chains that use Ethereum-style addresses, called EVM-compatible networks, can share the same address format. The balances on each chain remain separate.
How Value Reaches Another Chain
A bridge is one method. Ethereum.org describes bridges as tools that connect two blockchain ecosystems so information and assets can transfer. MetaMask describes a bridge as a way to swap tokens across networks, and it offers that flow through its Swap button. At a basic level, MetaMask says a bridge uses contracts on the chains involved, with a way to confirm a deposit on one network and issue equivalent tokens on another.
That is not the only method. Ethereum.org notes that a centralized exchange can also move value: deposit on one supported network, then withdraw on another, if the exchange lists both. Other services exist for specific tokens. Designs differ, and MetaMask says there is no definitive listing of bridges. MetaMask does not endorse the examples it names. Some tokens cannot be sent from one network to another.
These routes carry their own risks. Ethereum.org lists smart-contract bugs, software failures, user error, and, for trusted designs, censorship or custodial risk. A confirmed deposit on the source chain does not, by itself, prove the destination credit is complete.
If the Send Already Went to the Wrong Network
MetaMask warns against sending tokens directly from one network to another and says that attempt will most likely cause permanent loss. Its recovery article is more specific. Do not treat every wrong-network send as gone, and do not treat recovery as guaranteed.
On EVM-compatible networks such as Polygon, Arbitrum, Optimism, and Avalanche, MetaMask says a Secret Recovery Phrase generates the same address. Tokens sent to an address you or the recipient control may still sit at that address on the network you actually used. Seeing them can require switching the wallet to that network and adding the token if it does not appear. Access depends on who controls the address and whether that wallet or recipient can open the network.
An exchange deposit is different. Coinbase tells customers to select the correct network or funds will be lost. It also says it cannot retrieve on-chain sends made from Coinbase to the incorrect address or network. For some unsupported deposits into a Coinbase address, Coinbase offers an asset-recovery service limited to certain assets and networks. Ineligible attempts fail. Coinbase says some assets are not recoverable. Other exchanges set their own deposit-network rules.
If tokens were sent to an address on a non-EVM network, MetaMask says they are likely gone. Seed phrases generate different addresses on different networks, so the destination may not match an account anyone can open. Sending to a smart contract rather than a regular account is also uncertain. MetaMask says there is no guarantee of recovery.
What Remains Unknown
Bridge and exchange tools vary by token and route. MetaMask cannot give one set of steps that works for every bridge. Wait times are not fixed. MetaMask says bridging is often not instant and can take several minutes on each chain.
Whether a specific wrong-network send can be recovered depends on the networks involved, the destination, and who can sign for that address. Check the transaction on a block explorer for the network you actually used before assuming a loss or a recovery path.
Sources
- MetaMask Help, User Guide: Custom networks and sidechains: https://support.metamask.io/more-web3/learn/user-guide-custom-networks-and-sidechains/
- MetaMask Help, Field guide to bridges: https://support.metamask.io/more-web3/learn/field-guide-to-bridges/
- MetaMask Help, Funds sent on the wrong network: https://support.metamask.io/manage-crypto/move-crypto/send/funds-sent-on-wrong-network/
- ethereum.org, Blockchain bridges: https://ethereum.org/en/bridges/
- Coinbase Help, Steps to send crypto: https://help.coinbase.com/en/coinbase/trading-and-funding/cryptocurrency-trading-pairs/steps-to-send-crypto
- Coinbase Help, Recover unsupported crypto: https://help.coinbase.com/en/coinbase/trading-and-funding/sending-or-receiving-cryptocurrency/recover-unsupported-crypto
Disclosure: This explainer follows MetaMask, ethereum.org, and Coinbase documentation current as of September 29, 2026. Recovery and cross-chain tools vary by network and destination. The featured image is a generated illustration, not a photo of a live transfer. This article is not financial, legal, or investment advice. AI-assisted research and writing. Cited sources, not AI alone, support the claims.


