TradingView drawing workflow

Fibonacci channels on TradingView: parallel levels and anchors

A Fibonacci channel places ratio levels on lines parallel to a chosen trendline. On TradingView, the first two anchors set the slope and the third sets the base channel width. Unlike horizontal Fibonacci retracement levels, a sloping channel has a different price at each bar. Freeze the anchors before testing later touches or breaks; a ratio alone does not confirm a trade.

See the decision guide

Draw the channel from confirmed swings

For an uptrend, choose a low A, a later higher low B, and the intervening high C. Click A and B first to define the rising baseline, then C to set its parallel width. For a downtrend, use a high A, a later lower high B, and the intervening low C. The third click can therefore be earlier in time than the second click.

  • Select Fib Channel from the drawing toolbar. Open Coordinates to enter or check the three bar and price positions. Use ordinary candles and a linear price scale for the worked example below.
  • In Style, display the levels you intend to use and extend the lines to the right if evaluating later bars. Record which line is 0 and which is 1 before interpreting 0.618.
  • Choose wick extremes or closing-price swings consistently. Do not switch between them only where the alternate choice improves the historical fit.
  • A trendline from selected anchors is not a regression fit. Fibonacci spacing supplies neither a statistical confidence interval nor a probability of reversal.

Calculate the parallel levels at a specific bar

This hypothetical linear-coordinate model assigns the A-to-B baseline to ratio 0 and the parallel through C to ratio 1. Let x be chart bar index and y be price. The slope is m = (yB - yA) / (xB - xA), baseline L(x) = yA + m × (x - xA), signed width W = yC - L(xC), and ratio line F(r, x) = L(x) + r × W. These equations define the example; verify your drawing's labels and coordinates against them.

  • All lines rise by 0.5 per bar. Their separation stays constant: the 0.618 line is always 9.27 price units above this baseline.
  • Width here is the signed vertical price gap at the same bar, not the difference between C and A, the distance between C and B, or a pixel measurement.
  • For W < 0, increasing r moves downward. The physical lower base boundary is min(F(0, x), F(1, x)); the upper is max(F(0, x), F(1, x)). Do not assume the 1 line is always on top.
  • A ratio above 1 projects beyond the C parallel, while a negative ratio projects across the baseline in the opposite direction. Neither creates an automatic target or stop.
Input or calculationHypothetical value
Anchors, in click orderA = (10, 100); B = (30, 110); C = (20, 120)
Slope m(110 - 100) / (30 - 10) = 0.5 price units per bar
Baseline at C and signed widthL(20) = 105; W = 120 - 105 = 15
Baseline at bar 40L(40) = 100 + 0.5 × 30 = 115
0.382 and 0.618 at bar 40115 + 0.382 × 15 = 120.73; 115 + 0.618 × 15 = 124.27
1 and 1.618 at bar 40130; 139.27
0.618 at bar 42116 + 0.618 × 15 = 125.27

Compare channel ratios with horizontal retracement

Horizontal Fibonacci retracement divides the price span between two extremes. For a hypothetical move from 100 to 120, a retracement of 61.8% measured down from the high is 120 - 0.618 × (120 - 100) = 107.64. That price stays fixed while the two anchors stay fixed. Check the drawing orientation: measuring 0.618 upward from 100 instead gives 112.36.

  • The ratio is the same number, but its reference distance and direction differ. A channel touch does not establish that price retraced 61.8% of the preceding move.
  • If the baseline slope is zero, the channel lines are horizontal. Even then, their values match a retracement only when the endpoints, width and orientation also match.
QuestionHorizontal retracementChannel in this example
What is the reference distance?20 price units between low and high15-unit parallel width
What does 0.618 mean here?61.8% of the advance retraced from 12061.8% of width above the rising baseline
Price at bar 40107.64124.27
Price at bar 42107.64125.27

Freeze the anchors when they become knowable

For a reproducible selection rule, call a low confirmed only when it is strictly below the lows of two bars on each side; use the symmetric rule for a high. Reject ties and missing bars. In the example, B at bar 30 becomes confirmed only after bar 32 closes, assuming bars 31 and 32 both have lows above 110 and the left-side test also passes. A and C must already satisfy their own tests.

  • Save the A/B/C coordinates and mark bar 32 as the channel activation close. Begin this example's prospective observations at bar 33. A drawing extending back through A does not mean the completed channel was available at A.
  • If bar 32 instead has a low of 109, B fails this rule and the proposed channel never activates. Do not retain it as a successful historical setup.
  • Keep the active anchors fixed even after a miss. If a later swing motivates a replacement, save a new channel version and its activation time; retain the old version's outcome.
  • This two-bar rule is an explicit research choice, not the definition of every pivot indicator. A discretionary selection also needs a timestamp and a reason recorded before the result.

