reference · Technical analysis
Ichimoku Cloud: Midpoints and Time Alignment
Ichimoku combines several range-midpoint lines with forward and backward plot offsets. A line drawn to the right of today is calculated from information available today, not from a future price observation.
Separate calculation time from display time
A common configuration uses conversion and base lines formed from the midpoint of the highest high and lowest low over nine and 26 observations. Leading span A averages those two lines; leading span B uses the midpoint of a longer, often 52-observation range. The leading spans are plotted forward, while a lagging span plots a close backward. TradingView explains these components and settings.
These are range midpoints, not averages of every closing price in the window. A single high or low can influence the line until it leaves the lookback. The conventional 9, 26 and 52 settings are parameters rather than universal statements about market cycles.
A hypothetical completed-bar example
Suppose the nine-observation high and low are 110 and 100. Conversion line is 105. The 26-observation high and low are 112 and 96, making the base line 104. Leading span A calculated now is (105 + 104) / 2 = 104.50.
If the 52-observation range extends from 90 to 114, leading span B is 102. The area between 104.50 and 102 is the cloud calculated at this observation and drawn at the configured forward offset. Its position on a later chart coordinate does not mean a future market has traded at those levels.
Assume the current close is 108. A lagging-span display may plot that close 26 observations earlier. At the earlier date, 108 was not yet known. Reading the back-plotted value as a signal available on that earlier date would introduce future information into a test.
Match arrays by timestamp
A software implementation should distinguish the raw calculated span from the shifted series used for display. Comparing current price with a cloud visible at the current coordinate usually involves spans calculated earlier. Comparing it with a newly calculated, forward-displaced cloud answers a different question.
Specify whether offsets count bars or calendar time, especially when sessions omit periods. Also identify whether an unfinished higher-timeframe bar contributes to a lower-timeframe display. A historical chart can conceal the intermediate values that changed before confirmation.
Do not count correlated lines as independent proof
The lines derive from overlapping price history. Several bullish-looking relationships can therefore share the same underlying observations. A cloud crossing does not supply a calibrated probability, account-specific risk allowance or an executable fill. Thin clouds, thick clouds and color changes need objective definitions if they are used as conditions.
Before studying performance, export the component values and label both calculation and display timestamps. Read the look-ahead reference, compare ordinary average-crossing rules, and use a reproducible test. Correct time alignment is a prerequisite for interpreting results; an attractive historical cloud is not a substitute.
Questions and answers
Does the forward cloud forecast future prices?
No. It displays values calculated from existing observations at a forward offset. Forecasting performance would need separate empirical evidence.
Are the conversion and base lines moving averages?
They are typically rolling high-low midpoints. That differs from averaging all closes within the same lookback.
Sources and further checks
Use the current source for your exact instrument, account and platform. Referencing a general specification does not establish support for every TradeCopier workflow.
- TradingView: Ichimoku Cloud · Checked September 19, 2026
Found an error? Send a correction with this page's address and a primary source. See our editorial standards for how we handle examples, claims and revisions.
