Jumper is easier to use when you separate moving value to another blockchain from changing one token into another. A bridge changes the network; a swap changes the asset. Choose a bridge when you want the same asset on another chain, and a cross-chain swap when you need a different destination asset.
Know what the route changes
A bridge transfers an asset between networks. Sending USDC from Ethereum to Arbitrum and receiving USDC is a bridge. Sending USDC on Ethereum and receiving ETH on Arbitrum is a cross-chain swap.
A blockchain bridge moves assets between chains, as described in the Ethereum glossary. The route may lock and mint tokens, burn and mint them, or use liquidity on both chains. What matters is the result: whether the asset stays the same or changes.
Jumper is a route aggregator rather than one bridge. Its explainer lists 60+ chains, 21 bridge protocols, and 22 decentralized exchanges. Routes still depend on the selected chains and tokens, available liquidity, and provider support.
One quote can combine a source-chain swap, a cross-chain transfer, and a destination-chain swap. If the source and destination assets match, it works mainly as a bridge. If they differ, it is a cross-chain swap, even if everything happens in one flow.
Use Jumper’s bridge route checker to review the provider, estimated output, fees, price impact, transaction count, and expected completion time before approving a wallet signature.
Choose carefully and check the transaction
A bridge suits someone who already has the right asset and only needs it on another network. A cross-chain swap suits someone who wants to arrive with a different asset for an app or wallet. Both involve trade-offs in security, speed, connectivity, and cost; Ethereum’s bridge guide summarizes the general considerations.
Before signing, select the source and destination networks, then choose the source and destination tokens separately. Confirm whether the destination token is the same asset or a different one. Compare the provider, minimum received, fees, and expected time, and keep enough native gas on the source chain. Review wallet approvals and save the source transaction hash.
Slippage matters most when a route changes tokens or uses shallow liquidity. The fastest route is not automatically the best if its minimum received amount is materially lower.
If funds appear stuck, do not submit the route again immediately. Check whether the source transaction succeeded, failed, or is pending. Then check the destination wallet on the correct network and search for the destination token contract if needed. If the source succeeded but the destination leg has not completed, use the route status or support flow with the saved transaction hash.