Bitcoin Transaction Fees

Definition: A Bitcoin transaction fee is the difference between the value consumed by a transaction’s inputs and the value assigned to its outputs. The sender effectively leaves this difference as an incentive for miners to include the transaction in a block. Wallets usually estimate a fee from the transaction’s size and the current market for block space; the amount is not a fixed percentage of the bitcoin being sent.13

Calculation Total input value minus total output value
Common rate unit Satoshis per virtual byte (sat/vB)
Main drivers Transaction size and demand for limited block space
Live fee reference mempool.space fee estimates; estimates change with network conditions
Directory Bitcoin Directory

How the fee is calculated

Bitcoin does not put a separate “fee” field into a transaction. Instead, the fee is the leftover value after all inputs are accounted for and all outputs—including any change returned to the sender—are created. If the inputs total 100,000 satoshis and the outputs total 99,500 satoshis, the fee is 500 satoshis. The transaction creator chooses the outputs and fee when constructing the transaction; nodes and miners apply their own rules when relaying or selecting it.13

A transaction’s absolute fee and its fee rate describe different things. The absolute fee is the total number of satoshis offered. The fee rate divides that amount by the transaction’s virtual size. For example, at 10 sat/vB, a 140-vB transaction pays 1,400 satoshis while a 280-vB transaction pays 2,800 satoshis. These numbers illustrate the arithmetic only; they are not a current recommendation.

Illustrative transaction Fee rate Absolute fee
140 vB 10 sat/vB 1,400 sats
280 vB 10 sat/vB 2,800 sats

Fee rate, virtual bytes, and transaction size

Most wallets quote a fee rate in sat/vB. A virtual byte is a standardized size measure introduced with Segregated Witness (SegWit): BIP 141 defines transaction weight from base and total size, then defines virtual size as weight divided by four and rounded up. Witness data is therefore counted differently from the older serialized-byte total. Bitcoin Core’s current mempool terminology also documents an adjusted virtual-size measure for some policy calculations, so exact displayed sizes can vary by context.23

Transaction size depends on its structure, not just the amount transferred. More inputs generally mean more data to authorize and verify. Outputs, script type, witness data, and a change output also affect the final size. A wallet selecting many small UTXOs may build a larger transaction than one spending a single large UTXO. This is why a small payment can have a relatively high fee when its transaction is large, while a larger payment can use less block space.

Why fees rise and fall

Bitcoin blocks have limited capacity, and transactions compete for inclusion. When many users are trying to use the available block space, users may offer higher fee rates to improve their chances of prompt confirmation. When demand is lighter, lower-fee transactions may be included sooner. Miners choose transactions for candidate blocks, and each node maintains its own mempool and relay policy. A fee estimate is therefore a forecast, not a promise: different wallets and services can show different estimates, and no quoted rate guarantees a particular confirmation time.

Wallet estimates are based on their available network information and the user’s selected target or urgency. A live fee estimator such as mempool.space can provide another view, but it observes its own data sources and should not be treated as a universal schedule. Check that a fee estimate is for Bitcoin on-chain transactions, since Lightning Network payments use a different payment channel system and fee structure.

Can a transaction fee be changed?

If a transaction remains unconfirmed, a wallet may offer a fee-bumping method. Replace-by-Fee (RBF) creates a replacement that conflicts with the earlier unconfirmed transaction and pays a higher fee under the rules accepted by relevant nodes. Whether this works depends on the wallet, transaction, and current relay and mempool policies; it is not a guaranteed cancellation or reversal.

Child Pays for Parent (CPFP) takes a different approach: the sender or recipient creates a child transaction that spends an output of the unconfirmed parent and offers enough fee for miners to consider the package’s combined fee rate. The child must be spendable, and the method depends on wallet support and package-relay or miner behavior. Neither method changes Bitcoin’s confirmed transaction history.

Fee-market milestones

  • December 4, 2015: BIP 125 was assigned, documenting opt-in Replace-by-Fee signaling for unconfirmed transactions.4
  • August 2017: SegWit activated on Bitcoin mainnet. BIP 141’s transaction-weight and virtual-size definitions gave wallets a different standardized way to measure witness transactions for fee calculation.12
  • Block 709,632, November 2021: Taproot activated on mainnet, adding another Bitcoin output and spending format. As with other formats, the transaction’s structure and weight remain relevant to the fee it needs.5

Common misconceptions and limits

  • A Bitcoin fee is not normally a percentage of the payment amount; it is tied to the input-output difference and the transaction’s size and fee rate.
  • A higher fee rate can improve the incentive to include a transaction, but it cannot force a miner to include it in the next block.
  • Fees are not a fixed tariff set by Bitcoin’s protocol. Wallet defaults, relay policy, mempool conditions, and miner decisions affect what is accepted and confirmed.
  • Fee estimates can become outdated quickly during changing demand. Review the final fee and destination in the wallet before signing.

Page updated: November 10, 2026.

Related Terms

Related Articles

See Also

Sources

  1. Bitcoin Developer Guide. “Transactions.” Accessed November 10, 2026. https://developer.bitcoin.org/devguide/transactions.html.
  2. Bitcoin Improvement Proposals. “Segregated Witness (Consensus layer).” BIP 141. Accessed November 10, 2026. https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki.
  3. Bitcoin Core Developers. “Fee and Size Terminology in Mempool Policy.” Bitcoin Core documentation. Accessed November 10, 2026. https://github.com/bitcoin/bitcoin/blob/master/doc/policy/mempool-terminology.md.
  4. Harding, David A., and Peter Todd. “Opt-in Full Replace-by-Fee Signaling.” BIP 125, assigned December 4, 2015. https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki.
  5. Bitcoin Improvement Proposals. “Taproot: SegWit version 1 spending rules.” BIP 341. Accessed November 10, 2026. https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki.