Daily Candles Differ Across Platforms: Four Checks to Find the Cause

Two daily candles can differ because their time windows, markets, price references or completion states differ. Start with the symbol and exact period rather than candle color. Both charts can accurately summarize their own data even when one looks positive and the other negative.

Two daily candles can differ because their time windows, markets, price references or completion states differ. Start with the symbol and exact period rather than candle color. Both charts can accurately summarize their own data even when one looks positive and the other negative.

Match four settings before comparing candles
WindowActual opening and ending timestamps
MarketVenue, pair, product and price reference
StateStandard chart and completed period

A matching weekday label does not establish that two candles include the same trades.

BTKWIN.COM · EDUCATIONAL EXAMPLE

A continuous market still needs daily boundaries

A daily candle summarizes open, high, low and close within a defined window. Trading throughout the week does not remove the need to choose its beginning and end. A day starting at 00:00 UTC differs from a day starting at midnight in a fixed UTC+3 example.

In the latter case, local midnight corresponds to 21:00 UTC on the preceding date. The next local midnight corresponds to 21:00 UTC on the following boundary date. Preserve dates alongside hours when converting, because a change in timezone can change the written calendar date.

An illustrative sharp move at 22:00 UTC therefore falls into differently bounded windows. A Monday label beneath two charts cannot by itself prove identical coverage. Record actual opening and ending timestamps rather than inferring the window from the visible day name.

Check one: display timezone versus candle construction

Changing labels on a chart’s time axis does not necessarily rebuild the underlying bars. The TradingView time documentation distinguishes exchange time from the chart’s display preference and its relationship to Pine calculations. Inspect bar timestamps and OHLC values rather than assuming every clock setting changes the aggregation.

Other interfaces can offer an aggregation control. The Binance spot market-data reference documents a kline timeZone parameter affecting intervals while request startTime and endTime remain UTC-based. That is a particular API behavior, not a universal meaning for similarly named settings.

For a controlled comparison, change only the relevant setting and examine one window. If clock labels change while OHLC stays identical, that supports a display-only change in that test. If values change, also verify source and pair before attributing the entire difference to timezone.

Check two: match pair, venue and reference price

BTC/USD and BTC/USDT can have similar-looking prices without being the same traded series. A spot market differs from a perpetual contract, and last-trade candles differ from mark-price or index candles. Copy the full symbol and source from both chart headers.

A high trade on one venue need not occur on another. Local bids, asks and executions can create different lows and highs even when time boundaries agree. If the windows align but values differ, inspect the actual market rather than keeping timezone as the only possible explanation.

A composite index can draw from several venues under its own methodology. It should not automatically match the extreme of a particular local trade. Identify whether the chart shows a directly traded market or a reference series. The bitcoin market page offers context, but the full market symbol remains essential for a candle comparison.

Check three: completion and the percentage reference

A current candle changes while its window remains open. Its displayed close is provisional, and later trades can expand the high or low. Comparing it with another source’s final completed candle mixes states. Save capture time and completion status and verify that both feeds are current.

A daily price card can also use a rolling twenty-four-hour reference while the candle body compares the current daily open and close. With hypothetical current price 105, daily open 100 and price twenty-four hours ago 110, candle change is +5%, while rolling change is approximately −4.55%.

Those results are compatible because their starting points differ. Read the percentage definition before using candle color to verify it. Custom coloring can use other comparisons too, so the actual open and close values provide stronger evidence than the chosen colors.

Check four: chart transformation and data quality

One chart can use standard candles and another a calculated style such as Heikin Ashi. Their displayed values should not be assumed to represent the same raw trade summary. Match chart type before comparing bodies and shadows or using values as execution evidence.

Check gaps, duplicate rows and stale updates in any exported data. A missing interval does not prove no trades occurred; a download can be incomplete or limited by record count. Review pagination and history limits before filling gaps. Inserting a constant price without disclosure creates synthetic bars and can change subsequent indicator calculations.

Rebuild an educational candle from smaller periods

Assume a simplified complete window consists of three chronological subperiods. Their hypothetical OHLC values are below. The combined open is the first open, the combined high is the maximum high, the combined low is the minimum low and the combined close is the final close.

SubperiodOpenHighLowClose
First10010499103
Second103110102108
Third1081099598
Combined window1001109598

Do not add opening prices or average highs to construct the larger candle. If compatible nonduplicated volumes accompany the subperiods, their volumes can be summed. OHLC and volume require different aggregation operations.

If another daily window starts at the second subperiod, this table does not contain its complete ending coverage. Removing the first segment is not sufficient; later segments must be added to preserve the intended duration. Compare complete shifted windows rather than a shortened sample against a full day.

Handle historical timezone changes and timestamp units

A geographic timezone can have seasonal offset changes, while a fixed offset such as UTC+3 stays fixed by definition. When reconstructing historical local days, use the rules applicable to the date. Today’s offset should not silently be applied to every historical year.

Six consecutive four-hour bars produce twenty-four hours only when they cover the required boundaries without gaps or duplication. Starting at another hour can produce a full-length rolling window that still differs from the venue’s daily candle.

Finally, record whether exported timestamps use seconds, milliseconds or another unit. Misreading that scale can create implausible dates. Keep symbol, venue, reference, chart type, timeframe, boundaries and completion status together. If a discrepancy remains, report the separate OHLC differences and inspect the underlying records instead of building a trading claim on settings that were never aligned.

Continue reading

English content and examples reviewed: 27 October 2026. Read the Arabic edition.

تامر طعمه
تامر طعمه
Articles: 484