Does SolBack take a cut of the tokens I send?

No. Batch Send takes nothing — no percentage, no per-recipient charge, no minimum. The same is true of Multi to Multi, Relay Transfer, Batch Query and Wallet Generator. SolBack only deducts a share on the tools that recover SOL for you: 10% of recovered SOL on the main close-accounts flow, or 5% if you use your own referral link, 10% on Burn Mode and NFT Burn Mode, and 20% of recovered rent on the multi-wallet tools — Rent Collector, Batch Asset Migration and Batch Burn.

How many wallets can I send to at once?

There is no fixed cap on the list. SolBack works out how many recipients go into each transaction at run time, from what you are sending and whether the recipients already hold it, so the number is not something you set. It then hands up to ten transactions to your wallet per approval, which turns a long list into a few approval prompts rather than one per recipient.

Why does sending a token to some wallets cost more than others?

Because a wallet that has never held that mint has no token account for it, and one has to be created. Solana charges about 0.00204 SOL as a rent-exempt deposit for that account, paid by whoever creates it — you. Recipients who already hold the token cost only the network fee. Sending plain SOL never triggers this, since SOL needs no token account.

Can I send SOL as well as SPL tokens?

Yes. Batch Send handles SOL and any SPL token in the connected wallet. SOL is the simpler case: no token accounts are involved, so the only cost is the network fee. Pick one asset per run — if you need to distribute two tokens, do two runs.

What happens if one transaction fails part way through?

The transactions are independent, so a failure is contained: recipients in the transactions that confirmed have been paid, and the rest simply did not happen. Nothing sits half-sent and nothing is held in escrow. Check the results, then re-send only the rows that did not go through.

Do I have to hand over a private key to use Batch Send?

Not for Batch Send — it signs through your connected wallet, so the key never leaves it. The tools that operate across many wallets at once do need those wallets' keys, and there the keys stay in your browser's memory for the run and are never uploaded. Wallet Generator likewise creates keys locally in the browser.

Free Solana Multisender: Batch Send SPL Tokens to Many Wallets

One list, one token, a handful of approvals. Paying five hundred wallets should not mean five hundred trips through your wallet's confirm screen.

Updated August 20266 min read

Short answer: a multisender pays many wallets from one wallet in a single pass. Open solback.app, choose Batch Send (One to Many), connect your wallet, pick SOL or any SPL token, paste your list of addresses and amounts, review it, and approve. SolBack deducts nothing from a transfer — no percentage, no per-recipient charge. You pay the ordinary Solana network fee, plus about 0.00204 SOL for each recipient who has no account for that token yet, because Solana itself charges that deposit. That is the entire cost.

What does a Solana multisender do, and when do you need one?

A multisender takes a list of recipient addresses and amounts and packs them into as few transactions as the network will carry, rather than one transfer at a time.

Done manually, a payout of two hundred wallets is two hundred pastes, two hundred amounts and two hundred confirm screens — every one a chance to paste the wrong address, mistype a decimal, or lose your place and pay someone twice. Solana transfers are final: no reversal, no support ticket, no chargeback. The manual route is not merely slow, it is the version most likely to go wrong.

The jobs that push people to a multisender share a shape: one source of funds, many destinations, one deadline.

Airdrops to a snapshot of holders, an allowlist, or the wallets that passed a quest.
Community payouts — contest prizes, bug bounties, raffle winners, quest rewards.
Paying contributors: moderators, translators, artists, node operators, anyone on a roster.
Refunds after a failed mint or a botched sale, where the list is already fixed for you.
Seeding wallets with SOL so a set of accounts can pay their own fees before an event.

How does SolBack's Batch Send work, step by step?

Step 1: Open Batch Send and connect your wallet

Go to solback.app, open the batch tools and choose Batch Send (One to Many). Connect the wallet holding the tokens — Phantom, Solflare, OKX and the other common adapters all work. Connecting shares your public address and nothing more.

Step 2: Pick SOL or an SPL token

