Batch send NFTs

Send a batch of NFTs to a batch of addresses: approve the batch tool once, how the list is filled, how token IDs fill in automatically, and why each line is its own transaction.

7 min readCost:One transaction per line, each paying its own gas; the service fee is charged per batch (same price as sending tokens)Updated 2026-10

NFTs are not like fungible tokens: every token ID in a collection is a separate item, so the list has to say which one goes to whom — a quantity on its own is not enough.

  1. Enter the NFT contractPaste the collection contract address; the page reads the name and symbol, and shows whether the batch tool is approved or not.
  2. Approve the batch toolThe first time you use a collection you have to approve it (setApprovalForAll). One approval covers the whole batch. The approval goes to the batch tool contract, not to any wallet.
  3. Fill in the listOne "recipient,tokenID" per line. CSV or TXT upload works too. If you enter addresses without token IDs, hit Auto-fill token IDs and it fills them from the NFTs the connected wallet holds, telling you how many are still missing.
  4. Check, then sendBefore sending, the tool confirms those token IDs are really in your wallet and points at the line number when one is not. Every line is a separate transaction, so a long list takes a while; when it finishes you get "N transactions in total".

Careful · If the contract has no batch transfer, it is one line at a time

Not every NFT contract implements batch transfers, so this sends one line per transaction. If it stops halfway it tells you how many went through and how many failed; the ones already sent are unaffected.

Related guides