Occasional user (a few transfers per week)
Rely on free Bandwidth for TRX transfers. Budget ~15 TRX per USDT transfer burned from your balance, or stake 200–500 TRX for Energy to eliminate this cost.
Master the TRON Resource Model to optimize your transaction costs. This guide explains how Energy and Bandwidth are generated, consumed, and recovered, providing a precise roadmap for using the network at near-zero cost through staking and rental strategies.
| Resource | Covers | Free allocation | How to get more |
|---|---|---|---|
| Bandwidth | TRX transfers, TRC-10 transfers, account activation | 600 points/day | Stake TRX for Bandwidth, or burn TRX |
| Energy | TRC-20 transfers, smart contract calls, DApp interactions | None | Stake TRX for Energy, rent from a provider, or burn TRX |
When a resource runs out, the network automatically falls back to burning TRX from your balance. You cannot disable this fallback — you can only ensure you have sufficient resources to avoid it.
Every transaction type has a Bandwidth cost based on its byte size. Common costs:
| Transaction type | Approximate Bandwidth cost |
|---|---|
| TRX transfer | ~267 Bandwidth |
| TRC-10 token transfer | ~275 Bandwidth |
| Account activation (sender pays) | ~270 Bandwidth |
| Multi-signature transaction | ~350–400 Bandwidth |
Bandwidth does not cover smart contract calls. Any transaction that triggers a smart contract (including USDT transfers) uses Energy instead.
Each account receives 600 free Bandwidth points per day, resetting at 00:00 UTC. For most users who do a handful of TRX transfers daily, this free allocation is sufficient. You never need to stake for Bandwidth unless you are making many TRX transfers per day.
Freezing TRX and allocating it to Bandwidth gives you additional Bandwidth capacity. The amount generated is dynamic based on network-wide staking ratios. At typical network conditions, the Bandwidth from staking is a multiplier on top of your free 600 — useful primarily for applications that automate high-volume TRX transfers.
When free Bandwidth is exhausted, the network burns TRX at a rate of 1 TRX = 1,000 Bandwidth. A standard TRX transfer costs ~267 Bandwidth, so each transfer without free Bandwidth or staked Bandwidth costs roughly 0.267 TRX.
Energy is consumed by any transaction that executes code on the TVM. The amount consumed depends on the complexity of the operation.
| Operation | Approximate Energy cost |
|---|---|
| USDT (TRC-20) transfer | ~64,895 Energy |
| SunSwap token swap (V2) | ~150,000–300,000 Energy |
| JustLend supply | ~200,000–400,000 Energy |
| Simple TRC-20 contract call | ~30,000–80,000 Energy |
These are approximations. The actual cost depends on the specific contract logic, storage operations performed, and network congestion. Highly active contracts like USDT are subject to the Dynamic Energy Model (DEM), which can increase Energy costs by up to 3.4× during peak usage. TRONSCAN shows the exact Energy consumed after each transaction.
Unlike Bandwidth, Energy has no free daily allocation. Your options are:
When you have no staked or rented Energy, the network burns TRX from your balance at the current governance-set rate of 100 sun per Energy unit (= ~10,000 Energy per TRX burned).
At 100 sun/Energy, a USDT transfer costs roughly:
# Existing holder (base 14,650 × no penalty): ~1.5 TRX# Existing holder (base 14,650 × 4.4 max DEM): ~6.4 TRX# New account (base 29,650 × 4.4 max DEM): ~13.0 TRXThis rate has decreased significantly from its 2022 level of 420 sun per Energy unit — the result of two governance votes reducing fees. For anyone sending USDT more than once or twice a month, staking TRX for Energy still pays for itself quickly.
Open the extension, click your account name, then select the Resources tab. You will see:
Navigate to your address on tronscan.org. The Resources section on your account page shows:
If you need Energy temporarily — for example, before your staking setup is in place — you can rent it from third-party providers. Energy rental services delegate their staked Energy to your address for a short duration (typically 1–3 days) in exchange for a small TRX fee.
How rental compares to TRX burning:
For a single USDT transfer at typical congestion (~64,000 Energy including the Dynamic Energy Model (DEM) penalty):
For infrequent users who don’t want to stake long-term, rental is cheaper than burning. For regular users, staking is more cost-effective than either.
Occasional user (a few transfers per week)
Rely on free Bandwidth for TRX transfers. Budget ~15 TRX per USDT transfer burned from your balance, or stake 200–500 TRX for Energy to eliminate this cost.
Regular DeFi user (daily DApp interactions)
Stake 500–2,000 TRX for Energy. This covers multiple USDT transfers and DApp interactions per day without any TRX burn. Maintain 10–20 TRX liquid as a buffer.
Developer / high-volume application
Stake heavily for Energy and use delegation to fund user transaction costs. Monitor the dynamic Energy rate weekly and adjust stake as network conditions change.
Always keep a TRX buffer
Even with full staking, unexpected operations may exceed your Energy allocation. Always keep at least 10–20 TRX liquid in your wallet to avoid failed transactions.
The TVM executes contract operations one instruction at a time, consuming Energy at each step. This is the same model used by Ethereum and all EVM-compatible chains: computation is charged as it runs, not after a final outcome is determined. When a transaction reverts — because a contract condition was not met, a slippage limit was exceeded, or the fee limit was reached — the operations that already executed cannot be undone, and neither can the Energy those operations consumed.
Any TRX burned to cover Energy before the revert point is settled by the network. It cannot be returned.
You want to send USDT. You have no staked Energy, so the network will burn TRX from your balance to cover the cost. For a transfer to an existing holder at typical congestion, that is roughly 6–7 TRX; for a new account it can reach 13 TRX. Your wallet holds 6 TRX. The fee limit (the maximum TRX you authorize the network to burn for this transaction) is set to 6 TRX.
The transaction begins executing. At 6 TRX burned the fee limit is reached before the contract completes. The transaction reverts with OUT_OF_ENERGY.
The USDT transfer did not go through. The 6 TRX burned up to the revert point is gone. You now need additional TRX to cover a retry.
| Situation | What happens |
|---|---|
| Fee limit set below the actual Energy cost | The transaction burns TRX up to the fee limit, then reverts. The burn is not returned. |
| TRX balance only slightly above the estimated Energy cost | Minor variation in contract execution paths can push the actual burn over your available balance, triggering a revert. |
| Contract logic revert (e.g. slippage exceeded on a swap) | The transaction fails for a business-logic reason after partial execution — all Energy consumed before the revert point is still charged. |
Set the fee limit with margin. TronLink’s confirmation screen shows the fee limit before you sign — this is the right moment to check it. For a USDT transfer, costs range from ~1.5 TRX (low congestion, existing holder) to ~13 TRX (peak congestion, new account). A fee limit of 15–20 TRX leaves comfortable room. A 1.5× buffer on the expected cost is a practical rule of thumb.
Keep your TRX balance above the fee limit. The fee limit caps the burn, but the wallet still needs enough liquid TRX to reach that cap. Having 15–20 TRX available when attempting a USDT transfer means unexpected congestion won’t strand the transaction.
Stake TRX for Energy. With staked Energy, a failed transaction costs only Bandwidth — no TRX burn occurs on the Energy side. Staking ~1,600 TRX generates enough Energy per day (~14,650 Energy) to cover a single USDT transfer to an existing holder at zero burn cost.
Simulate before sending. TRONSCAN’s contract interface can run a call against the current chain state without broadcasting a transaction, confirming success and showing the exact Energy required before you commit.
TronLink displays the fee limit and the estimated Energy cost on the confirmation screen before you sign. Checking that your fee limit exceeds the estimated cost — and that your TRX balance exceeds your fee limit — takes seconds and covers the main risk. The fee limit is a parameter you control; setting it accurately is part of managing your resources on TRON.
All TRON resources — free Bandwidth, staked Bandwidth, and staked Energy — recover linearly over a 24-hour sliding window from the moment they are consumed. There is no hard reset at a fixed clock time. Think of each resource pool as a battery that begins recharging the instant you spend capacity.
| Resource | Daily capacity | Recovery behavior |
|---|---|---|
| Free Bandwidth | 600 points | Consumed points recover linearly over 24 hours from the time of use |
| Staked Bandwidth | Proportional to staked TRX | Consumed capacity recovers linearly over 24 hours from the time of use |
| Staked Energy | Proportional to staked TRX | Consumed capacity recovers linearly over 24 hours from the time of use |
If you consume all of your staked Energy at 10:00 AM, it is fully recovered by 10:00 AM the following day. Wait 12 hours and you have recovered 50%. You do not need to wait the full 24 hours — whatever has recovered is immediately available for your next transaction.
If you consume more resources before the previous amount has fully recovered, the system performs a weighted recalculation that merges your current recovery progress with the new consumption. In practice, this means heavy repeated usage keeps your pool partially depleted rather than restoring it to full between transactions.
Sending two USDT transfers in quick succession can fail on the second even when your staked Energy comfortably covers a single transfer. The first transaction consumed a portion of your pool; that portion is still mid-recovery when the second transaction runs. Either space transactions by a few hours, or stake enough TRX that a single USDT transfer represents a small fraction of your total pool — leaving plenty recovered capacity for follow-on transactions.