How to Collect SOL and Tokens from Multiple Wallets into One

Short answer: open solback.app, go to Batch Collector (Many to One), paste the private keys of the wallets you want to empty — one per line — and enter the single destination address. SolBack scans the wallets 10 at a time, shows what each one holds, then sweeps SOL or one chosen token into that address. The keys stay in your browser's memory and are never uploaded. The transfers themselves take nothing: you pay only the Solana network fee. Wallets with no SOL left for gas can be covered by a single funded payer wallet.

Why does SOL end up scattered across a dozen wallets?

Because Solana makes wallets free to create, and almost every strategy on it rewards having more than one.

Airdrop farming is the obvious case: a spread of addresses, each interacting with a protocol, each left with a little SOL. Trading bots get their own wallets so one bad key does not sink everything. Burners get spun up for a mint, or a site you did not want to touch with your real wallet. Then the season ends and the addresses go quiet.

What is left in each one is rarely worth a manual transfer on its own: some dust SOL, a token nobody trades any more, and a set of empty token accounts each still holding its 0.00204 SOL deposit. Across a whole farming set it stops rounding to nothing.

The manual route is the real cost — importing each key into a wallet extension, switching accounts, sending, switching back. Batch tooling exists because the job is repetitive, not because it is hard.

What actually happens to your private keys when you paste them in?

This deserves to come before the instructions, not after them.

In SolBack's multi-wallet tools, each line you paste is decoded in your browser — base58 or the Solana CLI [1,2,3...] array format both work — and turned into a keypair held in memory. Transactions are built and signed locally, then the signed transaction goes to an RPC node. The key is never sent to a server and never written to storage; close the tab and it is gone. The Wallet Generator works the same way, creating new keys in your browser.

That is the technical answer, and it is worth being blunt about what it does not cover. Pasting a private key anywhere is inherently sensitive. The model is only as strong as the machine and browser running it: a compromised laptop, a malicious extension or a lookalike domain defeats it entirely.

If a wallet still matters to you, do not import it here. Connect it normally on the main page, where the key never leaves the extension.

How do you check what those wallets hold before touching a key?

Start read-only. Batch Query takes public addresses, not private keys, and tells you what is in them.

Pick a query type — reclaimable rent, SOL balance, or one specific token — paste one address per line, and rows stream in as they resolve, with CSV export at the end. There is no wallet connection and nothing to sign.

Do this before any sweep. Wallets that turn out to be genuinely empty never need their keys imported at all, and you learn which ones carry enough rent or balance to justify the run.

How do you collect SOL from multiple wallets, step by step?

Step 1: Open Batch Collector (Many to One)

Go to solback.app, open the batch tools, and choose Batch Collector (Many to One). This tool runs on imported keys rather than a connected wallet, so there is nothing to connect first.

Step 2: Import the private keys

Click Import Wallets and paste one key per line; both base58 and the array format are accepted. Lines that cannot be parsed are skipped and counted rather than silently dropped — that is how you catch a truncated paste.

Step 3: Let the scan run

SolBack derives each address from its key and reads it on-chain, working through the list 10 wallets at a time so a long list does not get rate-limited by the RPC node. Each row fills in with its address, SOL balance and token accounts. Nothing is signed during the scan.

Step 4: Pick the token and the destination

Leave the token field empty to sweep SOL, or paste a mint address to sweep one specific token. Then enter the destination address, and check it character by character — an on-chain transfer cannot be reversed, and this is the one field in the run where a mistake is unrecoverable.

Step 5: Cover the fees, then start

If some of the wallets have no SOL left to pay their own fee, turn on the unified gas payer first and paste one funded wallet's key to cover every transaction in the run. Then select the rows you want and start. Each wallet is processed as its own transaction, signed locally with its own key, and rows update as they confirm. Leave the page open until the list finishes.

What if the old wallets have no SOL left to pay fees?

It is a genuine chicken-and-egg: a wallet holding a token but zero SOL cannot pay the fee to send that token out. Farming wallets end up here constantly, because the last thing they did was spend their remaining SOL on gas.

Turn on the unified gas payer and paste the key of one funded wallet. It becomes the fee payer for every transaction in the run, so the empty wallets never need a balance of their own — and you skip a manual round of dusting each address with SOL first.

Keep enough SOL in that gas wallet to cover the whole list. It also pays the roughly 0.00204 SOL rent if the destination needs a new token account created for a mint it has never held.

Can you sweep the rent out of the empty accounts at the same time?

Yes. Once a token account has been emptied, the account still exists and still holds its rent deposit. Enable Collect rent too and each emptied account is closed in place in the same run, releasing its 0.00203928 SOL back out.

The rent has its own destination field, so it can go to the same address as everything else or somewhere separate. Of the rent recovered this way, 20% goes to donations that keep the site running and 80% goes to your rent destination.

You can also skip it and close those accounts later from the wallet that owns them — see how to close empty token accounts, which handles up to 16 per transaction.

What does collecting from multiple wallets actually cost?

The pure transfer tools take nothing. Here is every deduction across the toolkit, stated plainly:

You always pay the ordinary Solana network fee, which goes to validators rather than to us, plus about 0.00204 SOL each time the destination needs a token account created for a mint it has not held.

The referral line is not a trick: the commission is 50% of the donation, and nothing stops you using your own referral link on your own wallet. That halves the main flow to an effective 5%.

Which of the nine batch tools fits your direction of travel?

Collecting is one direction. The rest of the set covers the others:

• Batch Collector (Many to One) — many wallets in, one address out. The subject of this guide.
• Batch Send (One to Many) — one wallet paying a list of recipients. Recipients per transaction are worked out at run time from what you are sending and whether the recipients already hold it, rather than being a fixed count, and your wallet is handed at most 10 transactions per approval batch.
• Multi to Multi — N senders paired line by line with N recipients, each pair its own transaction signed only by its sender.
• Relay Transfer — funds hop through single-use relay wallets generated locally, so source and destination are not directly linked.
• Batch Asset Migration — moves every token and NFT out of the listed wallets rather than one chosen mint.
• Rent Collector and Batch Burn — reclaim rent across many wallets, and destroy worthless tokens and NFTs in bulk.
• Batch Query and Wallet Generator — read balances without keys, and create fresh keypairs locally.

For a single wallet you already control, none of this is needed — connect it on the main page and use the ordinary close, burn and swap flows.