When you generate a new Bitcoin address, your wallet makes a quiet but important choice: which address format to use. SegWit, short for Segregated Witness, is a specific address format introduced to the Bitcoin network in 2017. It changed how transaction data is structured, and the result was lower fees, faster confirmations, and a meaningfully lighter blockchain. Understanding what a SegWit address is helps you use Bitcoin more efficiently and avoid paying more in fees than necessary.
What SegWit actually changed
Before SegWit, every Bitcoin transaction bundled two types of data together: the transaction details (who sends what to whom) and the witness data (the cryptographic signatures that prove the sender authorised the payment). That bundled structure had a problem. Signatures took up a lot of space, and Bitcoin blocks have a size limit, so including large signatures in every transaction slowed the network and pushed fees up during busy periods.
SegWit solved this by separating the witness data from the main transaction body. "Segregated Witness" is literally that: witness information moved to a separate section of the block, counted differently toward the block's weight. The practical effect was that more transactions could fit into each block without changing the block size limit. Fees dropped. Confirmation times improved. The fix also closed a long-standing bug called transaction malleability, where someone could alter the transaction ID before a payment confirmed.
The three address formats and how to tell them apart
Bitcoin currently has three main address formats in common use, and each one looks different at a glance.
- Legacy (P2PKH): starts with
1, for example1A1zP1eP.... This is the original format from 2009 and carries the highest fees. - SegWit wrapped (P2SH): starts with
3, for example3J98t1Wp.... This was a transitional format that made SegWit backward-compatible with wallets that hadn't updated yet. - Native SegWit (Bech32): starts with
bc1q, for examplebc1qar0srrr.... This is the most efficient format and the one most modern wallets now generate by default.
If your wallet gives you an address beginning with bc1q, you're already using native SegWit. If it starts with 3, you're using the wrapped version, which still saves fees compared to legacy but not as much as native SegWit. Both are valid and widely supported.
Why the fee difference matters
Bitcoin network fees are calculated by the byte size of your transaction, not by the amount you're sending. Because SegWit transactions are smaller in terms of the weight the network counts, they cost less to broadcast. A native SegWit transaction can be 30 to 40 percent cheaper than an equivalent legacy transaction during the same fee environment. When the mempool is congested, that gap widens. For someone making regular purchases or transfers, the savings compound quickly over time.
If you're new to how fees work, the Bitcoin network fee is calculated based on transaction weight rather than value, which is why address format has a direct impact on what you pay.
SegWit and the Taproot upgrade
SegWit was the foundation that made further upgrades possible. Taproot, which activated in November 2021, built directly on SegWit's architecture and introduced a new address format: Bech32m, identifiable by addresses starting with bc1p. Taproot brought Schnorr signatures, which make transactions even more compact and improve privacy for complex payment types. Understanding SegWit is the prerequisite for understanding what a Bitcoin Taproot address does and why wallets are now beginning to adopt the newer format.
SegWit and Taproot aren't competing standards. Taproot extends what SegWit started. Both formats coexist on the network, and your wallet may support all three modern types simultaneously.
Does every wallet support SegWit?
Most wallets released after 2018 support native SegWit. Popular software wallets like BlueWallet generate bc1q addresses by default. Hardware wallets from established manufacturers also default to native SegWit on Bitcoin. Older exchange accounts and some legacy wallets still generate 1 or 3 addresses, though sending to any of these formats from a SegWit wallet works fine. The address format of the sender and the recipient don't need to match; they just need to be valid Bitcoin addresses.
The only real compatibility issue arises if you try to send Bitcoin to a very old wallet that doesn't recognise Bech32 addresses. In that case, the wallet software will flag the address as invalid. The solution is simple: check whether the receiving party's software supports native SegWit, or ask them to share a 3 address instead as a fallback.
What SegWit means for beginners
For most beginners, SegWit doesn't require any action. If your wallet is reasonably modern, it's already using SegWit addresses without you having to configure anything. The things worth knowing are straightforward. First, check your address format: if it starts with bc1q, you're on native SegWit and paying the lowest fees available for standard transactions. Second, don't assume that a 1 address is wrong or insecure; legacy addresses still work perfectly, they just cost more to transact from. Third, if you're switching wallets, make sure you understand how your wallet handles Bitcoin change addresses, since the format of your change outputs affects the total fee structure of each transaction.
SegWit is one of those protocol decisions that most users benefit from without ever needing to think about it deeply. Knowing it exists, and knowing what the address prefix tells you, is enough to make smarter choices about which wallet to use and how to interpret the fees you're quoted before you send.