TRON Energy vs Bandwidth: Can You Buy, Sell or Rent Them?

You cannot sell TRON bandwidth or energy the way you sell a token. Neither is a transferable asset; both are shares of the network’s daily resource supply that come from staked TRX. What you can do is lend them: under Stake 2.0, an account with staked TRX can delegate its bandwidth or energy to another address while the TRX stays staked under its own name. Every “sell bandwidth” or “buy TRON energy” offer works this way: the seller stakes and delegates, and the buyer pays.

So a buyer has four ways to cover a transaction: use the free 600 bandwidth a day, rent a delegation, stake their own TRX, or let the network burn TRX. A seller has one: stake TRX and delegate it, directly or through a marketplace. Resources you received by delegation cannot be delegated again, so rented energy cannot be resold.

Last checked November 9, 2026, against TRON’s developer docs, the TRONSCAN chain parameters API and TronGrid.

Four ways to pay for a USDT transfer

The figures below are for one USDT transfer to an address that already holds USDT: 64,285 energy and 345 bandwidth, from the example transaction the TRON docs link to.

The staking figures use the network totals TronGrid’s wallet/getaccountresource returned on November 9, 2026: 18,610,279,743 TRX staked for energy and 26,631,914,757 TRX staked for bandwidth. With the docs’ formula, one staked TRX yields 180,000,000,000 ÷ 18,610,279,743 = about 9.67 energy a day, or 43,200,000,000 ÷ 26,631,914,757 = about 1.62 bandwidth (calculations). The numbers move whenever total stake changes. Our TRON staking guide covers the 14-day unstaking wait and the risks of locking that much TRX.

Can you sell TRON bandwidth or energy?

Only by delegating it. TRON’s delegation docs set the rules:

• What can be delegated: bandwidth and energy. TRON Power, the voting weight from staking, cannot be delegated.
• Only your own stake: you can delegate resources from your own Stake 2.0 stake. Resources you received through delegation cannot be delegated again.
• Minimum: 1 TRX of stake per delegation. The balance field is the TRX behind the resources, not an energy or bandwidth amount, so what the recipient gets depends on the network’s current totals.
• Recipient: must be an already activated address other than your own, and not a contract. Delegation does not activate an account.
• Lock: a delegation can be locked so you cannot take it back early. The maximum lock is chain parameter getMaxDelegateLockPeriod, which TRONSCAN showed at 864,000 blocks on November 9, 2026, about 30 days at 3 seconds a block (calculation). An unlocked delegation can be withdrawn at any time.
• Taking it back: undelegating also takes a proportional part of the recipient’s resources that are still recovering, so a buyer can lose part of a rental that has not yet refilled.

A delegation transaction names the owner, the receiver, the stake behind it, the resource and the optional lock. It has no field for a price. Payment between seller and buyer is a separate arrangement, which is the gap rental services fill.

Marketplaces describe the seller’s side on their own sites. TronSave’s provider guide asks for at least 5,000 TRX staked, a permission that lets TronSave delegate and reclaim the resources on the provider’s behalf, and a listing, automatic or manual. The 14-day unstaking period still applies to the staked TRX. TRON’s own docs also point to the JustLend energy rental market for renting energy.

How renting works for the buyer

From the buyer’s side, a rental is a delegation to your address for a fixed time. The services publish their own steps:

• TronZap (tronzap.com): send TRX to the address on its homepage; energy is calculated from the amount, “arrives within a minute and lasts 1 hour.” Its page showed 2.45 TRX for 65,000 energy and 4.90 TRX for 131,000 on November 9, 2026. It also rents bandwidth and energy-and-bandwidth bundles.
• TronSave (buyer guide): order on the website with a connected wallet, through a Telegram bot from an account balance, or with ZapBuy, a TRX transfer to its bot address that creates a 1-hour energy rental for the sending wallet. ZapBuy’s minimum is 65,000 energy, and TronSave says to send from a regular wallet, not a contract or an exchange. Its Auto Buy tops up energy or bandwidth when an address falls below a threshold.

Rent to the address that will sign the transfer, check that it is activated, and order about 131,000 energy if the recipient has never held USDT. Use the energy before the rental ends: it does not refill after that.

Is buying bandwidth worth it?

For most senders, no. A USDT transfer is about 345 bytes, so the free 600 a day covers one (calculation: 600 ÷ 345 = 1.7), and a 270-byte TRX transfer fits twice. The second USDT transfer of the day is where people get caught: bandwidth sources are not combined. If your staked bandwidth or free quota cannot cover the whole transaction, the network burns TRX for all 345 bytes, 0.345 TRX, not just the shortfall.

That 0.345 TRX is small next to the 6.43 TRX energy burn, which is why TRON’s docs note that energy delegation is more common than bandwidth delegation. Renting or staking bandwidth pays off for addresses that send many transactions a day, such as payment or exchange wallets.

Energy vs bandwidth: what each pays for

Bandwidth pays for the size of a transaction in bytes, and every on-chain transaction uses it. Energy pays for smart contract execution: each TRON Virtual Machine instruction has a fixed energy cost. A TRX transfer needs bandwidth only; a USDT (TRC-20) transfer, a swap or a token approval needs both. For what makes a token TRC-20, see what TRC-20 means.

All five values are chain parameters (getFreeNetLimit, getTransactionFee, getEnergyFee, getTotalNetLimit, getTotalEnergyCurrentLimit), and the TRONSCAN API returned them unchanged on November 9, 2026. The energy price has been 100 sun since proposal #104 took effect on August 29, 2025; it was 210 sun before that and 420 sun before September 2024. The free bandwidth quota has been 600 since proposal #87 in July 2023.

Energy is settled differently from bandwidth. Staked or delegated energy can cover part of a contract call, with TRX burned for the rest, up to the transaction’s fee_limit. If that cap is too low, the call fails; see running out of energy on TRON.

Worked example: two real USDT transfers

The TRON docs link two USDT transfers from November 27, 2025 as examples. TRONSCAN’s API shows each one’s energy, the dynamic-energy surcharge inside it and the 345 bytes of bandwidth, which the sender paid by burning TRX.

USDT’s contract sits at the maximum dynamic-energy factor, 4.4 times its base cost, which is why most of each figure is surcharge. The new-holder transfer costs more because writing to an empty balance slot takes 20,000 energy instead of 5,000 before that factor is applied.

With the free bandwidth unused, the 0.345 TRX disappears. With 65,000 rented energy, the first transfer burns no TRX for energy; the second would still burn about 6.5 TRX for the missing 65,285 energy (calculation), so order 131,000 for a new recipient. For the full sending steps see how to send USDT on TRON.

How to see your energy and bandwidth

• On TRONSCAN: search your address, or connect a wallet and open Resources for the Stake 2.0 page. “My Resources” > “Resource Overview” lists what you staked and delegated and has a Reclaim button for delegations that are not locked.
• In TronLink: the Stake page lets you choose “Energy + TRON Power” or “Bandwidth + TRON Power” and shows estimated resources before you confirm.
• Through the API: wallet/getaccountresource returns limits and usage. Remaining free bandwidth is freeNetLimit − freeNetUsed, remaining staked or delegated bandwidth is NetLimit − NetUsed, and remaining energy is EnergyLimit − EnergyUsed.