You finished a chain swap, the asset is sitting in the destination wallet, and then a contract call, a withdrawal queue, or a wrapped balance leaves you needing the bridged form again. Most of the work has already been done. The rest is the bridge.
At that point the practical question is whether to wait out native unwrapping or to re-bridge, and which route gives you a clean re-entry without paying twice for liquidity you already paid for once. The real cost is the spread between the bridged and native forms on the destination chain, plus the route fee, and the wait for the source chain to settle if you unwind. On Ethereum mainnet, that can be twenty minutes of finality plus a contract call that runs another few. On L2s it is faster but the wrap premium tends to be larger, sometimes 30 to 80 basis points on a liquid pair, several times that on a thinner one. Crypto Bridge tooling worth using is the kind that quotes the wrapped-versus-native spread, the route fee, and the expected settlement window before you sign, not after.
Two things separate a clean bridge from a messy one. First, source confirmation: until the source tx has the finality the destination expects, the receiving leg is a claim, not a balance, and any UI that lets you act on it is lying. Second, route selection. The cheapest displayed fee often runs through a hop with thin liquidity, so the effective cost is the fee plus the slippage on the leg you do not see. Check the pool depth at the size you are moving, not the headline rate.
Bridge only what you will use in the near term. Holding bridged inventory is a carry cost paid in spread every time the native form moves against you, and it is the single most common reason a clean position turns into a slow bleed.