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 the tool builds the transfers in batches that you sign from your own wallet.

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, and account rent for any new SPL recipients.
• 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, your connected wallet or a private key. In Token Config, 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. In Advanced Send Settings, choose Equal, Random, or Percentage and set the total or the range. 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, account rent for any new SPL recipients, and the total leaving your wallet. Click Send to All and approve each batch in your wallet as it comes up.

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.
• 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.
• 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 a raw 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.
Rent and transaction value	Shown separately when required; not part of the platform fee.

How it works

#how-it-works

• It builds batched transfer instructions. Rather than one giant transaction, the tool groups recipients into batches sized to stay within Solana’s transaction limits, then asks you to sign them in order. A SOL batch starts at 18 recipients per transaction and an SPL batch at 6, since a fatter token batch is exactly what trips a wallet’s “could be malicious” warning, and on these normal batches the size shrinks automatically if the first batch fails its simulation. For 7 to 3000 recipients the tool first tries the address-lookup-table route, which packs 50 SOL or 30 SPL recipients per transaction, and falls back to normal batches if that route cannot be built.
• 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, paid from your wallet, and is what lets a brand-new holder receive the token.
• On the connected-wallet path it pre-simulates each batch before asking you to sign, so a batch that would fail is caught and surfaced as a plain message instead of a wallet warning.
• You sign every batch in your own wallet, one approval per batch. The platform fee is the last instruction of each batch and covers only that batch’s recipients, so a batch that fails charges no fee. On the private-key path, used only by people who paste their own key, the run’s whole platform fee goes out first as one standalone transfer, then each recipient gets its own transaction, with no pre-simulation and a limit of 1000 recipients.
• The browser remembers which recipients this wallet paid in the last 24 hours. Sending the same list again skips them with a notice and a Send to them again button. This only works in the same browser.

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

Transfers are batched each batch signed in your wallet

1. 1 Recipients grouped into batches batch
2. 2 Starts at 18 per SOL batch, 6 for SPL 18 SOL · 6 SPL
3. 3 Lookup table route: 50 / 30 per batch address-lookup-table
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 Each batch pre-simulated before signing simulateTransaction
7. 7 You sign the batches in order batch 1 → N

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). Each SOL recipient needs at least the rent-exempt minimum shown in the tool to create its account. Raise the per-address 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 for SOL and blocks an SPL send until the SOL is there. Balances can still move during a long run, so lower the total or use the Max helper.
• A few rows failed. Network hiccups happen mid-run. The button changes to Retry failed; click it and only the rows that did not succeed go out.

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. Holder Booster is the one tool that hands a key to our worker: the fresh distributor wallet it creates for each run, sent encrypted. 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