What's a Good sat/vByte Fee Right Now?

There is no single “good” Bitcoin fee. The right rate today might be 3 sat/vByte; next Tuesday afternoon it could be 80. A good fee is simply the lowest rate that still gets your transaction confirmed in the time frame you care about — and that number moves constantly with demand for block space.

That sounds frustrating, but it's actually good news: most people overpay because they guess high “to be safe.” Once you understand what sets the rate, you can pay the real market price instead of a panic price. Here's how to think about it.

First, what sat/vByte actually means

A Bitcoin fee isn't a percentage of the amount you send — it's a price for space. Every transaction takes up a certain number of virtual bytes (vBytes), and you bid a number of satoshis for each of those bytes. That bid is your fee rate: sat/vByte. Multiply it by your transaction's size and you get the total fee. Send $5 or $5 million — if the transactions are the same size, they cost the same fee.

Miners build each block (one every ~10 minutes) by picking the highest-bidding transactions first. So your fee rate is really your place in line. Bid above the crowd and you're in the next block; bid below it and you wait until demand falls.

The math: what a rate costs in practice

Total fee equals size in vBytes multiplied by rate in sat/vByte. A typical single-input, two-output native SegWit spend — one payment plus change, the shape of most everyday sends — is about 140 vBytes. Run that size at a few illustrative rates:

• →At 3 sat/vByte: 140 × 3 = 420 sats total.
• →At 20 sat/vByte: 2,800 sats for the identical transaction.
• →At 100 sat/vByte: 14,000 sats — over 30 times the quiet-network price for the exact same transfer.

Those rates are examples, not today's numbers, but the ratio is the lesson: the spread between a patient sender and a panicked one is routinely 10–30x. And size matters as much as rate. A legacy (non-SegWit) version of that same spend runs roughly 225 vBytes, so it pays about 60% more at any rate. Each additional SegWit input adds roughly 68 vBytes, so a wallet that has collected twenty small UTXOs can quietly build a 1,400-vByte transaction that costs ten times what you expected. The full size breakdown is in Bitcoin transaction fees explained.

Reading today's fee tiers

Live trackers — including SatSaver and mempool.space— group current rates into tiers based on how fast they're likely to confirm:

• →Fastest / next block — confirms in the next block or two (~10–20 min). The highest rate.
• →~30 minutes — a step down; confirms within a few blocks.
• →~1 hour — cheaper still, for anything that isn't urgent.
• →Economy / low priority — the floor. Confirms when the network clears, which can be hours — or minutes, if it's already quiet.

A “good” fee is the cheapest tier that meets your deadline. Paying a customer who's watching? Use the fast tier. Moving coins to cold storage on a Sunday? The economy tier is almost always fine.

Rough rules of thumb (and why they're only rough)

People want a cheat sheet, so here's an honest one for typical conditions in recent years. Treat these as orientation, not gospel — always check live before sending:

• →Quiet network: 1–5 sat/vByte often confirms within an hour or two.
• →Normal weekday: 5–20 sat/vByte for reasonably prompt confirmation.
• →Busy / spike: 40–150+ sat/vByte to get into the next few blocks.

The reason a fixed cheat sheet fails: Bitcoin fees can swing 80–90% within hours. A market crash, a big exchange moving funds, or a surge of activity can take the network from 4 sat/vByte to 60 in under an hour, then back down by morning. The number that was “safe” yesterday can be a massive overpay today. For what actually drives those spikes, see why Bitcoin fees get so high.

How to avoid overpaying

• →Don't trust your wallet's default blindly. Many wallets pad the “recommended” fee to guarantee speed. If yours lets you set a custom sat/vByte rate, check a live tracker first and enter the real economy or 1-hour rate.
• →Glance at the mempool before trusting any estimate. Thirty seconds of looking at how deep the queue is tells you whether rates are about to fall or climb — here's how to read it.
• →Match the fee to the urgency. Most sends aren't actually time-sensitive. If it can wait an hour, you can usually drop a tier or two.
• →Send when the network is quiet. Timing matters more than haggling over a couple of sats — see the cheapest time to send Bitcoin.
• →Bid low on purpose, with RBF enabled. With replace-by-fee turned on, a lowball bid isn't a gamble: if it hasn't confirmed by your deadline, bump the rate and rebroadcast. RBF vs CPFP explains both rescue tools.
• →Underpaid? You're usually not stuck forever. A low fee just means a slower confirm. If it's taking too long, there are safe fixes — see why your transaction is stuck.

When even a good fee is the wrong call

Sometimes the smart move isn't a better rate — it's not sending on-chain at all:

• →The payment is small. If the fee works out to more than a percent or two of the amount, on-chain is the wrong rail. Coffee-sized and tip-sized payments belong on Lightning, where fees are typically fractions of a cent — see Lightning vs on-chain fees.
• →You're consolidating UTXOs. Sweeping many small coins into one is good wallet hygiene, but it's the most byte-heavy transaction you'll ever build. Do it only when rates sit at the floor; consolidating during congestion torches the savings it was meant to create.
• →There's no deadline at all. Moving coins between your own wallets can wait indefinitely. Queue it at the economy rate and forget about it.

Quick answers

Is 1 sat/vByte ever enough?

Yes. 1 sat/vByte is the default minimum most nodes will relay, and when blocks aren't full it confirms fine. During sustained congestion, though, a 1 sat/vByte transaction can sit for days and may eventually be dropped from nodes' mempools. It's a floor bid, not a dead one — just make it with RBF enabled or genuine patience. Is it safe to send with a low fee? covers what actually happens to underpaid transactions.

Does sending more bitcoin cost more?

Not directly — fees price bytes, not value, so 0.001 BTC and 10 BTC in same-sized transactions pay the same fee. The indirect effect: a large send may need more inputs to fund it, and every extra input adds vBytes to the bill.

How fast will my chosen rate confirm?

There's no fixed answer, because confirmation speed is an auction outcome — it depends on what everyone else is bidding at that moment. A rate that beats most of the current queue lands in the next block or two; a rate below it waits its turn. How long does a Bitcoin transaction take? walks through the full timeline, block by block.

The bottom line

A good sat/vByte fee is the lowest rate that confirms within your deadline — and that's a live number, not a memorized one. Decide how fast you actually need it, read the current tiers, and pick the cheapest one that fits. Do that consistently and you'll routinely pay a fraction of what hurried senders pay for the exact same transaction.

Want the answer for right now instead of a rule of thumb? The live fee calculatorreads the current mempool and tells you the rate to use and whether it's worth waiting.