QbyteLab

Key takeaways

• Bitcoin has four common address types: Legacy (starts with 1), P2SH (starts with 3), native SegWit (bc1q) and Taproot (bc1p).
• You can identify any address by its first characters alone, before you look up a single transaction.
• Native SegWit and Taproot use bech32-style encoding and generally cost less in fees than Legacy addresses.
• One private key can produce every address type, because the address is just a different way of wrapping the same public key.
• For new activity today, Taproot (bc1p) or native SegWit (bc1q) are the practical defaults, with Legacy kept only for older systems.

You can identify any Bitcoin address type just by reading its first characters: 1 is Legacy, 3 is P2SH, bc1q is native SegWit, and bc1p is Taproot. Each Bitcoin address format encodes the same kind of ownership in a different way, and those differences change the fees you pay, the wallets that can send to you, and how much a chain watcher can infer about your spending. This guide walks through all four bitcoin address types, how to tell them apart at a glance, and which one makes sense for new activity today.

The four Bitcoin address types at a glance

Bitcoin did not launch with every format it uses now. New address types arrived through protocol upgrades, each one solving a specific problem while staying backward compatible with the coins that came before.

• Legacy (P2PKH) addresses start with 1. This is the original format from 2009, encoded in Base58Check.
• P2SH addresses start with 3. Introduced by BIP-16 in 2012, they let a single address stand in for a more complex spending script, such as a multisignature setup.
• Native SegWit (P2WPKH) addresses start with bc1q. They use bech32 encoding and arrived with the Segregated Witness upgrade, which activated on August 24, 2017.
• Taproot (P2TR) addresses start with bc1p. They use bech32m encoding and arrived when Taproot activated at block 709,632 in November 2021.

All four are valid. A modern wallet can hold and spend from every one of them, and coins never expire because they sit in an older format.

How to tell 1, 3, bc1q and bc1p addresses apart

The fastest check is the prefix, and you do not need any tools to do it.

• A string that begins with 1 and mixes upper and lower case letters is a Legacy address, for example a value like 1BvBM....
• A string that begins with 3 is a P2SH address, such as 3J98t.... From the outside you cannot tell whether it wraps a multisig script or a wrapped-SegWit script, only that the funds are locked behind a script hash.
• A string that begins with bc1q is a native SegWit address. These are lowercase only and noticeably longer, following the bech32 character set that deliberately excludes look-alike characters like 1, b, i and o.
• A string that begins with bc1p is a Taproot address, using the closely related bech32m encoding.

The bech32 formats used by bc1q and bc1p addresses were designed to be easier to read aloud and to catch typos. Because they are case-insensitive and skip ambiguous characters, a mistyped address is far more likely to fail its checksum than to silently send funds to the wrong place.

If you want to go beyond the prefix and actually inspect what an address has received, spent and held over time, an on-chain explorer is the right next step. Our companion guide on how to read any address's full on-chain history walks through that process address by address.

Fees, compatibility and privacy differences

The bitcoin address format you choose affects three practical things: what you pay, who can pay you, and what observers can learn.

Fees

Segregated Witness changed how Bitcoin measures the size of a transaction. Instead of counting every byte equally, the network calculates a block's weight, where non-witness data counts for more than witness data. Signature and unlocking information (the witness) receives a discount when weight is computed, and the block weight limit is 4,000,000 weight units, as defined in BIP-141.

Because much of a spend's data lives in the witness, native SegWit and Taproot inputs occupy less chargeable weight than the equivalent Legacy input. In steady conditions that means lower fees for the same payment. Taproot can push savings further for multisignature and complex scripts, since Schnorr signatures allow several signatures to be combined into one.

Compatibility

Legacy and P2SH addresses have the widest reach. Almost every wallet and service that has ever existed can send to a 1 or 3 address. The bc1q format is supported broadly today, though a small number of very old services may still choke on it. Taproot (bc1p) is the newest, so a handful of older platforms may not yet let you send to it, even though support has grown steadily since 2021.

Privacy

