Not enough bandwidth
When TRON says not enough bandwidth: how NetFee burns TRX, why this is not an energy problem, and how staking for bandwidth fixes native transfers.
This error is about bytes, not USDT compute
Not enough bandwidth means the transaction’s size exceeded remaining bandwidth (BandwidthLimit minus BandwidthUsed, plus any free quota). Native TRX transfers hit this first. A USDT send can hit it too, but USDT’s headline failure is usually energy.
If your USDT failed and a helper says “bandwidth,” verify the resource tab. Mixing the two meters is how people freeze TRX for the resource they already have.
NetFee is the burn that looks like a mystery TRX charge
When bandwidth is short, TRON burns TRX as NetFee so the transaction can still carry its bytes. You may not see a friendly “out of bandwidth” toast — only a smaller TRX balance. Open the tx and look for network fee versus an energy fee.
Fixing energy will not stop NetFee. Stake or freeze TRX targeting bandwidth, or wait if you only exhausted today’s free quota and the send is small.
Dust and test sends chew free bandwidth
Address-poisoning dust, repeated 1 TRX tests, and memo-heavy transactions spend bandwidth. A morning of “just checking the address works” can empty the free meter before the real payment. Batch tests after you have staked bandwidth, or use one test, not twelve.
Free daily bandwidth regenerates; staked bandwidth is the stable ceiling. If you move TRX often, stake. If you only needed one tiny send, waiting may be enough.
Do not buy a seed-phrase bandwidth unlock
There is no mnemonic ritual for bandwidth. Stake in TronLink, confirm BandwidthLimit on the bandwidth checker, then retry the TRX send. Websites that restore bandwidth after a failed transfer in exchange for a seed are thieves.
This desk does not sell bandwidth. Optional deep scan is read-only, about 2–3 TRX, and does not mint NetLimit.
If both meters are empty, fix both
A day of USDT plus TRX can empty energy and bandwidth together. Read both checkers on the sending address. Stake some TRX for energy and some for bandwidth if you truly use both. Renting energy will not refill bandwidth unless the product you bought was a bandwidth delegation — confirm the type.
Help: @wholetron with the tx hash. Independent desk, not the TRON Foundation.
FAQ
What does not enough bandwidth mean?
Remaining bandwidth cannot cover the transaction’s byte size. The node may fail the send or burn TRX as NetFee.
Is this why my USDT failed?
Sometimes as a secondary fee, but USDT TRC20 usually fails first on energy. Check both meters.
How do I get more bandwidth?
Stake or freeze TRX for the bandwidth resource, or wait for free daily bandwidth if the send is small.
Will renting energy fix bandwidth?
Only if the rental actually delegated bandwidth. Energy delegation does not pay for transaction bytes.
Why did TRX decrease on a simple transfer?
Likely NetFee from a bandwidth shortfall. Inspect the transaction’s fee fields.
Can I paste a seed to unlock bandwidth?
No. That is a scam. Stake in your wallet. We never ask for a seed phrase.
Does deep scan add bandwidth?
No. It is a read-only ~2–3 TRX confirmation.