How to Prepare a Recipient CSV for an SPL Token Airdrop

Treat the recipient file as an execution contract

Each row tells the sending workflow where value should go and how much should be transferred. A formatting mistake can stop a run; a valid but incorrect row can send the wrong allocation.

Keep the file small in structure and strict in review. For the current MultiSender Suite import flow, use one recipient per line in address,amount order without a header row.

• First value: recipient wallet address
• Second value: human-readable token amount
• Separator: one comma
• One recipient per line
• No private keys, recovery phrases, names, emails, or unrelated personal data

Use plain decimal amounts

Write amounts as plain decimal strings such as 1, 0.5, or 125.25. The number of fractional digits must not exceed the decimals supported by the selected token.

Avoid thousands separators, currency symbols, formulas, and scientific notation. Spreadsheet software can silently reformat long addresses or numeric values, so export and inspect the final text rather than trusting the visual sheet alone.

Remove duplicates before import

A repeated wallet can represent an intentional second allocation or an accidental duplicate. The sending tool cannot infer business intent from identical addresses, so decide the rule before importing.

Create a normalized source list, group repeated addresses, and either combine their amounts or document why multiple rows should remain.

• Trim spaces before and after addresses
• Compare addresses exactly after normalization
• Confirm whether repeated wallets should be merged or retained
• Recalculate the total after any merge
• Keep the reviewed source file as the audit copy

Validate with the selected token

Amount validity depends on token decimals, so choose the correct chain and token before treating a file as ready. MultiSender Suite checks amount precision using the selected token configuration and displays the valid recipient count and total amount for review.

Address format still deserves an independent review. Confirm that every recipient belongs to the intended network and that the first test recipients are wallets you can verify.

Run a final pre-import checklist

Save a reviewed copy before importing, and do not edit the source during the send. If anything changes, create a new version and review the total again.

• No header row
• Exactly address,amount on each non-empty line
• No duplicate recipient left unexplained
• No amount with excessive decimal places
• Final row count and token total confirmed
• Small test list prepared
• No secret or personal data included