Multi Sender

Multi Sender sends SOL or an SPL token out to a whole list of recipient wallets in a single run on Solana mainnet. You paste or upload the list of addresses, pick how each address gets its amount, and after one approval in your own wallet the tool sends the transfers in batches.

Multi Sender j.tools/en/tools/multi-sender

Open tool

Multi Sender 0.001 SOL Platform fee

Open tool

Platform fee

0.001 SOL per recipient

Network fee, rent and transaction value are separate.

When this tool fits

#when-this-tool-fits

• You are running an airdrop or a community and reward distribution. Working from a holder list? The Airdrop to holders guide walks the full flow.
• You need batch payouts to many wallets at once.
• You are handing out presale or test allocations from a fixed list.
• You want to send one token to a known set of recipients instead of clicking through transfers one by one.

Before you start

#before-you-start

• A connected wallet (how to connect), or your own imported wallet if you sign with a private key.
• Enough balance to cover every recipient amount plus the platform fee, the network fee, account rent for any new SPL recipients, and a small reserve of about 0.001 SOL that comes back when the send ends.
• For an SPL token: the token’s mint address, picked with the built-in token selector. Your sending wallet must already hold that token.
• Your list of recipient addresses, ready to paste, upload as CSV, or add by hand.

Use only short-lived operational wallets; never enter a seed phrase or a long-term wallet key.

Use

• Only short-lived operational wallets

Never enter

• A seed phrase
• A long-term wallet key

How to use it

#how-to-use-it

1. Pick the token to distribute

   Choose the wallet source at the top right: your connected wallet, or Local Signer with a private key. Under Token, open the picker and choose SOL or any SPL token your wallet holds.

2. Add recipients and choose distribution mode

   Click Import Wallet to paste addresses or upload a file, or use Add Row. Under Distribution, choose Equal, Random, or Percentage and set the total or the range. Every wallet then sits in one table with its amount, its share of the total and any problem with the row. If the list has problems, use Clean up list to drop invalid, duplicate, and self-address rows.

3. Review and send

   The summary shows total recipients, what recipients receive, the platform fee, the network fee, the wallet approvals, account rent for any new SPL recipients, and the total leaving your wallet. Click Send to All, approve once in your wallet, and keep the tab open until the send finishes. A result window then shows how many wallets received it, what was sent and the SOL that left your wallet.

Key settings

#key-settings

• Token type: Send native SOL or an SPL token. There is no separate switch: the token you pick decides it. The choice changes which fees and rent apply, since SPL deliveries may create recipient accounts.
• Token mint: The SPL mint address, required only for SPL sends. Pick it with the built-in token selector, or let a ?token= link fill it for you. Your sending wallet must already hold this token.
• Recipients: Your list of addresses. Every address must be a valid Solana pubkey and every amount above zero. Paste them or upload a file through Import Wallet, or add rows by hand. The import reads only the address on each line; amounts come from the distribution mode or from what you type into a row.
• Distribution mode: How per-recipient amounts get worked out. Equal splits a total evenly across all rows. Random gives each row a random amount between a min and a max you set. Percentage gives each row a random weight inside a min and max percentage band, then splits the total by those weights, so the band shapes the spread rather than fixing any row’s share. In Equal and Percentage, a row whose amount you typed keeps it, and the total skips that row.
• Max helper: Shown in Equal and Percentage. For SOL it fills your balance minus the platform fee, the network fee, and a 0.002 SOL margin. For an SPL token it fills your whole token balance, so keep enough SOL aside for the fees and any account rent.
• Wallet table: Search by address, and filter to All, Issues or Locked rows. Lock this amount on a row keeps its figure out of the distribution. Tick rows to open the bulk bar: Set amount gives the selected rows one amount, Lock locks them and Remove deletes them. Use the total everywhere releases hand-typed amounts back to the distribution.
• Clean up list: Appears when the list has invalid, duplicate, or self-address rows, and strips them in one click, keeping the first copy of a duplicate. Those rows block the run, so clean them up or remove them by hand before you send.
• Program addresses: A row that points at a program or system address (the System Program, a token program, a sysvar) is marked Program address, not a wallet and keeps the send closed, because nothing sent there reaches a person. Remove it to send.
• Sender private key: Used only on the private-key path, for self-custody users entering their own key. The connected-wallet path uses your wallet adapter and never touches your wallet’s key.

Fees and costs

#fees-and-costs

Caution

About fees. Every action has two costs: the Solana network fee paid to validators, and the J Tools platform fee. The platform fee always shows in the app before you confirm, and nothing is charged until you sign. Fees can change over time, so trust the in-app summary rather than a number you saw once.

Cost	Amount
J Tools platform fee	0.001 SOL per recipient
Solana network fee	Paid to validators during the transaction; shown in the live summary.
Sender reserve	About 0.001 SOL held by the one-time sender, back in your wallet when the send ends.
Rent and transaction value	Shown separately when required; not part of the platform fee.

How it works

#how-it-works

