> For the complete documentation index, see [llms.txt](https://docs.dexlab.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dexlab.space/products/minting-lab/multisender.md). # Multisender Reference: Fee Schedule, Recipient File Format, and Retries Bulk send SPL and Token-2022 tokens to many Solana wallets. Service fee: first 20 recipients free, then 0.001 SOL each, never more than 0.3 SOL per batch. The DexLab Multisender sends an SPL or Token-2022 token from your wallet to a list of recipients in batched transactions that your wallet signs. This page is the reference for the fee schedule and the recipient file format. The app guide [How to Airdrop SPL Tokens to Multiple Wallets](https://app.dexlab.space/token/airdrop) walks through the send step by step. 👉 **Open the Solana multisender:** ## What the Multisender does * Sends one SPL or Token-2022 token to every address on your list. The token program is detected from the mint, so a Token-2022 token needs no extra setting. * Takes recipients as pasted lines or as an uploaded `.xlsx`, `.xls`, `.csv`, or `.txt` file with an address column and an amount column. * Runs a pre-flight check before anything is signed. It probes every recipient account, counts the recipients that still need a token account, checks the amount decimals against the on-chain mint, and shows the total SOL cost and the number of wallet popups. * Is non-custodial. Your wallet signs every transaction, and transfers land directly in each recipient token account, so recipients do not need to claim anything. * Verifies every transfer on-chain after the send and offers a Retry button for rows that failed. The Multisender sends SPL and Token-2022 tokens. It does not send SOL itself, and it does not build the holder list for you: bring the list of addresses you already have. ## What a batch costs As of 2026-09, the service fee depends on how many recipients are in the batch: the first 20 recipients are free, each recipient after that costs 0.001 SOL, and a single batch never pays more than 0.3 SOL. This schedule replaced a flat per-recipient rate, so check the quote the app shows you rather than trusting an older figure. The fee is quoted before you sign and is charged on Solana mainnet. There is no service fee on devnet, so you can rehearse the exact list first. | Recipients in the batch | Service fee | | ----------------------- | ----------- | | 20 | 0 SOL | | 50 | 0.03 SOL | | 100 | 0.08 SOL | | 241 | 0.221 SOL | | 320 or more | 0.3 SOL | The cap takes over at 320 recipients, so every batch of 320 or more pays the same 0.3 SOL service fee however large it is. That is a statement about the price, not about a tested batch size: the largest send verified on mainnet so far is 241 recipients, and the form has no measured ceiling above that. Split a very large list into several sends and confirm each one before starting the next. Solana network fees (about 0.000005 SOL per transaction) and rent for first-time recipient token accounts (about 0.00204 SOL each) are paid to the network on top, from the sending wallet. ## How to send tokens to many wallets 1. Open the [Multisender](https://app.dexlab.space/multisender) and connect a Solana wallet. 2. Choose the token: pick an SPL or Token-2022 mint from your wallet, or paste the mint address. 3. Add recipients: paste them line by line or upload a file in the format below. 4. Run the pre-flight check and read the cost estimate and the popup count. 5. Approve the batches. Transfers are signed in chunks of 75 per wallet popup, then verified on-chain. ## Recipient file format Two columns, address first and amount second. A header row such as `address,amount` is allowed and is skipped automatically. Columns can be separated by a comma, a tab, or spaces, and quoted CSV cells are read correctly. The same layout works when you paste the rows straight into the form. ``` address,amount ,100 ,250.5 ``` * Supported files: `.xlsx`, `.xls`, `.csv`, `.txt`. For a spreadsheet, the first sheet is read. * Amounts are in whole tokens, not raw units. Decimal amounts keep their precision and are checked against the mint decimals in the pre-flight. * Duplicate addresses are rejected by default. The form has an option to allow duplicates when one wallet should receive more than one row. * Invalid addresses and amounts are listed with their row numbers before the send, so you can fix the file and upload it again. ## Verification and retries After the last batch is signed, the Multisender reads each recipient account on-chain and reports how many transfers are verified. Rows that failed, or that could not be confirmed, appear in the result table with a Retry button. The service fee is not charged again for recipients it already covered, so a retry pays just the network fees. The result table can be downloaded as a CSV with the address, amount, transaction ID, and status of every row. ## FAQ **How much is the service fee?** As of 2026-09, the first 20 recipients are free, each recipient after that costs 0.001 SOL, and a single batch never pays more than 0.3 SOL. Solana network fees and token account rent are extra and go to the network. See [Solana Token Creation Fees](/products/minting-lab/factory-fee.md#multisender) for every DexLab fee in one place. **Does it work with Token-2022 tokens?** Yes. The mint is inspected on-chain and the matching token program is used, with transfer-checked instructions in both cases. **Is it non-custodial?** Yes. Tokens never leave your wallet without a transaction you sign, and DexLab never holds them. **What happens to failed rows?** Confirmed transfers stay on-chain. Failed rows are listed with a Retry button, and the retry does not pay the service fee again. **Can I test before spending real SOL?** Yes. Switch the app to devnet and run the same list. There is no service fee on devnet. 👉 [Open the Solana multisender](https://app.dexlab.space/multisender) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dexlab.space/products/minting-lab/multisender.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.