TRC20 USDT Fees Explained: Energy, Bandwidth, TRX Burn

A TRC20 USDT fee is really the cost of TRON energy and bandwidth, paid in resources or burned TRX. Here's how it works, why sending to a zero-balance wallet costs about twice as much, and what it means for merchants.

TTillCrypto team7 min read

If you've ever sent USDT on TRON and watched your wallet burn several TRX for what was supposed to be a cheap transfer, you've met TRON's resource model. A TRC20 USDT fee isn't a fixed price. It's the cost of the bandwidth and energy your transaction uses, paid either from resources your account already has or by burning TRX on the spot. The prices below are what TRON charges as of late 2026. They change now and then; the mechanism behind them changes far less often.

What a TRC20 USDT fee actually is

TRON has no gas auction like Ethereum. Every transaction consumes up to two resources, and the network charges for them according to rules set by governance:

  • Bandwidth pays for the size of the transaction in bytes. Every transaction uses it.
  • Energy pays for running smart contract code. Only contract calls use it.

A plain TRX transfer is just a small signed message, so it needs bandwidth only. A USDT transfer is a call to the USDT smart contract (TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on mainnet), so it needs bandwidth and energy. Once you know that, most of the "why did this cost 13 TRX?" questions answer themselves.

If your account doesn't have enough of a resource, the network burns TRX to cover it. That burned TRX is what wallets show as the "fee".

TRON energy and bandwidth, side by side

Bandwidth Energy
Pays for Transaction size in bytes Smart contract execution
Free allowance 600 per activated account, refilling gradually over 24 hours None
Get more by Staking TRX or receiving a delegation Staking TRX or receiving a delegation
Burn rate if you lack it 1,000 sun (0.001 TRX) per unit 100 sun (0.0001 TRX) per unit
Used by a USDT transfer Roughly 345 Roughly 65,000 to 130,000

The burn rates come from TRON's official resource docs as of late 2026. Both can be changed by governance proposal, and the energy price has moved several times before, so treat them as current values, not constants. To check the live numbers, query wallet/getchainparameters and look at getEnergyFee and getTransactionFee.

One rule surprises people: bandwidth is all or nothing. The network tries your staked bandwidth, then your free bandwidth, and if neither covers the whole transaction, it burns TRX for the full amount. So 255 bandwidth left over from your free allowance doesn't help a 345-byte transaction at all. Energy works differently, which matters when we get to renting it below.

Why sending USDT costs more than sending TRX

A TRX transfer to an existing account is a couple of hundred bytes. The free 600 bandwidth usually covers it, so for most people sending TRX costs nothing.

A USDT transfer runs contract code that reads and updates two balances inside the USDT contract. That costs energy, and nobody gets energy for free. With no staked or delegated energy, you burn TRX for all of it.

Here is roughly what that comes to at 100 sun per unit of energy:

Transfer Energy used (approx.) TRX burned if you have no energy
USDT to an address that currently holds some USDT ~65,000 ~6.5 TRX
USDT to an address with a zero USDT balance ~130,000 ~13 TRX
TRX to an already-activated address 0 Usually 0 (free bandwidth)

Add about 0.35 TRX for bandwidth if your free allowance is already used up.

The energy figures match what Dwellir measured on mainnet in November 2026 (64,285 and 130,285). They already include the penalty from TRON's dynamic energy model, which multiplies the energy cost of heavily used contracts. USDT has sat at the maximum multiplier for a long time, so if these numbers move, they're more likely to drop than rise. You can check the contract's live energy_factor with wallet/getcontractinfo.

Why a zero balance makes the fee double

Send 50 USDT to a wallet that already holds a few USDT and you'll burn about 6.5 TRX. Send the same 50 USDT to a wallet holding none, and it's about 13.

The reason is storage. The USDT contract keeps a table of balances. Changing a balance that's already non-zero is relatively cheap. Writing to a balance that's currently zero, whether the address is brand new or was emptied last week, costs far more energy. The amount you send doesn't matter. Only the recipient's balance at that moment does.

There's a separate cost for addresses that have never been activated on TRON at all. Sending TRX directly to an unactivated address charges a 1 TRX account creation fee, and free bandwidth can't be used for that transaction. If you also lack staked bandwidth, another 0.1 TRX is burned on top.

Staking, renting, or burning: three ways to pay

