Send to a thousand
wallets at once.

Counted from the chain. Not live, updated once a month.

1. 01.

   How much does it cost?

   0.001 SOL per recipient plus Solana network fees — around 0.000015 SOL per signature at the compute price these transactions request, priced against the cluster before you sign. If a token recipient needs a new associated token account, its rent deposit is added: the account size is read from the mint you selected, including any Token-2022 extensions that make it larger, and the rent for that size comes from the cluster.

2. 02.

   How many wallets can I send to?

   There is no list limit. The browser divides recipients into batches of at most 5, and every batch is signed individually. Where your wallet supports it you can approve up to 10 of those batches per request — a 350-recipient list is 70 transactions and 7 approvals rather than 70 — or keep one request per transaction. Confirmed batches remain settled if a later one fails or you stop.

3. 03.

   What assets are supported?

   Native SOL, standard SPL tokens, and Token-2022 tokens whose extensions have been measured against the deployed programs — close authority, permanent delegate, metadata and group pointers, the group and membership state those pointers refer to, and metadata stored inline in the mint. Because inline metadata is written at whatever length the issuer chose, a mint is also refused if its extension area runs past the size a transfer has been measured against, which is several times what an ordinary name, symbol and URI occupy. Mints that charge a transfer fee are sendable: the rate and its per-transfer cap are read from the mint when the send is planned, and the sheet shows how much the fee will take in total and how much will reach recipients between them, before you sign. Each transfer states its own expected fee on chain, so if the mint's terms change in between, the transfer fails rather than quietly delivering less. The fee is not paid to sØl or to the mint's issuer at the time of transfer: it is held back inside each recipient's own token account, and can only ever be moved from there by whatever address the mint names as its withdraw-withheld authority — which may be nobody at all, in which case it stays where it is. Token-2022 mints carrying transfer hooks, confidential transfers, pausing, interest, scaled amounts, non-transferability or a frozen default state are listed but not sendable, each with its reason: they change what a transfer costs or does in ways that cannot be shown in advance, and this tool refuses what it has not measured. Recipient token accounts are created automatically when needed.

4. 04.

   Which wallets work?

   Any wallet that implements the Solana Wallet Standard can connect, including Phantom, Solflare, and Backpack. The wallet remains the signer for every batch.

5. 05.

   Is the recipient list uploaded?

   No. Pasted rows and CSV contents are parsed and held in browser state. Your configured Solana RPC provider still receives the public account queries needed to read balances and determine which recipient token accounts exist.

6. 06.

   What happens if a transaction fails?

   Each batch is independent. A failed batch shows its error while earlier confirmed batches remain final and irreversible. Review the progress and Solscan links before retrying anything.

7. 07.

   What stops the same list being sent twice?

   Within the same browser profile, and only where the browser supports cross-tab locking, one run at a time: a send in progress holds a lock that other tabs of the same browser cannot take, and a second tab pressing send is told why nothing happened. A browser that cannot take that lock is refused the send outright rather than sent unguarded, and told so. That is the whole of it. Nothing links one browser to another, one device to another, or one run to the next — the tool keeps no record of what has already been paid, so a list sent again from another browser, another device, or the same tab after a run has finished will pay every recipient again. Check the previous run's Solscan links before repeating a send.

8. 08.

   Can I undo a wrong address?

   No. Solana transfers are irreversible once confirmed. You are responsible for checking every recipient and amount in the preview before approving each signature.

9. 09.

   Can a program address receive tokens?

   Yes. Recipient validation intentionally allows valid off-curve Solana public keys, including PDAs, because programs can legitimately control token accounts. Only send tokens to a PDA when its program provides an instruction that can move them from the associated token account; otherwise they may be permanently unreachable. The System Program address itself is rejected.

bulk sends are irreversible · recipient lists remain in browser state · no share card is created because a send is not a recovery receipt