Bitcoin Address Types Explained: Legacy, SegWit, Native SegWit, and Taproot

Every Bitcoin address format tells you something about how a transaction is constructed and how much it will cost. There are four main address types in use today — and using the wrong one can cost you significantly more in fees.

Here's what each type means, how to recognize it, and which one you should be using in 2026.

The Four Bitcoin Address Types

Address Type	Prefix	Format	Fee Efficiency	Adoption
Legacy (P2PKH)	1...	Base58	Baseline (highest fees)	Legacy support
P2SH (Pay-to-Script-Hash)	3...	Base58	~15% cheaper	Multisig, wrapped SegWit
Native SegWit (Bech32)	bc1q...	Bech32	~40% cheaper	Dominant
Taproot (Bech32m)	bc1p...	Bech32m	~45% cheaper	Growing

1. Legacy Addresses (P2PKH): Starts with "1"

Legacy addresses — technically Pay-to-Public-Key-Hash (P2PKH) — are the original Bitcoin address format. Satoshi used them. They still work. Every wallet and exchange supports them.

Example: 1A1zP1eP5QGefi2DMPTfTL5SLmv7Divf6k

The problem: Legacy transactions are the largest in bytes, which means the highest fees. A standard Legacy transaction uses about 148 vBytes per input. A Native SegWit transaction uses only 68 vBytes per input — less than half.

When you'll still see Legacy addresses:

• Old wallets from before 2017
• Some ATMs and payment processors that haven't updated
• Long-term HODLers who set up wallets years ago and haven't migrated

Should you use Legacy addresses in 2026? No, unless you have a specific reason. There's no security advantage and you'll pay more in fees.

2. P2SH Addresses: Starts with "3"

P2SH (Pay-to-Script-Hash) addresses were introduced in 2012 via BIP 16. They allow more complex spending conditions to be encoded — most importantly, multisig wallets and Wrapped SegWit.

Example: 3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy

Wrapped SegWit (P2SH-P2WPKH) uses a 3... address to contain a SegWit script. It's a compatibility bridge: the outer 3... address works with older wallets that don't understand native SegWit, but you still get partial fee savings (~15% cheaper than Legacy).

When you'll see P2SH:

• Multisig wallets (2-of-3, etc.) created before Taproot
• Exchanges or services that haven't upgraded to native SegWit
• Payment processors maintaining backwards compatibility

Should you use P2SH? It depends. For multisig, many wallets now use Native SegWit (P2WSH) or Taproot. For simple payments, skip to bc1q or bc1p.

3. Native SegWit (Bech32): Starts with "bc1q"

Native SegWit — technically P2WPKH (Pay-to-Witness-Public-Key-Hash) — is the sweet spot for most Bitcoin users in 2026. It was introduced with SegWit activation in August 2017 and uses the Bech32 encoding format.

Example: bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq

The "witness" data in SegWit transactions is given a discount under Bitcoin's fee calculation rules — witness bytes count as 0.25 vBytes each rather than 1 vByte. This is why Native SegWit transactions are ~40% cheaper than Legacy.

The tradeoff: A small number of very old wallets and services don't support Bech32 addresses. But this is increasingly rare in 2026. Major exchanges (Coinbase, Kraken, Gemini), hardware wallets (Coldcard, Ledger, Trezor), and software wallets all support bc1q.

Should you use Native SegWit? Yes — this is the recommended default for most users. It's widely supported, significantly cheaper than Legacy, and well-established.

4. Taproot (Bech32m): Starts with "bc1p"

Taproot is the newest address format, activated on the Bitcoin network in November 2021 via BIPs 340, 341, and 342. It uses a Bech32m encoding (a slight variation of Bech32) and starts with "bc1p".

Example: bc1p5cyxnuxmeuwuvkwfem96lqzszd02n6xdcjrs20cac6yqjjwudpxqkedrcr

Taproot addresses offer several improvements:

1. Schnorr signatures — Taproot uses Schnorr signatures instead of ECDSA. Schnorr signatures are smaller and support key aggregation (multiple signers can produce a single signature, saving bytes).

