The short answer
| Recipient | Energy needed | Roughly, if burned as TRX |
|---|---|---|
| Already holds USDT | ~64,285 | ~6.43 TRX |
| Has never held USDT | ~130,285 | ~13.03 TRX |
This is why rental packages come as 65,000 and 131,000: they are sized to the two cases, with a small margin. The amount of USDT you send does not change the figure — sending 10 USDT and sending 100,000 USDT consume the same Energy.
Why a USDT transfer costs more than a TRX transfer
Sending TRX is a native operation. The protocol moves a balance and charges you Bandwidth for the size of the transaction — a few hundred bytes, usually free.
Sending USDT is not a transfer at all, from the network's point of view. It is a call to a smart contract — the TRC-20 contract that keeps a ledger of who holds what. Executing contract code costs Energy, and the more work the contract does, the more Energy it burns.
What doubles the cost
The contract stores balances in a mapping from address to amount. When it credits the recipient, one of two things happens:
- The recipient already has a USDT balance, so the contract overwrites a storage slot that already exists. That is the cheap path.
- The recipient has never held USDT, so the contract has to allocate a brand-new storage slot. Writing a slot from nothing is one of the most expensive operations in the EVM, and it roughly doubles the Energy the transfer consumes.
The recipient's USDT history is what matters, not yours. Sending to a fresh exchange deposit address, a newly created wallet, or a friend who has only ever held TRX will hit the expensive path — every time, until they hold a non-zero USDT balance.
What it costs if you have no Energy
Energy is not optional. If your address does not have it, the network takes the equivalent in TRX and burns it. The conversion rate is a network parameter called getEnergyFee, expressed in sun (1 TRX = 1,000,000 sun).
At the time of writing that parameter sits at 100 sun, so one Energy costs 0.0001 TRX. Multiply it out and a routine transfer burns around 6.4 TRX, and a transfer to a first-time USDT recipient around 13 TRX.
Do not treat that rate as fixed. It is set by TRON governance and has been changed by vote several times, always downward so far. Check the live value rather than trusting a number in an article, including this one.
How to check the numbers yourself
Two checks are worth knowing, and both take seconds.
- For the current Energy price, query the network parameters — the getchainparameters endpoint on any TRON node returns getEnergyFee in sun. Divide by 1,000,000 to get TRX per Energy.
- For what a specific transfer will actually cost, use a node's triggerconstantcontract call against the USDT contract with your sender and recipient. It simulates the call without broadcasting it and returns energy_used — the real figure for that exact pair of addresses.
- For what you already have, open your address in TronScan and read the Resources panel: it shows Energy and Bandwidth, both available and total.
The simulation is the only method that gives you a precise answer, because it accounts for the current state of the contract rather than a rule of thumb.
Bandwidth is a separate bill
Energy pays for contract execution. Bandwidth pays for the bytes your transaction occupies, and they are metered separately.
- A TRC-20 transfer is roughly 345 bytes, so it needs about 345 Bandwidth.
- Every TRON account gets 600 free Bandwidth per day, which covers one such transfer and not two.
- If you are short, the network burns TRX at 0.001 TRX per Bandwidth point — about 0.345 TRX per transfer. Small, but it is why a wallet with Energy and zero TRX can still fail to send.
Sending to a TRON address that has never been activated costs an extra 1 TRX account-creation fee, on top of everything above. That is a property of the address, not of USDT.
Worked examples
| Scenario | Energy | Bandwidth | What you need |
|---|---|---|---|
| Paying a supplier you have paid before | ~64,285 | ~345 | One 65,000 package |
| First payment to a new client's wallet | ~130,285 | ~345 | One 131,000 package |
| Five payouts to regular recipients | ~321,425 | ~1,725 | A 650,000 package covers it with room |
| Topping up your own fresh wallet | ~130,285 | ~345 | 131,000, plus 1 TRX if the address is new |
Package sizes are guidance, not a guaranteed transaction count. If a batch matters, simulate the first transfer and size from the real number.
When to get Energy in advance
Burning TRX works and needs no preparation, which makes it fine for a one-off transfer. It stops making sense the moment transfers become routine: you are paying the network's own conversion rate, which is the most expensive way to obtain Energy.
- Occasional single transfers — burning TRX is simpler and the difference is small.
- Several transfers a week — renting Energy is cheaper per transfer and the saving compounds quickly.
- Payouts, bots or an exchange desk — rent programmatically before each broadcast and treat Energy as an input cost, not a surprise.
Whichever route you take, the number to plan around is the recipient's history, not the amount you are sending. Check it once and the rest is arithmetic.