Is a falling wedge bullish or bearish?

It is usually interpreted as a bullish setup, but both boundaries still point down. An eligible upward break supplies confirmation under a chosen rule; price can instead break support or fail after an upward break. The shape is not a buy instruction.

Is a descending wedge pattern the same as a falling wedge?

Yes, when both names refer to downward-sloping, converging boundaries. A descending broadening wedge is different: its lower boundary falls faster and its width increases.

How many touches does a falling wedge need?

The count depends on the chosen definition. This example uses three confirmed highs and two confirmed lows, with two points anchoring each line and the third high testing resistance. More touches can delay recognition and change the sample; they do not establish a success rate.

Can a falling wedge be a continuation pattern?

Yes. A downward wedge can be a correction within an established uptrend. After a prior decline, the bullish interpretation is a reversal instead. Record the prior-trend classification before evaluating the breakout.

Does a close above the wedge mean price has turned upward?

Not necessarily. Descending resistance can move below a falling close, as the numerical example shows. Requiring a close above the last reaction high is a different, later confirmation rule. Neither condition guarantees continued gains.

Does this page provide a non-repainting wedge indicator?

No. It provides an explicit detector specification and an illustrative event calculation. A generated implementation still needs syntax checks, timestamp review and testing. Confirmed pivots reduce one source of changing anchors but become available only after their required future bars close.

TradingView chart patterns

Falling wedge pattern: convergence and confirmation

A falling wedge pattern has two downward-sloping boundaries that narrow toward each other. The upper boundary falls faster than the lower boundary. Also called a descending wedge pattern, it carries a bullish interpretation only after an upward break; the downward shape itself is not confirmation. It can form during a downtrend or as a pullback within an uptrend, and either setup can fail.

See the decision guide

Separate downward slope from narrowing width

On a linear price scale, let U(t) = aU + mU × t be resistance and L(t) = aL + mL × t be support, where t counts bars. Width is W(t) = U(t) - L(t). A falling wedge requires mU < mL < 0 and W(t) > 0. Width changes by mU - mL each bar, so it shrinks when the upper slope is more negative.

Compare the two line values at the same bar. Subtracting a low from a high recorded on a different bar does not measure the vertical width.
Nearly equal slopes can produce negligible contraction. Choose a minimum width reduction before examining the results.
Chart zoom changes visible angles. Logarithmic price coordinates also change the line equations; keep the display scale and detector calculations consistent.

Structure	Slope relationship	Consequence
Falling wedge	mU < mL < 0	Both lines fall and width shrinks
Descending parallel channel	mU = mL < 0	Both lines fall at the same rate
Descending broadening wedge	mL < mU < 0	Support falls faster and width grows
Descending triangle	mU < 0; mL = 0	Support is flat rather than falling

Define touches and tolerance before drawing the wedge

Two highs and two lows can anchor the boundaries, but a detector still needs an objective rule for choosing them. This hypothetical specification uses three highs and two lows so that a third high tests resistance. Its values are research assumptions, not universal requirements or recommended settings.

A 0.30-unit tolerance has different significance at different price levels and tick sizes. A volatility-based or tick-based tolerance would be a separate specification.
Only the selected confirmed turning points count as touches. Several adjacent candles near a line do not supply several independent swings.
After creation, the first close above U(t) + 0.30 confirms an upward break. A close below L(t) - 0.30 first invalidates the candidate. Otherwise keep waiting until expiry.
Consume the candidate after the first directional event. Save rejected and expired candidates instead of shifting the lines to fit later prices.

Decision	Illustrative specification
Pivots	Require two bars on each side with strictly lower highs or strictly higher lows; reject ties and bars qualifying as both types
Selection	Use the latest five confirmed pivots only if their order is high-low-high-low-high and consecutive points are at least four bars apart
Anchors	Connect the first two highs for U(t) and both lows for L(t); require the third high to be within 0.30 price units of U(t)
Contraction	Require mU < mL < 0, positive width and W(last pivot) / W(first pivot) ≤ 0.50
Containment	Every close from the first pivot through candidate creation must lie between L(t) - 0.30 and U(t) + 0.30
Active window	Freeze both lines at creation. Evaluate the next eight bars, but expire before the lines meet. Do not replace an active candidate

A falling close can still break descending resistance

Assume hypothetical highs at bars 0, 10 and 20 are 120, 114 and 108, with intervening lows at bars 5 and 15 of 107 and 105. They give U(t) = 120 - 0.60t and L(t) = 108 - 0.20t. Assume the surrounding candles pass the pivot and containment rules. The final high becomes known at bar 22 close; the candidate cannot be traded at bar 20.

