How to transfer NFTs from MetaMask to a cold wallet? (Security tutorial)

Understanding NFT Storage Requirements

1. NFTs reside on blockchain networks as unique tokens, most commonly on Ethereum, Polygon, or Solana, and are not stored directly in wallet software like MetaMask.

2. Ownership is recorded on-chain via smart contract addresses and token IDs, meaning the wallet only holds the private keys that authorize transfers.

3. A cold wallet must support the same blockchain network and token standard (e.g., ERC-721 or ERC-1155) as the NFT’s native chain.

4. Not all hardware wallets natively display NFTs in their user interface, but they can still securely hold and sign transfer transactions if the connected software supports it.

5. Before initiating any transfer, verify that the cold wallet’s firmware and companion application (e.g., Ledger Live or Trezor Suite) are updated to the latest version compatible with the target network.

Preparing Your Cold Wallet

1. Install the appropriate app on your hardware device—Ethereum app for ERC-721/ERC-1155 NFTs on Ethereum or Polygon, Solana app for Solana-based NFTs.

2. Ensure the cold wallet’s derivation path matches the one used by MetaMask (typically Ethereum’s default m/44'/60'/0'/0).

3. Confirm that the receiving address derived from the cold wallet is fully functional by sending a small test transaction of native gas token (e.g., ETH or MATIC) to it.

4. Use a clean, air-gapped computer when interacting with the cold wallet to avoid malware interception during signing.

5. Write down and physically store the cold wallet’s recovery phrase in a secure location—never digitally.

Exporting NFT Metadata and Ownership Proof

1. Navigate to the NFT’s page on a trusted explorer such as Etherscan or OpenSea and locate its contract address and token ID.

2. Copy the exact contract address—case-sensitive—and validate it against the official project repository or verified contract on Etherscan.

3. Download the NFT’s metadata JSON file if available, which contains attributes, image URI, and provenance details for local archival.

4. Save the transaction hash of the original mint or last transfer to confirm chain history and prevent disputes over authenticity.

5. Store all exported data on encrypted offline media—not cloud services or email—to preserve integrity and confidentiality.

Executing the Transfer via MetaMask

1. In MetaMask, switch to the correct network where the NFT resides (e.g., Ethereum Mainnet or Polygon PoS).

2. Click “NFTs” tab, select the desired asset, and click “Send”—MetaMask will auto-detect the contract and prompt for confirmation.

3. Paste the cold wallet’s public address as the recipient. Double-check every character using a checksum-aware validator.

4. Review gas fees and ensure sufficient native token balance in MetaMask to cover the transaction cost.

5. Confirm the transaction in MetaMask and wait for on-chain confirmation—do not close the browser or interrupt the process.

Frequently Asked Questions

Q: Can I send an NFT directly from MetaMask to a Trezor Model T without third-party tools?A: Yes—if Trezor Suite supports the network and the NFT’s contract is recognized, you can initiate the transfer in MetaMask and sign it using Trezor’s hardware interface.

Q: What happens if I send an NFT to a cold wallet address that doesn’t support the token standard?A: The NFT remains on-chain and owned by that address, but may not appear in wallet interfaces; recovery requires manual interaction with the contract using the private key.

Q: Does MetaMask need to stay connected after signing the transfer?A: No—once the transaction is broadcast to the network and confirmed, MetaMask’s role ends; ownership shifts permanently to the cold wallet’s address.

Q: Why does my NFT not show up in Ledger Live after transfer?A: Ledger Live does not index all NFTs by default; users must manually add the contract address under “Add Token” and select “NFT” to view it.