How to Send TRC-20 Tokens to Multiple Addresses (Step-by-Step, 2026)

There are exactly two practical ways to send TRC-20 tokens to multiple addresses on TRON: sign one transfer per recipient by hand, or upload the whole list and send it as one batch through a multisender contract. For anything beyond a dozen recipients, the batch wins on every axis — with 100 recipients it turns roughly 200 minutes of wallet work into about 5 and cuts network fees by more than half. This guide walks through both methods step by step, with real cost numbers from our fee calculator at 10, 100, and 1,000 addresses, and the mistakes that eat most first-time distributions.

What you'll need

Whichever method you pick, the checklist is the same:

• A TRON wallet. TronLink (browser extension or mobile) is the default; TokenPocket and other TronLink/WalletConnect-compatible wallets work too.
• TRX for fees. Every TRC-20 transfer consumes energy, and energy is ultimately paid in TRX — either burned at the network price or rented cheaper on the market. As a reference point from our constants: a single USDT transfer to a wallet that already holds USDT burns about 6.77 TRX (≈$2.03), and about twice that to a fresh address.
• The recipient list. Addresses and amounts. For manual sending this can live anywhere; for a batch you want a two-column CSV — address, then amount — or the same list pasted as text.
• Optional but smart: a testnet rehearsal. The full batch flow runs on the Shasta and Nile testnets with free test tokens. If this is your first distribution, do a dry run there.

A note on preparing the list, because it decides how smooth everything else goes. Keep it in the spreadsheet you already use, with exactly two columns: the TRON address (starts with T, 34 characters) and the amount as a plain number with a dot decimal — no header row, no currency symbols, no thousands separators. Export to CSV when it is time to send. If the list came from a form or a chat, expect stray whitespace and duplicates; sort by the address column once and scan it before uploading. The guide's CSV section lists every format rule and the classic export traps by spreadsheet locale.

Which method fits your situation?

An honest decision rule before the step-by-steps:

• 2–5 recipients, once: send manually. Setting up anything would take longer than the transfers.
• A dozen or more, or any recurring send: batch. The crossover is not subtle — validation, one review screen, and one signature start paying for themselves the moment the list stops fitting in your head. Recurring payouts (salaries, weekly rewards) benefit twice, because the same CSV template gets reused every cycle.
• Hundreds or thousands: batch, without debate. Manual sending at this size is not merely slow; it is an error surface no careful person should accept, since every one of those transfers is irreversible.

The detailed cost-and-time breakdown by scenario lives in Multisender vs manual sending; below is the short version with numbers.

Method 1: manually, transfer by transfer

The obvious way, and for two or three recipients the right one: open the wallet, paste an address, enter the amount, double-check, sign. Repeat.

The pain grows linearly and then some. At a careful pace of about two minutes per transfer, ten recipients cost you twenty minutes; a hundred cost more than three hours of unbroken focus. Every paste is a fresh chance to send an irreversible transfer to the wrong address, and there is no review screen at the end — your attention is the review screen, transfer after transfer. Afterward you hold a stack of separate transaction hashes to reconcile against your spreadsheet by hand.

Fees scale the same way: each transfer is its own transaction, paying its own energy and its own bandwidth, with no batching discount of any kind. We break the honest crossover point — when manual stops making sense — in Multisender vs manual sending.

Method 2: one batch with Multisender

The batch flow takes the same inputs and compresses the work into six short steps:

1. Open the dApp and connect your wallet. Go to the app via trxsend.com and connect TronLink or any compatible wallet. Nothing is deposited anywhere — funds stay in your wallet until you sign.
2. Pick the network. Mainnet for the real thing; Shasta or Nile if you are rehearsing.
3. Select the token. USDT and popular TRC-20s are in the list; any other TRC-20 works by pasting its contract address. TRX and TRC-10 are supported as separate types.
4. Upload the list. A CSV, XLS, or XLSX with two columns — address, amount — or paste the list as plain text. The validator checks every address, flags malformed entries and duplicates, and shows the parsed list with totals on one review screen. This is the moment to actually read it.
5. Approve the allowance. One wallet signature grants the verified multisender contract permission to move exactly this distribution's amount of your token.
6. Confirm the MultiSend. A second signature sends the batch. Around 150 recipients fit in one transaction; longer lists continue as consecutive batches in the same flow. Every individual transfer appears on TRONSCAN under the batch transaction, and recipients are paid within minutes.

