<p>Taproot inputs are smaller but outputs are larger. Specifically, P2WPKH (Native SegWit) inputs and outputs take 68 and 31 vbytes in a transaction, respectively, while P2TR (Taproot) inputs and outputs take 57.5 and 43 vbytes, respectively. In terms of fees this makes Taproot transactions about 1.5% more expensive when you don't use multisig or scripting.</p>
<p>Source: <a href="https://bitcoinops.org/en/tools/calc-size/" rel="nofollow noreferrer">https://bitcoinops.org/en/tools/calc-size/</a></p>

CC BY-SA 4.0
2021-06-21T02:47:40.323Z
Note that the cost for the output is paid by the sender, but the recipient saves the cost on the smaller input; the recipient picks the address they'd like to get paid to, though. :)
Murch
CC BY-SA 4.0
2021-06-11T10:55:13.240Z
2021-06-29T23:14:54.323Z
2021-06-29T23:14:54.323Z
Vojtěch Strnad
<p>How would the most basic taproot transactions (not involving scripts) compare to P2WPKH transactions in terms of vbytes or fees?</p>

CC BY-SA 4.0
2023-09-11T19:36:08.460Z
Related: https://bitcoin.stackexchange.com/q/119301/5406
Murch
<transaction-fees><taproot><p2wpkh><p2tr>
How do the fees for taproot transactions compare to P2WPKH?
Darius
# How do the fees for taproot transactions compare to P2WPKH?

(Asked by: username_0 on 2021-06-11)

How would the most basic taproot transactions (not involving scripts) compare to P2WPKH transactions in terms of vbytes or fees?

**Tags:** transaction-fees, taproot, p2wpkh, p2tr

> **Comments:**
> **username_1**: Related: https://bitcoin.stackexchange.com/q/119301/5406  

---

## 1 answers

### Answer by username_2 on 2021-06-11. Score: 8 | Accepted answer

Taproot inputs are smaller but outputs are larger. Specifically, P2WPKH (Native SegWit) inputs and outputs take 68 and 31 vbytes in a transaction, respectively, while P2TR (Taproot) inputs and outputs take 57.5 and 43 vbytes, respectively. In terms of fees this makes Taproot transactions about 1.5% more expensive when you don't use multisig or scripting.

Source: <https://bitcoinops.org/en/tools/calc-size/>

> **Comments:**
> **username_1**: Note that the cost for the output is paid by the sender, but the recipient saves the cost on the smaller input; the recipient picks the address they'd like to get paid to, though. :)  

---

