SegWit vs Legacy Addresses: How Your Address Type Changes Your Fee

Two people can send the exact same amount of Bitcoin, at the exact same sat/vByte rate, and pay different fees. The reason is often the address type they're using. A modern SegWit address builds a smaller transaction than an old-style legacyaddress, and smaller transactions cost less. Here's how the address prefixes map to fee cost, why the difference exists, and how to make sure you're on the cheaper kind.

What the address prefixes mean

Every Bitcoin address starts with a few characters that tell you — and the network — what technical format it uses. Those formats confirm at different sizes:

• →Legacy — starts with 1… (called P2PKH). The original address format from 2009. Works everywhere, but builds the largest, most expensive transactions.
• →Nested SegWit — starts with 3… (P2SH-P2WPKH). A SegWit upgrade wrapped inside an older-style address for compatibility. Cheaper than legacy, but not as cheap as native SegWit.
• →Native SegWit — starts with bc1q… (P2WPKH, also called bech32). The current standard for most wallets. Smaller and cheaper than both of the above.
• →Taproot — starts with bc1p… (bech32m). The newest format. For a simple send it's roughly on par with native SegWit, sometimes a touch smaller.

A 3…address is easy to confuse with legacy because it doesn't look like a “SegWit” address, but it is one under the hood. The two bc1formats are the ones that look different — and they're where the savings really show up.

Why the size — and the fee — differs

Bitcoin fees aren't charged by how many coins you move; they're charged by how much block space your transaction takes up, measured in vBytes(virtual bytes). Two sends of very different amounts can occupy the same space and pay the same fee. If you're new to that idea, start with how Bitcoin fees work.

SegWit's trick is called the witness discount. It splits a transaction into two parts: the core data, and the “witness” data (the signatures that prove you own the coins). The witness part is counted at only one-quarter of its weight when measuring vBytes. Signatures are a big chunk of any transaction, so moving them into the discounted witness section drops the effective vByte size a lot.

The practical result

For a typical simple send (one input, two outputs), the savings are meaningful:

• →Native SegWit (bc1q…) is usually around 30–40% smaller than the same send from a legacy (1…) address — so you pay roughly 30–40% less in fees for it.
• →Nested SegWit (3…) lands in between: cheaper than legacy, but larger than native SegWit because of its extra wrapping.
• →Taproot (bc1p…) is similar to native SegWit for a basic payment — comparable, occasionally a little better. It shines most for more complex or multi-signature spends. See Taproot and fees.

The exact percentage shifts with how many inputs and outputs your transaction has, so treat these as ballpark ranges, not guarantees. The direction, though, is always the same: native SegWit and Taproot build smaller transactions than legacy.

How to tell which type you're using

You don't need any tools — just look at the address your wallet gives you when you tap Receive:

• →Starts with 1 → legacy (the expensive one).
• →Starts with 3 → nested SegWit.
• →Starts with bc1q → native SegWit (cheap).
• →Starts with bc1p → Taproot (cheap).

Most wallets released in the last few years hand you a bc1q or bc1p address by default, so there's a good chance you're already on the efficient side. If your receive address still starts with 1 or 3, you're leaving money on the table every time you spend.

How to “switch” to a cheaper address type

Switching is simpler than it sounds, because you don't convert your existing coins into a new format. Your address type only affects the fee when you spend. To move to the cheaper kind, you just start using a native SegWit or Taproot address going forward:

• →Check your wallet's settings. Many wallets let you pick the default address type for new receive addresses — choose native SegWit (bc1q) or Taproot (bc1p).
• →Receive to the new address. The next time someone pays you, use the bc1 address. New coins arrive at the efficient format.
• →Optionally consolidate. If you have older coins sitting at a 1… or 3… address, you can send them to your new native SegWit address — ideally during a low-fee window so the one-time move is cheap. See what a good sat/vByte fee is.

The bottom line

Your address type quietly sets the size of every transaction you send, and size sets the fee. Legacy 1… addresses are the most expensive; native SegWit bc1q… and Taproot bc1p…are the cheapest, typically cutting a simple send's fee by around a third. You're paying the same rate per vByte either way — you're just buying fewer vBytes. If your receive address starts with bc1, you're already there. If it doesn't, switch your wallet's default and start receiving to the new format. For the full picture on how the fee market works, see Bitcoin transaction fees explained.

See what a send costs at the current rate with the SatSaver tracker. Mempool data from mempool.space.