When you deposit or receive Bitcoin, your personal wallet(cold wallet or hot wallet) may show a BTC address in different formats. These formats all receive BTC, but they can differ in compatibility and (sometimes) network fee efficiency.
This article explains the 4 most common BTC address formats in beginner-friendly terms and how to recognize them.
Legacy (P2PKH)
A Legacy (P2PKH) Bitcoin address is the original, classic BTC address format that has been used since the early days of Bitcoin. It is typically encoded in Base58Check and is easy to recognize because it usually starts with “1”. Legacy addresses are widely supported across nearly all wallets, exchanges, and services, but they do not use SegWit, so transactions spent from Legacy addresses generally take more space on-chain and may cost higher network fees compared to newer SegWit-based formats.
Pros: Legacy addresses provide the broadest compatibility, making them the safest option when dealing with older services or systems that may not support newer formats.
Cons: Because Legacy does not benefit from SegWit’s efficiency improvements, spending from Legacy addresses often results in larger transaction sizes and therefore higher fees compared to SegWit and Taproot.
Nested SegWit (P2SH-P2WPKH)
A Nested SegWit address, often referred to as P2SH-P2WPKH, is a SegWit address that is wrapped inside a P2SH structure to maintain compatibility with older platforms. It is usually encoded in Base58Check and most commonly starts with “3”. This format was widely adopted as a transition option because many services could support P2SH addresses before they fully supported Native SegWit (Bech32). In practice, Nested SegWit offers fee savings compared to Legacy, while still remaining compatible with a broad range of systems.
Pros: Nested SegWit provides better fee efficiency than Legacy while keeping strong compatibility with services that may not support Bech32 addresses.
Cons: Although it is more efficient than Legacy, Nested SegWit is generally not as fee-efficient as Native SegWit, and it can sometimes confuse users because it looks like a traditional “3…” address even though it uses SegWit internally.
Native SegWit (Bech32) (P2WPKH / P2WSH)
A Native SegWit address is a SegWit-native Bitcoin address format that uses Bech32 encoding and can be identified because it typically starts with “bc1q”. The most common Native SegWit type for everyday receiving is P2WPKH, while more complex scripts such as multisig may use P2WSH. Because SegWit moves signature data to the witness area, spending from Native SegWit addresses is usually more weight-efficient, which often results in lower network fees compared to both Legacy and Nested SegWit. Native SegWit is now widely supported by modern wallets and exchanges, and it is commonly recommended as the default BTC address type.
Pros: Native SegWit often provides lower fees and better efficiency than Legacy and Nested SegWit, and its Bech32 encoding is designed with improved error detection to reduce mistakes when typing addresses.
Cons: While support is now widespread, some older platforms may still reject Bech32 addresses, so users occasionally need to fall back to a Legacy or Nested SegWit address for compatibility.
Taproot (Bech32m) (P2TR)
A Taproot (P2TR) Bitcoin address is the newest widely used address format and is designed to improve efficiency and privacy for certain types of transactions. Taproot addresses use Bech32m encoding and are recognizable because they typically start with “bc1p”. Taproot introduces Schnorr signatures and more flexible spending conditions, which can allow certain complex scripts or multisig constructions to appear more like regular transactions in some cases, improving privacy and reducing on-chain footprint in specific scenarios. Although Taproot adoption continues to grow, some services still have partial support, so availability depends on the wallet or platform.
Pros: Taproot can improve efficiency for certain spending patterns and can enhance privacy in situations where advanced scripts or multisig conditions are used, while also representing the most modern BTC address standard.
Cons: Taproot is not yet as universally supported as Legacy or Native SegWit, so some exchanges, wallets, or services may not accept Taproot addresses for deposits or withdrawals.
Pros & Cons Comparison Table
| Address format | Prefix example | Advantages | Limitations |
| Legacy | 1... |
Offers the broadest compatibility across wallets, exchanges, and service providers, including legacy systems that may not support newer address standards. | Does not support SegWit, which typically results in larger transaction sizes when spending and may lead to higher network fees compared to SegWit- and Taproot-based formats. |
| Nested SegWit | 3... |
Provides SegWit-related fee savings while retaining strong compatibility, as the address is presented in a widely supported P2SH format. | Generally less fee-efficient than Native SegWit, and the 3... prefix may be misunderstood as a non-SegWit address despite SegWit being used internally. |
| Native SegWit | bc1q... |
Typically delivers improved fee efficiency versus Legacy and Nested SegWit, and Bech32 encoding includes stronger error-detection features that help reduce address-entry mistakes. | Although widely supported today, certain older platforms may not accept Bech32 addresses, requiring users to use Legacy or Nested SegWit for compatibility. |
| Taproot | bc1p... |
Enables enhanced efficiency and privacy in specific transaction scenarios, particularly for advanced spending conditions, and represents the latest widely adopted BTC address standard. | Ecosystem support remains uneven, and some wallets or platforms may not support Taproot addresses for deposits or withdrawals at this time. |
FAQ
Q: Can I send BTC between different address formats?
A: Yes. In most cases, you can send BTC between different address formats (for example, from a 1... Legacy address to a bc1q... Native SegWit address). The key requirement is that the sending wallet or platform must support the recipient’s address format.
Note: On Zoomex, the BTC address you get on the platform is a Legacy address (it starts with 1...). However, you can still deposit BTC to Zoomex from other BTC address types, such as Nested SegWit (3...), Native SegWit (bc1q...), and Taproot (bc1p...).
Q: Does the network fee depend on the sender’s address format or the recipient’s address format?
A: In most cases, the network fee depends mainly on the sender’s address format, because the fee is largely determined by the inputs (the coins being spent) and the signature data included in the transaction. Transactions that spend from Legacy (1...) addresses usually take up more space on the blockchain than transactions that spend from SegWit (3... / bc1q...) or Taproot (bc1p...) addresses, so they often cost more in network fees.
Disclaimer: This article is provided for general information and educational purposes only and does not constitute investment, financial, trading, or legal advice. Cryptocurrency transactions involve risk, and Bitcoin deposits and withdrawals are irreversible once submitted to the blockchain. You are solely responsible for verifying that you are using the correct network, address format, and wallet details before making a transaction. To the fullest extent permitted by applicable laws and regulations, Zoomex shall not be liable for any losses, damages, or incidents arising from or related to your deposit or withdrawal, including but not limited to transactions sent to an incorrect address, sent on an unsupported network, or processed with insufficient or incorrect information.