TRON GOBLIN
explorerv0.3-beta
MAINNET
block #0
Explorer / Blog / Bandwidth and energy on Tron: which one do you actually need?

Bandwidth and energy on Tron: which one do you actually need?

Tron splits transaction throughput into two resources. Different operations need different ones — a practical guide to which is which.

Tron has two transactional resources: bandwidth and energy. They cover different costs, are paid for in different ways, and are needed for different operations. Most confusion about Tron fees comes from conflating them or assuming you need both for everything. You don't.

Here's the practical guide to which is which.

The two resources, in plain English

Bandwidth covers the cost of broadcasting a transaction. Every transaction has a serialized byte size — its raw_data plus signatures — and the network charges one bandwidth point per byte. Bandwidth is consumed by every transaction, no exceptions.

Energy covers the cost of executing smart-contract code. Energy is roughly analogous to gas on Ethereum. It's only consumed when your transaction triggers a contract — calling a TRC20 transfer, swapping on SunSwap, depositing to JustLend. Native operations like sending TRX or freezing for resources don't touch energy at all.

Which operations need which

Every transaction needs bandwidth. Only some need energy. Here's the breakdown:

OperationBandwidthEnergy
TRX transferYes
TRC10 transferYes
USDT / USDC / TRC20 transferYesYes
SunSwap / DeFi interactionYesYes (lots)
Stake / UnstakeYes
Vote for SRYes
Account creationYes
Contract deploymentYesYes (lots)

The pattern: anything that runs contract code costs energy. Anything that doesn't, costs only bandwidth. TRC20 tokens like USDT are smart contracts, so a USDT transfer costs both. A native TRX transfer is bandwidth-only.

How you actually pay for them

Both resources have three payment paths, in increasing cost-per-tx order.

1. Free quota (bandwidth only)

Every account on Tron gets 1,500 free bandwidth per day, no stake required. This refills automatically each day at midnight UTC. It's enough for ~5–6 simple TRX transfers per day with zero TRX cost.

There's no equivalent free quota for energy. If you want to send a USDT transfer for "free" (no per-tx cost), you have to stake or rent.

2. Stake (lock TRX, get daily resources)

You stake TRX explicitly for one resource type — bandwidth or energy. The network gives you a daily share of the global pool proportional to your share of the total stake. The TRX is locked in protocol stake; under Stake 2.0, unstaking takes 14 days.

The math: your daily resource = (your stake / total network stake for that resource) × total daily pool. Pull live numbers and project the conversion in the resource calculator.

3. Burn (pay per transaction)

If you have neither free quota nor stake, the protocol burns TRX from your balance to pay for the resources you used. Current burn rates from chain parameters:

  • Bandwidth: 1000 sun per point (0.001 TRX). A typical transaction uses ~270–400 bandwidth points.
  • Energy: 100 sun per unit (0.0001 TRX). A USDT transfer uses ~31,000 energy. A SunSwap swap uses ~130,000.

Burn rates are governed by on-chain SR proposals and change occasionally. The fee estimator always reflects current values.

4. Rent (energy only — short-term, no lockup)

Stake 2.0 added DelegateResourceContract, which made energy markets viable. You can rent energy from on-chain markets at typically 15–25% of the burn rate, no TRX lockup. Bandwidth has no equivalent commodity market — most users get enough from the free quota or modest stake.

The energy markets explainer covers the mechanism and the practical providers.

When to stake which one

For most users, the answer is energy, not bandwidth. The reasoning:

  • Bandwidth is mostly free. The 1,500/day quota covers casual usage. You'd need to send ~5+ transactions a day, every day, before bandwidth becomes a real cost center.
  • Energy is needed for any TRC20 transfer. Sending USDT, swapping on SunSwap, interacting with any DeFi protocol — all need energy, none of them touch the bandwidth quota.

If you're a heavy USDT mover (a payment processor, an exchange, an OTC desk), the stake calculus is straightforward: stake enough to cover your daily energy needs, never think about it again.

If you're a casual user who only sends TRX or TRC10 occasionally — you don't need to stake at all. The free bandwidth quota has you covered.

TL;DR

  • Bandwidth = byte-cost of broadcasting. Every tx uses some. 1,500 free per day per account.
  • Energy = execution cost of contract code. Only contract-touching ops use it. No free quota.
  • Stake covers daily resource needs. Burn covers occasional overflow. Rent (energy only) is the cheapest steady-state option for heavy users.
  • If you mostly send USDT, you need energy. If you mostly send TRX, you probably don't need anything.

Plug your real volume into the resource calculator for concrete numbers.