Bitcoin Address Types: How to Identify Legacy, SegWit, and Taproot
If a Bitcoin address starts with 1, it is usually a Legacy address. If it starts with 3, it is usually a P2SH-style address, commonly Nested SegWit. If it starts with bc1q, it is usually Native SegWit. If it starts with bc1p, it is usually Taproot.
That prefix check is the fastest way to identify the most common Bitcoin address types and understand whether a wallet or exchange is likely to accept them. This guide explains Bitcoin address formats only. It does not cover wallet reviews, tracing wallet owners, or how to buy Bitcoin. Its purpose is practical: help you recognize Legacy, SegWit, and Taproot addresses, understand the differences, and know what to check before sending BTC.
What is a Bitcoin address?
A Bitcoin address is a public receiving address on the Bitcoin network. It is the string you share when someone needs to send you BTC. Different Bitcoin address types represent different script standards, which is why Bitcoin does not use one single address format for every case.
A Bitcoin address can look valid at a glance because it has the right prefix and character pattern, but that alone does not prove the destination is trusted or even intended. Visual recognition helps with identification, not with trust. That distinction matters whenever you copy, paste, or confirm a receiving address.
Main Bitcoin address types at a glance
| Address type | Typical prefix | Common label | Practical meaning |
|---|---|---|---|
| Legacy | 1 | P2PKH | Older format with broad compatibility |
| Nested SegWit | 3 | P2SH-P2WPKH or P2SH-P2WSH | Transitional SegWit format for compatibility with older platforms |
| Native SegWit | bc1q | Bech32 / P2WPKH or P2WSH | Modern SegWit format commonly used for routine BTC transfers |
| Taproot | bc1p | P2TR / Bech32m | Newer format associated with Taproot support |
These are all valid Bitcoin address families, but they do not encode spending conditions in the same way. In practice, the sending platform must support the destination format.
Legacy addresses
Legacy addresses commonly begin with 1 and are based on P2PKH, or Pay-to-Public-Key-Hash. This is the older Bitcoin address format that many users still recognize first.
Their main advantage is compatibility with older infrastructure. Their main drawback is that spending from Legacy outputs is generally less data-efficient than spending from SegWit outputs, which can matter when network activity is high. Legacy addresses are still valid Bitcoin addresses, but they are no longer the default choice on many current wallets.
Nested SegWit addresses
Nested SegWit addresses commonly begin with 3. They are usually P2SH-wrapped SegWit addresses, often described as a bridge format between older and newer Bitcoin support.
This format became popular because it allowed SegWit-style spending while still fitting into systems that already understood P2SH addresses. Today, Nested SegWit still works well, but it is often used mainly where compatibility with older services still matters.
Native SegWit addresses
Native SegWit addresses commonly begin with bc1q and use Bech32 encoding. On many modern wallets and exchanges, this is a standard receive format.
For routine BTC transfers, Native SegWit is often the most practical choice because it is broadly supported on many current services and is usually more data-efficient than Legacy when funds are later spent. Bech32 was also designed to be easier for software to validate, which helps reduce formatting issues. If you want more context on cost differences, it can help to review Bitcoin transaction fees separately.
Taproot addresses
Taproot addresses commonly begin with bc1p and are based on P2TR outputs. They use Bech32m rather than standard Bech32, which is one reason not all bc1 addresses are the same type.
Taproot is a newer Bitcoin address format. Its practical effect depends on wallet implementation and platform support, but it is increasingly present across updated Bitcoin services. Some wallets support sending to Taproot addresses before making Taproot the default receive option.
Legacy vs SegWit vs Taproot: what actually matters
For most people, the key differences are not the full script details but compatibility, current support, and transaction data efficiency. Legacy is the oldest common format and remains useful when dealing with older systems. SegWit formats, especially Native SegWit, are commonly preferred for everyday use because they are more space-efficient in many cases. Taproot is the newest major format and may be useful if your wallet and the destination platform fully support it.
SegWit is a Bitcoin upgrade, not a different coin. Taproot is also still Bitcoin, not a separate network. The important question is simply whether the platform sending the BTC accepts the destination address format you are using.
Are all bc1 Bitcoin addresses the same?
No. Not all bc1 addresses are the same Bitcoin address type.
A bc1q address usually means Native SegWit. A bc1p address usually means Taproot. They may look similar at first glance because both begin with bc1, but they belong to different output types and can have different support levels depending on the wallet or exchange. When someone says a platform supports “bc1 addresses,” it is worth confirming whether that includes both Native SegWit and Taproot.
What’s a valid Bitcoin address?
A valid Bitcoin address usually has the expected prefix, follows the character rules of its format, and belongs to the correct Bitcoin network. A wallet or exchange will often perform address validation automatically before allowing a withdrawal.
Still, a valid-looking Bitcoin address does not prove that the recipient is trusted, that the pasted address was not changed by malware, or that you are sending to the intended destination. Visual checks can help you spot obvious mistakes, but they cannot verify ownership or intent. If you are choosing where to store BTC yourself, a separate guide on how to choose a Bitcoin wallet can help with wallet-side decisions.
Before you send BTC: 5 checks that prevent common address mistakes
- Check the prefix. Confirm whether the address begins with 1, 3, bc1q, or bc1p, so you know which Bitcoin address type you are using.
- Confirm the network. Make sure it is a Bitcoin mainnet address, not a testnet address or an address from another network.
- Check platform support. The sending wallet or exchange must accept that destination format, especially for bc1p Taproot addresses.
- Recheck the pasted address. Compare the first and last characters with the original source to reduce copy-paste or replacement errors.
- Use a small test transaction when needed. If the amount is large or the platform is unfamiliar, a test transfer adds a practical layer of confirmation.
Address type can affect compatibility more than speed. Confirmation time depends mainly on network conditions and fee selection, which you can read about in how long a Bitcoin transaction takes.
Common mistakes when using Bitcoin addresses
A common mistake is assuming every BTC address works everywhere. In reality, one platform may send to Legacy and Native SegWit addresses but not yet accept Taproot. Another mistake is focusing only on whether the address looks valid while ignoring whether it belongs to the intended recipient.
Users also run into trouble when they switch wallet account types without noticing, or when they confuse Bitcoin mainnet addresses with testnet formats. Most preventable errors happen before the transaction is sent, which is why a simple destination check matters more than memorizing technical terms.