One bitcoin is divided into 100 million satoshis. Sats are not a separate asset. They are the smallest accounting unit inside every bitcoin wallet, the native unit of the protocol code, and the unit miners, fee estimators, and Lightning invoices use by default. This guide explains the conversion math, how wallets and exchanges display each unit, why fee screens show "sats/vB" instead of dollars, and the decimal-placement mistakes that cost beginners meaningful amounts. Figures are current as of May 2026 where noted.
What is a satoshi, and how does it relate to one bitcoin?
A satoshi (abbreviated "sat") is the smallest unit of bitcoin that can be recorded on the main chain. One bitcoin equals exactly 100,000,000 satoshis, and one satoshi equals 0.00000001 BTC. The ratio has been hard-coded in Bitcoin Core since the Bitcoin network launched in January 2009 and cannot be changed without breaking every existing transaction Bitcoin Wiki).
The unit is named in honor of Satoshi Nakamoto, Bitcoin's pseudonymous creator. The name first appeared in community usage around 2010 and was formalized in Bitcoin Core's source code and documentation soon after. Every line of Bitcoin Core that handles monetary amounts works in satoshis internally; BTC is only a display format applied at the user-interface layer (source: GitHub).
Why the 8-decimal cap exists
Bitcoin amounts are stored on-chain as 64-bit integers representing satoshis, not as floating-point BTC values. That integer type has a maximum value large enough to hold the full 2.1 quadrillion-sat supply (21,000,000 BTC × 100,000,000) with room to spare. Using integers avoids the rounding errors that plague floating-point arithmetic in financial code. The visible consequence is that every on-chain amount is a whole number of sats, and every BTC value rounds to exactly eight decimal places.
If Bitcoin ever needed finer precision on the base chain, a change to the core amount type would require a network-wide upgrade. No such change has been proposed seriously. The Lightning Network handles sub-sat precision separately, which is covered later in this guide.
"Buying sats" and "buying bitcoin" are the same action
If you spend $100 on 0.001 BTC, you also spent $100 on 100,000 sats. Your wallet can show either number. Nothing about the purchase changes. The common beginner mistake is treating sats as if they were a cheaper altcoin or a fractional "share" of bitcoin, similar to how brokerages sell fractional stock. That analogy is wrong in one crucial way: fractional shares are an accounting layer added by the broker, and different brokers track them differently. Sats are native to the protocol. Every wallet, every node, and every block explorer counts the same sats the same way.
One useful analogy, and where it breaks
Sats are to BTC roughly what cents are to a dollar, except the ratio is 100 million instead of 100. The analogy is useful for explaining divisibility to someone who has never handled digital money. It breaks at two points. First, dollars are divisible only to two decimal places in everyday use; bitcoin is divisible to eight, which is why microtransactions are possible without inventing a new unit. Second, physical cents exist as coins; sats exist only as ledger entries. You will never hold a single sat in your hand the way you hold a penny.
How do I convert between BTC and satoshis quickly?
The math is a single multiplier: 100,000,000. To convert BTC to sats, multiply by 100 million (or move the decimal eight places to the right). To convert sats to BTC, divide by 100 million (or move the decimal eight places to the left). There is no other step, no exchange rate, no fee, and the number is fixed forever by protocol (source: River).
In practice, most wallets let you toggle the display unit in settings. If you never want to do the math yourself, pick one unit and stick with it. The numbers below are the conversions you are most likely to encounter.
Common BTC-to-sats conversions
Memorizing a few anchor points is faster than doing arithmetic every time.
BTC amount | Sats equivalent | Typical context in 2026 |
|---|---|---|
1 BTC | 100,000,000 sats | Full unit, rare to send whole |
0.1 BTC | 10,000,000 sats | Large purchase, ETF basket equivalent |
0.01 BTC | 1,000,000 sats | Common savings-stacking increment |
0.001 BTC | 100,000 sats | Everyday retail purchase range |
0.0001 BTC | 10,000 sats | Small tip, Lightning payment |
0.00001 BTC | 1,000 sats | Micro-tip, game reward |
0.0000001 BTC | 10 sats | Micropayment, sub-tip |
0.00000001 BTC | 1 sat | Smallest on-chain unit |
At a May 2026 BTC price range of roughly $80,000 (source: Finance), 1,000 sats is about $0.80, and 100,000 sats is about $80. Those numbers drift with the spot price, so wallets typically show a live fiat estimate alongside the sat count.
The decimal-shift shortcut
If the "multiply by 100 million" framing is hard to hold in your head, use this visual rule instead:
BTC to sats: write the BTC amount, drop the decimal point, and pad with zeros until you have eight digits after where the point used to be. Example: 0.00012345 BTC becomes 12,345 sats.
Sats to BTC: write the sat count, then prepend enough zeros to make the total eight digits, and place a decimal point at the front. Example: 12,345 sats becomes 0.00012345 BTC.
In regions that use comma as the decimal separator, "0,001 BTC" is read as "zero point zero zero one BTC," identical to "0.001 BTC" in US notation. Wallets following European conventions may display it that way. Never type amounts by hand when the value matters; copy and paste the number or scan a QR code.
A working conversion example
Suppose a merchant invoices 47,500 sats. To price that in BTC, shift the decimal eight places left: 0.00047500 BTC, usually displayed as 0.000475 BTC. At a May 2026 BTC price of $71,000, 47,500 sats is about $38 The merchant's point-of-sale app does this conversion automatically for the fiat display; you only need the math to sanity-check that the sat amount on screen matches the dollar amount you expected.
How do wallets, exchanges, and fee screens show these units?
Almost every Bitcoin wallet lets you switch the display between BTC and sats in a settings menu; the underlying balance never changes, only the presentation. Fee screens behave differently: they are often forced to sats or sats/vB because the amounts involved are too small to display cleanly in BTC. Understanding which screen uses which unit is the difference between paying the correct fee and overshooting by 100x.
Mobile wallets (BlueWallet, Muun, Phoenix, Breez) default to sats for small balances. Hardware wallets (Ledger, Trezor) and desktop clients (Bitcoin Core, Sparrow) often default to BTC because they target larger balances. Exchanges usually show BTC with eight decimal places on the trade screen but switch to sats for fee rates and Lightning invoices.
Where you will see BTC by default
Long, precise BTC amounts are the default for balances above about 0.01 BTC, any spot-market trade screen, and any cold-storage context where the user wants an unambiguous record. BTC is also the default on tax reports and accounting tools because dollar values are calculated from BTC at a known block time.
Where you will see sats by default
Sats are the default for Lightning invoices and channel balances, fee-estimation screens (almost always sats/vB), small on-chain amounts under 0.01 BTC, and most "stacking sats" accumulation apps (Swan, River Learn, Strike). If you see a five- or six-digit number next to a bitcoin logo on a wallet screen, it is almost certainly sats, not BTC.
Toggling your wallet display
Most wallets follow the same pattern for switching units:
Open the wallet's settings or preferences screen.
Locate the "Display," "Units," or "Denomination" option.
Select BTC, sats, or (less commonly) mBTC.
Confirm, return to the main balance screen, and verify the number changed as expected.
Nothing else changes. The bitcoin on your keys is identical before and after.
The last step matters. New users sometimes toggle display units and panic because the balance jumps from a tiny fraction to a large whole number (or vice versa). No bitcoin moved, was converted, or was exchanged. Only the label changed. On the operations side, unit-display confusion is one of the most frequent categories of support inquiries we see, and it almost always resolves the moment the user checks the fiat equivalent.
Fee screens explained in one screen
Every on-chain fee screen you will encounter shows two numbers: a fee rate (in sats/vB) and a total fee (usually in sats or, on some wallets, BTC). The fee rate is what you set; the total fee is what the wallet calculates based on your transaction's size.
A typical May 2026 low-priority fee rate of 2 sats/vB on a ~200-vByte transaction produces a total fee of about 400 sats, or roughly $0.32 at a $80,000 BTC price. The rate you choose also affects how quickly confirmations on your transaction arrive. A higher-priority rate of 20 sats/vB on the same transaction is 4,000 sats (about $3.20). Wallet presets ("low / medium / high" or "next block / 30 min / 1 hour") choose the rate for you based on live mempool data.
Why do Bitcoin fees use sats/vB instead of dollars?
Bitcoin fees are priced in "satoshis per virtual byte" because block space, not dollar value, is the scarce resource the fee is paying for. Every transaction takes up a certain number of vBytes of block space, and miners prioritize transactions that pay the highest rate per vByte. Showing fees in dollars would hide the rate structure that determines how fast your transaction confirms.
A virtual byte (vB) is a weighted measure of transaction size introduced with the 2017 SegWit upgrade, a widely adopted soft fork in Bitcoin's history. It penalizes pre-SegWit data and discounts witness data, so one vB roughly corresponds to one "block-space unit" as miners see it (source: Bitcoin Wiki). Wallets, block explorers, and fee estimators all speak in sats/vB, so the unit is worth understanding even if the wallet picks the number for you.
Total fee versus fee rate: Why two sends at the same rate can cost different amounts
If you send 0.01 BTC twice at the same "medium" preset, the two transactions may charge different total fees. The reason is size. A simple single-input, single-output Bitcoin transaction might be 140 vBytes. A consolidating transaction that spends ten small UTXOs might be 1,000 vBytes or more. At 10 sats/vB, the first pays 1,400 sats and the second pays 10,000 sats. Same fee rate, seven times the total fee, because the second transaction is seven times larger.
This is also why fee screens display both numbers. The rate tells the network how urgent your transaction is; the total tells you how much you are actually paying. A reasonable sanity check before confirming any on-chain send is to verify both: "Am I paying ~2 sats/vB (low priority) or ~50 sats/vB (something is wrong)?" and "Is the total fee a reasonable fraction of the amount I am sending?"
When to leave fees on auto, and when to intervene
Most wallet auto-fee logic queries mempool data in real time and picks a rate that should confirm within the window you selected. For typical beginner use (buying, sending small amounts, receiving exchange withdrawals), auto-fees are almost always correct. When we monitor mempool.space during congestion spikes, auto-fee presets tend to track real mempool clearance rates within a few sats/vB of optimal, which is good enough for non-time-critical payments.
Manual override helps in two scenarios. During very empty mempools (1 sat/vB minimum), paying the preset "medium" rate can overshoot by 10x; dropping to minimum saves money with little risk. During congestion with a time-sensitive transaction (closing a leveraged position, meeting a withdrawal deadline), bumping the rate manually above the auto-fee estimate gets you into the next block faster. Outside those cases, auto is fine.
What about mBTC, µBTC, and other rarely used units?
Bitcoin supports several intermediate units between the full BTC and a single sat, but two (sats and BTC) dominate everyday usage. Milli-bitcoin (mBTC = 0.001 BTC = 100,000 sats) still appears in some older wallets. Micro-bitcoin (µBTC = 0.000001 BTC = 100 sats), sometimes called a "bit," was proposed as a standard but never gained traction (source: Bips). Centi-bitcoin (0.01 BTC) and deci-bitcoin (0.1 BTC) appear in technical documentation but almost never in user interfaces.
The community has effectively consolidated on two units: BTC for large balances and sats for small amounts. Treat mBTC, µBTC, and "bits" as legacy labels you may occasionally encounter but do not need to use.
BIP-176: the "bits" proposal and why it did not stick
BIP-176 was published in 2017 to propose "bits" as the standard informal unit, equal to 100 sats or 0.000001 BTC. The argument was that with BTC above $10,000, amounts under $10 had too many decimal places to read comfortably in BTC, and sats produced numbers in the tens of thousands that felt awkward for small purchases. "Bits" landed in the middle: a coffee priced at about $5 would be roughly 500 bits.
The proposal stalled because the wider community had already adopted "sats" in forum culture, Lightning invoice wording, and marketing language (the "stacking sats" meme predates BIP-176). Wallet teams chose sats for the sats/vB fee-rate convention, which locked the unit in for fee estimation. By 2020 "bits" were effectively dormant (source: Bitcoin Wiki).
When you might still see mBTC
A few older exchanges and desktop wallets (particularly pre-2020 builds) default to mBTC for account balances. If you import an older wallet or read an older guide, the numbers may look unfamiliar: "1.5 mBTC" is 150,000 sats or 0.0015 BTC. Switching to BTC or sats in the settings usually makes the number match what other modern wallets show.
Why "sats" won in practice
Sats are whole numbers. Most on-chain fees, most Lightning invoices, and most small everyday bitcoin amounts fit comfortably in the 1 to 1,000,000 sat range. Whole numbers read faster than eight-decimal BTC values and also read faster than three- or four-decimal mBTC values. The "stacking sats" phrase and the sats/vB fee convention anchored the unit in both culture and technical defaults. The result is that in 2026, any new Bitcoin app ships with a BTC/sats toggle as standard and a mBTC or bits option only as a legacy fallback, if at all.
How do Lightning invoices use millisatoshis, and what changes on-chain?
The Lightning Network uses an even smaller internal unit: the millisatoshi (msat), where 1 sat equals 1,000 msats. This enables sub-sat precision for routing fees and channel-balance accounting inside a Lightning payment. When a Lightning payment eventually settles on-chain (channel close), amounts are rounded down to the nearest whole sat because the base Bitcoin blockchain only records integer sat values (source: Lightning Labs).
For end users, msats almost never appear in the main balance view. They show up in routing-fee displays and in detailed invoice strings. A Lightning invoice for a 1,500-sat payment is typically written as "1500" in the amount field but encoded internally as "1500000 msat." If you see a four- or five-digit number ending in "msat" on a Lightning wallet, that number divided by 1,000 is the sat amount.
Why Lightning needs sub-sat precision
Lightning payments can hop through several channels on their way to the final recipient. Each hop charges a tiny routing fee, often much smaller than one sat. Without sub-sat precision, routing nodes would round fees up to one sat per hop, making small payments impractically expensive. A 10-sat payment routed through three hops at 100-msat fees each costs 10.3 sats to send, not 13 sats, because the routing fees are tracked in msats and only the final on-chain settlement rounds.
On-chain rounding when Lightning channels close
When a Lightning channel closes and its balance settles on-chain, any fractional-sat portion is rounded down to the nearest whole sat. If a node's final balance is 1,500.7 sats (or 1,500,700 msats), the on-chain output will be 1,500 sats. The 0.7-sat fraction is effectively donated to miner fees at channel close. This is a known design trade-off: Lightning favors payment precision during routing over perfect balance accuracy at close.
"Can I send half a sat?" answered once, cleanly
On-chain: no. The Bitcoin protocol does not accept non-integer sat amounts, and any wallet trying to send 0.5 sat would fail to construct a valid transaction. On Lightning: yes, as 500 msats. The Lightning payment flows through channels with sub-sat precision until it reaches the recipient, where the balance is credited in msats. If that recipient later closes their channel, the msat remainder rounds down at settlement.
What common unit mistakes do beginners make, and what do they cost?
The most expensive beginner mistake is misreading decimals and sending 10x or 100x the intended amount. The second is confusing BTC and sat amounts when typing into a wallet that defaults to one unit while the recipient expects the other. Both can be avoided by copy-pasting amounts, scanning QR codes, and verifying the fiat equivalent before confirming.
Unit-conversion errors are the least forgiving mistake in bitcoin because on-chain transactions cannot be reversed. Once the transaction confirms, the bitcoin is at the destination address regardless of what the sender intended. Exchanges sometimes help with internal transfers, but once a withdrawal leaves the platform, recovery depends on the goodwill of whoever controls the receiving key.
"Unit bias": the belief that sats are "cheaper"
Unit bias is the mistaken idea that 10,000 sats is "cheaper" than 0.0001 BTC because one number is smaller. Both amounts are identical in value. New users sometimes prefer the sat-denominated offer because a six-digit sat price feels smaller than a decimal BTC price. The psychological pull is well-documented and even has a marketing use (some exchanges deliberately quote in sats to make small purchases feel more accessible), but it is a display effect, not a price difference.
Checking the fiat equivalent is the cleanest defense. If 10,000 sats and 0.0001 BTC both show as roughly $8 at a May2026 price of $80,000 per BTC, they are the same amount. They will always be the same amount, because the 100-million-sat-per-BTC ratio is fixed.
The most common costly error: decimal misplacement
Sending 10x or 100x the intended amount happens when a user types an amount manually and misplaces the decimal point. "0.001 BTC" and "0.01 BTC" differ by 10x. At an $80,000 BTC price, that is a $80 error versus a $800 error on a single button press. The error is more common when the destination is not a regular recipient, when the sender is copying an amount from one app into another, or when the sending wallet displays BTC while the reference amount was quoted in sats.
The practical defense is to copy-paste or scan, never type, any amount that matters. If you must type, type the amount in whichever unit the wallet is currently set to, then verify the fiat equivalent against the amount you expected to send.
Sending on-chain to a Lightning invoice (or vice versa)
An on-chain Bitcoin address and a Lightning invoice are not interchangeable. On-chain addresses are derived from the recipient's public and private key pair; an address looks like "bc1q..." (bech32) or "1..." / "3..." (legacy). A Lightning invoice starts with "lnbc..." and includes the amount, a memo, and a payment hash in its string. Sending on-chain to a Lightning invoice, or scanning a Lightning QR into an on-chain-only wallet, fails at the address-validation step in most wallets. Older or permissive wallets can fail silently, locking the funds in a format the recipient cannot access. The pre-send checklist below catches this.
Pre-send checklist
Before confirming any bitcoin send, run through five quick checks:
Unit: is the amount on screen in BTC or sats? Does it match the invoice?
Network: is the recipient expecting on-chain BTC or Lightning? Does the address or invoice format match?
Amount in fiat: does the live fiat estimate match what you expected to pay?
Fee: is the fee rate reasonable for current mempool conditions?
Address or invoice: did you copy-paste or scan? Are the first and last four characters exactly the ones the recipient sent?
What are "dust" outputs, and why does sending one sat almost never work?
A dust output is a small on-chain UTXO model whose fee to spend exceeds its value. Bitcoin Core's default policy treats outputs below roughly 294 to 546 sats (depending on address type) as dust and refuses to relay transactions that create them. Attempting to send a single sat on-chain will usually fail at the wallet or node level before it ever reaches a miner (source: GitHub).
Dust exists because block space has a minimum economic floor. Every UTXO you own has to be spent again someday, and spending it costs fee-sats proportional to its size in vBytes. If the UTXO is smaller than the fee it would cost to spend, the economic value is negative and the UTXO becomes unspendable in practice. The dust limit encodes that reality as a policy rule.
The 294 / 546 numbers in context
For legacy P2PKH outputs (addresses starting with "1..."), the default dust limit is 546 sats: about three times the per-byte cost of the input that would spend the output, under a 1 sat/vB relay-fee assumption. For SegWit outputs (bech32 addresses starting with "bc1..."), the limit is lower (about 294 sats) because SegWit inputs are smaller in weighted vBytes. Taproot outputs have similar treatment.
These numbers are policy, not consensus: individual nodes and miners can adjust them, and some have argued for removing the filter entirely to let the market decide. For beginners, the effective rule is: do not try to send fewer than about 600 sats on-chain, and use Lightning instead for amounts under that threshold.
Dust attacks and privacy
"Dust attacks" describe a tracking technique where a third party sends a small unsolicited dust amount to many addresses, then watches the on-chain activity to cluster addresses that later spend that dust together. The defense is not to spend dust UTXOs. Most modern wallets let you freeze dust outputs so they are never selected for outgoing transactions, which preserves both fee efficiency and privacy.
What to do with small leftover sats
If you end up with a tiny on-chain balance (say 300 sats) that is below the dust limit or uneconomical to move, the practical options are to wait for a very low-fee window and consolidate it with a larger UTXO, accept that the balance is effectively stranded until fees drop further, or (for amounts that will otherwise be burned on closure) send it through Lightning if the wallet supports an on-chain-to-Lightning swap. The error to avoid is paying a high fee to move a small amount on-chain just to "clean up" the balance, which can cost more than the dust is worth.
FAQ
Is a satoshi a different cryptocurrency than bitcoin?
No. A satoshi is a unit of bitcoin, not a separate asset. Buying 10,000 sats is identical to buying 0.0001 BTC because 1 BTC equals exactly 100,000,000 sats. The sat is the unit Bitcoin Core uses internally; BTC is just the name for one hundred million sats. No wallet, exchange, or block explorer treats them as different things.
How many sats are in 1 BTC, and can that ratio ever change?
Exactly 100,000,000 sats per BTC. The ratio has been fixed since the network launched in January 2009 and is hard-coded into every Bitcoin Core release. Changing it would require a network-wide upgrade that no one has seriously proposed, because it would break every existing wallet, transaction record, and block explorer.
If bitcoin gets expensive, can I still buy a small amount?
Yes. Bitcoin is divisible to eight decimal places, so you can buy any amount from one sat (0.00000001 BTC) upward. At a May 2026 BTC price around $80,000, $10 buys roughly 12,500 sats. Most exchanges set minimum-order sizes in dollars rather than BTC, so the minimum is usually $1 to $10, not 1 BTC. For practical steps, see the guide on how to buy bitcoin safely.
Why is my wallet showing sats instead of BTC?
Because the display-unit setting is set to sats. Most wallets let you switch between BTC and sats in the settings menu, usually under "Display" or "Units." The actual balance does not change when you toggle; only the label and decimal placement do.
What does "sats/vB" mean on a fee screen?
Satoshis per virtual byte. It is the rate you pay for block space, not the total fee. A transaction of 250 vBytes at 10 sats/vB costs 2,500 sats in total. Fee estimators use live mempool data to suggest a sats/vB rate that should confirm within your chosen time window.
Can I send half a sat?
Not on the Bitcoin main chain. The protocol rounds all on-chain amounts to whole sats. On Lightning you can route payments with millisatoshi precision (500 msats = 0.5 sats), but when a Lightning channel closes and settles on-chain, the balance rounds down to the nearest whole sat. The sub-sat remainder is lost to the miner fee.
What is the difference between mBTC, µBTC, "bits," and sats?
They are all bitcoin subunits at different scales. One mBTC equals 100,000 sats. One µBTC (or "bit" per BIP-176) equals 100 sats. Sats are 1 × 10^-8 BTC and are the smallest on-chain unit. In 2026 the community has effectively consolidated on BTC and sats for display, with mBTC and bits appearing only in legacy wallets.
Why do two identical-looking sends cost different amounts in sats?
Because the fee depends on transaction size in vBytes, not on the BTC amount being sent. A simple one-input, one-output transaction is small; a transaction consolidating ten UTXOs into one is much larger. At the same sats/vB rate, the larger transaction charges more total sats. The amount of bitcoin being sent does not affect the fee directly.
Is "stacking sats" a different strategy from "buying bitcoin"?
No. "Stacking sats" is a community phrase for accumulating bitcoin in small increments over time, usually on a recurring schedule. The asset, the blockchain, and the cost basis are identical to buying bitcoin. The phrase exists because small regular purchases feel more natural when measured in whole sats (say 20,000 sats a week) than in eight-decimal BTC (0.0002 BTC a week). For the underlying cost-averaging approach, see dollar-cost averaging versus lump-sum buying.
Do I need to keep my wallet set to sats or BTC?
Pick whichever makes your typical amounts easier to read. Sats work well for balances under about 0.01 BTC, Lightning payments, and anything fee-related. BTC works well for larger balances, exchange trading, and tax records. Most wallets let you switch at any time; nothing in your balance changes when you do.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. All facts independently verified.
Disclaimer: This content is for educational purposes only and does not constitute financial, investment, legal, or tax advice. Crypto assets are highly volatile and carry significant risk of loss. Always verify local regulations and consult a qualified professional before making financial decisions.