What is the Fibonacci arcs tool called on TradingView?

TradingView calls it Fib Speed Resistance Arcs. It constructs ratio arcs from two baseline anchors. Check the enabled levels and Full Circles setting to identify the exact construction being reviewed.

Does widening a chart always change an arc signal?

No. A fixed data-coordinate curve can stretch visually without changing its price intersections. A circular model recalculated in changed screen proportions can change them. Compare the same timestamp and unchanged anchors before and after resizing; the worked model here does not establish TradingView rendering behavior.

Does a Fibonacci arc touch predict a reversal?

No. A touch is an intersection under a specified rule. Price can continue through the curve or gap past it. A predictive claim requires a prospective rule, all eligible observations and evidence beyond selected screenshots.

Can a Pine script read my hand-drawn Fibonacci arcs?

No. Pine scripts cannot interact with manual chart drawing tools. Provide the script with anchor inputs and a calculation model, then check its output independently before using it for alerts.

TradingView drawing workflows

Fibonacci arcs on TradingView: geometry, scaling and tests

Fibonacci arcs are curved ratio levels constructed from a selected swing baseline. TradingView calls its tool Fib Speed Resistance Arcs. Unlike a horizontal retracement or a straight fan ray, an arc combines horizontal and vertical distance. Record both anchors and chart proportions before interpreting a contact: a visually attractive curve is not evidence that price will reverse.

See the decision guide

Anchor the baseline and save its settings

Choose a completed swing and select Fib Speed Resistance Arcs from the Fibonacci drawing tools. Place the two endpoints on the chosen extremes. Open Coordinates to check both bar positions and prices. In Style, record the enabled ratios and Full Circles setting; that setting adds the other half of each circle. TradingView supports custom levels, so labels and anchor order belong in the record.

Choose wick extremes or closes before drawing. Save symbol, interval, session, adjustment settings, anchor timestamps and prices, and the time you selected them.
For a mechanical swing rule, require a high to exceed the highs of two bars on each side, or a low to fall below both neighboring pairs. Reject ties. This example rule makes the endpoint available only after the second later bar closes.
Save a screenshot before looking ahead. A retrospective endpoint at bar 40 cannot produce a signal at bar 40 if it required bars 41 and 42 for confirmation.
Check which endpoint is the center and which way the visible arc extends on your drawing. Do not transfer the ratio label to another drawing without checking its orientation.

Keep arcs, fans and retracements distinct

The same ratio can describe different geometry. A horizontal retracement divides a price range; a fan projects straight rays; an arc uses curved distance levels. The reference distance and direction determine what a label means.

For a hypothetical rise from 100 to 130, a 50% horizontal retracement is 115 at every later bar. A 50% arc need not pass through 115 at those bars.
The 0.500 midpoint is a common charting convention, not an adjacent-number Fibonacci ratio. Using it in the example below makes the geometry easy to recompute.

Construction	What stays fixed	What a later bar tests
Horizontal retracement	A price level for fixed anchors	Price versus one horizontal threshold
Fibonacci fan	A ray in the chosen coordinate model	Price versus a sloping line at that bar
Fibonacci arc	A ratio radius in a specified distance model	Price versus the selected curved branch at that bar

Calculate one explicit arc model

This is a hypothetical circular-coordinate model, not a reverse-engineered TradingView formula or a measured chart result. Let A = (bar 0, price 100), B = (bar 40, price 130), and choose B as the center. Let h be horizontal units per bar and v be vertical units per price unit. Baseline length D = sqrt((40h)^2 + (30v)^2). For ratio r, radius R = rD. The lower branch at bar t is P(t) = 130 - sqrt(R^2 - (h(t - 40))^2) / v.

With h = 4, v = 4 and r = 0.500, the baseline has horizontal span 160, vertical span 120 and length 200. Its half-radius is 100.
At bar 50, horizontal distance from B is 40. P(50) = 130 - sqrt(10000 - 1600) / 4 = 107.0871, rounded to four decimals.
At the midpoint of the baseline, bar 20 and price 115, distance from B is exactly 100. That verifies the half-radius intersection on the baseline; it does not make the rest of the arc a horizontal 115 level.
The upper branch uses a plus sign. A full circle can have two prices at the same bar, so name the branch before defining a contact.

Show what changing chart proportions can change

If a circular model is recalculated using screen distances, widening the plot while retaining the same visible bars can increase h without increasing v. The table changes that one assumption. Doubling both scales preserves h/v and the calculated price; doubling only the horizontal scale does not.

