How NFT Bridges Move a Token Between Chains

An NFT moves across chains when a bridge removes it from use on the source chain, verifies a transfer message, and releases or creates its counterpart on the destination. The original token does not travel between blockchains; a contract coordinates the change in ownership and representation.

What happens to the original NFT?

In a lock-and-mint design, the bridge holds the original NFT in custody and mints a wrapped version on the destination chain. Wormhole’s published NFT bridge design describes this flow: a native NFT is locked, while a wrapped NFT is burned when sent onward or returned.

The wrapped token is linked to the original collection and token ID, but it has a different contract on the destination chain. For a fuller account of how wallets and applications fit into this model, see omnichain. A burn-and-mint design instead destroys the source representation and creates its mapped counterpart on the destination.

How does the bridge complete the transfer?

The bridge sends a message that identifies the source NFT, token ID, destination chain, and recipient. A verifier or protocol checks that message; the destination contract then releases an NFT it holds or mints the mapped version, depending on the design.

Wormhole’s design specifies that the destination processes a verified message and tracks used messages to prevent the same transfer being completed twice. Some systems deliver the message automatically; others require the user to submit or claim it on the destination chain. Until that step completes, the NFT may be locked or burned on the source while the destination version is not yet available.

• Check that the bridge supports both the source and destination chains.
• Confirm the collection’s contract and token ID before starting.
• Enter a wallet address that can receive NFTs on the destination chain.
• After completion, verify the destination contract and token ID in the wallet or chain explorer.

What can change when an NFT is bridged?

The NFT’s identity depends on its chain of origin, collection contract, and token ID—not just its name or image. Wormhole’s design includes the source chain and contract, token ID, recipient, and metadata URI in its transfer message, but that does not guarantee every destination application will display or support every property.

Metadata may be stored off-chain, and a destination version may not carry chain-specific features such as game logic or marketplace settings. The destination token can also be treated as a wrapped asset rather than the collection’s original NFT. That distinction matters for listings, access rights, and recognition by applications.

Which transfer route should you choose?

For most holders, the better route is the one specified by the collection’s creator or official project for the intended destination. It is more likely to produce the representation that the project recognizes, while a generic bridge may create a wrapped token that other apps do not recognize.

Before approving a transfer, compare the bridge’s displayed source and destination details with the collection’s instructions. Keep the transaction record, and check the destination chain after the message completes. The key trade-off is custody versus representation: a lock-and-mint route leaves the original in escrow, while a burn-and-mint route relies on the bridge’s contracts and message verification to recreate the mapped NFT.