Airdrop Tool
The easiest way to run a Token Airdrop
Run a token airdrop to thousands of wallets on ten networks, with no coding and no scripts.
Select Blockchain
No active airdrop yet
Configure the recipients above and click Send Airdrop. Transaction progress will appear here.
Smithii in numbers
+12,000
Tokens Launched
+3,360,000
Makers Generated
+576,000.32
Volume Generated (SOL)
+9,000
Users Served
+12,000
Tokens Launched
+3,360,000
Makers Generated
+9,000
Users Served
+576,000.32
Volume Generated (SOL)
Audited
Verify on-chain
Building Tools since 2023
Airdrop Tool Features
An airdrop is three jobs, not one: build the recipient list, send to all of it without paying per-transfer overhead, and be able to show afterwards which wallets received what. This tool covers all three — take a holder snapshot or upload your own CSV, send in batches from your own wallet, and keep a per-run record of every confirmed and failed transfer.
The list comes first
Most airdrops go to people who already hold something. Take a snapshot of a token or an NFT collection and its export drops straight into the recipient field — or paste your own CSV of addresses and amounts.
Send now or schedule it
On Solana an airdrop can be scheduled instead of sent immediately, which is what you want when the distribution has to land at a specific moment rather than whenever you happen to be at the keyboard.
A record of what landed
Every run keeps its own log: which wallets confirmed, which failed and the signature for each batch. Failed recipients retry without re-sending the ones that already went through.
Why use Airdrop Tool?
Snapshot the holders and airdrop to them without leaving the tool.
Ten networks from one form, so the airdrop follows the token rather than the other way round.
A different amount per wallet, straight from a CSV.
Every run logged, with the signature for each batch.
Non-custodial: tokens move from your wallet to the recipients in a transaction you sign.
Tools that make you
Efficient
Discover other of our most used tools that will make your life 10x easier.
If you need more help contact our team
Got questions?
If you need more help contact our team
A fee per recipient wallet, charged in the network's own currency, plus that network's gas. The table below is the fee on each one. The gas is what really moves the total — the same 5,000-wallet airdrop can differ by two orders of magnitude between networks.
| Network | Fee per wallet | Schedule | Explorer |
|---|---|---|---|
| Solana | 0.001 SOL | Yes | Solscan |
| Ethereum | 0.0001 ETH | No | Etherscan |
| Base | 0.0001 ETH | No | BaseScan |
| BNB Chain | 0.001 BNB | No | BscScan |
| Polygon | 0.5 POL | No | PolygonScan |
| Arbitrum | 0.0001 ETH | No | Arbiscan |
| Avalanche | 0.025 AVAX | No | Snowtrace |
| Blast | 0.0001 ETH | No | BlastScan |
| Robinhood | 0.0001 ETH | No | Blockscout |
| Sui | 0.078 SUI | No | SuiScan |
From a snapshot, usually. If you are rewarding holders of a token or an NFT collection, take a holder snapshot and use its CSV export directly. If the list comes from somewhere else — a form, a whitelist, a Discord export — paste it in as address and amount pairs.
Both work — each CSV row carries its own figure — so the question is what you are rewarding. A flat amount treats everyone on the list equally, which suits a whitelist or a community reward and cannot be gamed by splitting a balance across wallets. A proportional share weights by holdings, which suits a dividend or a loyalty distribution but hands most of the supply to the largest holders. Proportional airdrops usually want a floor and a cap so the tail still receives something and one whale does not take half.
They are the same machinery seen from two ends. "Multisender" describes what the contract does — one token to many addresses in batched transactions. "Airdrop" describes why you are doing it. This page is organised around the campaign; if you want the mechanics, the multisender page covers batching in more detail.
There is no hard cap. The list is split into batches automatically — 1,000 recipients per transaction on EVM so the batch cannot exceed the block gas limit, and a smaller number on Solana where the limit is transaction size. Airdrops of tens of thousands of wallets run fine; they just take more batches.
Only the failing batch is affected. Confirmed batches stay confirmed, the tokens for the failed ones never left your wallet, and the run log lists exactly which recipients still need sending so you can retry just those.
No. This is a push airdrop — the tokens arrive in their wallets without any action on their part. If you would rather they claimed it themselves, which caps your cost at the number of people who actually want the token, that is a claim site instead.
A push airdrop and a claim airdrop are different products
Pushing means you pay to deliver tokens to every wallet on the list, whether or not the owner ever wanted them. Claiming means you publish a list and let people come and pay their own gas to take their share. Pushing is better when the list is small, when you want the tokens visible in wallets immediately, or when the recipients are unlikely to go looking. Claiming is better for large lists where most of the addresses will never engage — you only pay for the ones who show up. The cost curves cross surprisingly early, so it is worth doing the arithmetic before committing to either.
The recipient list is where airdrops go wrong
The send is the easy part. What breaks airdrops is the list: addresses captured from a form with a typo, exchange deposit addresses that will never credit the user, contracts that cannot receive tokens, or a snapshot taken at a moment that lets someone buy in the hour before and qualify. Taking the snapshot from the chain rather than from a spreadsheet removes most of that, and choosing the block deliberately removes the rest.
Why the network matters more than the tool fee
For a 5,000-wallet airdrop the per-wallet tool fee is a rounding error next to gas. On Ethereum L1 every recipient pays for a storage write at L1 prices; on an L2 or on Solana the same distribution costs a fraction of it. If the token is not yet deployed and the airdrop is a large part of the plan, that consideration belongs at the token creation stage, not after. If it is already deployed, batching is what you have — which is what this tool does.