Send, Swap and Bridge can all begin with a few selections in MetaMask, but they solve different problems. Send changes who controls an asset. Swap changes which asset you hold. Bridge changes the blockchain on which an asset is available, and a cross-chain swap can change both network and token in one route. Choosing the wrong action can leave funds on the wrong chain, create an unnecessary approval or turn a simple transfer into a more expensive multi-step transaction.

Last reviewed: October 14, 2026. MetaMask interfaces, supported networks, route providers, fees and transaction features can change. Confirm the current quote and behavior in the official MetaMask application and documentation. This independent guide is educational, is not affiliated with MetaMask and is not financial advice.

Quick answer: use Send when the recipient should receive the same asset on the same network, Swap when you want a different token without changing networks, and Bridge when the destination is another blockchain. Read the complete quote—not only the headline rate—verify source network, destination network, token contract, recipient, minimum received and gas, then track every submitted transaction by hash.

1. Send, Swap and Bridge solve different problems

A wallet interface can make these actions look similar because each ends with a confirmation. Underneath, they create different instructions. A Send normally transfers an existing asset to another address. A Swap interacts with liquidity to exchange one token for another. A Bridge relies on a cross-chain mechanism that observes or locks value on one network and delivers corresponding value on another.

The right starting question is not “Which button is cheapest?” It is: who should own the result, which token should they receive, and on which network must it exist? Those three decisions identify whether the job is a transfer, an exchange, a network move or a combination.

2. MetaMask Send vs Swap vs Bridge at a glance

Action What changes Typical network relationship Main checks
Send Owner or destination address Asset remains on the selected network Recipient, network, token and gas
Swap Token held by the same account Usually same-chain, though current MetaMask flows can offer cross-chain routes Token contracts, quote, price impact, slippage and approvals
Bridge Network, and sometimes token Source and destination are different chains Both networks, route, destination asset, time and destination gas
Send & Swap Recipient and token Depends on the quoted route Recipient, received token, quote and supported transaction behavior

3. Decide by the desired final state

Write the final state in one sentence before opening a quote. “Alice should receive 50 USDC on Base” is specific. “Move 50 USDC” is not, because USDC exists on several chains and the recipient may expect a particular network. If you hold USDC on Base and Alice expects Base USDC, Send is enough. If you hold ETH on Base and she expects USDC on Base, a swap-and-send route may help. If your funds are on Ethereum and she expects Base, a cross-chain route is required.

This habit prevents interface labels from driving the decision. The final owner, asset and chain matter more than which feature appears first in the wallet.

4. What a normal Send does

A Send instructs the selected blockchain to transfer its native asset or a token from your account to a recipient. It does not convert the token and does not cause another blockchain to recognize the transfer. For an ERC-20 token, the transaction calls the token contract on the active network; for a native asset, it transfers value directly under that network’s rules.

You need the correct recipient, sufficient balance and enough gas under the current network’s fee rules. On supported networks MetaMask may offer gas-included options, but availability is contextual. Always treat the final confirmation as authoritative for that transaction.

5. Send does not move tokens between networks

Ethereum, Base, Arbitrum, Polygon and BNB Smart Chain are separate ledgers. Sending from an address while Base is selected records the transaction on Base, even if the same 0x address also exists on Ethereum. The asset does not jump chains because the destination characters look compatible.

If the recipient controls that address on the source network, recovery may be possible by switching to that network. If an exchange or service does not support the deposited network, recovery depends on its policy and may be impossible. Confirm the receiving platform’s asset-and-network combination before sending.

6. The same address can represent separate network balances

An EVM account often displays the same public address across compatible networks because the same key controls it. That does not combine balances, token contracts or transaction histories. Ten USDC on Ethereum and ten USDC on Base are separate onchain positions.

Compare the entire address and the selected chain. A correct address on an unsupported chain is still the wrong destination workflow. For non-EVM networks, address formats and account models may differ further, so never assume a copied address is multi-network by default.

