---
title: TRON energy and bandwidth: what a USDT transfer costs
description: What bandwidth and energy are, how staking TRX grants them, how much energy a USDT TRC-20 transfer burns, why rented energy is cheaper than burning TRX.
url: https://sablebolt.io/blog/tron-energy-and-bandwidth
---

[USDT between networks](https://sablebolt.io/blog)

# TRON energy and bandwidth: why a USDT transfer costs what it costs

Sablebolt Team 17 October 2026 10 min read

Contents

1. Two resources, not one fee
2. Where bandwidth and energy come from
3. What a USDT transfer actually burns
4. Energy rental as a market
5. Why the same transfer has two prices
6. Worked example: 100 USDT, three wallets
7. What a wallet needs before it can send USDT
8. Checklist before sending USDT on TRON
9. FAQ

Two people each send 100 USDT on TRON on the same afternoon. One pays about 13 TRX in fees. The other pays almost nothing. Neither of them did anything clever; the difference is where their wallet got its energy from, and whether the address they paid had ever held USDT before.

TRON does not charge a gas price the way Ethereum does. It charges two resources, bandwidth and energy, and only burns TRX when a wallet has run out of them. Understanding that one rule explains every USDT fee you will see on TRON, including why an "empty" wallet cannot send USDT at all. The figures below come from the TRON developer documentation and from live chain parameters and transactions, all checked on 11 October 2026.

## Two resources, not one fee

|  | Bandwidth | Energy |
|---|---|---|
| What it pays for | The size of a transaction in bytes, stored on chain | The computation a smart contract performs when it runs |
| Which transactions use it | Every transaction, including a plain TRX transfer | Only transactions that call a contract — a USDT transfer is one |
| Free allowance | 600 points per account, recovering over a rolling 24 hours | None |
| How to get more | Stake TRX for bandwidth | Stake TRX for energy, or receive it from someone who did |
| If you have none | The network burns TRX at 1,000 sun per point (0.001 TRX) | The network burns TRX at 100 sun per unit (0.0001 TRX) |

A sun is one millionth of a TRX. Both burn prices are chain parameters, set by vote and changeable; the values above are what the network returned on 11 October 2026. The free bandwidth quota, 600, is also a parameter, named getFreeNetLimit in the [TRON resource model documentation](https://developers.tron.network/docs/resource-model) .

A plain TRX transfer needs only bandwidth, and a typical one fits inside the free 600, which is why sending TRX from a fresh wallet feels free. A USDT transfer is a call to the USDT contract, and a contract call needs energy. Energy has no free allowance. That single fact is the source of nearly every "why is my USDT stuck" question on TRON.

## Where bandwidth and energy come from

**Staking.** The TRON documentation calls it freezing; wallets call it staking. You lock TRX and choose which resource it earns. Your share of the network's daily supply of that resource is proportional to your share of all TRX staked for it:

- bandwidth = (your TRX staked for bandwidth ÷ all TRX staked for bandwidth) × 43,200,000,000
- energy = (your TRX staked for energy ÷ all TRX staked for energy) × 180,000,000,000

The two large numbers are the network-wide daily limits, both chain parameters. Because the denominator moves as other people stake and unstake, the amount of energy one TRX earns changes from day to day; Tronscan shows the current figure. Resources regenerate: energy you use today is back within 24 hours, so a stake that covers one USDT transfer covers one transfer every day, for as long as it stays staked. Unstaking is not instant — the chain parameter getUnfreezeDelayDays was 14 on the check date, so TRX comes back two weeks after you ask for it.

**Delegation.** Staked resources can be delegated to another address, which can use them without staking anything itself. The [bandwidth and energy documentation](https://developers.tron.network/docs/bandwidth-and-energy) describes this through a dedicated contract type, with an optional lock period; the longest lock the chain allowed on the check date was 864,000 blocks, which at one block every 3 seconds is about 30 days. Delegation is what makes energy rental possible, and it is almost always energy that gets delegated, because bandwidth has a free tier and energy does not.

**Burning.** If a wallet has neither staked nor delegated resources, the network takes the shortfall from its TRX balance at the burn prices above. The order is fixed: for bandwidth, staked or delegated first, then the free quota, then burn; for energy, staked or delegated first, then burn. For a contract call, the transaction also carries a fee_limit — the most TRX the sender is willing to burn — and if the call needs more, it fails with the energy spent and nothing transferred.

≈ 2–5 min 1 confirmation on TRON

[Swap USDT TRC-20 to USDT BEP-20](https://sablebolt.io/swap/usdt-trc20/usdt-bep20)

## What a USDT transfer actually burns

Documentation gives the rules, not the figure, so we looked at the ledger. On 11 October 2026 we read thirty consecutive transfers of the USDT contract (TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t) on [Tronscan](https://tronscan.org/) . Every one of them used one of two energy amounts:

| Situation | Energy used | Bandwidth used | If the energy is burned, at 100 sun |
|---|---|---|---|
| The receiving address already holds USDT | 64,285 | 345 | 6.43 TRX |
| The receiving address has never held USDT | 130,285 | 345 | 13.03 TRX |

The bandwidth, 345 points, fits inside the free 600 once a day; if the free quota is used up, it costs 0.345 TRX. The energy is the real cost. The doubling for a first-time recipient comes from the contract having to create a new storage entry for that address's balance, which costs more computation than updating an existing one.

In the same thirty transfers, about half burned TRX for their energy and half paid from staked or delegated energy with zero TRX burned. That is the two prices from the first paragraph, on the same afternoon, for the same operation.

**The figures are current, not constant.** TRON runs a dynamic energy model: when a contract's recent energy use passes a threshold, every call to it is charged a multiplier that steps up gradually, decays when the load falls, and is capped — on the check date the cap was 4.4 times the base cost. The USDT contract is by far the busiest on the network. The way to know what a transfer costs today is to open a recent USDT transfer on Tronscan and read the energy line, exactly as we did.

## Energy rental as a market

Because delegation exists, energy has a price separate from the burn price. Someone who has staked a large amount of TRX for energy can delegate a slice of it to your address for an hour or a day, and charge a little TRX for it. Wallets, exchanges and standalone services do this; the service receives a small TRX payment, delegates enough energy for one or more transfers, and takes it back when the period ends.

The rental price is set by supply and demand between renters and stakers, so no figure printed here would stay true. What is true by construction is the relationship: rented energy costs less than burning TRX for the same transfer, or nobody would rent it. The burn price is the ceiling of the market. On the check date that ceiling was 6.43 TRX for a transfer to an existing holder and 13.03 TRX for a new one.

## Why the same transfer has two prices

| Way to pay for 64,285 energy | What you give up | When it makes sense |
|---|---|---|
| Burn TRX | 6.43 TRX, gone | You send USDT rarely and keep some TRX anyway |
| Rent energy for this transfer | A small TRX payment, set by the market | You send occasionally and do not want TRX locked up |
| Stake TRX for energy | TRX locked, returned 14 days after unstaking; the energy regenerates daily | You send USDT most days; the stake pays for itself quickly |

This is why a wallet app, an exchange and a friend can all tell you different numbers for "the fee to send USDT on TRON" and all be right. One burns, one has staked, one rents on your behalf and rolls the cost into a fee. None of them is quoting the network; they are quoting their own arrangement with it.

## Worked example: 100 USDT, three wallets

All three wallets hold 100 USDT and want to send it to a friend who already holds USDT, so the transfer needs 64,285 energy and 345 bandwidth.

**Wallet A** holds 100 USDT and 0 TRX. The transfer cannot be sent. There is no energy to use and no TRX to burn; the wallet shows a balance it cannot move. This is the most common state a new TRON wallet is in after receiving its first USDT.

**Wallet B** holds 100 USDT and 10 TRX, nothing staked. The transfer goes through: the free bandwidth covers the 345 points, and the network burns 64,285 × 100 sun = 6.4285 TRX for the energy. Wallet B is left with 3.57 TRX. A second transfer the same day to a friend who has never held USDT would need 13.03 TRX, which Wallet B no longer has — it would fail.

**Wallet C** holds 100 USDT, 1 TRX, and has rented energy for the day. The free bandwidth covers the bytes, the delegated energy covers the 64,285, and nothing is burned. The 1 TRX stays; it is there as a reserve in case the rental has lapsed. Wallet C paid the renter whatever the market asked, which was below 6.43 TRX, or it would have burned instead.

To put a figure in your own currency, multiply the TRX amounts by today's TRX price, which is on the [TRON coin page](https://sablebolt.io/coin/tron) .

## What a wallet needs before it can send USDT

- **An activated account.** A TRON address that has never received anything does not exist on chain yet. The first incoming transfer activates it; the sender pays a creation fee of 1 TRX, set by a chain parameter, on top of the transfer's own cost. Contract calls to a new address are the 130,285-energy case above.
- **Energy for one transfer**, from one of the three sources: staked TRX, rented energy, or a TRX balance large enough to burn — on the check date, 6.43 TRX for an existing holder and 13.03 TRX for a new one.
- **Bandwidth**, which the free 600 points cover for one or two transfers a day; a TRX balance covers the rest at 0.001 TRX per point.
- **A fee_limit high enough.** Wallet apps set this for you; if you are building the transaction yourself, a fee_limit below the energy cost makes the transfer fail with the energy spent.

If a wallet holds USDT and no TRX, the TRX has to arrive from outside: from an exchange withdrawal, from a friend, or by swapping a little of something you hold elsewhere into TRX, for example [USDT TRC-20 → TRX](https://sablebolt.io/swap/usdt-trc20/trx) sent from an exchange or another wallet that can pay its own fee. A few TRX is enough for several transfers; keep it topped up and the wallet never shows a balance it cannot move.

This is also why a swap from USDT on TRON to another network is paid for twice: once by your wallet, in energy or TRX, to send the deposit; and once by the payout network's fee, which the route page shows before you send. The first is explained here; the second is on the route page, for example [USDT TRC-20 → USDT BEP-20](https://sablebolt.io/swap/usdt-trc20/usdt-bep20) . A one-time deposit address may never have held USDT, so plan for the higher energy figure.

## Checklist before sending USDT on TRON

- The wallet holds TRX, staked energy or rented energy for at least one transfer — check which, and how much.
- You know whether the receiving address already holds USDT; if not, plan for double the energy.
- The wallet's free bandwidth is not already spent today, or there is TRX to cover 345 points.
- The receiving address is a T… address on TRON, and the token is the [USDT contract](https://sablebolt.io/coin/tether) TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t.
- If the fee looks far higher than 13 TRX, stop: the contract's dynamic multiplier or your fee_limit is the first thing to check on a recent Tronscan transfer.

## FAQ

Why can I send TRX from a new wallet for free, but not USDT?

A TRX transfer uses only bandwidth, and every account has 600 free bandwidth points a day. A USDT transfer calls a contract and uses energy, which has no free allowance. Without staked or rented energy, the wallet burns TRX for it — and a new wallet has none.

How much TRX do I need to keep in the wallet?

Enough to burn for one transfer in the worst case: on 11 October 2026, 13.03 TRX for a transfer to an address that has never held USDT, plus a small reserve for bandwidth. If you rent or stake energy, a reserve of a few TRX is enough.

Does the fee depend on the amount of USDT?

No. 1 USDT and 100,000 USDT cost the same energy; the contract does the same work. It depends only on whether the recipient already holds USDT, and on the dynamic multiplier for the contract at that moment.

Is renting energy safe?

Delegation gives your address the right to use someone else's staked energy; it does not give them any right over your wallet. The risk is paying for energy that does not arrive, so rent from the wallet or service you already use, and check that the energy shows in your account before sending.

Why did my transfer fail and still charge me?

The transaction's fee_limit was lower than the energy the call needed, or the account ran out of energy mid-execution. The network keeps the energy spent on the failed attempt. Check a recent USDT transfer on Tronscan for today's energy figure, and let the wallet set the fee_limit.

Will the 64,285 and 130,285 figures still be right next month?

Perhaps not. They depend on the dynamic energy model, which responds to the contract's load, and the burn price depends on a vote. The method does not change: open the latest USDT transfer on Tronscan and read its energy and fee lines.

## Related posts

- [USDT between networks USDT TRC-20 to BEP-20: three ways to move it and what each costs Exchange account, bridge, or a swap between two addresses: what each one asks of you, where each is dearer, and how 500 USDT moves through all three. 15 October 2026 10 min](https://sablebolt.io/blog/usdt-trc20-to-bep20-three-ways)
- [USDT between networks Sent USDT to the wrong network: what can and can't be recovered Four cases, decided by who controls the receiving address. One is a five-minute fix, one depends on a support team, one is impossible by design, and one is usually a loss. 16 October 2026 10 min](https://sablebolt.io/blog/sent-usdt-to-the-wrong-network)
- [USDT between networks How to pay someone whose USDT wallet is on a different network Their address starts with 0x and your USDT is on TRON. Three ways to make the payment, and what the receiver will see. 14 October 2026 9 min](https://sablebolt.io/blog/pay-usdt-to-a-different-network)