What is a Bitcoin address, and which format should you use?
A Bitcoin address is the string you share to receive bitcoin. This guide explains the four formats, from legacy addresses that start with 1 to Taproot's bc1p, which one to use, and how to avoid losing coins to a wrong address.
Published · 7 min read
A Bitcoin address is the string of letters and numbers you share so someone can send you bitcoin. Think of it as a mailbox for one payment. Your wallet can make a new one whenever you like, and for privacy it should. The first character, a 1, a 3, or the letters bc1, tells you the format.
Addresses look cryptic. They are not meant to be memorized. You copy one, paste it, or scan a QR code, and the wallet does the rest. What matters is getting every character right, because a Bitcoin payment cannot be undone once it confirms.
How a Bitcoin address works
An address is not your account, and it is not your key. It is derived from your keys, which come from your wallet's seed phrase. When you set up a wallet, it creates a secret seed. From that seed the wallet can produce a near endless supply of private keys, public keys, and the addresses that match them. You never run out.
The math runs one way. A public key turns into an address, but nobody can work backward from the address to your private key. That is what lets the address sit in public on the blockchain while your coins stay safe.
Addresses also differ in how they are written. Older legacy and P2SH addresses use an encoding called Base58 and are case sensitive, so a wrong capital letter breaks them. The bc1 formats use a newer scheme called bech32, which the Bitcoin Wiki notes is case insensitive. That is why a bc1 address is all lowercase, and why you can read it aloud or print it without fretting over capitals.
The four address formats, from 1 to bc1p
Bitcoin has four main address formats in regular use. They were added over the years, each one cheaper or more private than the last, and all four still work. You can send from any type to any other, so a 1 address can pay a bc1p address without trouble.
Legacy addresses start with 1. These are the original type, known as P2PKH, and they use an encoding called Base58. They still work fine. They also take up the most block space, so they tend to cost the most in fees. Trezor describes the legacy format as a remnant of earlier technology.
P2SH addresses start with 3. Pay to Script Hash arrived in 2012 through a change known as BIP16. It can hold a wrapped version of SegWit that trims fees compared with a plain legacy send. If you are not sure whether a service supports newer formats, an address starting with 3 is the safe fallback.
Native SegWit addresses start with bc1q. SegWit went live on August 24, 2017, at block 481,824, and its native addresses use an encoding called bech32. They are built to use data efficiently. A simple one in, two out send runs about 141 vBytes with native SegWit, against roughly 226 for the same send from a legacy address, per Spark's figures. That is close to 38 percent less data. Since you pay fees by data size, a smaller transaction means a smaller fee. The wrapped form behind a 3 address sits in between, near 167 vBytes.
Taproot addresses start with bc1p. Taproot activated on November 14, 2021, at block 709,632, and uses a refined encoding called bech32m. For a plain single payment, Taproot is not much cheaper than native SegWit, and it can even be a touch larger. Its real strengths are privacy and complex spends. A two of three multisignature wallet, for example, can drop from about 104 vBytes to about 58 using a Taproot key path, per Spark, close to a 45 percent cut. It also makes a fancy spend look like an ordinary one, so an outside observer learns less about your setup.
Reading an address at a glance
You can tell a lot from the opening characters alone. A 1 means a legacy address, a 3 means P2SH, bc1q means native SegWit, and bc1p means Taproot. Length is another tell. Most addresses run 26 to 35 characters, and a typical one is 34, according to the Bitcoin Wiki, so a string far outside that range should make you pause.
A built-in checksum does the rest of the work. Those are a few characters baked into the address so that software can, in the Bitcoin Wiki's words, automatically find and reject a typing error. Fumble a character on a copy and paste, and your wallet should refuse the address rather than fire coins into the void. That safety net is real. It guards against typos, though, not against pasting a valid address that belongs to the wrong person.
Which format should you use?
For everyday use, native SegWit (bc1q) is the practical default. It keeps fees low and is widely supported across exchanges and wallets. Many wallets, including Trezor Suite, set it as the standard.
Taproot (bc1p) leans on privacy more than raw fee savings. For a plain payment it will not save you much over bc1q, and in some cases it is slightly larger, so the honest answer here is boring. Use bc1q unless you have a reason to use Taproot, such as a multisignature setup where its efficiency and privacy earn their keep.
One catch. A few older services still cannot send to bc1 addresses at all. If a withdrawal screen rejects your bc1q or bc1p address, that is usually why. An address starting with 3 will still get the coins into your wallet, which can then move them internally.
Why you should not reuse an address
Reusing an address does not break Bitcoin, but it chips away at your privacy. Every payment to an address is public and permanent on the blockchain. Use the same address for your salary, a refund, and a public donation page, and anyone can tie those together and watch the balance rise and fall.
The fix costs nothing. Let your wallet hand out a fresh address each time you receive. The Bitcoin Wiki puts it plainly: a unique invoice should be used for each transaction. Your old addresses keep working too, so money sent to a past one still arrives.
How to avoid sending to the wrong address
A Bitcoin transaction is final. Once it confirms, there is no bank to call and no undo button. Trezor states it directly: in most cases there is no way to recover bitcoin sent to the wrong recipient if the address was valid.
Two habits remove most of the risk. First, never type an address by hand. Copy and paste it, or scan the QR code, then check that the first four and last four characters match on both screens. Second, send a small test amount before a large transfer, or when the address is new to you.
Checksums cover typos, not swaps. Address-swapping malware can quietly replace what you copied with an attacker's valid address, and the checksum will accept it without complaint. That is why the final check matters most. When you can, confirm the address on your hardware wallet's own screen before you approve the send.
What to watch
Formats keep shifting toward bc1. Legacy and P2SH addresses are not going away soon, but more services now default to native SegWit, and Taproot use is still climbing from a low base. If you run an older wallet, updating it is the simplest way to get cheaper sends and wider support.
Two things are worth keeping in mind. Bitcoin addresses are free and disposable, so make a new one often. And the network does not care which format you hold, because every type can pay every other type. Get the characters right, keep your seed safe, and the address itself becomes the easy part.
Frequently asked
What is a Bitcoin address?
A Bitcoin address is a short string of letters and numbers that you share so someone can send you bitcoin. Your wallet creates it from your private keys. You can generate a new address for every payment, and most wallets do this for you to protect your privacy.
What do the different Bitcoin address formats mean?
The first characters show the format. An address starting with 1 is a legacy address, one starting with 3 is a P2SH address, bc1q is native SegWit, and bc1p is Taproot. The bc1 formats are newer and cheaper to send. You can send between any of them.
Can I get my bitcoin back if I send it to the wrong address?
Usually no. A confirmed Bitcoin transaction cannot be reversed, and no support line can claw the coins back if the address was valid. Always paste or scan the address, check the first and last characters, and send a small test amount first when the total is large.
Sources, and what is behind them
- Invoice address, Bitcoin WikiDocumentation
- Bitcoin account types: SegWit, Legacy and Taproot explained, TrezorDocumentation
- Bitcoin addresses and how to use them, TrezorVendor announcement
- Bitcoin address types: from legacy P2PKH to Taproot, SparkOther