7. What MetaMask Swap does

MetaMask Swaps obtains quotes from available liquidity sources and routes, then presents an expected exchange between the selected input and output tokens. MetaMask describes itself as the interface and quote aggregator rather than the liquidity provider. Execution interacts with the selected route onchain.

A same-chain swap changes the asset while keeping the result on the selected network. For example, swapping ETH for USDC on Arbitrum produces the quoted USDC on Arbitrum, not Ethereum USDC. Current MetaMask interfaces may also provide cross-chain swaps, so check both source and destination network in every quote.

8. A quote is a temporary execution proposal

A quote describes a route available at a particular moment: the input, estimated output, fees, price effect, slippage boundary and contracts involved. Market conditions and gas estimates can change before confirmation. A previously attractive quote should not be treated as a standing promise.

Refresh an expired quote rather than approving an unexplained change. Compare the estimated amount received after costs—not only the displayed exchange rate. A route with a slightly better rate can produce a worse result after network and service costs.

9. How routing affects a swap

An aggregator can compare multiple liquidity venues and may split or sequence trades to improve the result. That convenience adds contracts and execution assumptions. The best route for a small trade may differ from the best route for a large one because liquidity depth, price impact and gas costs scale differently.

Review the route when the interface exposes it. More hops are not automatically unsafe, and fewer hops are not automatically cheaper. What matters is the total expected output, trusted contracts, execution protections and whether the route matches your intent.

10. Headline rate versus amount received

The headline exchange rate is only one component. The useful number is the minimum or estimated amount that reaches your account after the swap. Network cost, MetaMask or provider fees, liquidity price impact and slippage can all influence the outcome.

For a meaningful comparison, keep the same input amount and network, refresh quotes close together, and compare net output. Do not compare a gross market price from one screen with a net executable quote from another.

11. Price impact is caused by the trade itself

Price impact measures how the requested size changes the execution price against available liquidity. A large order in a shallow pool can move the pool price substantially. This differs from ordinary market movement while a transaction is pending.

If price impact is high, consider whether the token or pool is legitimate, whether liquidity is sufficient, and whether a smaller trade or different timing would materially improve execution. Splitting an order can create multiple fees and does not guarantee a better result, so calculate total cost rather than assuming.

12. Slippage tolerance sets an execution boundary

Slippage tolerance states how far execution may move from the quote before the transaction should fail. It is a protective limit, not an extra fee and not a guarantee that the quoted result is economically good. Volatile or low-liquidity pairs are more likely to move beyond a narrow tolerance.

Use a tolerance appropriate to the market and read the minimum received. Do not increase it merely to force an unfamiliar token through. A repeated failure can indicate poor liquidity, a rapidly moving market, restrictive token behavior or a problematic route.

13. Low and high slippage have opposite trade-offs

Setting Potential benefit Potential cost
Very low tolerance Rejects fills that move beyond a tight boundary Higher likelihood of failure and spent gas in changing markets
Moderate tolerance Balances execution probability and price protection Still requires evaluation for the specific pair
Very high tolerance Makes execution more likely Can permit a much worse fill and increase exposure to adverse execution

There is no universal ideal percentage. Token liquidity, volatility, trade size, network congestion and route design matter. Treat warnings and unusual defaults as reasons to investigate, not obstacles to click through.

14. Fees must be read as a stack

A Send usually has a network fee. A Swap can include network gas, a service fee and execution effects. A Bridge can include source-chain gas, bridge or route costs, liquidity effects and sometimes destination-side execution. Gas-included features may collect cost from another token rather than eliminating it.

Record both what you pay and what should arrive. A “zero fee” label can refer to one component while spreads, gas or route costs remain. MetaMask features evolve, so rely on the current confirmation rather than an old fee percentage from an article or screenshot.

15. Token approval and swap are separate authorizations

