Airdrop tokens to holders

An airdrop is two jobs back to back. First you build a list of who holds your token right now. Then you send the airdrop amount to every wallet on that list. J Tools splits this across two tools that hand off cleanly: Holder Snapshot exports the recipient list, and Multi Sender distributes to it. Wallet Scope sits between them, because every address you leave on the list is an address you pay for.

Run the airdrop in the app →

If you already have your recipient list, skip the first two steps and start at Vet the list.

Before you start

#before-you-start

A connected wallet (how to connect).
The mint address (CA) of the token whose holders you want to reach.
The token you are airdropping, already sitting in your sending wallet. It can be the same token or a different one.
Enough SOL to cover the platform fee, the network fees, and account rent for any recipient that does not yet hold the token you are sending.

The full flow

#the-full-flow

Snapshot the current holders

Open Holder Snapshot, pick your token with the selector, and run the scan. The scan is read-only and moves nothing. It groups every token account by owner and returns a ranked list with each holder’s balance and share of supply. Set a top-holder limit that covers everyone you intend to reach. If you are airdropping to your own token’s holders, it pays to verify the token is safe first so you know exactly what you are distributing.

Open Holder Snapshot →
Export the recipient list

Download the snapshot with Export Excel. Each row of the spreadsheet carries the holder address and balance, exactly what the sender needs. The header stamps the mint and the generated-at time, so you know which moment this list represents.
Vet the list before you pay for it

A snapshot returns every address holding the token, and a fair number of them are not people. Pools, program accounts, burn addresses, your own treasury, and wallets holding rounding dust all sit in that export, and each one you fund costs you a token account’s rent for nothing.

Paste the addresses into Wallet Scope and run the free scan. Up to 500 wallets per run, no wallet connection required. Every row comes back with its SOL and token balances, its age, and an on-chain label when the address is an LP pool, a program, a burn address, or an exchange. The Clusters view groups wallets by who sent them their first SOL, which is how you spot a block of wallets funded from one source, including your own bundle if you launched with one.

Note which addresses you do not want to fund; you will strip those rows out of the snapshot list in the next step. If your snapshot runs past 500 rows, vet it in slices of 500.

Open Wallet Scope →
Shape the list for sending

Decide how much each wallet gets. For a flat airdrop, keep just the address column and let Multi Sender split a total evenly. For a pro-rata airdrop weighted by holdings, format each line as recipient,amount using the snapshot balances. Drop the rows you flagged in the scan, along with anything else you do not want to pay, like your own treasury or a burn address.
Load it into Multi Sender

Open Multi Sender and choose SOL or your SPL token. The importer does not read .xlsx files, so copy the address and amount rows out of the spreadsheet and paste them in, or save the sheet as a CSV first and upload that. Run Clean up list to drop invalid, duplicate, and self-address rows before anything goes out.

Open Multi Sender →
Set amounts and review the summary

Pick a distribution mode (Equal, Random, or Percentage) or keep the per-row amounts from your file. Read the summary: total recipients, total leaving your wallet, the platform fee, the network fee, and rent for new recipient accounts. This is your last checkpoint before signing.
Send in batches

Click Send to All. The run goes out in chunks you approve in your wallet, and each row reports success or failure as it lands.

Snapshot timing matters

#snapshot-timing-matters

Batching, gas, and rent

#batching-gas-and-rent

Multi Sender does not push the whole list in one giant transaction. It splits the work into batches, and a very large snapshot is easiest to run as separate lists, one after another.

What	Why it works this way
Batched signing	A connected wallet approves the run in chunks instead of one oversized transaction. Each SPL batch covers a handful of recipients so it stays under Solana’s transaction size limit and confirms reliably.
Network fees	Each batch pays its own small network fee. More recipients means more batches, so budget SOL for the whole list, not a single transfer.
Recipient rent	Any wallet that does not already hold the token you are sending needs a new token account, and that account costs rent. The summary adds this up for you before you sign.
SOL minimums	For a SOL airdrop, every recipient amount has to clear the rent-exempt minimum the tool shows. Anything smaller cannot fund a fresh account, so the tool blocks it.

Verifying delivery

#verifying-delivery

Each recipient row updates live to pending, success, or failed. A successful row links straight to its transaction on Solscan, so you can spot-check any payout the moment it lands.

#related