A Bitcoin address is a unique string of letters and numbers that acts as a destination for receiving bitcoin, similar to how an email address is a destination for receiving messages. Anyone who has your address can send you bitcoin, but only you can spend what arrives there. If you have ever copied a long code starting with "1", "3", or "bc1" to receive a payment, you have already used one.
There is more going on under the surface than most guides let on, though. An address does not actually "hold" your coins, wallets deliberately give you a new address for every payment, and the format you use directly affects the fees you pay. This guide covers how Bitcoin addresses work, the different address types, how to get one, and how to send and receive BTC without losing funds.
Manage your Bitcoin securely with the self-custody Bitcoin.com Wallet app.
Key takeaways
- A Bitcoin address is a public identifier for receiving BTC. It is safe to share, unlike your private key, which must stay secret.
- Addresses do not store bitcoin. They point to entries on the blockchain that your private key can unlock.
- There are four main Bitcoin address formats: Legacy (starts with "1"), Nested SegWit (starts with "3"), Native SegWit (starts with "bc1q"), and Taproot (starts with "bc1p").
- Newer formats cost less to spend from. A typical Native SegWit transaction is roughly 38% smaller than its Legacy equivalent, which translates directly into lower fees.
- Bitcoin transactions are irreversible. Always verify the full address before sending, and be aware of address poisoning scams that plant lookalike addresses in your transaction history.
- Your wallet generates a fresh address each time you receive funds. This is normal, and old addresses keep working.
What is a Bitcoin address?
A Bitcoin address is a short, shareable identifier that tells the Bitcoin network where a payment should go. It typically contains between 26 and 62 alphanumeric characters and is generated by your wallet software at no cost.
The email analogy is useful, but it only goes so far. An email inbox stores your messages. A Bitcoin address stores nothing. When someone sends you bitcoin, the network records a transaction output on the blockchain, a public ledger maintained by thousands of computers worldwide. That output is locked to your address and sits on the ledger as an unspent transaction output, or UTXO, until you spend it.
Your wallet scans the blockchain for outputs locked to your addresses and adds them up. That total is the "balance" you see on screen. The coins never live inside the address or the wallet app itself. They live on the blockchain, and your address simply marks which entries belong to you. This distinction matters in practice: it explains why you can restore a wallet on a new phone from a seed phrase and find your balance intact, and why losing your phone does not mean losing your bitcoin.
Public keys, private keys, and where addresses come from
Every Bitcoin address is the end product of a chain of cryptography that starts with a private key. The process runs in one direction only:
- Private key - Your wallet generates a very large random number. This is the master secret that authorizes spending. Whoever knows it controls the funds.
- Public key - The wallet derives a public key from the private key using elliptic curve mathematics. The math is easy to run forward and practically impossible to reverse, so the public key reveals nothing about the private key.
- Address - The public key is hashed and encoded into the compact, error-resistant string you share with other people.
People sometimes describe this pair as a "public address" and a "private address". Strictly speaking, the address is the public part and the private key is not an address at all, but the safety rule behind the phrasing is exactly right: the address is designed to be shared, and the private key must never be shared with anyone, ever. Anyone who obtains your private key (or the seed phrase that generates it) can take your bitcoin, and no support desk can undo that.
A quick rule of thumb:
- Bitcoin address: share freely. Post it, print it, put it on an invoice.
- Public key: technically shareable, though wallets rarely ask you to.
- Private key and seed phrase: never share, never type into a website, never photograph.
What does a Bitcoin address look like?
Each format has a distinctive prefix, so you can identify the type at a glance. Some real examples:
- Legacy:
1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa(this particular one is famous, it received the first block reward ever mined, in January 2009) - Nested SegWit:
3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy - Native SegWit:
bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4 - Taproot:
bc1p0xlxvlhemja6c4dqv22uapctqupfhlxm9h8z3k2e72q4k9hcz7vqzk5jj0
Two details in the design make addresses safer to handle than they look. First, the encoding deliberately excludes confusing characters: older Base58 addresses never contain 0 (zero), O (capital o), I (capital i), or l (lowercase L). Second, every address contains a built-in checksum. If you mistype a character, wallet software detects that the checksum does not match and rejects the address outright, so a simple typo almost always results in an error message rather than lost funds.
Addresses are also commonly shared as QR codes. Scanning a code with your phone camera copies the address perfectly, which removes the risk of manual typing errors entirely. Most wallets display a QR code automatically on the receive screen.
The four Bitcoin address types
Bitcoin's address formats have evolved alongside the protocol. Each new generation reduced transaction size, which lowers fees, and added capabilities. All four types remain valid, and any type can send to any other type.
| Address type | Technical name | Starts with | Introduced | Relative fee cost | Best for |
|---|---|---|---|---|---|
| Legacy | P2PKH (Pay-to-Public-Key-Hash) | 1 | 2009 | Highest | Compatibility with very old software |
| Nested SegWit | P2SH (Pay-to-Script-Hash) | 3 | 2012 (BIP 16) | Medium | Legacy-compatible SegWit, older multisig |
| Native SegWit | P2WPKH, Bech32 encoding | bc1q | 2017 (BIP 173) | Low | Everyday transactions, the current default |
| Taproot | P2TR, Bech32m encoding | bc1p | 2021 (BIP 341) | Low | Privacy, multisig, advanced scripts |
1. Legacy addresses (P2PKH): start with "1". The original format, in use since the genesis block in 2009. Every wallet and exchange on earth supports it, but it is the least efficient. Signature data sits in the main body of the transaction, making Legacy transactions the largest and most expensive per payment.
2. SegWit addresses (P2SH-P2WPKH and Bech32): start with "3" or "bc1". SegWit (Segregated Witness) activated in August 2017 and moved signature data into a separate, discounted section of the transaction. It arrived in two flavors. Nested SegWit wraps the new format inside an older "3" style P2SH address so that outdated software can still send to it. Native SegWit uses the purpose-built Bech32 encoding defined in BIP 173, is all lowercase, catches typos more reliably, and delivers the full fee saving. As of early 2026, roughly 85 to 90% of Bitcoin transactions spend at least one SegWit input, and "bc1q" is the default receive format in most modern wallets.
3. Taproot addresses (P2TR): start with "bc1p". Activated in November 2021 through BIP 341, Taproot introduced Schnorr signatures and a more flexible scripting system. Its standout feature is privacy through uniformity: a complex multi-signature arrangement spends from a Taproot address looking identical to a simple single-key payment, so observers cannot tell sophisticated setups apart from ordinary ones. According to Glassnode data, around 29% of Bitcoin transactions used at least one Taproot input as of March 2026, up from single digits before the format found mainstream wallet support, though a small number of older services still cannot send to "bc1p" addresses.
Why the format affects your fees
Bitcoin fees are charged per unit of transaction data, not per amount sent, so smaller transactions cost less. A typical single-input, two-output payment weighs approximately 226 virtual bytes from a Legacy address, around 166 from Nested SegWit, roughly 141 from Native SegWit, and about 111 from Taproot. In quiet network conditions the difference is pennies. During fee spikes, when confirmation can cost several dollars per transaction, spending from a Legacy address can cost roughly double the equivalent Native SegWit payment. If your wallet still defaults to an address starting with "1", switching the account type to Native SegWit is one of the simplest fee savings available.
How to get a Bitcoin address
You never create an address manually. Wallet software generates addresses for you, and the process takes about a minute. There are two routes, and the difference matters.
Self-custody wallet (you control the keys):
- Download a reputable wallet app on your phone or computer, or set up a hardware wallet.
- Create a new wallet and write down the seed phrase (usually 12 or 24 words) on paper. Store it offline. This phrase can regenerate every key and address in the wallet, so treat it like the master password to your money.
- Tap "Receive". The wallet displays your Bitcoin address and its QR code.
- Copy the address or let the sender scan the code.
Custodial account (an exchange controls the keys): log in, go to the deposit section, select Bitcoin, and copy the deposit address shown. This is convenient, but the platform holds the private keys on your behalf, so you are trusting its security and solvency rather than your own seed phrase.
Why your address keeps changing
New users are often alarmed when their wallet shows a different address every time they hit "Receive". Nothing is wrong. Modern wallets are hierarchical deterministic (HD), meaning they derive a practically unlimited sequence of addresses from your single seed phrase. Wallets rotate to a fresh address after each incoming payment as a privacy measure: since every Bitcoin transaction is public, reusing one address forever would let anyone who has paid you browse your entire payment history. Old addresses remain valid indefinitely, and funds sent to them still land in the same wallet.
How to send and receive bitcoin safely
Bitcoin transactions are permanent. There are no chargebacks, no reversals, and no customer service line that can claw a payment back. A few habits eliminate nearly all real-world mistakes:
- Verify the full address, not just the ends. Malware known as a clipboard hijacker can silently replace a copied address with an attacker's address. Check the entire string after pasting, and on a hardware wallet, confirm the address shown on the device screen itself.
- Beware address poisoning. In this increasingly common scam, an attacker sends a tiny "dust" payment to your wallet from an address crafted to visually mimic one you use, matching the first and last characters. The goal is that you later copy the imposter address from your transaction history. Never copy addresses from past transactions; always take them from the recipient directly.
- Use QR codes when possible. Scanning removes typing errors completely.
- Send a small test amount first for large transfers, confirm it arrives, then send the rest. The extra fee is cheap insurance.
- Match the network. A Bitcoin address is for Bitcoin only. Sending BTC to an Ethereum or Bitcoin Cash address (or vice versa) can result in permanent loss. Reputable wallets block obviously invalid combinations, but double-checking costs nothing.
- Confirm the amount and address before hitting send, then wait for at least one network confirmation before treating a received payment as final.
What if you send to a wrong but valid address anyway? The checksum only protects against typos that produce an invalid string. If the address is real, the transaction settles normally and only the person holding that address's private key can return the funds. If nobody holds the key, the coins are unspendable forever. This is why every safety habit above focuses on verifying before sending, because after sending, there is nothing to fix.
Bitcoin addresses and privacy
Bitcoin is pseudonymous, not anonymous. Addresses contain no names or personal data, but every transaction ever made is publicly recorded and permanently visible. Anyone can paste an address into a blockchain explorer and instantly see its balance and complete transaction history.
That transparency cuts both ways. It lets you verify payments independently without trusting anyone, and it also means that once an address is linked to your identity, through an exchange account with identity verification, a public donation page, or a forum post, your activity on that address becomes traceable. Blockchain analytics firms and law enforcement routinely cluster addresses and follow funds this way.
The practical defenses are straightforward: let your wallet rotate addresses automatically, avoid reusing an address once it has been spent from, and avoid publicly associating your name with addresses you want to keep private. Bitcoin.org's privacy guide covers these practices in more depth. For most users, the default behavior of a modern wallet already provides reasonable privacy hygiene.
Conclusion
A Bitcoin address is the public, shareable half of the cryptographic system that secures your bitcoin: a compact identifier that directs payments to entries on the blockchain only your private key can unlock. As of 2026, Native SegWit "bc1q" addresses are the everyday standard, Taproot "bc1p" adoption continues to build on the back of its privacy and multisig advantages, and the older "1" and "3" formats remain fully functional for compatibility. Understand the prefixes, guard your private key, verify before you send, and addresses become one of the simplest parts of using Bitcoin.
