How to Send Bitcoin to Another Wallet: Address Types, Fee Settings, and a Clean First Transfer
Sending BTC wallet-to-wallet is five inputs — and Bitcoin adds two quirks other chains don't have: multiple address formats (1…, 3…, bc1…) and a fee market you choose your speed in. What each address type means, how to pick a fee tier without overpaying, and the walkthrough for a clean first send.
The short answer: sending bitcoin between wallets is the standard five-step transfer — coin, network, address, amount, confirm — with two Bitcoin-specific wrinkles worth two minutes of understanding: addresses come in several formats (starting with 1, 3, bc1q, or bc1p — all valid, all compatible to send to), and you choose your own fee, which is really choosing your place in line: a higher fee confirms in the next block or two; a stingy one waits. Below: what the address types mean, how to set fees like someone who's done this before, and the clean-first-transfer routine.
Bitcoin address types, decoded in one table
All current wallets can send to all of these — the prefix mostly tells you the receiver's wallet generation and your fee efficiency:
| Starts with | Type | What it means for you as sender |
|---|---|---|
bc1q | SegWit (bech32) | The modern standard — cheapest to spend from, case-insensitive, hard to mistype |
bc1p | Taproot | Newest format; fine to send to from any current wallet |
3 | Script (P2SH) | Older multisig/wrapped style — still everywhere, still fine |
1 | Legacy | The original format — works, but transactions from it cost the most in fees |
Practical takeaways: never type any of them by hand (read pasted addresses at both ends and the middle); if your own wallet still gives you a 1… receiving address, consider generating a modern one — your future fees will thank you; and a very old wallet app that refuses a bc1… address needs an update, not a workaround.
The fee tier: you're bidding for a seat, not paying a toll
Bitcoin fees are set by you (or your wallet's suggestion) in sats per virtual byte — and the amount you're sending doesn't matter, only the transaction's data size and how crowded the mempool is. Wallets translate this into tiers:
- Priority/fast: targets the next block — worth it when a merchant or exchange is waiting
- Normal: an hour-ish on a typical day — the right default for wallet-to-wallet moves
- Economy: hours to eventually — fine for repositioning funds nobody's waiting on
Two habits complete the picture: glance at your wallet's current-congestion indicator before choosing (the same tier costs very different sats on a quiet Sunday versus a busy Monday), and prefer wallets supporting RBF (replace-by-fee) — the undo button for choosing "economy" and regretting it, and the calm answer to a stuck transaction.
The clean first transfer, start to finish
- 1Get the receiving address from the destination wallet's "Receive" screen — copy or scan, never transcribe
- 2Paste and verify — first 4, last 6, one middle chunk against the source
- 3Choose amount — remember the fee comes on top from your balance; "send max" buttons handle the math for emptying a wallet
- 4Pick your fee tier for how long you're happy to wait
- 5Send a test first if this address is new and the amount matters — $10 through, confirmed, then the balance. Two fees are cheap insurance
- 6Track it — paste the TXID into any explorer; one confirmation for small amounts, 3–6 for meaningful ones
The mistakes specific to bitcoin sends
- Sending BTC to a non-BTC address (an Ethereum
0x…or Solana address): format incompatibility means wallets refuse — the guardrail works. The residual danger is wrapped BTC products on other chains: if someone gives you a0x…address "for bitcoin", they're asking for a token on another chain, not BTC — slow down and confirm which. - Fee panic in both directions: overpaying 10× for an urgent-feeling transfer nobody was waiting on, or economy-tier for a merchant payment that then sits pending at checkout. Match the tier to who's waiting.
- Emptying a wallet by hand-math: balance minus amount minus fee is fiddly — use the wallet's max/sweep function.
- Repeating a "stuck" send: the first one is queued, not gone — bump the fee instead of doubling the payment.
FAQ
Can I send bitcoin from one wallet type to another — say, legacy to SegWit?
Yes — all standard formats interoperate. The receiver's format doesn't change your send; your own wallet's format changes your fees.
How much does sending bitcoin cost?
Whatever tier you choose against current traffic — from well under a dollar on quiet days to several during spikes. For context, payment-optimized chains move stablecoins for fractions of a cent.
How long will my transfer take?
Tier-dependent: next block (~10 min) to hours — plus your exchange's queue if withdrawing rather than wallet-sending.
Is there a minimum amount I can send?
Practically, sends below a few dollars stop making sense on-chain because the fee rivals the amount — the "dust" zone. For small-value transfers, fast-chain stablecoins are the economical rail.
Should I use Lightning instead for wallet-to-wallet?
If both wallets speak it, Lightning is fast and near-free for small amounts — with its own setup realities. On-chain remains the default for meaningful sums and cold storage moves.
What's the safest way to move a large amount of BTC?
Test-then-balance, normal-or-priority fee, and patience for 3–6 confirmations. Large moves deserve the full ritual precisely because settlement is final.
How do I send bitcoin to someone else's wallet step by step?
Their address (read ends-and-middle), the amount, a fee tier matched to your patience, confirm — the five-step habit applied to BTC's address formats and fee market, which is this article.
Can I send bitcoin from an exchange to a wallet?
Yes — that's the standard self-custody move: withdraw screen, paste your wallet's receive address, expect the exchange's fee and review pause on first sends. Test amount first for meaningful sums.
What happens if I send bitcoin to an invalid or wrong address?
Invalid addresses are rejected by the checksum — the send never happens. A valid but wrong address is the one unrecoverable error; the fifteen-characters reading habit exists for exactly this.
Why is my wallet suggesting different fee levels?
That's the auction from the article — you're bidding for block space, not paying a toll. Low bids ride cheap and slow; the fee slider is a patience dial, not a quality dial.
What is RBF and should I enable it?
Replace-by-fee: the regret button — it lets you re-bid a stuck transaction's fee upward instead of waiting it out. Enable it by default; you'll want it precisely once, badly.
Do I need to keep bitcoin in the same wallet type I received it in?
No — all current wallets send to all four address formats; the format describes the destination's era, not a compatibility wall. Fees differ slightly by format; correctness doesn't.
Can I cancel a bitcoin transaction after sending?
Not once mined — finality is the feature. While still unconfirmed: RBF can replace it, which is the closest thing to cancel that exists.
Should I send BTC or convert to stablecoins for payments?
Moving between your own wallets: BTC as BTC, obviously. Paying someone: the conversion route is usually cheaper and faster than on-chain BTC — and what most checkouts are built around.
How do I receive bitcoin in my wallet?
Share a receive address — freely; it's public by design. Modern wallets rotate receive addresses automatically for privacy; any of the old ones still works.
Does sending bitcoin between my own wallets have tax implications?
Moving your own funds between your own wallets is generally just custody rearrangement, but rules and record-keeping expectations vary by jurisdiction — same principle as merchant obligations: the rail doesn't change them; ask a local professional.
If you're moving BTC because you're about to spend it somewhere: check whether the checkout takes stablecoins first — converting at your exchange and paying on a fast chain is usually cheaper than the on-chain BTC fee alone. And if you're the one selling: a checkout that accepts both kinds of customer takes fifteen minutes.