Fibonacci and Elliott Wave: map ratios to a valid wave count
Elliott Wave analysis uses Fibonacci ratios to compare the lengths of related motive and corrective waves. The ratio is applied after a wave count is defined. It does not prove that the count is correct.
Direct answer
Use retracements to measure corrective waves against the preceding move and extensions to project motive or C-wave targets. Keep at least one alternate count because a different pivot assignment changes every Fibonacci result.
Inputs needed before calculating a wave target
Count
Primary and alternate wave labels
Degree
Compare waves at the same scale
Anchors
Exact start and end price for each wave
Status
Confirmed or still in progress
Common Fibonacci checks by wave role
These are analysis references, not fixed outcomes. A valid count and its structural rules come first.
| Wave role | Ratios to inspect | Question being tested |
|---|---|---|
| Wave 2 | 0.382, 0.500, 0.618 of wave 1 | How much of wave 1 was retraced? |
| Wave 3 | 1.000, 1.618 of wave 1 from wave 2 | Where could the impulse extend? |
| Wave 4 | 0.236, 0.382 of wave 3 | Is the correction shallow or deep? |
| Wave 5 | Compare with wave 1 and waves 1 to 3 | Does the final leg show a related length? |
| Wave C | 1.000, 1.618 of wave A from wave B | Where could the correction complete? |
A disciplined Fibonacci and Elliott Wave workflow
- 1
Label the structure first
Mark motive and corrective legs before drawing ratios. Do not choose a count because one Fibonacci line happens to match a later price.
- 2
Check the structural rules
For an impulse, verify that wave 2 does not retrace beyond wave 1, wave 3 is not the shortest motive wave, and wave 4 respects the chosen rule set.
- 3
Measure related waves
Compare waves at the same degree. A small intraday leg should not set the target for a weekly wave without an explicit nesting model.
- 4
Keep an alternate count
Write the price that invalidates the primary count and what structure replaces it. This prevents one preferred label from becoming unfalsifiable.
- 5
Test rules, not chart stories
Code the pivot, confirmation, and invalidation logic. Review losing and relabeled cases, not only charts where the projection looked precise.
How I audit a wave projection
When I label a SPY impulse, I save the alternate count beside the primary one. A target without an invalidation level is just a preferred story.
I calculate retracements from the exact wave endpoints before rounding them into chart zones. That keeps the arithmetic reproducible.
I separate completed waves from in-progress projections. TradingView can redraw an unfinished pattern as new bars arrive.
The wave count is the fragile input
Fibonacci arithmetic is simple. The hard part is deciding which pivots belong to the same wave degree. If the count changes, the anchor prices and targets change with it.
That subjectivity is why an alternate count matters. Each count should have a specific invalidation price and a clear reason for promotion or rejection.
Use clusters as conditional zones
A cluster occurs when projections from separate, related waves fall near one another. It can narrow the area to inspect, but it does not create certainty.
Record how the cluster was built. A useful note names each wave pair, ratio, anchor, and calculation. Without that trail, the cluster cannot be checked.
- Keep motive and corrective projections in separate labels.
- Do not add ratios after price reaches the area.
- Measure test performance with the original count, not a relabeled chart.
What automation can and cannot do
Code can find pivots, check a limited set of structural rules, and draw projections consistently. It cannot remove every judgment about wave degree or pattern quality.
Pineify can generate an inspectable indicator or strategy for a stated wave model. Keep the labels and invalidation rules visible so the output can be reviewed.
Illustrative wave 3 projection
Assume an illustrative SPY wave 1 moves from 500 to 520 and wave 2 ends at 507.64.
Wave 3 projection = wave 2 end + wave 1 length x ratio
Wave 1 length = 520 - 500 = 20 Wave 2 end = 507.64 1.000 projection = 527.64 1.618 projection = 507.64 + (20 x 1.618) = 540.00
The inputs are invented to explain the calculation. They are not current SPY prices or an Elliott Wave forecast.
Build a wave projection tool with visible rules
The script should expose the pivot method, wave labels, structural checks, and alternate count instead of hiding them in a score.
Create a Pine Script v6 overlay that detects confirmed pivots with adjustable left and right bars. Allow the user to label five motive points and three corrective points. Check the basic impulse constraints, plot wave 2 retracements at 0.382, 0.5, and 0.618, and plot wave 3 projections at 1.0 and 1.618 of wave 1. Show the invalidation price and label every projection as conditional.Generate the Pine Script
Continue the analysis
Tools for the next check
Trend-Based Fibonacci Extension
Draw a three-point Fibonacci extension, calculate common targets, and keep TradingView anchors consistent.
Silver 1.618 Fibonacci Extension
Calculate a 1.618 silver extension from fixed swing anchors with an illustrative example, validation rules, and source-backed formulas.
Fibonacci Extension Calculator
Calculate extension reference prices with two-point and three-point ABC methods for stocks, forex, and crypto.
Fibonacci Retracement Visualizer
Calculate and visualize Fibonacci retracement and extension levels on an interactive chart from uploaded price data or manual high and low inputs.
Fibonacci Retracement Settings
Set up Fibonacci ratios, anchors, labels, chart scale, and alerts in TradingView with an auditable baseline template.
Sources and method notes
This page is an information tool, not investment advice. Elliott Wave labels and Fibonacci projections are conditional analyses. They do not predict a price, wave completion, or return.