The bar 23 close fell by 0.10 from bar 22, yet crossed the buffered resistance because the line fell by 0.60. A line break and rising price are different conditions.
A stricter variant could require a close above the last swing high plus the same buffer: 108.30. Bar 23 would not pass. That variant confirms later or not at all; it is not automatically better.
For this example, flag an early failed breakout if a later close falls below U(t) - 0.30 within three bars of the break, while width remains positive. Bar 24 at 105.20 passes that failure test because 105.20 < 105.30. Preserve the original break and the failure flag.
In an alternative path without an earlier upside break, a bar 24 close at 102.80 is below L(24) - 0.30 = 102.90 and invalidates the bullish candidate. A wick below support with an inside close would not.
The eligible bars are 23 through 29: bar 30 is excluded by the intersection even though the eight-bar limit has not yet elapsed. These invented prices illustrate event rules, not market performance.

Bar	Upper line	Lower line	Width or event
0	120.00	108.00	Width 12.00
20	108.00	104.00	Width 4.00; ratio 4 / 12 = 0.333
22	106.80	103.60	Close 106.70: candidate known, price inside
23	106.20	103.40	Close 106.60 > 106.50: upward confirmation
24	105.60	103.20	Alternative later close 105.20: return inside
30	102.00	102.00	Lines meet; no positive-width wedge remains

Reversal and continuation use the same geometry

StockCharts describes a falling wedge chart pattern after a decline as a potential bullish reversal and a downward wedge within an established uptrend as potential continuation. Record that context before the wedge begins. Classifying it from the eventual rally would introduce knowledge of the outcome.

Choose a fixed trend classification rule and lookback using only bars before the first selected pivot. Keep reversal and continuation results separate when evaluating it.
StockCharts also discusses expanding volume and a break above a prior reaction high as confirmation evidence. If used in a detector, specify the volume baseline or exact price threshold rather than relying on an impression of strength.
A successful boundary break does not establish a target or a win rate. Trade outcomes also depend on entry timing, exits, costs and the market sample.

Context	Question being tested	Failure to retain
Prior decline	Does an upside break interrupt the established decline?	Price breaks support or returns inside after an upside break
Prior advance	Does the downward correction end and the prior advance resume?	The pullback develops into a larger decline
Unclear prior trend	Does the geometry qualify without a directional context label?	Do not force the example into a reversal or continuation sample

TradingView confirmation has a timestamp

TradingView documents 5/5 pivots and closing-price breakouts for its Falling Wedge indicator. In Progress may use unconfirmed final points. Its Pattern Breakout alert covers the target direction only, so a downward break does not trigger that alert. These built-in rules differ from the custom two-right-bar example above.

A five-right-bar pivot at bar 20 needs bars 21 through 25 before confirmation. Drawing its marker at bar 20 does not mean the signal existed there in real time.
Keep pivot time, pivot confirmation time, candidate creation time and breakout time in separate fields. Bar-by-bar review should use only information available at each decision.
Waiting for a completed bar avoids acting on its changing intrabar close. It does not remove all repainting causes or prevent a later failed breakout.
The early failure flag above is a custom audit rule. TradingView has its own Failed status, including a lower-boundary break; do not treat the two definitions as interchangeable.

Display the detector before adding strategy orders

Give Pineify AI Coding Agent the pivot selection, line equations, tolerance, contraction threshold, confirmation rule and expiry. Ask for a Pine Script draft that displays candidate IDs, frozen boundaries and confirmation markers. Review those outputs against the written rules before converting the detector into a strategy.

Check the generated script syntax and inspect cases where the drawing appears late, the lines nearly cross, a touch misses tolerance or a breakout returns inside.
A strategy needs additional rules for order timing, position size, stop, profit exit and maximum holding period. A detector alert alone supplies none of those execution assumptions.
Test a fixed specification with costs and a separate evaluation period. Record invalidations and failed breaks as well as surviving patterns; this guide supplies no tested settings or measured edge.

Where Pineify fits

Pine Script AI Coding Agent

Draft a detector from explicit falling-wedge rules, then inspect its anchors and event times in TradingView. This educational page does not scan live symbols or supply a validated trading strategy.

Draft falling-wedge rules

Related resources

TradingView chart patterns Rising wedge geometry Broadening wedges and expanding width Bar-close alert frequency

Frequently asked questions

Educational information, not investment advice. Example prices, thresholds and event paths are hypothetical. No backtest, live performance or success rate is presented. Pattern recognition and breakout confirmation do not guarantee a direction or profit.

Sources and verification

Last verified: 2026-10-16

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.