Batch send tokens

Three ways to build the recipient list, fixed vs random amounts, approvals and retrying a failed batch, and how to confirm every address actually received its tokens.

8 min readCost:0.01 per batch (in the native coin of that chain, 0.000001 on testnet) plus gas; up to 200 addresses per batchUpdated 2026-10

Sending tokens to a list is what this tool does: one "address,amount" per line, all of it goes out in a single transaction. NFTs have their own tool, Batch send NFTs, and if all you want is a higher holder count with no specific recipients, use Grow holders.

  1. Build the listOne "address,amount" per line; commas or spaces both work. You can also upload a CSV or TXT file — there is a template on the page. Duplicate addresses are not an error, they are removed automatically.
  2. Choose what you are sendingNative coin (BNB/ETH) is the simplest. An ERC-20 token needs one approval first, and you can approve only the amount this run needs.
  3. Set the amountsA fixed amount is fine for a campaign. If you want the chain history to look natural, use a random range so every address gets a different number — identical amounts across a long list are a fingerprint in themselves.
  4. Test with a few addressesSend to 3 to 5 of your own addresses first, confirm the tokens arrive and the amounts in your wallet are right, then run the full list.
  5. Send it and reconcileA list over 200 addresses is split into batches automatically — one transaction per batch, and you confirm each one before it goes. The fee is charged per batch, including a batch that fails. Afterwards paste the same list into Batch balance check to see who is missing.

Careful · Three traps worth knowing

An exchange deposit address in the list may be credited as a deposit and arrive late; an oversized token approval is easy to forget and rarely gets revoked; and funding the same address set day after day makes the cluster obvious on-chain.

Related guides