When you move USDT (TRC-20) at scale — an exchange processing withdrawals, a payment app, an airdrop, or an agency serving clients — the energy bill is one of your biggest hidden costs. Buying energy one order at a time doesn’t work at volume. This guide shows how to buy TRON energy in bulk with TronSave and cut per-transfer fees across thousands of sends.
The problem at scale
A single USDT (TRC-20) transfer needs roughly 65,000 energy (about 130,000 if the recipient has never held USDT). Multiply that across thousands of daily withdrawals and, without rented energy, you’re burning a large amount of TRX every day. Renting energy in bulk turns that spiky, expensive fee into a predictable, much lower cost.
The arithmetic is fixed by the protocol. Since TRON Proposal #104 took effect on 29 August 2025, energy burns at 100 sun per unit, and 1 TRX = 1,000,000 sun. One ordinary transfer with no energy therefore burns 6.5 TRX; a transfer to an address that has never held USDT burns about 13 TRX, because the contract must create a new balance slot rather than update one.
| Daily transfers | Energy needed | Burned TRX (100 sun) | Rented at 30 sun | Rented at 10 sun |
|---|---|---|---|---|
| 100 | 6,500,000 | 650 TRX | 195 TRX | 65 TRX |
| 1,000 | 65,000,000 | 6,500 TRX | 1,950 TRX | 650 TRX |
| 10,000 | 650,000,000 | 65,000 TRX | 19,500 TRX | 6,500 TRX |
The burn column is not negotiable. The rental columns are illustrative: energy is priced by a live order book in sun per unit of energy, so your actual cost is energy × unit price ÷ 1,000,000 TRX. Take the current number from the TronSave energy market, not from any table — including this one.
Sizing the order: amount, duration, price
Three inputs decide what you pay, and getting them wrong is the expensive mistake at volume.
- Amount. Minimum is 64,000 units, just under one USDT transfer; there is no practical ceiling. Size against your worst-case day and count first-time recipients at 130,000, not 65,000.
- Duration. 15 minutes, 1 hour, 3 hours, or 1–30 days, defaulting to 3 days. Short durations suit a one-off batch; a continuous pipeline is better served by a multi-day rental you extend than by a stream of tiny orders.
- Price. A unit price in sun, set by speed tier (Slow, Medium, Fast) or manually. A low price may sit unmatched on a thin order book; a higher one fills sooner. That is a real trade-off, not a fee.
The advanced options matter at volume: allow partial fill lets an order match several providers rather than wait for one big one, minimum delegate sets the smallest chunk you will accept from a single provider, and immediate buy refuses to create the order at all if it cannot fill now. For large recurring needs there is Smart Order — minimum 10,000,000 energy and 3 days — which keeps topping you up after the initial match and refunds unused duration in TRX. Full comparison: TronSave order types explained.
Bulk-Buy: energy for many addresses at once
TronSave’s Bulk-Buy tool solves a different problem from one large order: it delegates energy to many different addresses in a single flow instead of one order per wallet — the shape of the problem for an exchange with hot wallets, a payment app with per-merchant addresses, or an agency covering client wallets.
- Open the Bulk-Buy tool from the TronSave Tools menu (energy pricing comes from the same TronSave energy market order book).
- Upload a CSV with one TRON address per line, or paste the list.
- Set a single amount and duration that will be applied to every address in the list.
- Confirm — the tool processes the list in batches of up to 100 addresses per call and shows a per-address status so you can see exactly which ones succeeded.
Two practical details. Bulk-Buy is paid from your TronSave internal balance rather than by signing each order on-chain, so fund that balance before a large run. And inactive wallets can be activated within the flow — an unactivated TRON address cannot receive a delegation, and activation costs a small TRX fee per wallet, so a list of freshly generated addresses carries that line item.
Automate it with the API & SDKs
For production systems, drive energy purchasing straight from your backend. TronSave ships a REST API and official SDKs for TypeScript, Rust, Python, Java and PHP, so your withdrawal pipeline can rent exactly the energy each payout needs, right before it sends. See the API automation guide and the developer docs / API.
The pattern that survives production is estimate, then buy. The estimate endpoint returns the unit price, duration, TRX cost and how much resource is actually available at that price, letting your job refuse to proceed when the book is thin or the price has spiked. Most endpoints allow around 15 requests per second — ample for batch work, not for per-transaction polling — so cache and batch your calls. Nile testnet mirrors everything at api-dev.tronsave.io with separate keys and balances. Working code in the Python walkthrough and the SDK guide.
Extend instead of re-buying
When a rental’s duration ends the delegation is reclaimed — the energy simply stops being there. For a continuous pipeline, letting orders lapse and re-buying is more expensive and more fragile than extending. ExtendOrder pushes an existing delegation’s expiry out to any point 1–30 days from now, provided the new expiry is later than the current one, and can add energy at the same time (additional purchases start at 100,000). Extend duration only, buy more only, or both — see the Extend feature guide. Set a reclaim alert alongside it: TronSave can warn you a configurable number of minutes before expiry, which is the difference between extending on schedule and finding out through a wall of failed withdrawals.
When it goes wrong: OUT_OF_ENERGY
A transfer that runs out of energy reverts with OUT_OF_ENERGY: the transaction does not complete, and the fee consumed before the revert is not refunded. At volume this rarely arrives as a single failure — it arrives as a cluster, when a rental expires mid-shift or a batch was sized on the average recipient rather than the worst case.
The half-funded batch is the specific trap. Budget 3,250,000 energy for 50 transfers, discover eight destinations are first-time USDT holders needing 130,000 each, and you are 520,000 short — the run stops partway, some payouts landed and some not. Classify destinations before sizing the order, verify the delegation has arrived before you fire, and keep Auto-Buy armed as a floor under the whole thing. More on recovery: fixing out-of-energy failures.
Or run it from Telegram
Ops teams that don’t want to build an integration can buy energy from the TronSave Telegram bot — handy for on-the-fly top-ups without opening a dashboard.
Pair Bulk-Buy with Bulk-Send
If you’re paying out to many addresses — payroll, rewards, or an airdrop — combine bulk energy with bulk token sending so both the energy and the transfers are handled in batches. Together they keep large USDT operations fast and cheap.
Note the direction of each tool: Bulk-Buy spreads energy across many sending addresses, while Bulk-Send pays many recipients from one wallet. An airdrop usually needs the second — one well-funded sender plus a CSV of destinations. TRC-20 sends through the bulk tool also need an approve transaction first, which itself consumes energy.
FAQ
Is bulk energy delivered instantly?
Yes — once payment confirms, energy is delegated to the target address in seconds.
Is it non-custodial?
Yes. Energy is delegated to your addresses; TronSave never holds your keys or funds.
Can I cover recipients who’ve never held USDT?
Yes — budget the higher energy (~130,000) for first-time-recipient transfers when you size your bulk order.
What is the minimum energy I can buy?
64,000 units, set just below the cost of one USDT transfer so no order is too small to be useful. Smart Order is the exception, at 10,000,000.
Do I need TRX if I have rented energy?
Yes, a little. Energy covers contract execution, but every transaction also consumes bandwidth, and a wallet with neither free bandwidth nor TRX cannot broadcast — see how much TRX a USDT send needs.
Scaling USDT payouts? Start on the TronSave energy market or read the API docs to automate bulk energy.
