At Tronsell.io, we deal with TRON transaction costs every day, and one situation comes up in user questions again and again: you hit Send, and the wallet throws back an error — “Not enough bandwidth.” The transaction doesn’t go out, and the wallet page gives you no hint about what to do next. The good news: this error has nothing to do with your internet connection, and it can almost always be resolved in under two minutes. Below, I’ll explain what the error means and the four ways to fix it.
What “Not Enough Bandwidth” Actually Means
On TRON, bandwidth points pay for the storage a transaction occupies. One bandwidth point covers one byte of transaction data. A plain TRX transfer takes up about 270–300 bytes, and a TRC-20 USDT transfer about 345 bytes. Without enough bandwidth, the transaction cannot be written to the blockchain, and it fails. If you want the full picture of how bandwidth works — costs, limits, and how to get more — we’ve put it in our guide to what TRON bandwidth is and how it works.
Your bandwidth points come from three sources, and the network draws them down in this order:
- A free daily allowance. Every activated account receives 600 free bandwidth points per rolling 24-hour window.
- Staked or delegated bandwidth. Bandwidth obtained by staking TRX through Stake 2.0, or bandwidth delegated to your address by another account.
- A TRX burn. If the first two fall short, the network burns TRX from your balance at 0.001 TRX per bandwidth point to cover the rest.
The key detail: as long as your wallet holds enough TRX, the system burns it automatically to make up the bandwidth gap. The “Not enough bandwidth” error appears only when your available bandwidth is exhausted and your TRX balance cannot cover the burn fee either. That is why the error shows up most often on empty wallets or wallets holding very little TRX.
Why Your Free Allowance Didn’t Cover Your Transfer
Three common reasons:
- You already sent a transaction in the past 24 hours. Free bandwidth does not reset all at once at midnight. TRON runs on a rolling 24-hour window, and the allowance recovers gradually. If you sent a transaction this morning, that portion of your allowance is still in its recovery cycle.
- The guide you read is outdated. Many older tutorials still quote 5,000 free bandwidth points per day — that was the old parameter. The current network allowance is 600 points, roughly enough for two TRX transfers or one USDT transfer a day, with little to spare.
- Your wallet holds almost no TRX. Without a TRX balance, there is nothing to burn as the fallback payment for the transaction’s byte fee, and the network rejects the transaction outright at the broadcast stage.
Four Ways to Fix the Error
1. Top Up a Small Amount of TRX (Fastest)
You can work out the expected fee in advance: transaction bytes × 0.001 TRX. For a USDT transfer, the bandwidth cost comes to about 0.35 TRX; for a plain TRX transfer, about 0.30 TRX. Keeping 1–2 TRX in the wallet is enough to pay the bandwidth fee and get the transaction out normally. The system burns the TRX and charges the fee automatically — you don’t need to adjust any settings.
A warning for USDT senders: that calculation covers the bandwidth side only. If you have neither staked nor rented energy, a USDT transfer also burns about 6.5 TRX to pay for energy. If your TRX balance cannot cover that energy burn, the transaction does make it on-chain but fails during execution with an OUT_OF_ENERGY error, and the resources already consumed are not refunded. The next section explains this mechanism in detail.
2. Wait for the Rolling 24-Hour Window to Recover
If the transaction can wait a few hours, this option costs nothing. The allowance recovers gradually rather than resetting all at once at a fixed time, so capacity slowly climbs back. How fast it comes back depends on when your earlier transactions went out.
3. Stake TRX for Bandwidth
If you send transactions every day, staking beats burning. At current network-wide stake levels, staking 1 TRX for bandwidth yields about 1.6 bandwidth points per day (the actual yield moves with the total TRX staked across the network). Two things to understand before you stake: the stake must be designated for bandwidth — a single stake cannot be split between bandwidth and energy — and once you unstake, a 14-day waiting period applies before the TRX can be used again.
4. Receive Delegated or Rented Resources
Another account can delegate bandwidth directly to your address, with a minimum equivalent of 1 TRX. For users sending USDT, though, the resource that really needs attention is energy — see the next section.
The Check Most People Miss: Energy
Let me make one thing clear first: the bandwidth error has nothing to do with energy. That check is completed before the transaction is broadcast, and it only compares available bandwidth against the size of the transaction data, with burning TRX as the fallback. A plain TRX transfer consumes no energy at all, yet it can still trigger this error.
Energy appears in this guide because of what happens after you have cleared the bandwidth error. A USDT (TRC-20) transfer has to run a smart contract, and executing that contract consumes TRON energy (Energy). Energy is a separate resource, and it comes with no free allowance. A wallet empty enough to hit the bandwidth error almost certainly has no staked or delegated energy either, and both resources fall back on the same TRX balance for their fees. For the fundamentals — what energy is and how it connects to TRX fees and transactions — see our complete guide to TRON energy.
The two also differ in one crucial way: a bandwidth shortfall stops the transaction before it ever reaches the chain, while an energy shortfall hits after the transaction is already on-chain — it fails during contract execution, and the resources consumed up to that point are not refunded. One real test case: a wallet holding 6 TRX, with no energy and its free bandwidth untouched, sent USDT. The transaction failed with OUT_OF_ENERGY — yet all 345 bandwidth points and 60,000 energy were consumed, burning the entire 6 TRX.
In late September 2026, we sampled 14 consecutive real USDT transfers: 11 of them consumed 64,285 energy (transfers to addresses that already held USDT), and the other 3 consumed 130,285 energy (first transfers to addresses that had never held USDT).
Under the current rules, each unit of energy burned is charged at 0.0001 TRX. If your wallet holds no energy, the transfer burns TRX straight from your balance: about 6.5 TRX for a standard transfer, and about 13 TRX for a first transfer to an address with no USDT at all.
So even with the bandwidth error fixed, USDT senders still burn about 6.5 TRX per transaction to pay for energy. You can rent energy on the TRON energy market (we run this service at Tronsell.io, and other platforms offer it as well). Renting generally brings the cost down to a fraction of what burning TRX directly would cost, and most rental packages also cover the bandwidth the transfer needs. That gap is exactly what our guide to renting TRON energy and paying 70–90% less on every USDT transfer walks through.
How We Check Resources Before Sending
Open the resource page in your wallet, or look up your address on TronScan. Both show your remaining bandwidth, remaining energy, and recent consumption. It is a 30-second habit that heads off most resource errors before they happen: check those two numbers first, then decide whether to send the transaction, top up your TRX, or rent resources. If you’re not sure how much energy a transfer actually needs, I’ve broken it down in our guide to how much TRON energy you need to send USDT — and why it doubles.
Frequently Asked Questions
Does a failed “not enough bandwidth” transaction cost anything?
No. The transaction is rejected before it reaches the blockchain, so no bandwidth, no energy, and no TRX is consumed. Fix the resource gap and send again. An out-of-energy failure is a different case: by that point the transaction is already on-chain, and the bandwidth and energy it consumed are not refunded. If a transfer of yours has already failed this way, start with our guide to fixing the out-of-energy error on TRON and saving your USDT.
How much bandwidth does a USDT transfer need?
About 345 bandwidth points, plus roughly 64,000–65,000 energy — or about 130,000 if the receiving address has never held USDT. Bandwidth alone is never enough to complete a TRC-20 transfer.
Why do older articles say 5,000 free bandwidth points?
The free allowance was reduced to 600 points per day through TRON’s on-chain governance parameter (getFreeNetLimit). Old tutorials were written against the previous value. Always check current chain parameters before trusting a guide’s numbers.
Can I send USDT with zero TRX in my wallet?
Not by default. The energy for the contract call must come from staked energy, delegated energy, or burned TRX. A wallet with zero TRX and zero resources cannot broadcast a USDT transfer — but a wallet fully covered by delegated resources can.
Sources
- TRON Developer Documentation, “Bandwidth and Energy” — 600 free bandwidth points per rolling 24-hour window, linear 24-hour recovery, burn prices of 0.001 TRX per bandwidth point and 0.0001 TRX per energy unit, 14-day unstaking delay. Accessed October 9, 2026.
- TRON Developer Documentation, “Resource Model” — chain parameters getFreeNetLimit (free bandwidth quota) and getTransactionFee (bandwidth burn price), resource delegation minimum of 1 TRX. Accessed October 9, 2026.
- Toscale, on-chain measurement of 14 consecutive USDT transfers — energy consumption of exactly 64,285 or 130,285 per transfer, and a 345-byte (345-point) bandwidth charge on multi-transfer days. September 27, 2026.
- Chaingateway, TRON Energy and Bandwidth Calculator — per-transaction consumption reference (about 64,000 / 134,000 energy tiers, 345 bandwidth points for a TRC-20 transfer). 2026.
- Gaspeek, TRON Bandwidth Calculator — transaction size examples (about 268 bytes for a TRX transfer) and bandwidth yield of roughly 1.6 points per day per 1 TRX staked. Accessed October 9, 2026.
- TRON White Paper v2.0 — historical reference for the original 5,000 free bandwidth points per day, a parameter since superseded.
- FeeSaver, “FAILED – OUT OF ENERGY Troubleshooting” — documented reproduction of an on-chain USDT transfer failure: a wallet holding 6 TRX with no energy sent USDT; the transaction failed with OUT_OF_ENERGY and still consumed 345 bandwidth points and 60,000 energy (6 TRX burned). Accessed October 9, 2026.
- OneKey, “TRC20 Transfer Failed? Troubleshooting” — failed on-chain transactions may still consume bandwidth, energy, or TRX without refund. Accessed October 9, 2026.
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Chain parameters such as resource prices and free allowances are governed on-chain and can change; verify current values before making transaction decisions.