Bitcoin Address Formats Explained
Not all Bitcoin addresses look the same — and there is a good reason for that. Bitcoin has evolved through several address formats over its 15-year history. Each format represents improvements in efficiency, security, and functionality. Here is a plain-language breakdown of every format you will encounter.
Format 1: Legacy (P2PKH) — starts with "1"
Example: 1A1zP1eP5QGefi2DMPTfTL5SLmv7Divf
The original Bitcoin address format, introduced by Satoshi Nakamoto in 2009. P2PKH stands for Pay-to-Public-Key-Hash. These addresses start with the number 1 and are 25–34 characters long (Base58 encoding).
Pros: Universal support across all wallets and exchanges.
Cons: Higher transaction fees because transactions are larger in bytes. Still fully valid but considered outdated.
Format 2: P2SH — starts with "3"
Example: 3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy
Introduced in 2012 (BIP 16), P2SH (Pay-to-Script-Hash) addresses support more complex transaction logic, including multi-signature wallets(requiring multiple keys to spend). They also wrap SegWit scripts, which is why many early SegWit wallets use "3" addresses.
Pros: Lower fees than Legacy for SegWit-wrapped transactions; supports multisig and other scripts.
Cons: Slightly larger transaction size than native SegWit.
Format 3: Native SegWit / Bech32 — starts with "bc1q"
Example: bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq
Introduced with the SegWit upgrade (BIP 84) in 2017, Bech32 is the most widely used modern format. The bc1q prefix identifies it as a native SegWit P2WPKH address.
Pros: Lower transaction fees (SegWit data is discounted); better error detection (Bech32 encoding can detect most copy-paste mistakes); no uppercase/lowercase ambiguity.
Cons: A small number of older exchanges and wallets don't support sending to bc1 addresses — though this is increasingly rare.
Format 4: Taproot / Bech32m — starts with "bc1p"
Example: bc1p0xlxvlhemja6c4dqv22uapctqupfhlxm9h8z3k2e72q4k9hcz7vq5zuyut
The newest Bitcoin address format, activated in November 2021 (BIP 341/342). Taproot addresses use Schnorr signatures and MAST (Merkelized Abstract Syntax Trees), enabling more complex smart contract-like scripts while making all transaction types look identical on-chain — improving privacy.
Pros: Lower fees for complex transactions; enhanced privacy (multisig transactions look like single-sig); foundation for Lightning Network improvements and future Bitcoin scripting.
Cons: Still gaining adoption — not all wallets and exchanges support sending to bc1p addresses.
Which Format Should You Use?
- For everyday use: Native SegWit (
bc1q) — best balance of fee savings and compatibility - For maximum compatibility (sending to old services): P2SH (
3...) - For advanced scripts / privacy focus: Taproot (
bc1p) if supported - Legacy (
1...): Avoid unless required by a specific service
Can You Send Between Different Formats?
Yes — all Bitcoin address formats are interoperable. You can send from a Legacy wallet to a Bech32 address, or from Taproot to P2SH. What matters is that your sendingwallet supports the destination format, which all modern wallets do.
Fee Differences in Practice
Transaction fees are determined by bytes of data, not by value. A typical SegWit transaction is about 40% cheaper than an equivalent Legacy transaction. For frequent Bitcoin users, switching from Legacy to Native SegWit can save significant amounts over time.
Start Exchanging