Choose what you are distributing. SOL is the simple case: a plain transfer, no token accounts involved. Any SPL token in the wallet can be picked instead. The tool reads the mint's decimals, so the amounts you type are token units rather than raw integers — check them anyway, because decimals are where batch payouts go wrong most often.

Step 3: Paste or import the recipient list

Paste your address and amount pairs, or import them from a file. One row per recipient. Invalid addresses and malformed rows are flagged before anything is signed — the last cheap moment to catch a broken spreadsheet export.

Step 4: Review the totals

Before signing, confirm three numbers: how many recipients are in the list, how much leaves your wallet in total, and how many recipients need a token account created for that mint. That third one is the number people forget, and the only part of a batch send costing real SOL beyond the network fee.

Step 5: Approve the transactions

SolBack groups the recipients into transactions, then passes up to ten transactions to your wallet in a single approval. You review the batch once and sign once; the wallet signs the whole set. Stay on the page while they broadcast.

Step 6: Confirm the results

Each transaction settles independently. When the run finishes, check the results and re-send only the rows that did not confirm — nothing to unwind, nothing in escrow.

What does a batch send actually cost?

SolBack takes nothing from a transfer. Not a percentage, not a flat fee per recipient, not a minimum. The transfer tools are genuinely free to use.

We are specific because it is not true of every tool on the site, and we would rather draw the line ourselves than let you find it at the confirm screen. SolBack funds itself from the tools that recover SOL for you. Tools that only move your own money take nothing.

Tool	What it does	What SolBack deducts
Batch Send (One to Many)	Pays a list of wallets from one wallet	Nothing
Multi to Multi	Pays many recipients from many senders	Nothing
Relay Transfer	Moves funds between wallets	Nothing
Batch Query	Reads balances across wallets	Nothing
Wallet Generator	Creates keypairs locally in the browser	Nothing
Close empty accounts	Recovers rent from your own wallet	10% of recovered SOL, or 5% with your own referral link
Burn Mode / NFT Burn Mode	Burns worthless tokens and NFTs for their rent	10% of recovered rent
Rent Collector / Batch Asset Migration / Batch Burn	Recovers rent across many wallets at once	20% of recovered rent

Why do free multisenders still cost SOL?

Because part of the cost is not a fee at all — it is a deposit the Solana protocol requires, and no website can waive it.

An SPL token lives in a token account, one per wallet per mint. If a recipient has never held the token you are sending, that account has to be created, and Solana charges roughly 0.00204 SOL to make it rent-exempt. Whoever creates it pays, which in a batch send is you. Recipients who already hold the token cost nothing extra.

Recipients needing a new token account	Rent you pay to create them
10	0.02039 SOL
50	0.10196 SOL
100	0.20393 SOL
500	1.01964 SOL

That SOL is not burned or pocketed. It sits in the account it created, and the recipient can reclaim it later by closing the account once the balance is zero. Solana rent explained covers where the money goes and how it comes back.

Sending SOL skips this entirely. SOL needs no token account, so a batch of plain SOL transfers costs only the network fee — no per-recipient rent, however many wallets are new to you.

How many recipients fit into one transaction?

There is no fixed number, and be wary of any tool that quotes you one. A Solana transaction has a hard size limit, and each recipient adds bytes to it — more when that recipient also needs a token account created, since that adds a whole extra instruction.

SolBack decides the number at run time rather than exposing a setting. It checks a sample of your list to see whether recipients already have an account for that mint, and packs fewer per transaction when accounts have to be created — so a run of addresses that all hold the token already packs more densely than a run of brand-new wallets. Plain SOL, which needs no token account at all, packs the most densely of the three.

Because that check is a sample rather than a full pass, a list that starts with existing holders and ends with new wallets is the awkward case. If a run like that reports failures, split it: send to the existing holders in one pass and the new wallets in another.

What you do notice is the signing. Your wallet is handed up to ten transactions per approval, signed together rather than one prompt at a time. A list long enough to need thirty transactions is three approvals, not thirty.

What should you check before you hit send?

Five minutes of checking is cheaper than an irreversible mistake. Before the first approval:

