Renko Charts: Bricks and Synthetic Price Paths

Specify the construction before reading the shape

A Renko setup needs a brick-size rule, a starting reference, a price source and a reversal convention. Some implementations use fixed price increments; others derive size from ATR. TradingView explains its Renko construction and source-resolution choices. Bricks can summarize movement without preserving every transaction or elapsed interval.

A long row of similarly sized bricks does not imply a steady sequence of equally timed opportunities. Several bricks can appear during one rapid movement, while a quiet interval produces none. Indicators applied to a brick chart therefore measure brick observations, not automatically minutes or days.

An original fixed-size illustration

Assume a fixed brick size of 2, a last completed upward brick closing at 100, and a simple convention requiring two brick sizes to reverse. A move to 102 completes another upward brick; a move to 104 completes one more. A small move back to 103 creates no completed downward reversal under this stated rule.

A move from that 104 close down to 100 can meet the two-brick reversal requirement, creating the next downward brick according to the implementation's placement rule. Other Renko variants handle reversals differently. This example should not be used to infer the output of a vendor whose rules have not been checked.

Suppose a time bar has open 100, high 106, low 98 and close 104. It could have visited the high before the low or the low before the high. Those paths may produce different brick sequences. OHLC alone cannot establish the exact intrabar order of events.

Synthetic prices are not guaranteed fills

A completed brick can display convenient open and close coordinates that were not available as executable quotes at the time a strategy recognized the brick. TradingView warns about execution assumptions on non-standard chart data. Treating every synthetic open as a fill can create unrealistic backtest results.

ATR-based sizing adds another dependency. The brick size depends on the volatility calculation and its evaluation time. Changes in data resolution, available history or platform reconstruction can affect the displayed past. Record those settings and retain decision-time output when comparing live and historical behavior.

Use the chart for the task it actually supports

Renko can help describe filtered price movement, but an execution test should use an independently timestamped market-price stream and a specified rule for when a brick becomes known. Include spread, costs and a realistic next executable observation. Do not assume one displayed brick equals one fill opportunity.

Compare Heikin-Ashi's different synthetic transformation and ordinary OHLC information limits. The backtesting guide explains how to separate a signal representation from execution data. That separation preserves the chart's descriptive value without converting a clean visual pattern into fabricated performance.