<p>This website (<a href="https://www.buybitcoinworldwide.com/fee-calculator/" rel="nofollow noreferrer">https://www.buybitcoinworldwide.com/fee-calculator/</a>) shows the approx size of transactions according to the address type, number of inputs and number of outputs and the final fee (after you set how much sat/byte you want to pay)</p>

<p>As you play with it you will see that the most important if you are worried about fees is to reduce the number of inputs. The best practice is to consolidate your small inputs in native segwit addresses (bc1...) when fees are low. </p>

<p>This way when you need to transfer bitcoins when the network is congested you will have a smaller transaction size, paying less fees.</p>

<p>Be careful with your <strong>privacy</strong> while doing so.</p>

CC BY-SA 4.0
2020-05-21T03:34:40.683Z
2020-05-21T11:33:36.910Z
2020-05-21T11:33:36.910Z
bitm
<p>What are input/output sizes for various transaction types? </p>

<p>I see some numbers like 210 byte for input for p2sh-p2wpkh here (<a href="https://bitcoin.stackexchange.com/questions/84004/how-do-virtual-size-stripped-size-and-raw-size-compare-between-legacy-address-f#">How do virtual size, stripped size and raw size compare between legacy address formats and native segwit?</a>), but curious to know more detailed breakdown of input/output for each transaction types. </p>

<transaction-fees>
Input/Output size for various transaction types
1_want_to_be_good_dev
# Input/Output size for various transaction types

(Asked by: username_0 on 2020-05-21)

What are input/output sizes for various transaction types?

I see some numbers like 210 byte for input for p2sh-p2wpkh here ([How do virtual size, stripped size and raw size compare between legacy address formats and native segwit?](https://bitcoin.stackexchange.com/questions/84004/how-do-virtual-size-stripped-size-and-raw-size-compare-between-legacy-address-f#)), but curious to know more detailed breakdown of input/output for each transaction types.

**Tags:** transaction-fees


---

## 1 answers

### Answer by username_1 on 2020-05-21. Score: 0

This website (<https://www.buybitcoinworldwide.com/fee-calculator/>) shows the approx size of transactions according to the address type, number of inputs and number of outputs and the final fee (after you set how much sat/byte you want to pay)

As you play with it you will see that the most important if you are worried about fees is to reduce the number of inputs. The best practice is to consolidate your small inputs in native segwit addresses (bc1...) when fees are low.

This way when you need to transfer bitcoins when the network is congested you will have a smaller transaction size, paying less fees.

Be careful with your **privacy** while doing so.


---