Validate the addresses. A well-formed address can still be the wrong one. Spot-check rows against their source, and take the invalid-row warnings seriously rather than deleting them to make the list load.
Check the decimals. Confirm that the total shown matches what you expect to send. An off-by-one on decimals is a 10× payout in whichever direction hurts.
De-duplicate. Merged snapshots love to repeat an address. The tool will happily pay it twice.
Run a test send. Two or three rows, small amounts, your own wallets. Confirm they land before committing the real list.
Fund the fees. Keep enough SOL for the network fees and for every new token account, or the run stalls part way through.
Avoid exchange deposit addresses. Many need a memo or tag and will not credit tokens arriving from a batch. Send to self-custodied wallets.

Transfers cannot be undone. Once a transaction confirms, the tokens belong to the recipient. There is no reversal on Solana and no admin who can claw them back — not us, not your wallet, not the network. Test first.

When should you use Multi to Multi instead?

Batch Send has one sender. When the funds are spread across several wallets that becomes a constraint: you would consolidate first, then distribute, paying fees twice and leaving a trail through one hub address.

Multi to Multi is the answer for that shape — many senders paying many recipients in one run, with each source paired to its destinations. Like Batch Send, it deducts nothing. It is the tool for distributing from a set of funded wallets without funnelling everything through one address first.

Batch Query reads balances across a list of wallets before you commit to anything, and Wallet Generator creates fresh keypairs in the browser. Alongside them sit the rent-recovery tools — Rent Collector, Batch Asset Migration and Batch Burn, which sweep across your wallets and take 20% of the rent they recover.

Anything that works across multiple wallets needs those wallets' private keys to sign. In SolBack those keys stay in your browser's memory for the run and are never uploaded anywhere — and Batch Send itself never needs one, since it signs through your connected wallet.

Send to your whole list in one pass

Batch Send handles SOL and any SPL token, packs the recipients automatically, and takes nothing on top. You pay Solana, not us.

Open Batch Send Free to use. Transfers carry no SolBack deduction — you pay the network fee plus about 0.00204 SOL for each recipient who needs a token account created.

Still have questions about batch sending on Solana?

Does SolBack take a cut of the tokens I send?: No. Batch Send takes nothing — no percentage, no per-recipient charge, no minimum. The same is true of Multi to Multi, Relay Transfer, Batch Query and Wallet Generator. SolBack only deducts a share on the tools that recover SOL for you: 10% of recovered SOL on the main close-accounts flow, or 5% if you use your own referral link, 10% on Burn Mode and NFT Burn Mode, and 20% of recovered rent on the multi-wallet tools — Rent Collector, Batch Asset Migration and Batch Burn.
How many wallets can I send to at once?: There is no fixed cap on the list. SolBack works out how many recipients go into each transaction at run time, from what you are sending and whether the recipients already hold it, so the number is not something you set. It then hands up to ten transactions to your wallet per approval, which turns a long list into a few approval prompts rather than one per recipient.
Why does sending a token to some wallets cost more than others?: Because a wallet that has never held that mint has no token account for it, and one has to be created. Solana charges about 0.00204 SOL as a rent-exempt deposit for that account, paid by whoever creates it — you. Recipients who already hold the token cost only the network fee. Sending plain SOL never triggers this, since SOL needs no token account.
Can I send SOL as well as SPL tokens?: Yes. Batch Send handles SOL and any SPL token in the connected wallet. SOL is the simpler case: no token accounts are involved, so the only cost is the network fee. Pick one asset per run — if you need to distribute two tokens, do two runs.
What happens if one transaction fails part way through?: The transactions are independent, so a failure is contained: recipients in the transactions that confirmed have been paid, and the rest simply did not happen. Nothing sits half-sent and nothing is held in escrow. Check the results, then re-send only the rows that did not go through.
Do I have to hand over a private key to use Batch Send?: Not for Batch Send — it signs through your connected wallet, so the key never leaves it. The tools that operate across many wallets at once do need those wallets' keys, and there the keys stay in your browser's memory for the run and are never uploaded. Wallet Generator likewise creates keys locally in the browser.