Don't keep only USDT in a TRON wallet. When you send it, the fee doesn't come out of the USDT. TRC20 USDT is a balance held inside a smart contract, every transfer runs that contract, and TRON bills the run in energy and bandwidth, which you can only get with TRX: stake TRX to earn them, receive energy another account delegates to you, or let the network burn TRX on the spot. No TRX and no energy, and the transfer won't go through.
How much you need depends on who you're paying. On 14 October 2026 we pulled TRON's chain parameters through the public TronGrid API and estimated a 1 USDT transfer. If the recipient address already holds USDT, it takes 64,285 energy; if it has never held USDT, 130,285. Energy cost 100 sun that day (1 TRX = 1,000,000 sun), so paying purely by burning TRX comes to roughly 6.43 TRX in the first case and 13.03 TRX in the second. Each transfer also uses about 345 bandwidth, which is free if your free allowance covers it and about 0.345 TRX if it doesn't. TRON can change the prices and the surcharge cap by governance proposal, and the surcharge factor itself moves with contract usage, so read these as October 2026 figures and check the estimate your wallet shows before you hit send.
Pulling USDT out of an exchange is a separate case. The exchange pays the on-chain cost and charges you a withdrawal fee in USDT, so there's no TRX to arrange; section five covers it.
(The on-chain figures above are query-based estimates, not a transfer we made. For how TRC20 differs from ERC20 and BEP20 in the first place, see TRC20, ERC20 and BEP20: what's the real difference for USDT.)
Energy and bandwidth: what a transfer actually spends
TRON splits the cost of a transaction into two resources. Bandwidth is charged by the transaction's size in bytes and every transaction needs it. Energy is only spent when a smart contract runs, and a TRC20 USDT transfer is exactly that.
The difference that matters is the free allowance. TRON's Resource Model documentation puts it plainly: every account gets free bandwidth, currently 600, but energy has no free quota and comes only from staking TRX or from energy another account delegates to you. Whatever energy you have covers part of the cost, and the sender burns TRX for the rest. That gap is why a wallet full of USDT can still refuse to send: the USDT is all there, and what's missing is TRX to burn.
Bandwidth follows a stricter rule. Paying for Resources says the network does not combine payment methods, nor burn TRX only for the part a quota doesn't cover. In practice, if the free allowance can't pay for the whole transaction, the whole transaction's bandwidth is paid in burned TRX. A USDT transfer needs about 345 bandwidth, so 600 free covers one and leaves 255; send a second straight after and 255 falls short of 345, so that one burns its full bandwidth, about 0.345 TRX.
What one transfer burns at today's chain rates
The table is a snapshot from 14 October 2026. Parameters come from TronGrid's getchainparameters (energy 100 sun, bandwidth 1,000 sun), and the energy figures from estimating a transfer call on the USDT contract. Eight real USDT transfer receipts pulled the same day showed only these same two energy figures. The parameters move with governance proposals, so the estimate in your wallet at the time of sending is the one to trust:
| Case | Energy used | Of which dynamic surcharge | If all energy is paid by burning TRX, about |
|---|---|---|---|
| Recipient already holds USDT | 64,285 | 49,635 | 6.43 TRX |
| Recipient has never held USDT | 130,285 | 100,635 | 13.03 TRX |
| Bandwidth (same in both cases) | About 345 bandwidth | 0 within the free allowance; about 0.345 TRX if not | |
The surcharge column needs a word of explanation. The documentation says that when a contract's recent energy use passes a threshold, its effective energy cost is multiplied by a factor between 1x and 4.4x. The USDT contract was being surcharged that day: 49,635 of the 64,285 is surcharge, leaving a base of just 14,650. Because the factor moves, figures in older guides that don't match today's won't tell you how much TRX to hold.
My own rule is to hold enough for the expensive case, about 14 TRX once you round up 13.03 plus a possible 0.345 for bandwidth.
You often don't know whether the other address has held USDT before. Extra TRX is still your money sitting in your wallet; too little, and the transfer won't send until you've gone off and found some TRX.
A recipient with no USDT history doubles the cost
Same 1 USDT, yet because the recipient has never held USDT, energy jumps from 64,285 to 130,285, and the base part without the surcharge goes from 14,650 to 29,650. Both are a little over double. TRON's resource docs don't explain this gap separately, so all we give here are the measured figures.
What that means for you: sending the first USDT to a brand-new address, such as a wallet you've just created or one a friend has just installed, budget for the expensive case, the roughly 14 TRX above. If you don't know an address's history, look it up in a block explorer first and see whether it has any USDT activity; the same lookup is walked through in our guide to tracing a missing deposit or withdrawal on a block explorer.
If energy runs short, a failed transfer still costs you
This is where money gets wasted for nothing. When a wallet calls a contract it attaches a fee_limit: the cap on that transaction's total energy cost, in sun, counting staked or delegated energy as well as any TRX burned. According to Paying for Resources, if the energy used would exceed the budget the fee_limit allows, the transaction reverts with OUT_OF_ENERGY. Your USDT never leaves, but the energy already consumed is still charged, up to the fee_limit.
The moment to stop is when your wallet's energy estimate is clearly more than the energy you hold and your TRX balance can only cover part of the gap. Top up TRX or energy first, then send.
If your wallet lets you edit the fee_limit, don't lower it to save money; a lower limit only makes a half-way failure more likely, and what's spent on a failure isn't refunded.
Why an exchange withdrawal doesn't need your TRX
When you withdraw USDT from an exchange, the exchange sends the on-chain transaction and pays for its resources. What you pay is the exchange's withdrawal fee, in USDT. Taking Gate as the example, its fee page (Deposit & Withdrawal tab) on 14 October 2026 listed USDT on Tron (TRC20) at 1.50 USDT per withdrawal, with a 10 USDT minimum and no deposit fee. That is a one-day snapshot; the figure on the live withdrawal page is the one that counts.
Reverse the direction and it changes. Depositing from your own wallet to an exchange costs nothing on the exchange's side, but your wallet is the one sending, so the energy and bandwidth are yours to cover and you still need TRX. For which networks cost more or less to withdraw on, Cheapest network to withdraw USDT lists the current snapshot.
Compare common networks on speed, cost and compatibility, then confirm which one the receiving side supports.
"1.1 TRX to activate a new address" is about a different transfer
Search this topic and you'll often read that sending USDT to a new address first costs about 1.1 TRX to activate it. The number is real; it's just been applied to the wrong thing. TRON's documentation says that a direct TRX or TRC-10 transfer to an address that hasn't been activated incurs a 1 TRX account creation fee, and if staked or delegated bandwidth can't cover the transaction, a fixed getCreateAccountFee, currently 0.1 TRX, is burned on top of that. When both apply, 1.1.
Sending TRC20 USDT calls the USDT contract; it isn't a direct TRX transfer. None of the official pages we checked apply that account creation fee to a TRC20 transfer. The extra a new address costs shows up in our estimate as roughly double the energy. Budget TRX by energy, not by 1.1, or you'll come up about a dozen TRX short.
Getting energy: staking, delegation and "rental"
Per the documentation, energy has exactly two sources: staking your own TRX, or receiving energy another account delegates to you. Energy you use recovers gradually over 24 hours.
Staking suits someone who sends USDT often. The TRX stays locked rather than spent, and the energy refills on its own. If you send once or twice a month, letting the wallet burn TRX is simpler, and for occasional small transfers like that I wouldn't bother staking.
The many "energy rental" services online run on that same delegation mechanism: someone delegates energy to your address and you pay them. We haven't verified any of these services and don't recommend one. If you do use one, at minimum make sure the energy is being delegated to your address, and that nobody is asking you to hand over USDT, a seed phrase or a private key first.
FAQ
My wallet holds USDT but no TRX at all. Can I still send the USDT?
Usually not. A TRC20 USDT transfer runs a contract and consumes energy, and energy has no free allowance. Without staked or delegated energy the shortfall has to be covered by burning TRX, and with no TRX there is nothing to burn. Send a little TRX to the address first, or have another account delegate energy to it.
Do I need TRX in my wallet before withdrawing USDT to it from an exchange?
No. The exchange sends the on-chain transaction and covers its resources; you pay the exchange's withdrawal fee in USDT. You only need TRX later, when you send USDT out of that wallet.
Sources and further reading: the resource rules follow TRON's developer documentation, Paying for Resources, Bandwidth and Energy and Resource Model, checked 14 October 2026; chain parameters and energy estimates come from the public TronGrid API (api.trongrid.io), queried 14 October 2026; the withdrawal fee is from Gate's fee page (Deposit & Withdrawal tab), checked 14 October 2026. This is an independent third-party explainer, not investment advice.