• It sends with one approval. Your wallet signs one funding transaction to a one-time sender, a fresh wallet made in this browser tab and saved in the browser’s storage before anything is signed. The funding carries the SOL or tokens to send, the platform fee, network fees with some slack, rent for any new token accounts and a small reserve of about 0.001 SOL. The tab then signs and sends every batch from that sender with no further prompt: 18 recipients per transaction for SOL, 8 for a token.
• For SPL tokens, each recipient gets an idempotent associated-token-account create instruction packed alongside the transfer. It does nothing when the account already exists. When it is missing, that small account costs a one-time rent, read from the chain and paid out of the funding, and is what lets a brand-new holder receive the token.
• The funding transaction is pre-simulated before your wallet shows it, and the network checks each batch as it is sent, so a batch that would fail is reported on its rows instead of landing.
• Each batch carries the platform fee for its own recipients, so a batch that does not land charges no fee. When the send ends, whatever the sender did not spend (SOL, tokens and the reserve) goes back to your wallet. Keep the tab open while it sends; the page asks before you close it. If the tab closes mid-send, open the tool again in the same browser with the same wallet once 10 minutes have passed since the send started, and what the sender still holds comes back to your wallet. Your next send there runs the same check first.
• A Token-2022 token with a transfer fee or a transfer hook goes out the other way: your wallet approves each batch on its own, 6 recipients per transaction, each one pre-simulated before you sign. On the private-key path, used only by people who paste their own key, each recipient gets its own transaction signed with that key, with no pre-simulation and a limit of 1000 recipients, and the platform fee goes out after the sends as one transfer covering only the recipients that were paid.
• Every row in the list is sent as pasted; an address paid in an earlier send is not skipped. Within a run, a batch whose result was unclear is checked on the chain before it is offered again, so Retry failed never pays the same recipient twice.

How to use it

1. 1 Pick the token to distribute
2. 2 Add recipients and choose distribution mode
3. 3 Review and send

How it works

One approval, the tab sends the rest no fee for a wallet it did not reach

1. 1 Recipients grouped into batches batch
2. 2 One approval funds a one-time sender one-time sender
3. 3 18 per SOL batch, 8 per token batch 18 SOL · 8 SPL per tx
4. 4 SPL: missing ATA created, you pay rent createAssociatedTokenAccountIdempotent
5. 5 Platform fee: 0.001 SOL per recipient 0.001 SOL × N
6. 6 Network checks each batch as it is sent preflight
7. 7 What is left comes back to your wallet sweep

Sent to every recipient, status per row mainnet

Multi Sender · circles are the steps in How to use it, squares the steps in How it works

Before you sign

#before-you-sign

Check the live summary before signing. The app is the current source of truth for amount, fee and route.

Common issues

#common-issues

• Send is blocked by invalid rows. Invalid, duplicate, or self-address rows stop the run. Duplicates would double-pay and self-sends just waste fees, so run Clean up list first.
• Amount too small (SOL). A SOL recipient whose address holds nothing yet needs at least the rent-exempt minimum shown in the tool, read from the chain, to open its account. Raise the per-address amount. An address that already holds SOL can take any amount.
• Not enough balance. The page checks your balance against what the send needs before you start, which is a little more than the total leaving your wallet because it keeps a margin for fees. It warns while you set up and blocks the send, SOL or token, until the balance is there. Balances can still move during a long run, so lower the total or use the Max helper.
• A row is a program address. The send stays closed while a row points at a program, a token program or a sysvar instead of a wallet. Remove that row.
• A few rows failed. Network hiccups happen mid-run. The result window and the button both offer Retry failed; click it and only the rows that did not succeed go out. Download CSV receipt saves the run, and New send starts over.
• The tab closed mid-send. What the one-time sender still holds goes back to your wallet when you open the tool again in the same browser with that wallet connected, at least 10 minutes after the send started. A younger sender is left alone, since its run may still be going in another tab.

Practical tips

#practical-tips

• Stage from a holder snapshot. Pull a recipient list from a token’s holders, then paste or upload the addresses into Multi Sender for a clean airdrop. The Airdrop to holders guide covers the end-to-end path.
• Vet the list before you pay it. Run the recipient addresses through Wallet Scope first and strike the rows that should never be paid. Plan around its limits on a long list: 500 addresses per run, funder clusters for the first 300, so a 900-recipient list is not fully checked after one pass.

Related tools

#related-tools

• Many-to-Many Transfers
• Batch SOL and Token Collector
• Solana Holder Booster
• Wallet Scope: Bulk Wallet Analyzer

Note

About wallet warnings. Some tools bundle several instructions into one transaction, for example creating a token and its metadata together. Phantom can show a caution banner for these transactions, and where the tool tells you to expect one, it does not mean something is wrong. Read what you are signing, then approve if it matches what you set up. If a warning appears that the tool did not mention, decline it and tell support.

Tip

J Tools is non-custodial. We never store your wallet’s private keys and never ask for your seed phrase. Every transaction you approve in a connected wallet is signed inside that wallet, and its key never reaches our servers. A few multi-wallet tools do let you paste private keys for throwaway hot wallets, which stay in your browser tab and sign there. A few bots that keep running after you close the tab (Holder Booster, Maker Bot, Bump Bot, Flash Volume’s Auto bot and Auto Freeze) sign from a wallet J Tools creates for that bot or run and keeps encrypted on our server. It is never a wallet you keep, it signs only for that bot, and what is left goes back only to your wallet. For Auto Freeze it is a session key, the second signer of a 1-of-2 multisig, and your wallet can take the authority back alone. Never paste a key tied to long-term holdings, and if a page ever asks for your seed phrase, stop and close it.

Help

#help

Fees and safety · All tools · Support