Education
•
5 minute read
Share Article
Table of Contents
TRON doesn’t charge a single gas fee like Ethereum. Instead, every transaction consumes one or two network resources: Bandwidth and Energy. If your address has enough of them, the transaction runs without burning any TRX. If it doesn’t, the network burns TRX to cover the gap.
Understanding these two resources explains almost everything about how TRON fees behave: why a TRX transfer is often free, why a USDT transfer can cost several TRX, and why the same transfer sometimes costs twice as much. This guide covers how the resource model works, how much each type of transaction uses, what happens when you run out, how resources regenerate, and how to check your own balance.
How TRON’s resource model works
Every TRON transaction has two properties the network needs to pay for: its size, and the amount of computing work it causes. Bandwidth pays for size. Energy pays for computing work. Simple transactions only need Bandwidth, while anything that runs a smart contract needs both.
Bandwidth: paying for transaction size
Bandwidth is measured in points, and one point equals one byte of transaction data. Every transaction uses Bandwidth, because every transaction has to be stored on the blockchain. A basic TRX transfer is only a few hundred bytes, so it uses a few hundred points.
Every activated TRON account receives a free daily allowance of 600 Bandwidth points. That is usually enough for one or two simple transfers a day. Beyond that, Bandwidth comes from staking TRX, from another account delegating it to you, or from burning TRX.
Energy: paying for smart-contract work
Energy measures the computing work a smart contract performs. Token transfers on TRON, including USDT TRC-20, are smart-contract calls, so they need Energy. The more complex the contract logic, the more Energy it uses.
Unlike Bandwidth, Energy has no free daily allowance. It comes only from staking TRX, from delegation by another account, or from burning TRX at the moment of the transaction. That is why USDT transfers are where most users feel TRON’s fees.
Energy vs Bandwidth at a glance
The two resources work in parallel but follow different rules.
Bandwidth | Energy | |
|---|---|---|
What it pays for | Transaction size in bytes | Smart-contract computation |
Used by | Every transaction | Smart-contract calls, including TRC-20 transfers |
Free daily allowance | 600 points per activated account | None |
Price when burned | 1,000 sun per point (0.001 TRX) | 100 sun per unit (0.0001 TRX) |
Can be staked for | Yes | Yes |
Can be delegated | Yes | Yes |
Regenerates | Yes, over 24 hours | Yes, over 24 hours |
One sun is one millionth of a TRX. The network can change both burn prices through a vote of Super Representatives, and the Energy price was last changed in August 2025, when it fell from 210 to 100 sun.
How much Bandwidth and Energy transactions use
Consumption depends on the type of transaction. The figures below are typical values; exact numbers vary slightly with the data a transaction carries and, for contracts, with the contract’s current state.
Operation | Bandwidth | Energy |
|---|---|---|
TRX transfer | About 270 points | None |
TRC-10 token transfer | About 280 points | None |
USDT transfer to a wallet that holds USDT | About 345 points | About 65,000 |
USDT transfer to a wallet with no USDT | About 345 points | About 131,000 |
Staking, unstaking, voting, claiming rewards | A few hundred points | None |
DEX swap or DeFi action | A few hundred points | Varies, often 100,000 or more |
Deploying a smart contract | Depends on contract size | Depends on contract size, often very large |
Operations built into the TRON protocol, such as staking and voting, are system contracts and use only Bandwidth. Anything that calls a user-deployed smart contract uses Energy as well.
Why a USDT transfer uses so much Energy
Two things drive the Energy cost of USDT. The first is the difference between wallets. When USDT is sent to an address that has never held it, the contract has to create a new balance record in its storage, and writing new storage is expensive. That is why the second transfer type in the table uses roughly twice as much Energy as the first.
The second factor is TRON’s dynamic energy model. Contracts that are used very heavily can have their Energy consumption raised by a multiplier, which spreads network load more fairly. USDT is the most heavily used contract on TRON, so its transfers cost more Energy than a simple token transfer would otherwise need. The multiplier can change, which is why published figures for USDT sometimes shift slightly.
Operations with fixed fees
A few account-level operations don’t follow the resource model and instead carry a fixed TRX fee. Activating a new address, which happens automatically when it receives its first TRX transfer, costs about 1 TRX, usually paid by the sender. Our guide on activating a TRON wallet explains the process. Updating account permissions, for example to set up multi-signature control, costs 100 TRX. These fees are burned in addition to any Bandwidth the transaction uses.
What happens when you run out of resources
If an address doesn’t have enough Bandwidth or Energy, the transaction doesn’t simply stop. The network burns TRX from the sender’s balance to make up the difference, at the prices shown in the comparison table above. Only if there isn’t enough TRX either does the transaction fail.
In practice this means a USDT transfer to a wallet that holds USDT burns about 6.5 TRX for Energy, and a transfer to a new wallet burns about 13 TRX. A TRX transfer without Bandwidth burns roughly 0.27 TRX. For a complete breakdown of what different transfers cost in TRX and dollars, see our guide to TRC-20 fees on TRON.
The order in which resources are used
The network always tries the cheapest source first. For Bandwidth, the order is:
Bandwidth from TRX you have staked, or that another account has delegated to you.
Your free daily allowance of 600 points.
TRX burned from your balance.
Bandwidth sources aren’t combined within one transaction. If neither your staked Bandwidth nor your free allowance can cover the whole transaction on its own, the entire transaction is paid by burning. Energy works differently: the network uses whatever staked or delegated Energy you have, then burns TRX only for the part that is missing.
There is one more possibility for Energy. A contract developer can choose to pay part of the Energy for calls to their contract, so users of some applications pay less than the table suggests. Our article on sponsoring fees on TRON explains how that works.
Fee limit and failed transactions
Every smart-contract call carries a fee limit: the maximum amount of TRX the sender allows the network to burn for Energy. If the transaction needs more than that, it stops partway and fails with an out-of-energy error, and the Energy used up to that point is still spent. The fee limit has to be high enough to cover a full burn even if you expect staked or delegated Energy to pay, because it is checked before execution. Our guide to FeeLimit on TRON explains how to set it.
Other common messages, such as “account resource insufficient” or “insufficient TRX to cover network fees”, mean the address lacks both the resource and the TRX to burn for it. Each variant is covered in our overview of TRON network errors.
How Bandwidth and Energy regenerate
Resources on TRON are not one-time credits. They refill automatically. Your free Bandwidth allowance recovers gradually over 24 hours after you use it. Bandwidth and Energy from staking behave the same way: once used, they recover in a straight line across the following 24 hours, reaching the full amount again a day later.
This has a practical consequence. A stake that produces 65,000 Energy doesn’t cover one USDT transfer and then disappear; it covers roughly one such transfer every day for as long as the stake stays in place. Delegated resources regenerate the same way while the delegation lasts. Unused resources don’t accumulate beyond your maximum, so there is no benefit in saving them up.
Why do you need Energy?
Because almost everything people actually do on TRON involves smart contracts. Sending USDT, swapping on a decentralised exchange, lending, minting NFTs, or interacting with any application runs contract code, and contract code consumes Energy.
With no Energy on your address, each of those actions burns TRX. For an occasional transfer the cost is modest. For someone sending USDT every day, or a business sending hundreds of transfers, burning becomes a significant and unpredictable expense, because the dollar value of the burned TRX rises and falls with the TRX price. Having Energy available on the address removes most of that cost and makes it predictable.
Ways to cover Bandwidth and Energy
There are three ways to pay for resources: burn TRX each time, stake your own TRX, or receive resources that someone else has staked and delegated to you. Burning needs no preparation but costs the most. The other two need a little setup and cost much less per transaction.
Staking TRX for Bandwidth or Energy
Under TRON’s Stake 2.0 system, you lock TRX and choose one resource in return. A single stake produces either Bandwidth or Energy, not both, so if you need both you create two stakes. The amount you receive is your share of the network’s daily resource pool, based on your share of all TRX staked for that resource. Staked TRX also gives you votes for Super Representatives, which earn rewards. Unstaked TRX becomes available to withdraw after a 14-day waiting period.
Receiving delegated resources
Stake 2.0 also lets any account delegate the resources from its stake to a different address. This is how you can cover a wallet that holds little or no TRX: one address stakes, another uses the resources. It is also the mechanism behind renting TRON Energy, where a provider delegates resources to your address for an agreed period and reclaims them afterwards. Your private key and funds are never involved, because delegation needs only your public address.
A delegation can be open-ended, in which case the delegating account can reclaim the resources at any time, or locked for a set period, during which it can’t be withdrawn. Every delegation is recorded on-chain, so you can confirm on Tronscan exactly which address delegated resources to you, how much, and when.
Which approach suits you depends mostly on how much TRX you hold and how regularly you send. We compare the two in detail, with a worked cost example, in TRON Energy staking vs renting.
How to check and estimate your resources
Before sending anything important, it is worth knowing what resources your address has and what the transaction will need.
Checking resources in TronLink and on Tronscan
In TronLink, your available Bandwidth and Energy are shown on the account screen, usually with a bar that shows how much has been used and how much remains. On Tronscan, paste your address into the search bar and open the resources section of the account page. It shows your free and staked Bandwidth, your Energy, what you have delegated to others, and what has been delegated to you. Developers can read the same data through the getaccountresource method of a TRON full node or TronGrid.
Estimating Energy before you send
Most wallets show an estimated resource cost on the confirmation screen before you sign. For more precision, developers can simulate a contract call with the estimateenergy or triggerconstantcontract methods, which return the Energy the call would use without broadcasting it. You can also look up a similar past transaction on Tronscan: each transaction page lists the exact Bandwidth and Energy it consumed and how much TRX was burned.
For USDT in particular, the quickest check is whether the recipient already holds USDT. If they do, plan for about 65,000 Energy; if not, plan for about 131,000.
FAQ about TRON Bandwidth and Energy
Short answers to the questions people ask most often about TRON’s two resources.
What’s the difference between TRON Energy and Bandwidth?
Bandwidth pays for the size of a transaction and is used by every transaction. Energy pays for smart-contract computation and is used only by contract calls such as USDT transfers.
Do I need Bandwidth to send USDT?
Yes. A USDT transfer uses about 345 Bandwidth points in addition to its Energy. The free daily allowance usually covers one or two such transfers.
How much free Bandwidth do I get per day?
Each activated account receives 600 free Bandwidth points, which recover gradually over 24 hours after use. There is no free Energy.
Why did my USDT transfer use 131,000 Energy?
Because the recipient had never held USDT. Creating a new balance record in the contract roughly doubles the Energy needed compared with sending to a wallet that already holds USDT.
How much does one unit of Energy cost in TRX?
When burned, one unit of Energy costs 100 sun, which is 0.0001 TRX. So 65,000 Energy equals about 6.5 TRX.
Do TRX transfers use Energy?
No. Sending TRX or TRC-10 tokens uses only Bandwidth, which is why these transfers are often free within the daily allowance.
Can I stake TRX for both Energy and Bandwidth?
Yes, but each stake produces only one resource. Split your TRX into two stakes to receive both.
Latest Release