2. MAST (Merkelized Abstract Syntax Trees) — Complex scripts (like multisig or timelocked payments) are hidden by default. A Taproot multisig transaction looks identical to a single-sig transaction on the blockchain — a major privacy improvement.

3. Lower fees for complex transactions — Multisig, Lightning channel opens/closes, and other complex operations cost less with Taproot.

4. Enables future upgrades — Taproot's script language (Tapscript) is designed to be extensible, making future soft forks easier.

Why isn't everyone on Taproot yet? Adoption takes time. Many services upgraded to Native SegWit and haven't yet moved to Taproot. As of 2026, Taproot adoption is growing significantly — especially for new wallets and Lightning implementations. See our Taproot deep-dive for the full technical breakdown.

Bitcoin Address Types: Quick Reference

1...    = Legacy (P2PKH)         — old, avoid for new wallets
3...    = P2SH                   — multisig, wrapped SegWit
bc1q... = Native SegWit (P2WPKH) — recommended default
bc1p... = Taproot (P2TR)         — best for new wallets

Which Address Type Should You Use?

For receiving Bitcoin (single-sig wallet): Use Native SegWit (bc1q) or Taproot (bc1p). Most modern hardware wallets (BitBox02, Foundation Passport, Coldcard Mk4) default to Native SegWit or offer Taproot as an option. Either choice gives you lower fees and broad support.

For multisig wallets: Taproot (P2TR) is becoming the standard for new multisig setups. Our multisig guide covers the full setup. Legacy multisig (P2SH) still works but costs more in fees.

For sending Bitcoin: You can always send Bitcoin from any address type to any other address type. The format of the receiving address determines the transaction structure and fees. Sending to a bc1q or bc1p address is cheaper than sending to a 1... or 3... address, even if your own wallet uses Legacy.

For exchanges: When withdrawing from an exchange, set your withdrawal address to your Native SegWit or Taproot wallet address. The Coldcard Q, Ledger Nano X, and Keystone 3 Pro all generate appropriate addresses by default.

Can You Convert Between Address Types?

Bitcoin address types aren't something you "convert" — they're determined by how your wallet creates keys. If you want to move from a Legacy wallet to Native SegWit:

1. Create a new wallet in a modern app (Sparrow, Electrum, Blue Wallet)
2. Select Native SegWit (P2WPKH) or Taproot as the address type
3. Send your Bitcoin from the old address to the new one
4. The old address is now empty; use the new one going forward

This is a normal on-chain transaction. The fee you pay depends on the input type (your old Legacy inputs) and the output type (new bc1q or bc1p address).

Address Types and Your Seed Phrase

Your seed phrase doesn't change based on address type. The same 12 or 24 words can derive Legacy, P2SH, Native SegWit, or Taproot addresses — they just use different derivation paths:

Address Type	Derivation Path
Legacy (P2PKH)	m/44'/0'/0'
P2SH-P2WPKH	m/49'/0'/0'
Native SegWit (P2WPKH)	m/84'/0'/0'
Taproot (P2TR)	m/86'/0'/0'

This is why wallet recovery sometimes requires selecting the correct address type — the wrong derivation path will show a zero balance even with the correct seed.

Frequently Asked Questions

What's the best Bitcoin address format in 2026? Native SegWit (bc1q) is the recommended default — widely supported, ~40% cheaper than Legacy, and battle-tested since 2017. Taproot (bc1p) is excellent for new setups and offers additional privacy benefits.

Why do some addresses start with 3? P2SH addresses start with 3 and are used for multisig wallets and wrapped SegWit. They provide more scripting flexibility than Legacy but have been largely superseded by native SegWit and Taproot.

Can I send Bitcoin from a Legacy wallet to a Taproot address? Yes. You can send between any address types. The sender's address type determines their input size; the receiver's address type determines the output size. Mixing types works fine.

Why does my wallet show different addresses sometimes? Many wallets generate a new receive address for each transaction for privacy — this is expected behavior. All of these addresses belong to your wallet and funds sent to any of them are accessible with your seed phrase.

What is a bc1p address? A bc1p address is a Taproot address (P2TR). The "p" distinguishes it from native SegWit (bc1q). Taproot uses Bech32m encoding and Schnorr signatures, offering better privacy and lower fees for complex scripts.