Address type also leaks information. When most participants used Legacy addresses, a bc1q output stood out. As native SegWit and Taproot become common, individual transactions blend in more. Taproot adds a deeper privacy property: a simple single-signature spend and a complex multi-condition spend can look identical on chain, because the extra conditions only reveal themselves if they are used. That makes it harder for an observer to distinguish an ordinary payment from a smart-contract-style spend.

Which type to use today and why

For new activity, native SegWit (bc1q) and Taproot (bc1p) are the sensible defaults.

• Choose native SegWit (bc1q) when you want low fees and the broadest modern compatibility. It is well supported across wallets and exchanges and is a safe everyday choice.
• Choose Taproot (bc1p) when you value the best privacy characteristics and the most efficient handling of multisignature or scripted spends. Taproot support is now common in major wallets.
• Keep Legacy (1) or P2SH (3) only when you must interact with an older system that cannot handle bech32, or when you are dealing with funds that already sit in those formats.

There is no rush to move existing coins between formats. Consolidating outputs into a newer type costs a transaction fee, so it usually makes sense to switch formats naturally as you receive and spend, rather than sweeping everything at once. For an argument that segwit vs taproot address choices should favor Taproot going forward, the Taproot upgrade specification in BIP-341 lays out the reasoning behind Schnorr signatures and the more flexible spending model.

How the same key produces different address types

Here is the part that surprises many people the first time they see it: one private key can back a Legacy address, a P2SH address, a native SegWit address and a Taproot address at the same time.

A Bitcoin address is not the key itself. It is a compact, checksummed encoding of a script that locks coins to a public key. The private key derives a public key, and the public key can then be wrapped in different ways:

• For a Legacy address, the public key is hashed and encoded in Base58Check, producing a string that starts with 1.
• For a native SegWit address, that same hash is placed in a witness program and encoded in bech32, producing a bc1q string.
• For a Taproot address, the public key is tweaked and encoded in bech32m, producing a bc1p string.

Because the underlying key is identical, whoever controls the private key controls all of these addresses. They are simply different envelopes around the same ownership. This is also why a wallet can show you separate balances for different address types while a single recovery phrase restores every one of them.

Understanding this relationship is the core of practical Bitcoin research. If you want to verify it hands-on, the Bitcoin Research Tool by QbyteLab includes an offline HEX, WIF and address converter that takes a single key and shows you the Legacy, SegWit and Taproot addresses it produces, all computed on your device with no network calls. The same app pairs that converter with an on-chain explorer and detailed address dossiers, so you can move from "what type is this address" to "what has this address actually done" without leaving the tool. For a broader look at tracking coins without ever holding keys, our note on running a crypto app with no custody covers the privacy-first approach behind it.

Putting it into practice

Next time you copy or receive a Bitcoin address, glance at the first characters before anything else. That single habit tells you the fee profile, the likely compatibility and the privacy posture of whatever you are about to send or receive. If you want to inspect the key math yourself and confirm how one key maps to every format, download the Bitcoin Research Tool by QbyteLab on the App Store or Google Play, open the offline converter, and paste in a test key to watch all four address types appear side by side.

Frequently asked questions

How do I tell what type a Bitcoin address is?

Read the first characters. A leading 1 is Legacy, a 3 is P2SH, bc1q is native SegWit, and bc1p is Taproot.

What is the difference between a SegWit and a Taproot address?

Native SegWit addresses start with bc1q and use bech32 encoding, while Taproot addresses start with bc1p and use bech32m. Taproot also enables Schnorr signatures and more private spending conditions.

Can the same private key have multiple address types?

Yes. A single key pair can be encoded as a Legacy, P2SH, SegWit or Taproot address. Each format wraps the same public key in a different script, so they are different addresses controlled by one key.

Which Bitcoin address type is cheapest to use?

Native SegWit and Taproot addresses generally pay lower fees than Legacy addresses because witness data receives a discount when a block's weight is calculated.

Are Legacy addresses still safe to use?

Yes, Legacy addresses still work and hold funds securely. They simply tend to cost more in fees and offer less flexibility than newer formats.