An ERC-20 approval lets a specified contract spend up to an authorized amount from your account. The subsequent swap uses that authority. The approval itself does not necessarily perform the exchange, and a failed swap does not automatically remove a previously granted allowance.

Read the spender, amount and network. Prefer a limited amount when practical, and review remaining approvals later. Disconnecting a site is not the same as revoking an onchain allowance. MetaMask’s approval-management tools and reputable explorers can help inspect current permissions.

16. Why a failed swap may still spend gas

Validators or sequencers process submitted transactions and charge for computational work even when contract conditions ultimately revert. A slippage check can protect the token outcome while the network fee remains spent. That gas goes to network operation, not automatically to MetaMask.

Before retrying, identify the likely cause. Blindly resubmitting with higher gas or slippage can repeat the loss or weaken protection. Refresh the quote, verify balances and allowance, inspect the transaction status, and confirm that the token is transferable.

17. What a Bridge does

A bridge coordinates value across separate blockchains. Depending on its design, assets may be locked, burned, minted, released from liquidity or exchanged through a sequence of providers. The source transaction and destination delivery are related but may not appear as one identical transaction on both chains.

MetaMask’s bridge and cross-chain swap experience can aggregate routes and let users compare options. Aggregation simplifies selection but does not make every route instantaneous or risk-free. The underlying networks and providers still determine settlement behavior.

18. Source network, destination network and destination token

A bridge quote has at least three critical asset fields: what leaves, where it leaves from, and what should arrive where. “USDC to USDC” is incomplete without network names because token contracts and issuer-supported forms can differ across chains.

Read the destination token contract when it matters, especially for similarly named or bridged assets. Confirm that the destination application accepts that exact representation. A ticker and logo are not sufficient proof of authenticity.

19. Bridge versus cross-chain swap

A simple bridge route aims to move an equivalent asset between networks. A cross-chain swap can accept one token on the source chain and deliver another token on the destination chain. The combined route may replace a manual sequence of swap, bridge and second swap.

Fewer confirmations can improve convenience, but evaluate the combined result. Compare the final token amount, destination liquidity, route providers, estimated duration and recovery path. A bundled operation can also be harder to diagnose because several stages sit behind one interface.

20. Bridge is not the same as switching networks

Switching MetaMask’s active network changes which blockchain the wallet displays and queries. It does not submit a transaction and does not move assets. Bridging submits an onchain action intended to create a corresponding result on another network.

If you switch from Ethereum to Base and the balance becomes zero, first ask whether the asset was ever bridged or received on Base. Do not add a fake token contract merely to make a balance appear. Check the address on reputable explorers for both networks.

21. Cheapest route versus fastest route

Bridge quotes can optimize for different outcomes. A lower-cost route may take longer or require more stages. A faster route may charge more or depend on available liquidity. Estimated duration is useful for comparison but cannot guarantee when both networks and providers will finalize.

Choose according to the transaction’s actual need. For a routine transfer, waiting may be acceptable. For time-sensitive collateral or protocol activity, arrival time matters—but urgency should not override verification.

22. Destination gas is part of route planning

Receiving a token on a new network does not guarantee you can use it. Most follow-up transactions require that network’s native gas asset or a supported gas-included mechanism. Bridging all value into a non-gas token can leave an account unable to swap, approve or send.

Check whether the quote includes destination refueling, delivers a native token or supports fees in another asset. Do not accept unsolicited “gas help” links. If separate funding is required, verify the network and send a small amount through a trusted route.

23. Gasless and gas-included do not mean cost-free

MetaMask documents gasless swap functionality on supported configurations. Instead of requiring a separate native-token balance, the quote can account for the network fee using the token being spent. On some networks this may involve smart-account functionality and required settings.

The user experience removes a separate gas-balance problem, not the economic cost. Compare input and output carefully. Availability depends on the network, token, wallet version and transaction type, so do not build a recovery plan around it without confirming the current quote.

24. Send & Swap changes asset and recipient together

