Sat Per Byte Calculator
Bitcoin fees have almost nothing to do with how much money you send. A $10 transfer and a $10 million transfer can cost exactly the same fee, while two $100 transfers can cost wildly different amounts, because every transaction pays for the block space it occupies, priced in satoshis per virtual byte (sat/vB). Enter a fee rate and a transaction size below to get the total fee in sats, BTC and USD, estimate the size from your address type and input count, or work backwards from a fee you already paid to the rate it represents.
Fee = fee rate (sat/vB) × transaction size (vB). Estimates only, not live mempool data.
The total fee is rounded to the nearest whole satoshi. The confirmation tier is rough guidance from the rate alone; actual confirmation depends on live mempool conditions.
Estimate transaction size
Count your inputs (the UTXOs being spent) and outputs (recipient plus your change address), pick the address type, and the estimator fills the size field in and calculates the fee.
Work backwards: what rate did I pay?
If a past transaction shows its total fee and its size (any block explorer lists both), divide them to recover the fee rate it paid.
Quick Answer
A typical native SegWit transaction of 276 vB at 10 sat/vB costs 2,760 sats (0.00002760 BTC, about $1.66 at a $60,000 BTC price). The fee is always the rate multiplied by the size: double the rate and the fee doubles, which is why the same transaction costs 41,400 sats ($24.84) at a congested 150 sat/vB. Enter your own rate and size in the calculator above for sats, BTC, USD and a confirmation tier in one result.
Key takeaways
- Total fee (sats) = fee rate (sat/vB) × transaction size (vB). The amount of bitcoin sent never enters the formula.
- Size comes from inputs and outputs, not value: each native SegWit input adds about 68 vB, each output about 31 vB, plus roughly 10 vB of overhead.
- This calculator uses the rate you type, not live mempool data. Check a mempool explorer for the going rate before you send.
- The reverse tool recovers the rate from any completed transaction: total fee ÷ size, for example 25,000 sats ÷ 250 vB = 100 sat/vB.
- Quick Answer
- How to use the sat per byte calculator
- The Bitcoin fee formula: one multiplication
- Worked example: a 276 vB SegWit payment at five fee rates
- Transaction sizes by address type: where the vB come from
- What fee rate should you choose? Reading the five tiers
- What competing calculators miss
- Sat/byte vs sat/vB: why the name of this page is the old unit
- Ways to pay less in fees
- Frequently asked questions
- Add This Calculator to Your Website
- References
How to use the sat per byte calculator
There are three tools in the card: the fee calculator, the size estimator and the reverse rate finder. The results stay hidden until you run one of them.
- Enter the fee rate: the sat/vB figure your wallet proposes, or tap Economy (~2), Standard (~10) or Priority (~50) to compare tiers. The worked example pre-fills 10 sat/vB.
- Enter the transaction size in vB: copy it from your wallet's confirmation screen, or scroll to the estimator, pick your address type, count inputs and outputs, and click "Estimate size and fill it in". That fills the size field and runs the fee calculation in one step.
- Add a BTC price if you want the USD figure: it is optional and changes nothing else. Without it, the result line reads "Enter a BTC price to see USD".
- Click Calculate fee: the result shows the fee in sats as the big number, then the same fee in BTC and USD, the multiplication itself, and a confirmation tier badge.
- Or work backwards: in the bottom section, enter a completed transaction's total fee and size to find the rate it paid.
Invalid entries are rejected with a plain message instead of a wrong number: a blank rate ("Enter a fee rate in sat/vB."), a blank size ("Enter a transaction size in vB (or use the size estimator)."), a negative rate ("Fee rate cannot be negative.") and a zero size ("Transaction size must be greater than zero."). The reverse tool has its own matching messages. Two quiet behaviours are worth knowing: commas are stripped from numbers, so "1,0" reads as 10, and a negative BTC price is treated as no price at all.
The Bitcoin fee formula: one multiplication
Total fee in satoshis = fee rate in sat/vB multiplied by transaction size in vBytes. That is the whole formula, the same one given by Bitcoin Core's estimatesmartfee documentation context and by every serious fee estimator.
In BTC: fee ÷ 100,000,000 | In USD: fee in BTC × BTC price
Reverse: fee rate (sat/vB) = total fee (sats) ÷ size (vB)
Size estimate: size (vB) = inputs × input size + outputs × output size + 10 overhead
A satoshi is the smallest unit of bitcoin: 100,000,000 sats make 1 BTC, which is why the BTC line always carries eight decimals. A virtual byte is how Bitcoin measures transaction data after SegWit: signature (witness) data counts at a quarter of its raw size under the weight rules set out in BIP 141, so a SegWit transaction's vB size is smaller than its byte size. Miners fill blocks by weight and pick the highest sat/vB first, so the rate is your bid for block space and the size is how much of that space you are bidding on.
Worked example: a 276 vB SegWit payment at five fee rates
A native SegWit transaction spending 3 inputs and creating 2 outputs estimates at 3 × 68 + 2 × 31 + 10 = 276 vB, which is exactly what the estimator produces and what is pre-filled above. At 10 sat/vB the fee is 2,760 sats.
The same 276 vB transaction at five rates shows what timing does to a fee. Every row is a real run of this calculator at a $60,000 BTC price.
| Fee rate | Total fee | In BTC | In USD | Tier |
|---|---|---|---|---|
| 1 sat/vB | 276 sats | 0.00000276 | $0.17 | Very low |
| 2 sat/vB | 552 sats | 0.00000552 | $0.33 | Low |
| 10 sat/vB | 2,760 sats | 0.00002760 | $1.66 | Standard |
| 50 sat/vB | 13,800 sats | 0.00013800 | $8.28 | High |
| 150 sat/vB | 41,400 sats | 0.00041400 | $24.84 | Very high |
Same coins moved, fifteen times the price between 10 and 150 sat/vB, purely because of when the transaction is sent. That spread is the entire reason this calculator exists.
Transaction sizes by address type: where the vB come from
Size is built from per-input and per-output weights that depend on your address type. The estimator uses the widely used approximations in the table, plus a flat 10 vB for the transaction overhead (version, input and output counts, locktime).
| Address type | Per input | Per output | 1 input, 2 outputs |
|---|---|---|---|
| Legacy (P2PKH, starts 1) | 148 vB | 34 vB | 226 vB |
| Nested SegWit (P2SH-P2WPKH, starts 3) | 91 vB | 32 vB | 165 vB |
| Native SegWit (P2WPKH, starts bc1q) | 68 vB | 31 vB | 140 vB |
| Taproot (P2TR, starts bc1p) | 57.5 vB | 43 vB | 153.5 vB |
Two honest quirks live in these numbers. First, they are approximations: a real transaction's exact vSize is what your wallet or an explorer reports, and published guides quote about 141 vB for the 1-input, 2-output native SegWit case where this estimator's rounded overhead gives 140 vB. Second, Taproot's cheap inputs and pricier outputs cross over: a 1-input Taproot payment (153.5 vB) is larger than the same native SegWit payment, and Taproot only pulls ahead as input counts grow, because each extra Taproot input costs 57.5 vB against SegWit's 68. For a spend built from many small UTXOs, address type matters more than anything else you control, which is the same UTXO logic that drives miner earnings on the ASIC calculator side of the network. What miners actually keep also depends on what they pay for power, which the cost per kWh calculator works out.
What fee rate should you choose? Reading the five tiers
The right rate is whatever the mempool demands for your deadline, and this calculator deliberately does not fetch live rates. The tier badge on every result grades the rate you typed against fixed bands, which stay useful as a sanity check.
| Tier | Rate | What the calculator says |
|---|---|---|
| Very low | Under 2 sat/vB | Only confirms when blocks have spare space. |
| Low | 2 to under 10 sat/vB | Fine when the network is quiet; can wait hours or longer when busy. |
| Standard | 10 to under 50 sat/vB | Usually confirms within a few blocks in normal conditions. |
| High | 50 to under 150 sat/vB | Strong chance of next-block confirmation. |
| Very high | 150 sat/vB and up | Top-of-mempool priority; only worth it when you are in a hurry. |
The bands are guidance, not a promise: during a fee spike, 50 sat/vB can sit for hours, and on a quiet Sunday 2 sat/vB can confirm in the next block. Fee estimation is a studied problem in its own right, as Bitcoin Optech's fee estimation overview explains, and the practical habit is simple: read the live rate from a mempool explorer, sanity-check the total here, then send. Fees are also where the network's security budget comes from, which is why a bitcoin premium calculator treats the BTC price and the fee market as two separate numbers that both move.
What competing calculators miss
Fee tools split into live dashboards and static calculators, and each camp leaves something out:
- Live estimators (Newhedge, mempool dashboards): real recommended rates refreshed from a node, which a static page cannot match. The gap: several show the fee for one fixed 140 vB reference transaction only, so a 12-input consolidation gets no number at all.
- SatoshiPerByte.org: the closest static rival, with the same rate × size formula and a size guide (about 141 vB for 1-in/2-out native SegWit, about 225 vB legacy). The gap: no per-address-type estimator you can drive with your own input and output counts, no USD output, and no reverse lookup for a fee already paid.
- Guide pages with worked tables (bitcoin.com, D-Central): solid explanations and correct spot examples (140 vB at 10 sat/vB = 1,400 sats; a 145 vB transaction at 30 sat/vB = 4,350 sats). The gap: the examples are fixed. You still do your own multiplication for any other size or rate.
- Fee explainers with sloppy size tables: at least one widely shared guide lists a nested SegWit input at 41 vB by mixing up weight units and vBytes (the input is 91 vB; 41 is a weight conversion error). Numbers like that understate a real fee by half.
- The gap this page fills: any rate × any size, an estimator driven by your address type and UTXO count, sats/BTC/USD in one result, a tier reading on the rate, and the reverse division for auditing fees you already paid.
Sat/byte vs sat/vB: why the name of this page is the old unit
They are the same number for legacy transactions and different numbers for everything modern. Before SegWit activated in 2017, fees were quoted per raw byte because bytes were all there was. SegWit's witness discount made raw bytes the wrong measure, and the network switched to virtual bytes; as Bitcoin.org's how-it-works overview puts the general model, the fee rewards miners for including your transaction, and inclusion is rationed by weight, not bytes.
So a page called "sat per byte" in 2026 is really about sat/vB: when a wallet or explorer shows a fee rate today, it means sat/vB unless it explicitly says otherwise. If an old guide quotes sat/byte for a SegWit transaction, its totals run high, because it charges full price for witness data the network discounts by 75%.
Ways to pay less in fees
The fee is rate × size, so savings come from shrinking either factor. The size side is entirely in your control:
- Spend from SegWit or Taproot addresses. A legacy input costs 148 vB against 68 vB native SegWit or 57.5 vB Taproot. On a 5-input spend that is a 400 vB difference before the rate is even applied.
- Consolidate UTXOs when rates are low. Combining ten small inputs into one, at 2 sat/vB on a quiet day, makes every future spend cheaper. Do it before you are in a hurry, not during a spike.
- Batch payments. Ten recipients in one transaction share one overhead and one set of inputs; ten separate transactions pay the overhead ten times.
- Wait out congestion when the payment allows it. Fee spikes around price moves and inscription bursts usually fade within hours or days.
- Know your rescue options. A stuck transaction flagged replaceable can be fee-bumped with replace-by-fee, the opt-in policy defined in BIP 125, and a recipient can pull a low-fee payment through with child-pays-for-parent. Neither refunds an overpaid confirmed fee: confirmed fees go to the miner, a point BIP 341's Taproot design also respects by keeping key-path spends as small as possible.
Frequently asked questions
Multiply 1 by the transaction size in vB. A 240 vB transaction at 1 sat/vB costs 240 sats (0.00000240 BTC). Tiny, though it may wait a long time unless blocks are empty.
Wallets estimate from current mempool congestion and usually target fast confirmation. If you are not in a hurry, choose a slower preset or set a custom sat/vB rate and check the total here before sending.
No. Fees depend on data size, which comes from the number of inputs and outputs, not the amount sent. One large input can be cheaper than many small ones: sending 5 BTC from a single UTXO costs less than sending 0.01 BTC built from twenty small ones.
They match for legacy transactions. For SegWit and Taproot transactions, vBytes reflect the witness discount and are what miners use to prioritize transactions, so sat/vB is the unit modern wallets quote.
No. Confirmed fees go to the miner. An unconfirmed replaceable transaction can be bumped with replace-by-fee (RBF), but only to raise the fee, never to lower it.
It multiplies your input count by the per-input size for your address type (148 legacy, 91 nested SegWit, 68 native SegWit, 57.5 Taproot vB), adds the output count times the per-output size, and adds 10 vB of overhead. Fractional counts are rounded down, and clicking it fills the size field and runs the fee calculation.
No. It calculates from the fee rate you type in, using fixed tier bands for guidance. Check a mempool explorer for the live rate before sending, especially during price volatility when rates move within minutes.
Divide its total fee by its virtual size: the reverse tool above does it. A transaction that paid 25,000 sats at 250 vB paid 100 sat/vB. Any block explorer shows both numbers on the transaction page.
Add This Calculator to Your Website
Embed this calculator on your own site with the code below. Pick a size to preview it live, then copy the code.
Powered by Calculator Zilo
References
- Bitcoin Improvement Proposals. BIP 141: Segregated Witness (Consensus Layer) (transaction weight and virtual size definitions behind the vB unit). Accessed October 24, 2026.
- Bitcoin Improvement Proposals. BIP 341: Taproot: SegWit Version 1 Spending Rules (key-path spend structure behind the 57.5 vB Taproot input size). Accessed October 24, 2026.
- Bitcoin Improvement Proposals. BIP 125: Opt-in Full Replace-by-Fee Signaling (the RBF policy for bumping an unconfirmed transaction's fee). Accessed October 24, 2026.
- Bitcoin.org, Bitcoin Developer Documentation. estimatesmartfee RPC Reference (how Bitcoin Core estimates a fee rate for a confirmation target). Accessed October 24, 2026.
- Bitcoin Optech. Fee Estimation Topic Overview (how wallets and nodes estimate sat/vB rates from mempool state). Accessed October 24, 2026.
- Bitcoin.org. How Bitcoin Works (the transaction and mining model: fees paid to miners for block inclusion). Accessed October 24, 2026.
