Renko creates bricks after a specified price threshold, rather than one rectangle for every equal interval of time. It discards some source information, and a brick edge is not automatically an executable price. First reproduce its construction; then test a separately defined trading rule.

What a Renko chart is and where it came from

The name derives from Japanese “renga”, brick. A complete specification needs size and units, source prices/resolution, initial grid and direction, reversal threshold, equality handling and updates. Fixed, ATR and percentage implementations differ; the same “Renko 10” label does not reproduce them.

Check the named implementation rather than infer its rules from an origin story. Sierra Chart documents standard and flexible intraday Renko, with met/exceeded and extra-tick reversal variants. Their boundary conditions must not be substituted for each other.

How brick size and the reversal rule work

In our declared fixed-size model, continuation requires at least B from the last completed edge and reversal at least 2B against direction; equality qualifies. The first reversal body spans B although its Close is 2B from the preceding Close. A single source Close can create further full bricks at once; that does not create separate earlier fill opportunities.

Retain the separate hypothetical EUR/USD seed with the last up brick ending 1.0950, B=0.0010=10 pips. A source Close 1.0938 is 12 pips lower and creates no reversal. At 1.0930, equality completes the first down body 1.0940→1.0930 under our chosen model. Another mode may require an additional tick; a confirmed chart-direction change is not proof the market continues down.

For an adaptive implementation, record how and when its threshold is measured and rounded, and whether it rebuilds old bricks. StockCharts describes ATR size taken at chart creation, which can alter earlier history on update; that differs from an algorithm freezing each historically available threshold. Neither choice establishes a cleaner profitable trend or one optimal pip size for a pair.

Illustrative example — EUR/USD, 10-pip brick (values for illustration only)
Starting pointa run of five light up bricks, the last one ending at 1.0950
Shallow pullbackprice slips 12 pips to 1.0938 — that is less than two bricks, so the chart stays silent
Reversal thresholdour inclusive model needs a 20-pip drop, at or below 1.0930
Reversal signalat 1.0930 the model draws 1.0940→1.0930; it records a grid reversal, not a market forecast

Same brick size, shifted grid origin

Two charts with brick size10 can complete a brick at different closes. They also need a defined grid origin.

Anchors100 and105 in a Renko modelOur algorithm uses size10, anchors100 or105, then Close108 and112. Anchor100 completes a100–110 brick; anchor105 has not reached115. The112 line marks the last supplied Close.BRICK SIZE DOES NOT DEFINE THE GRID100105110115Anchor100Anchor105Close data:first108,then112.Grid100:brick to110 completed.Grid105:3 units short of115.

Our Close-only algorithm is not attributed to a platform. B=10; origin100 or105 is known before108,112. Initial direction is upward; continuation requires the last edge+B and reversal a2B retreat. No reversal occurs here. A brick level is not an executable quote. StockCharts ChartSchool Renko Charts documents fixed brick size and Close versus High–Low inputs. Grid origins and the algorithm here belong to our model.

The solid rectangle is a completed brick; the outline is an unreached threshold. Both anchors were declared before the closes.

Close108 completes neither grid’s first brick. At112, grid100 has crossed110 and completed one brick; grid105 still awaits115. Matching B alone cannot align two results. Retain the anchor, Close source, reversal rule and prior-brick state. Define the grid before observing data, rather than fitting it to a later drawing.

How to read and use this chart step by step

Step 1 — set the chart and the right timeframe

TradingView offers Renko settings, while MT5’s standard chart modes are bars, candles and lines; any extra Renko implementation needs its own specification. Neither a default ten-pip brick nor D1/W1 source data is a universal recommended starting setting. The technical analysis foundations help compare the processed chart with its source.

TradingView uses source-resolution Close or OHLC and can use coarser bars for deeper history. Its moving resolution boundary can recalculate older bricks. For our own B=1 model, seed 99→100 upward and successive closed observations 104,98,102 give 4 up, 5 down, 3 up bricks: 12 total, ending 101→102. Using only final 102 instead gives 2 up bricks with the same final edge. End-level agreement does not establish signal-history agreement.

Step 2 — read direction from colour and sequence

Direction describes the processed sequence, not a trade recommendation. A long run and a later opposite brick are outputs of the saved input and construction rules; test any order/exits separately.

Step 3 — wait for a confirmed colour change

In TradingView, live projection bricks may change until the source interval closes and are not all preserved after reload. Historical reconstruction is a separate issue. A fixed-size own close-only algorithm must also wait for its chosen completed source observation; reaching a price threshold alone does not establish that every platform’s last brick is final.

Entry, stop and targets — an illustrative example

Our other hypothetical EUR/USD model has B=0.0010 and seed 1.1000→1.1010 upward, using only minute Bid closes 1.1018,1.1026,1.1004,1.0994,1.0987. It produces no new brick at t1, an up 1.1010→1.1020 at t2, none at t3, a reversal 1.1010→1.1000 at t4, then down 1.1000→1.0990 at t5. At t4 the supplied Bid is 1.0994, not the synthetic edge 1.1000; no sale at that edge follows from the chart.

Assume a later short fill of 10,000 EUR at Bid 1.0992 with Ask 1.0994, then cover at Ask 1.0982. In a USD account with hypothetical USD 2 commission and no other fees, gross is USD 10 and net USD 8. Substituting the brick edge 1.1000 as entry falsely gives gross USD 18 / net USD 16, an 8-pip / USD 8 overstatement. These are execution assumptions, not observed profits. Stop, target and quantity remain separate rules; an opposite brick is not automatically a submitted trailing stop.

Signal and execution must remain separate. Use actual Bid for a Forex short entry and Ask to cover, adding commission, financing and conversion where applicable. Spread is already represented in those fills. Ordinary stop execution can differ from its trigger; a chart colour does not establish a maximum loss.

Equal horizontal brick spacing does not mean equal elapsed time. Some products retain source timestamps, volume or true High/Low, so blanket “no time or volume” claims are too broad. Preserve source data and per-update algorithm state; do not price monetary risk from synthetic distances alone.

Strengths and weaknesses you need to know

Renko changes which movements are displayed. That is a data transformation, not evidence of calmer decisions or less random trading. Save all changing, rejected and completed observations to see what the chosen variant omits.

Keep projections, history rebuilds and execution errors separate when checking a test. The same final chart can omit earlier provisional signals. A conventional price chart can supply source context, but it cannot make synthetic fills valid or establish that the resulting strategy is suitable.

How it compares with Kagi, Three Line Break and Heikin-Ashi

Three Line Break uses previous-line extremes; early history before three lines needs separate handling. Kagi changes direction and thickness under specified price thresholds, not observed supply/demand strength. Heikin-Ashi transforms O/H/L/C with a recursive prior-body rule while retaining source intervals. Brick size alone does not define Renko, and no most-tunable or gentlest ranking follows.

What to do tomorrow to get comfortable with Renko

  1. Save the full construction settings and compare processed output with source prices. Verify units, grid origin and equality thresholds before interpreting colour.
  2. Check whether the selected adaptive mode changes earlier history. A threshold updated at chart creation is different from historically frozen thresholds; compare them as separate algorithms.
  3. Record every direction change and rejected trade under predeclared rules, including costs. Colour changes alone do not measure strategy losses.
  4. Keep source observations, brick state, signal-availability time and actual entry/exit prices. Evaluate separate data; demo practice or a smooth historical chart does not establish live readiness.
  5. Test signals from Renko against available market quotes. Do not fill at each intermediate grid edge when multiple bricks were created by one input record.