MetaMask’s Send & Swap flow can let the sender spend one token while the recipient receives another. This can avoid a separate preliminary swap and second transaction. It is still essential to verify the recipient and final received asset, because two intentions are combined.

Check whether the route stays on one network or crosses chains, whether Smart Transactions support applies, and what amount the recipient should receive. If the recipient is an exchange, merchant or contract, confirm it supports the exact delivered token and network.

25. Compare the complete confirmation screen

  • Sending account and full recipient address.
  • Source network and destination network.
  • Input token, output token and their verified contracts.
  • Input amount, expected output and minimum received.
  • Network fee, service fee and other displayed costs.
  • Slippage tolerance and price impact.
  • Approval spender and allowance amount, if requested.
  • Estimated duration and route provider details.

If the confirmation does not describe the outcome you intended, reject it. A security alert is useful but cannot know your private intention or whether you selected the correct chain.

26. Token identity requires more than a symbol

Anyone can create a token with a familiar name and logo. Confirm the network and contract address through the project’s official channels or a trusted asset list. This is particularly important after bridging, when native, wrapped and third-party representations may use similar symbols.

Do not interact with unsolicited tokens sent to your wallet. A token’s appearance in the interface does not prove value or safety, and an attached website can be a phishing attempt.

27. Recipient verification remains essential

Compare the complete recipient address using a trusted source. Transaction history can be poisoned with look-alike addresses, and clipboard malware can replace copied text. For a new or high-value destination, a small test can confirm control when fees and the receiving service allow it.

If hardware signing is used, compare the destination and amount on the hardware display. The computer screen alone may be manipulated. A swap back to your own account has different recipient risk, but a bridge or Send & Swap may still expose destination-address controls.

28. Practical decision examples

Goal Likely action Reason
Send Base USDC to a friend who accepts Base USDC Send Owner changes; asset and network remain the same
Convert ETH to USDC on Arbitrum Swap Token changes on one network
Move ETH from Ethereum to Arbitrum Bridge Network changes
Turn Ethereum USDC into Arbitrum ETH Cross-chain swap Network and asset both change
Pay a recipient in USDC while spending ETH Send & Swap, if supported Recipient and asset change in one quoted flow
View an existing balance on another chain Switch network No transfer is required if assets already exist there

29. What pending, failed and completed mean

Pending means a submitted transaction has not reached the expected final state. Failed means it was processed but reverted or could not execute; gas may still be charged. Completed on the source chain does not always prove a cross-chain destination has finished.

Use the transaction hash and the correct explorer. For bridges, the route’s status page may connect the source action with the destination delivery. Do not rely only on a wallet notification or temporarily stale balance.

30. Troubleshooting a pending Send

  1. Confirm the transaction is on the expected network and locate its hash.
  2. Check whether it is genuinely pending or only absent from the wallet activity view.
  3. Review nonce order; an earlier pending transaction can block later ones from the same account.
  4. Use MetaMask’s documented speed-up or cancellation controls only when applicable.
  5. Do not submit repeated transfers to the same recipient unless you know the original cannot complete.

A cancellation is normally another transaction using the same nonce and a competitive fee; it is not guaranteed if the original confirms first.

31. Troubleshooting a failed Swap

Inspect the explorer result and MetaMask message. Common areas include slippage, changed liquidity, insufficient gas, expired quotes, token transfer restrictions, allowance problems or a route-specific failure. Confirm whether the approval succeeded even though the swap failed.

Refresh the quote and reconsider the asset rather than immediately raising slippage. If an unfamiliar token repeatedly fails, investigate whether it is transferable and whether selling restrictions or malicious mechanics are involved.

32. Troubleshooting a pending Bridge

First verify that the source transaction confirmed. Then use the official route or bridge status tool to locate the destination stage. Different routes may wait for confirmations, liquidity delivery, relayer action or challenge periods. Estimated time is not a finality guarantee.

