What approval does the tool need?

A single setApprovalForAll per collection, or a per-token approval if you prefer. The approval is separate from the transfers and can be revoked afterwards.

Can I send several NFTs to the same wallet?

Yes. Each row is one transfer, so the same address can appear many times with a different token id each time.

What happens if I do not own a token in the list?

That row is flagged during the review step and skipped, so the rest of the batch still goes through.

Is there a limit on the list length?

Long lists are split into batches, and you confirm the batches as they go rather than signing one impossible transaction.

Send NFTs

Approve the NFT contract once, then paste recipient,tokenID pairs — up to 200 per batch, longer lists are split into multiple transactions.

NFT contract

Enter the NFT contract (ERC-721) you want to send from. Batch sending needs one approval that lets the batch contract move these NFTs.

NFT contract address

Approval lets the batch contract move NFTs from this contract — it does not transfer anything by itself, and you can revoke it later in your wallet.

Recipient and token ID

One per line: recipient,TokenIDEntering addresses only is fine. After upload, or when you choose Auto-fill TokenID, only token IDs actually held by this wallet are used. Up to 200 items per transaction; larger lists are split automatically.

Upload a file (CSV / TXT)

Or drop the file here

CSVTXT

Two columns: recipient, token ID. Addresses alone work too — use “Fill token IDs” below.

0 rows total

还没有可发送的条目

Batch NFT transfer — many NFTs, many wallets, one run

Batch NFT transfer sends NFTs you own to a list of wallets, either one NFT to many addresses or many NFTs to many addresses. It turns a giveaway or a migration into a handful of confirmations instead of one wallet popup per NFT.

NFTs per transaction: up to 200
Input: address,tokenId per line — paste only addresses and the tool fills the IDs in as 1, 2, 3 …
Long lists: split into several transactions of 200 automatically

How it works

1. Pick the network and the collection
ERC-721 and ERC-1155 are both supported; the tool reads the collection so it knows which transfer method to call.
2. Build the recipient list
One row per transfer: address plus token id, and an amount when the collection is ERC-1155. Paste the list or upload a file.
3. Review the ownership check
Rows whose token id is not in the sending wallet are flagged before anything is sent, so a typo cannot burn a batch.
4. Approve and run
One approval per collection, then the transfers run in batches of 200 rows so each transaction stays inside the gas limit.

FAQ

What approval does the tool need?: A single setApprovalForAll per collection, or a per-token approval if you prefer. The approval is separate from the transfers and can be revoked afterwards.
Can I send several NFTs to the same wallet?: Yes. Each row is one transfer, so the same address can appear many times with a different token id each time.
What happens if I do not own a token in the list?: That row is flagged during the review step and skipped, so the rest of the batch still goes through.
Is there a limit on the list length?: Long lists are split into batches, and you confirm the batches as they go rather than signing one impossible transaction.