Bitcoin Renko screenshots: why brick size matters
The same Bitcoin price observations can draw a reversal at one brick size and no new brick at another. Record the construction settings before interpreting the image.
A Bitcoin Renko screenshot needs its brick size and construction settings to be interpretable. Changing the size can turn the same price observations into a visible reversal, several continuation bricks or no new brick. A brick also does not represent a fixed number of minutes. Record those settings before treating its shape as evidence about price or elapsed time.
For an AI review, prepare an ordinary candlestick view with readable price references, then create a free ChartPilot account. This guide does not establish that ChartPilot supports Renko input or can reconstruct ordinary candles from bricks. Access checked November 3, 2026: New accounts receive 3 completed chart analyses in total, without expiry. The allowance is for the account's lifetime, not a daily or monthly reset. No card is required, and there is no automatic subscription or charge. Existing accounts retain their recorded access and billing under the current terms.
Record how the bricks were made
TradingView's Renko documentation distinguishes Traditional sizing, which uses a fixed amount, from ATR sizing, which derives a size from Average True Range, and Percentage (LTP) sizing. A label saying only “Renko” leaves the calculation unspecified.
Keep a settings note beside the saved image:
- Exact market: Bitcoin pair, venue and product type. Use the Bitcoin screenshot guide if those labels are unclear.
- Sizing method and parameter: for example, Traditional with a 100-unit box. Record the quote unit; 100 USD is not a percentage setting.
- Input source and interval: Close or OHLC, plus the chart's selected resolution.
- Capture context: the observation time, visible period and whether the rightmost bricks are projections.
These are comparison controls, not recommendations for an optimal Bitcoin brick size. If two images use different settings, their disagreement may be about construction rather than a different market observation.
One fictional sequence, two different pictures
This is an invented arithmetic example, not current Bitcoin data, a trading signal or a ChartPilot result. Suppose one fictional BTC/USD feed supplies completed 15-minute closes. Compare Traditional Renko views using the Close input, with fixed sizes of 100 USD and 250 USD. Both begin with an upward brick ending at 60,000: the smaller brick starts at 59,900, and the larger at 59,750.
The reversal rule matters. TradingView explains that continuation needs one box of movement, whereas reversal needs two boxes from the last brick's closing edge. The first opposite brick starts at the prior brick's opening edge, rather than overlapping it.
| Completed close | 100 USD bricks | 250 USD bricks |
|---|---|---|
| 10:00: 60,000 | Initial up brick ends at 60,000 | Initial up brick ends at 60,000 |
| 10:15: 60,200 | Two new up bricks; last ends at 60,200 | No new brick; last still ends at 60,000 |
| 10:30: 59,800 | Three new down bricks; last ends at 59,800 | No new brick; last still ends at 60,000 |
For the 100-unit view, the first move adds bricks ending at 60,100 and 60,200. From there, the reversal threshold is 60,200 − 2 × 100 = 60,000. The first down brick runs from 60,100 to 60,000; the next two end at 59,900 and 59,800.
For the 250-unit view, the next up threshold is 60,250 and the first down threshold is 59,500. Neither later close reaches either threshold, so neither produces a new brick. “No new brick” does not mean the market stayed still: the supplied closes changed by hundreds of dollars.
The smaller view therefore shows a turn while the larger remains at its prior brick. Neither result demonstrates which setting forecasts better. The exercise shows why a brick count or color sequence needs its settings attached.
Five bricks do not mean five intervals
In that example, five new bricks appear across two 15-minute input intervals. Multiplying five by 15 would invent 75 minutes where the supplied clock records 30. Several bricks can result from one sampled close, and another interval can contribute none.
TradingView uses the selected resolution's Close or OHLC data to construct Renko. Its calculation notes explain that historical precision depends on the available input data. A “15-minute” label identifies that input resolution; it is not a duration stamped onto every brick.
Nor do our three supplied closes reveal every intervening tick. The sequence of calculated bricks cannot fill that gap. To investigate when an event happened, return to the underlying time-based chart and inspect the relevant observations rather than reading the Renko columns as equal time steps.
A saved view and a reloaded view may differ
TradingView's calculation notes distinguish real-time projection bricks from bricks confirmed when the input interval closes. The projected right edge can change before that close. The same documentation explains that deeper history may use higher-timeframe data, with a moving boundary that can cause recalculation.
Keep the original capture and its settings if a later view looks different. Compare the same period and input resolution before interpreting that difference as a new market event. A screenshot records what was displayed when captured; a later reconstruction is not automatically a faithful replay of every intermediate display.
If wicks are part of the comparison, check their source too. TradingView's wick reference distinguishes extrema of sampled closes from highs and lows when OHLC is selected. Hiding wicks does not establish that no price excursion occurred.
Prepare the Bitcoin image you can actually check
Keep the Renko image as a labeled reference, then switch the same Bitcoin instrument to ordinary candles. Locate the period behind your question using timestamps, not an equal number of chart columns. Retain readable prices and enough surrounding structure to check the explanation. The TradingView upload walkthrough covers saving and choosing that file.
For a readable supported chart, ChartPilot supplies a BUY or SELL outlook, reference levels and confidence in the visible evidence. Compare the explanation with the ordinary-candle screenshot you actually uploaded. Do not assume that an unprovided Renko settings note or a second image influenced the result.
A brick edge is also not a promised execution price. TradingView warns against treating synthetic Renko prices as realistic order fills. ChartPilot does not execute trades or supply a live quote feed, and its assessment can be wrong.
Create a free ChartPilot account once the ordinary chart and your question are ready. Keep one distinction in the review note: brick size controls what the Renko construction displays; it does not turn that display into a complete timeline or a prediction.