A large transfer has no single Portal Bridge limit: the route, token, and Wormhole’s available capacity decide whether it proceeds or waits. Check the exact chain pair and amount before sending, then plan for a possible delay of up to 24 hours if the security Governor queues it.

There is no one limit for every transfer

The usable maximum depends on the token and route you select. A token contract or route may impose an amount cap, and the interface may reject an amount that exceeds it; separately, Wormhole’s Governor can delay a transfer because of the value moving out of the source chain.

Think of the route like a road with both a vehicle weight limit and a traffic control system. A transfer can fit the token’s own cap yet still wait because the chain’s recent outflows have used up the Governor’s available capacity. That capacity is measured in USD value over a sliding 24-hour window, rather than resetting at midnight.

Portal Bridge lets you choose the source chain, destination chain, token, and amount so you can inspect the route before submitting. For a large move, the key question is not just “How much can this token send?” but “Will this route clear promptly at this amount?”

Check the route before committing funds

Start by selecting the exact source and destination networks and the asset your app needs. Confirm that the destination accepts the asset form shown: a bridged token can have a different contract address from the native asset, even when the ticker and displayed value look the same.

Enter the full intended amount and review the interface’s estimate, including destination amount and fees. Check the source wallet balance after reserving its network’s gas token; sending the maximum displayed token balance can leave too little to pay for the transaction. If the app requires funds by a deadline, allow for a Governor delay instead of treating the usual transfer time as a guarantee.

For a large transfer I would check the originating transaction in Wormhole Explorer after it confirms, then follow the message status there. The Ethereum.org glossary explains finality as the point at which a transaction can no longer be reversed; the source chain’s confirmation is only one stage, since the destination still needs the cross-chain message and redemption.

Plan for a delay without splitting blindly

Wormhole’s Governor tracks chain outflows and may hold a message before Guardians sign it. Its documented behavior is to delay qualifying transfers until capacity returns, with a maximum delay of 24 hours; congestion can also delay a smaller transfer when recent activity has consumed the chain’s available allowance.

Splitting a transfer into several pieces is not a reliable way around this. Each piece creates another source transaction and fee, and the pieces still contribute to aggregate outflow during the same rolling window. A single large transfer may also receive extra scrutiny, so splitting can add cost without improving the arrival time.

If the route rejects the amount outright, first verify token decimals, the selected asset, and the amount cap shown by the interface. If the transaction has already been sent and is waiting, don’t submit duplicates: check its status in Wormhole Explorer and wait for the message to become available for completion.

Budget fees and choose a sensible transfer size

Expect a source-chain transaction fee, and budget for a destination-chain transaction if you must redeem manually. Automatic completion, when offered on that route, can include a relayer fee; the amount shown in the quote is the useful figure to compare, since gas varies by chain and network conditions rather than by a universal bridge tariff.

For example, if an app needs 8,000 USDC on the destination chain, compare the quoted net receipt and route status for 8,000 with what you need after fees. If it fits the route and a potential day-long delay is acceptable, send once; if timing is critical, move the minimum needed earlier and leave the remainder for a later window.

Your next step is to open the route, enter the app’s required amount, and verify the destination asset, net amount, fee estimate, and timing before you approve the source transaction.