Confirm a break against the moving boundary

Use the frozen 0-to-1 base channel and choose a 0.5-price-unit buffer for this example. An upper break requires a completed close strictly above the upper boundary plus 0.5; a lower break requires a close strictly below the lower boundary minus 0.5. At bar 40, the boundaries are 115 and 130, so the thresholds are 114.5 and 130.5. This is an observation rule, not a proven trading system.

  • If requiring two successive closes, recalculate the second threshold. At bar 41, the upper boundary is 130.5 and its buffered threshold is 131.0. Closes of 130.6 at bar 40 and 130.8 at bar 41 do not satisfy that two-close rule.
  • Decide in advance whether the first qualifying break retires the channel, whether re-entry is tracked, and which boundary matters. Crossing an internal 0.618 line is not exiting the base channel.
  • A later close back inside is a failed continuation observation to retain. A gap beyond a boundary can also occur without an executable fill at that boundary. Drawing geometry does not model orders, spreads or slippage.
Independent bar-40 scenarioResult under the stated rule
High 131; close 130.2Wick outside; no confirmed upper break
Close 130.5Exact threshold; no break with a strict comparison
Close 130.6Upper break after this bar closes
Low 114; close 114.8Wick outside; no confirmed lower break
Close 114.4Lower break after this bar closes

Reject degenerate geometry and mismatched charts

The formula requires different bar positions for A and B. If xA = xB, its slope is undefined. If C lies on the baseline, W = 0 and all ratio lines overlap. Treat both as invalid channel inputs rather than interpreting the overlap as strong confluence.

  • Near-zero width can place several levels inside one minimum price tick. Display rounded prices for readability, but decide whether comparisons use raw values or tick-rounded thresholds before evaluating them.
  • A flat or falling pair of lows does not satisfy the rising-trend selection rule, even though a geometric line can still be calculated.
  • The arithmetic example uses linear price spacing and one step per chart bar. Changing interval, session or bar construction changes that coordinate system. Preserve timestamps as well as the original bar references.
  • Do not transfer these price-unit calculations unchanged to a log-coordinate construction. Record the price scale and inspect actual intermediate levels. Zoom and screen angle alone cannot verify the calculation.
  • Missing history and revised or adjusted prices can change anchor selection. Keep the original settings and capture date with the observation.

Turn the fixed geometry into a chart aid and review record

Pineify's Pine Script AI Coding Agent can help draft a chart aid from explicit anchor inputs and break conditions. Provide A/B/C coordinates, the linear formula, confirmation time, selected ratios, buffer and close requirement. Pine scripts cannot read manually drawn TradingView objects, so the script needs its own inputs or a specified pivot-selection rule.

  • Request editable levels and a close-based alert condition. Review the generated source, run syntax validation, and compare bar 40 and bar 42 with the table before using it. Compilation does not prove correct anchors or alert timing.
  • Use Trading Journal to save the hypothesis and later review notes. Save screenshots separately and include their share links or file references in the notes; preserve the original capture before changing anchors.
  • Record symbol, interval, session, scale, anchor timestamps and prices, activation close, selected levels, buffer, break time and re-entry. Keep the planned rule separate from what happened afterward.
  • Test equal anchor bars, zero width, negative width, exact-threshold closes and missing confirmation bars. An automated helper cannot recover information that was unavailable when the decision was made.
Where Pineify fits

Pine Script AI Coding Agent

Draft a channel helper from explicit coordinates and close rules, then check its plotted prices and alert timing against your examples.

Also useful: Trading Journal. Save anchor hypotheses, screenshot references and review notes, including channels that failed after activation.

Draft a channel chart aid

Frequently asked questions

Educational information, not investment advice. Coordinates, prices and confirmation rules are hypothetical examples, not observed performance or live signals. Fibonacci levels do not guarantee support, execution prices or returns.

Sources and verification

Published by Pineify. Pineify is an independent product and is not affiliated with TradingView. Sources support the technical explanations; examples do not establish trading performance.