You can cover energy and bandwidth in three ways.

  1. Burn TRX. Keep some TRX in the sending wallet and let the network take what it needs. Simple and predictable, but it's the most expensive option per transfer.
  2. Stake TRX. Under TRON's Stake 2.0, you lock TRX and receive energy or bandwidth that refills over 24 hours. You get your TRX back when you unstake, after a waiting period (14 days on mainnet right now). It only pays off if you send USDT regularly, because a single transfer needs a lot of staked TRX behind it.
  3. Receive delegated energy. An account that has staked TRX can delegate its energy to yours. Third-party "energy rental" services sell this, usually for less than the burn cost. You're trusting a third party to deliver. And unlike bandwidth, energy can be topped up: if the rented energy falls short (say you rented 65k, but the transfer lands on a zero balance and needs 130k), the network uses what you have and burns TRX for the difference.

Whatever you choose, set a sensible fee_limit on contract calls. It's set in sun and caps the total energy cost of the call, counting energy from your stake as well as burned TRX. If the call needs more, it reverts with OUT_OF_ENERGY and you still pay for what was used. At current prices, something like 30 TRX (30,000,000 sun) covers even the zero-balance case with room to spare.

What TRC20 fees mean for merchants

When a customer pays you in USDT, the customer pays the network fee for that transfer. Their wallet burns the TRX or uses their energy. If they send from an exchange, the exchange charges its own withdrawal fee, which it sets itself.

That has a practical consequence: some exchanges deduct the fee from the amount sent, so you receive 99 USDT on a 100 USDT invoice. Tell customers the exact amount must arrive, and decide in advance how you'll handle short payments. We cover that and other awkward cases in crypto payment edge cases.

The fee comes back to you when money moves out:

  • If you run your own wallets, every withdrawal and every sweep from a deposit address to your main wallet is a USDT transfer that needs energy. One address per order means one sweep per order, and each deposit address needs TRX or delegated energy before it can move anything. And once you sweep a deposit address to zero, the next customer who pays into it is sending to a zero balance and pays the higher fee. Most DIY setups underestimate this.
  • If you use a payment gateway, the gateway pays the on-chain cost when it sends your payout and usually passes it on as a flat payout fee. A flat fee is easier to plan around than a number that swings between roughly 6.5 and 13 TRX depending on where you're sending.

For reference, TillCrypto charges 0% on incoming payments and a flat network fee of 2 USDT per TRC20 USDT payout (2 TRX per TRX payout). Because the fee is per payout rather than per payment, withdrawing a week of sales at once costs the same as withdrawing a single order. If you're weighing the two setups more broadly, how to accept USDT payments on your website walks through both.

If you're still choosing a network, our TRC20 vs ERC20 vs BEP20 comparison puts these costs next to Ethereum and BNB Chain.

Estimating a USDT transfer fee yourself

TRON nodes can simulate a contract call without broadcasting it and report how much energy it would use. With TronWeb:

js
import { TronWeb } from 'tronweb';

const tronWeb = new TronWeb({
  fullHost: 'https://api.trongrid.io',
  headers: { 'TRON-PRO-API-KEY': process.env.TRONGRID_KEY }, // keyless calls are heavily rate-limited
});

const USDT = 'TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t';
const sender = 'T...';    // an address holding at least 50 USDT
const recipient = 'T...'; // the address you want to price

const res = await tronWeb.transactionBuilder.triggerConstantContract(
  USDT,
  'transfer(address,uint256)',
  {},
  [
    { type: 'address', value: recipient },
    { type: 'uint256', value: 50_000_000 }, // 50 USDT, 6 decimals
  ],
  sender,
);

// A reverted simulation still returns energy_used, so check before trusting it.
if (!res.result?.result || res.transaction?.ret?.[0]?.ret === 'FAILED') {
  throw new Error(`Simulation failed: ${res.result?.message ?? 'reverted'}`);
}

const energy = res.energy_used; // already includes the dynamic energy penalty
console.log(`~${energy} energy, ~${(energy * 100) / 1e6} TRX if burned`);
// Plus ~0.35 TRX for bandwidth if the sender's free bandwidth is used up.

Run it once with a recipient that holds USDT and once with an empty one, and you'll see the gap for yourself. There's also a dedicated estimateenergy endpoint, but it's disabled by default on nodes, so not every provider supports it.

Sources and further reading

Accept USDT on your website

Hosted checkout, signed webhooks and a test mode. 0% processing fee, no monthly fee.