Do not initiate the same bridge again merely because the destination balance is late. Save the quote or route identifier, source hash, destination address, token contracts and timestamps. Contact only official support and never provide recovery words or private keys.

33. When the asset arrived but is not visible

Select the destination network and check the address on its explorer. If the explorer shows the token but MetaMask does not, the interface may need token detection or a verified custom-token import. Confirm the exact contract before adding it.

If the explorer shows a different token representation than expected, review the completed route. Do not send it to an exchange until that platform confirms support for the exact network and contract.

34. Do not repeat a transaction based on interface delay

Wallet activity lists and token balances can lag behind the blockchain or an RPC provider. Before repeating, check the transaction hash on the appropriate explorer and refresh or switch RPC only through a trusted configuration. A repeated Send can pay twice; a repeated Swap or Bridge can create unintended market exposure.

Save hashes as soon as they are submitted. The hash is the clearest starting point for distinguishing a display problem from an execution problem.

35. Security boundaries of an aggregator

Aggregation can reduce manual searching and compare available routes, but it cannot eliminate smart-contract, token, liquidity, network or user-selection risk. A quoted route can be legitimate while the chosen token or destination is not what you intended.

Security alerts and simulations are additional checks, not guarantees. Reject unexplained approvals, unlimited allowances, unfamiliar signatures and changed recipients. Keep higher-value holdings separated from routine experimental activity.

36. A safe workflow before confirming

  1. State the final owner, asset and network.
  2. Open MetaMask from a trusted installation, not a link in a message or advertisement.
  3. Select the correct account and source network.
  4. Verify token contracts and destination support.
  5. Compare net output, fees, slippage and route—not only the headline rate.
  6. Read every approval and transaction request independently.
  7. Verify the complete recipient on a trusted display when available.
  8. Submit once, save the hash and monitor the correct network or route tracker.

37. Post-transaction checklist

  • Confirm the source transaction status on the source chain.
  • For a bridge, confirm destination delivery on the destination chain.
  • Verify the exact token contract and amount received.
  • Retain enough destination gas for the next planned action.
  • Review approvals created during swaps or bridges and revoke those no longer needed.
  • Save transaction records needed for accounting or tax reporting.
  • Investigate unexpected tokens or permissions without visiting attached links.

Frequently asked questions

Is swapping the same as bridging in MetaMask?

No. A same-chain swap changes the token on one blockchain. Bridging changes the blockchain. A cross-chain swap can combine both, which is why every quote must show source and destination networks.

Does switching networks move my tokens?

No. It only changes which blockchain MetaMask displays. Moving value between chains requires a supported bridge or cross-chain route.

Why did my failed swap still charge ETH?

The network processed the submitted computation before it reverted. Slippage or another contract condition can prevent the token exchange while gas remains consumed.

Does gasless mean the transaction is free?

No. It generally means the network cost is handled through the quoted token flow instead of requiring a separate native-token balance. Check the net input and output.

Should I always select the cheapest bridge route?

No. Compare final output, estimated time, providers, destination gas and the route’s recovery process. Cheapest and fastest are different objectives.

Can I send a token directly from Ethereum to the same address on Base?

A normal Ethereum Send remains on Ethereum. Use a compatible bridge or cross-chain swap if the intended result must be on Base.

Why do I need an approval before a swap?

Many ERC-20 routes need permission for a contract to spend the input token. The approval and swap are separate onchain actions, and an unused allowance may remain afterward.

What information should I keep if a bridge is delayed?

Keep the source hash, route or quote identifier, source and destination networks, token contracts, destination address, amount and submission time. Never send support your Secret Recovery Phrase.

Official references

Use these official MetaMask resources to confirm the current interface, availability and transaction behavior:

The safest choice is the simplest operation that produces the intended owner, token and network. Define that result first, inspect the complete quote, and treat every approval and transaction as a separate decision.

Visit MetaMask ↗Official website