The full flow with per-screen details lives in the step-by-step guide.

What both methods cost

Numbers below are computed with the same engine as our fee calculator, assuming USDT, recipients already holding USDT, energy burned at 100 sun one-by-one versus market-rented energy (≈45 sun) in the batch flow, and TRX at $0.30. Fresh addresses roughly double the energy in both methods — the share of first-time holders in your list is the strongest cost lever you control.

Recipients	One-by-one: fees	One-by-one: your time	Batch: fees	Batch: your time	Fee savings
10	67.7 TRX ≈ $20.32	~20 min	29.3 TRX ≈ $8.78	~5 min	≈57%
100	677.4 TRX ≈ $203.21	~3.3 hours	289.6 TRX ≈ $86.89	~5 min	≈57%
1,000	6,773.5 TRX ≈ $2,032.05	~33 hours	2,895.2 TRX ≈ $868.57	~11 min	≈57%

Two footnotes that matter. First, the batch flow shows a small per-batch service fee in the dApp before you confirm (VIP plans remove it; it is excluded above because it varies). Second, the fee gap comes from two places: energy rented at market price instead of burned at the network price, and bandwidth paid once per batch instead of once per transfer. The full methodology, with every constant and its source, is on the calculator page.

After the batch: verify and keep records

A distribution is not finished when the wallet says "confirmed" — it is finished when you can prove who got what. The batch flow makes this side almost free, and it is worth doing properly.

Open the batch transaction on TRONSCAN: every individual transfer is listed under it with recipient, amount, and timestamp, all hanging off a single hash. Save that hash next to the CSV you sent — the pair is a complete, independently verifiable record of the payout. For recurring payouts, one hash per cycle keeps the books clean: your accounting spreadsheet gains one column, not a thousand rows of reconciliation. For airdrops, the same link doubles as a public proof of distribution you can post to the community, which quietly kills the "team never sent it" thread before it starts.

If a recipient claims they were not paid, resolution takes seconds: find their address under the batch on TRONSCAN. Either the transfer is there — case closed — or the address they gave you differs from the one in your file, which is a conversation about their form submission, not about your send. Compare that with the manual aftermath: digging through dozens of separate hashes trying to remember which one was theirs.

Common mistakes

Most failed first distributions trace back to the same short list:

• Comma decimals. Spreadsheets in many locales export 1,5 instead of 1.5. Amounts must use dot decimals or they will be misread.
• A leftover header row. The first line of the file must already be a real recipient, not address,amount.
• Invisible characters around addresses, picked up when copying from chats and web pages. The validator flags these, but cleaning the file first saves a round-trip.
• Ignoring the fresh-address premium. A list full of wallets that never held the token costs roughly twice as much energy. Know your share of first-time holders before you budget.
• Skipping the review screen. Validation catches malformed addresses; it cannot catch a valid address that belongs to the wrong person. On-chain transfers are irreversible — read the parsed list, and send a small test batch before the first big one.

For payout-specific practices see USDT payroll on TRON; for community distributions, the TRC-20 airdrop tool.

FAQ

How many addresses can I send to in one go? There is no hard cap on list size. A single transaction fits about 150 recipients; longer lists run as consecutive batches inside the same workflow — 10,000 recipients means roughly seventy confirmations, not ten thousand.

Do I need to write any code? No. The entire flow is a web dApp: connect a wallet, upload a two-column file, sign two transactions. Teams that need programmatic sending can ask about the API Early Access program via Telegram.

Which tokens can I batch send? TRX, every TRC-20 (USDT included — pick from the list or paste any contract address), and TRC-10 tokens.

Can I send a different amount to each address? Yes — the amount column is per-recipient. Equal-amount distributions are just a special case where the column repeats one value; nothing about the flow changes.

Is it safe to approve the contract? The allowance you sign is scoped to the distribution you are making, the contract is verified on TRONSCAN, and the service never takes custody — funds move from your wallet to recipients inside the transaction you sign. See the trust breakdown on the airdrop page.

What does energy actually cost right now? It moves with the network. As of our last verification, burning energy costs 100 sun per unit and renting it costs roughly 45 sun; a single USDT transfer consumes 64,285 units to an existing holder. The energy cost deep-dive explains where those numbers come from — and the calculator always shows the current totals for your list.