Bitcoin USD vs USDT prices: how to compare crypto quotes
A worked conversion shows why a Bitcoin quote in USDT can differ from a dollar quote—and how timestamps, price fields and liquidity change the comparison.
Published
Quick answer
Why BTC/USD and BTC/USDT can differ
USD is the U.S. dollar. USDT is Tether's dollar-referencing token, but a secondary-market trade can price one USDT above or below $1. To compare spot BTC quotes, multiply BTC/USDT by the observed USDT/USD rate, then compare that result with BTC/USD from a similar time and price definition.
BTC/USDT × USDT/USD = BTC price expressed in USD
Issuer redemption and exchange trading are different processes. See Federal Reserve research on stablecoin markets.

Conceptual illustration of currency conversion; no live market data is shown. · CoinAbout illustration

Conceptual illustration of currency conversion; no live market data is shown. · CoinAbout illustration
A bitcoin quote of 60,000 USDT becomes $59,880 when each USDT is valued at $0.998. That is a $120 difference before fees. These are hypothetical inputs, not current prices. The calculation explains why a BTC/USDT number cannot automatically be compared with a BTC/USD number as if both were dollars.
The useful question is not which screen displays the bigger price. It is whether the two screens describe the same asset, quote currency, moment and kind of price. Once those conditions match, the comparison becomes meaningful. Until then, an apparent premium may be a currency conversion, an older observation or a difference between a trade and an available order.
The worked conversion
Start with one hypothetical unit of bitcoin priced at 60,000 USDT. Now add a separate hypothetical observation of $0.998 for one USDT. Multiplying the two gives a dollar reference: 60,000 USDT per BTC × $0.998 per USDT = $59,880 per BTC. The USDT units cancel, leaving dollars per bitcoin.
If a direct BTC/USD quote were $60,000 at the same moment, the converted reference would be $120 lower. Using that direct dollar quote as the denominator, the difference is $120 ÷ $60,000 = 0.002, or 0.20%. Reversing the denominator would produce a slightly different percentage, so a useful comparison states its base rather than presenting an unexplained percentage gap.
The calculation has three separate inputs: the BTC/USDT quote, the USDT/USD conversion and the direct BTC/USD comparison. None is a substitute for the others. This example assumes the same observation time and comparable price definitions. It excludes commissions, available order size, slippage, withdrawal costs and transfer delays. It is a reference conversion, not a claim that someone could complete a profitable trade.
A second example shows how the currency leg can change the conclusion. Keep bitcoin at the same hypothetical 60,000 USDT, but value USDT at $1.002. The converted figure becomes $60,120. A stable-looking bitcoin quote has produced a different dollar reference because the conversion rate changed. The example does not describe an actual USDT discount or premium on any exchange.
Read the pair before the number
In a pair written BTC/USDT, BTC is the base asset and USDT is the quote asset. A price of 60,000 means 60,000 units of the quote asset for one unit of the base asset. For BTC/USD, the quote unit is the U.S. dollar. Treating the labels as interchangeable silently inserts a one-dollar conversion assumption into the calculation.
Binance's market-data documentation distinguishes a symbol price ticker, an order-book ticker, recent trades and time-bucketed candles. Its average-price response also identifies an averaging interval and the last trade time. Those separate definitions are a reminder to identify the field before comparing the number.
For a reader comparing two tabs, a short written label is often enough: “BTC/USDT last trade, venue A” and “BTC/USD best ask, venue B.” Writing those labels reveals that the comparison mixes both currency and price type. The next step is to align the definitions, rather than explain the difference with a story about investor sentiment.
A last trade is not an offer
Coinbase's product ticker reference describes a snapshot containing the last trade, best bid and ask, and 24-hour volume. It also exposes a time field. A response therefore contains several useful values; choosing one as the headline price is a measurement decision.
Imagine an illustrative market where the last completed trade was $59,900, the best bid is now $59,850 and the best ask is $59,950. A buyer cannot infer from the last trade alone that an order can be filled at $59,900. Equally, a seller should not treat the ask as an available selling price. These invented numbers illustrate the distinction; they are not an observation of an actual exchange book.
Size matters as well. If a displayed ask covers only a small quantity, a larger order can reach other price levels. A useful reference price can still be a poor estimate of the total cost of an order. That is why a comparison of headline quotes should not be promoted into an execution claim without evidence about quantity and the available book.
Coinbase's order-book documentation distinguishes the best bid and ask from deeper aggregated and non-aggregated levels. It also identifies auction-mode quotes as indicative. The practical lesson is to check what the response represents before treating a visible price as a firm opportunity.
Use the older of the two currency observations
Suppose the BTC/USDT observation is marked 12:00:05 UTC and the USDT/USD observation is marked 11:59:35 UTC on the same illustrative day. A page loading at 12:00:06 does not make both observations one second old. The conversion includes a currency observation that is 31 seconds old at page load.
The two legs can still be multiplied, but the result should carry that limitation. Giving the converted price the newer timestamp would hide the older input. For a reference comparison, retaining the older contributing observation time is a conservative way to make the dependency visible. It does not turn the two trades into a synchronized market snapshot.
There are also two different clocks to record: when the provider says the observation occurred and when the application received it. A fast fetch can return an old observation. A slower connection can deliver a recent observation late. Readers need the observation clock to assess market age and the receipt clock to understand delivery; replacing one with the other loses information.
A daily close answers another question
A daily candle close is useful for comparing completed periods. It answers a different question from a current last trade or an order-book quote. Mixing those fields can create an apparent price difference even when both data series are correctly labeled and working as designed.
Coinbase's candle reference defines bucket start time and the period's open, high, low, close and volume. It warns that historical data can be incomplete and that intervals without ticks have no published data. A gap in that response should not automatically become a zero price or a claim that the asset lost all its value.
Consider a hypothetical chart with a completed close of $60,000 and a later reference quote of $60,300. The difference is $300, or 0.50% relative to the completed close. That arithmetic does not establish when the move occurred within the intervening period. It also does not establish a cause. A headline explaining the change would need separate evidence about the event and the timing.
A comparison you can inspect
Before comparing quotes, write down the base asset and its identity, the quote currency, the venue or provider, the price field and the observation time. For a conversion, add the currency pair and timestamp of every additional leg. If any element is unavailable, describe the comparison as limited rather than supplying an assumed value.
Then calculate the converted reference and show the denominator for any percentage. Keep the original values alongside the result so rounding can be checked. Rounding $59,880 to $59.9 thousand may be fine for a compact display, but it hides information needed to recompute a $120 difference. Use the unrounded inputs for the calculation and round the presentation afterward.
Finally, ask what would change the conclusion. In the worked example, a different USDT/USD rate changes the converted dollar value. A different observation time weakens the comparison. A different price field changes what is being measured. Fees and available size can change an execution estimate. None of those uncertainties is resolved simply by collecting more screenshots of the same headline price.
CoinAbout's Bitcoin page is a useful place to start inspecting an asset, but a displayed reference should always be read with its source and freshness context. For a broader comparison, the market workspace provides asset navigation; the arithmetic still depends on the actual fields being compared.
This guide explains a measurement method, not a trading strategy. Crypto assets and stablecoins carry market, liquidity, custody and operational risks. A correct conversion cannot guarantee that a price will remain available, that transfers will complete on time or that a trade will be profitable.
Try the conversion
Compare BTC quotes in the same currency
These starting numbers are hypothetical, not live market data. Replace them with prices observed at comparable times and for the same spot instrument.
BTC/USDT × USDT/USD = $59,880.00 per BTC
−$120.00 (−0.20%) versus the direct BTC/USD reference
A difference after conversion does not prove an executable trade. Venue, quote definition, observation times, available size and fees can still differ.
Before comparing two displayed prices
- Confirm both quotes describe spot Bitcoin, not an index or derivative.
- Read each quote currency and price field, such as last trade, bid, or ask.
- Record the source venue and observation time for BTC/USDT, USDT/USD, and BTC/USD.
- Convert with the correctly oriented USDT/USD rate, then state the direct BTC/USD denominator for the percentage difference.
- Consider available quantity and costs before treating a gap as executable.
Send a correction or source question about this article.