If you have bridged ETH or USDC to Base before, the process probably felt familiar enough that you assumed it would work the same way for an NFT sitting in your wallet on another chain. It does not, at least not by default, and understanding why matters before you send a one of one piece of art through a tool you found through a search result.
NFTs are not portable the way fungible tokens are
A fungible token like ETH or USDC is interchangeable. Every unit is identical to every other unit, so a bridge only has to prove that a certain amount left one chain before releasing or minting the same amount on another. Our guide to how to bridge to Base covers how that process works for tokens like these.
An NFT is different by design. It is a specific token ID living inside a specific contract on a specific chain, and the contract address plus the token ID together are what a marketplace, a wallet, or a piece of software uses to recognize it as the real thing. There is no native mechanism in Ethereum or in Base's underlying design that lets a contract on one chain directly move an asset to a contract on another chain. The original NFT contract usually does not even know Base exists.
How NFT bridges actually work
Because there is no native path, most NFT bridges rely on a pattern often called lock and mint. The original NFT is locked, or in some designs burned, in a contract on the source chain. A new, separate contract on the destination chain then mints a token meant to represent that same NFT. If you later want to move it back, the process reverses: the copy on the destination chain is burned, and the original is released from escrow on the source chain.
This works, but it introduces something that a simple transfer never had: a middleman. The wrapped version you hold on the destination chain is not the original contract the creator deployed. It is a representation that a bridge's own contract vouches for. Whether that representation behaves exactly like the original, keeps the same metadata, and is recognized by the marketplaces and tools you expect, depends entirely on how that specific bridge built it.
What can go wrong
A few consequences follow from that design, and they are worth knowing before you use any NFT bridge.
The wrapped copy is not the canonical asset. If the original collection becomes valuable or well known later, marketplaces, verification badges, and royalty systems are built around the original contract address, not the wrapped one. A wrapped copy can end up disconnected from any of that, sitting on a chain where almost nobody is looking for it.
Royalties often do not carry over. Creator royalty logic lives in the original contract or in marketplace agreements tied to it. A bridge minting a generic wrapped token on another chain has no obligation, and often no mechanism, to honor the original creator's royalty terms on future sales.
The bridge contract becomes a single point of failure. While your NFT sits locked in escrow, its safety depends on the security of that specific bridge contract, not on the original collection's contract. If the bridge is exploited, drained, or simply abandoned, recovering the original asset can become difficult or impossible, regardless of how secure the original NFT contract itself was.
Phishing follows the confusion. Because the process is unfamiliar to a lot of holders, fake bridge interfaces and cloned marketplace listings for "bridged" versions of popular collections are a real and recurring scam pattern. Our guide to typosquatting and lookalike crypto sites covers how convincing these fakes can look.
None of this means NFT bridges are never legitimate. Some reputable projects run their own audited bridging infrastructure specifically for their own collection, and in that narrow case the risk is closer to using any other audited contract. The risk rises sharply with generic, third party bridges that claim to move "any NFT from any chain," since those are taking on custody of assets they had no role in creating.
What to check before you bridge an NFT
If you are considering moving an NFT to or from Base, a few checks are worth doing first.
- Look for an official route first. Check whether the collection's own creator or project has a documented, first party way to move the asset, rather than relying on a third party tool you found independently.
- Confirm the destination contract address, not just the collection name. A wrapped NFT will have a different contract address from the original by necessity. Verify it against anything the project itself has published, the same way our guide to checksum addresses recommends for any address you have not used before.
- Check whether marketplaces on the destination chain actually recognize the wrapped asset, including whether it will show up with correct metadata and image, before assuming it will list and sell the same way the original did.
- Treat it as a trust decision, not just a technical one. You are extending trust to the bridge's contract for as long as the asset sits wrapped. Weigh that against how much the asset is actually worth to you.
For most holders, the simplest and lowest risk option is to mint or acquire NFTs natively on the chain where you actually want them, including Base, rather than moving an existing one across through a bridge. If a specific collection does not exist on Base, that is usually a sign it was never designed to be portable in the first place, not a gap waiting for a workaround.