A price of 100 at bar 50 is below the first curve and above the second. A classification based on the curve can therefore depend on the distance model, even though the anchors and price data are identical.
A fixed curve in data coordinates may simply stretch when displayed, retaining its price intersections. Do not assume every resize recomputes the geometry. The table demonstrates a model dependency, not a claim about every TradingView resize.
TradingView documents proportion changes for its separate Circle tool and recommends Lock price to bar ratio there. The arcs help page does not publish a complete scaling algorithm. Record that setting, then check the actual arc instead of assuming identical behavior across tools.
A log price axis introduces another transform: equal vertical distances represent price ratios. The arithmetic price formula above is not a log formula. Keep log and linear observations in separate records.

Illustrative view	h / v	Radius R	Lower price at bar 50
Original proportions	4 / 4	100.0000	107.0871
Twice the horizontal spacing only	8 / 4	170.8801	92.2508
Both spacings doubled	8 / 8	200.0000	107.0871

Run a repeatable TradingView resize audit

Keep the same drawing and historical data while changing one display setting at a time. The purpose is to determine whether the selected arc has a stable price at a fixed timestamp, rather than whether it looks equally round.

Save the original layout with both endpoint coordinates, enabled ratios, circle setting, scale mode, price-to-bar lock state, visible date range and plot dimensions. Select a later timestamp where the chosen branch is visible.
Capture its approximate price intersection and screenshot. State the reading precision; do not report a sub-tick value from a thick line read by eye.
Resize only the chart width, restore the same visible date range if it changed, and recheck the same timestamp. Then restore the original layout and change only the vertical scale. Repeat with the price-to-bar ratio locked and record the outcome.
Compare a narrow and a wide layout using the same procedure. A sidebar, another pane or auto-fit can change the drawable area or axis range even when the browser window size stays constant.
If the intersection moves beyond the stated reading tolerance, treat the visual contact rule as layout-dependent. If it does not, record that result for those settings only. Missing or clipped arcs are unavailable observations, not proof of a price break.

Define an observable event before reviewing the outcome

For the fixed model above, evaluate only completed bars after the endpoint becomes available. Define a sampled contact as low ≤ P(t) ≤ high. Define failed support as close < P(t) - 1, with a one-price-unit research buffer chosen beforehand. These are example classifications, not recommended entries or stops.

An OHLC range containing the sampled curve price does not prove an intrabar path, a fill or a reversal. Retain immediate failures and expire untouched cases after a prespecified observation window.
Require finite inputs, h > 0, v > 0 and a nonzero baseline. In the original example, the branch exists only when |t - 40| ≤ 25. At bar 65 the branches meet at 130; at bar 70 the square-root input is negative and no real curve price exists.
Keep calculations unrounded when testing strict thresholds. Display rounding is separate from the rule; a threshold printed as 106.0871 is only an approximation.
Do not move anchors after a failed contact. A replacement drawing is a new hypothesis with a new activation time. Include all eligible drawings when reviewing results, not only the curves that fit later price action.

Independent bar-50 case	Result with P(50) = 107.0871
Low 106, high 109, close 108	Contact; no failed support
Low 104, high 105, close 104.5	No contact; failed support
Close equals the unrounded P(50) minus 1	No failure under the strict inequality
Curve undefined at this bar	No classification; do not substitute zero

Build a chart aid from rules you can specify

Pineify Pine Script AI Coding Agent can help draft a chart aid when you supply explicit coordinates, a fixed distance model, branch, activation time and event rules. Pine scripts cannot read manually drawn TradingView objects. A generated helper therefore needs its own inputs or a defined anchor-selection method; it must not claim to detect the native arc from a screenshot.

Ask for plotted model values and completed-bar contact or failure conditions. Compare the midpoint, bar 50, tangent bar 65 and undefined bar 70 before using an alert. Syntax validation alone does not establish mathematical equivalence with the native drawing.
Use Trading Journal diary notes to save the hypothesis, settings and later review. Store screenshots separately and put their share links or file references in the notes so the original evidence remains available.
Record observation counts, failures and expired untouched cases. A trading-performance test additionally needs entries, exits, position sizes, fees and slippage. Arc geometry does not supply them.

Where Pineify fits

Pine Script AI Coding Agent

Draft a chart aid from explicit arc coordinates and event rules, then verify its values and timing against known cases.

Also useful: Trading Journal. Keep the original hypothesis, screenshot references, resize observations and failed-contact reviews in diary notes.

Draft an arc chart aid

Related resources

TradingView workflows Log versus linear charts Record indicator settings Trading Journal

Frequently asked questions

Educational information, not investment advice. All coordinates, calculations and event cases are hypothetical. They are not observed TradingView results, live signals or evidence of profitable trading.

Sources and verification

Last verified: 2026-10-17

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.