Best Breaker Block Indicators on TradingView (2026), Code-Read.

Short answer: the popular breaker block scripts don't agree on what a breaker is. The most boosted, Order Blocks & Breaker Blocks by LuxAlgo (30,478 boosts), flips an order block the moment a candle's body gets through it, with no break of structure, on the live bar, and has no alerts. Breaker Blocks with Signals by LuxAlgo (16,839) is the closest to the textbook: it waits for a drop that makes a lower low, then a close back above the swing high, and boxes the last up candle before that high, so it never boxes a mitigation block. It decides on the live bar and keeps one breaker at a time. For breakers drawn on closed candles, Breaker Blocks by Flux Charts (2,734) flips an order block on a close through it, ends it on a close back, and alerts on each new one, but never checks structure. None of our desks draws breaker blocks.

Most lists name breaker block indicators.

This one reads them.

What we checked

We read every script against one rule, the one in our SMC Rule Book. A candle closes beyond a swing, and the last candle that closed the other way is the order block, its body the zone. A later candle closes beyond the zone's far edge; a wick beyond it that closes back is only a touch. Then the next break of structure goes the other way. From the later of those two closes, the zone is a breaker, watched from the other side. A close back beyond its new far edge ends it. If the move before the break never closed beyond the last low (or high), the same zone is a mitigation block, not a breaker. The order block itself, and the 14 scripts that draw it, are in our order block indicator code read; the rules sit together in our smart money concepts guide.

We searched TradingView's scripts for four terms on 31 October 2026 ("breaker block", "breaker blocks", "breaker" and "order blocks & breaker blocks") and kept every script with "breaker" in its name: 70 scripts, 45 open source, 17 protected and 8 invite-only. We took the 14 most-boosted open-source scripts that draw breaker blocks and read every line that decides what is drawn, and the library code where a script imports its rule (TradingFinder's four do). Six questions:

• What makes a breaker: an order block that price closes through, a touch and then a close, a failed swing, or a break of structure?
• Its range: the candle's body, its wicks, or another price?
• What ends it: a close back through it, a touch, or something else?
• Breaker or mitigation block: does it check whether the move before the break made a new low (or high)?
• When it decides: on a closed candle or the live one, and how many candles late its swing is known?
• Alerts and licence.

The table

Boosts as TradingView's search showed them on 31 October 2026. "Bullish" throughout: a bearish order block that failed upward. The bearish breaker is the mirror in every script.

Licences: LuxAlgo's three and BigBeluga's are shared under CC BY-NC-SA 4.0, which doesn't allow commercial use; AlgoAlpha's, ProjectSyndicate's and AGProLabs' carry no licence line; the other seven are under the Mozilla Public License 2.0.

Not in the table. Four open-source scripts in the top 18 have "breaker" in the name and draw no breaker block: LuxAlgo's Market Structure (Breakers) (5,799 boosts) draws a line at each broken 20-candle swing; Zeiierman's Implied Orderblock Breaker (4,072) boxes an order block at a break of structure and deletes it on a close through, with nothing flipping; ICT Breakers by Chartlix (3,267) calls its market structure shift line a "Breaker (MSS)"; and Flux Charts' Breaker Blocks Screener (1,090) lists breaker blocks in a table for five symbols instead of drawing them. IMGPro's HTF Structure / Order Blocks / Breakers (4,604) and SMRT Algo's MTF Breaker Blocks (2,084) are protected, free to add with the code hidden; astropark's (1,407) is invite-only.

Two order block scripts without "breaker" in the name do more with it. Market Structure Break & Order Block by EmreKb, 64,446 boosts on the order block search that day, draws a breaker box at every market structure break and labels it Bu-BB or Bu-MB, a mitigation block, by whether the low before the break was a lower low. Order Blocks by Flux Charts (26,400) marks an order block as a breaker when a wick goes through it, by default, but draws only the order block, ending at that candle.

What the code says

What makes a breaker?

Five flip an order block on a close through it and check nothing else. LuxAlgo's Order Blocks & Breaker Blocks and its Pure Price Action test the candle's body (math.max(close, open) above a bearish block's top); Flux Charts' Breaker Blocks and VEGAlgo's test the close. AlgoAlpha's wants two closes in a row. None of the five asks whether structure broke the other way.

TradingFinder's three tie it to the first touch. Their order blocks come from 9-candle swings (7 in the Unicorn script), and the breaker comes from their OrderBlockDrawing library: once price reaches the block, a close beyond its far edge on one of the next 3 candles makes it a breaker; the library clears one made on the touching candle before that candle closes. The Signals + Alerts script imports version 3, which allows 8. A close through the block later than that makes no breaker.

Two wait for structure. LuxAlgo's Breaker Blocks with Signals waits for a market structure shift: a close above the last swing high of its zigzag when structure was down, after the drop from that high made a lower low. It boxes the last up candle at or before that high: the textbook bullish breaker. TradingFinder's ICT Setup 02 waits for five swings of lower highs and lower lows, then a close above the second-last lower high, and boxes that high's candle.

pmk07's needs no close at all. A supply block turns into a breaker when a 3-candle swing low forms above it: a failed swing.

Three start from something else. BigBeluga's zones hang one ATR(200) from 5-candle swings that print while a volatility reading is high, and flip when a whole candle clears them. ProjectSyndicate's takes the last up candle before a swing high, if a candle with a body over 2 ATR(14) closed above it before the swing was confirmed. AGProLabs' takes the last down candle at or before a swing high, once a closed candle closes 0.75 ATR(14) above it.

Our rule book wants both: the close through the block, and the break of structure the other way. The five close-through scripts check only the first. Move the two closes: the same candles make a breaker under one rule and a failed order block under another.

At A's close of 101.20, the rule LuxAlgo's, Flux Charts' and VEGAlgo's share calls candle 10 a breaker. AlgoAlpha's waits for a second close above, and our rule book calls it a failed order block until a close above 102.00, the last swing high, breaks structure up.

Breaker or mitigation block?

Two scripts in the table check. LuxAlgo's Breaker Blocks with Signals draws a bullish breaker only if the low after the swing high is below the low before it (Ey < Cy, its zigzag's points); with no lower low it draws nothing, so it never boxes a mitigation block. TradingFinder's ICT Setup 02 checks it through its pattern: the low after the high it boxes must be a lower low (TypePoint2 == 'LL'). EmreKb's order block script, outside the table, draws the box either way and labels it Bu-MB, a mitigation block, when there was no lower low (l0 < l1 ? "Bu-BB" : "Bu-MB"). All three read those lows from wicks: a wick that sweeps the low and closes back counts as a lower low.

Eight more have it built in: their order block is born at a close (pmk07's: a swing) below a swing low, so the drop before any flip already made a lower low, on their own swing length. AlgoAlpha's, BigBeluga's, ProjectSyndicate's and AGProLabs' zones need no break at all, so a box they call a breaker can be what our rule book calls a mitigation block. The film shows the difference by closes, as the rule book reads it.

Body or wick?

Six box the whole candle by default: LuxAlgo's Order Blocks & Breaker Blocks and its Breaker Blocks with Signals, AlgoAlpha's, Flux Charts', VEGAlgo's and AGProLabs'. LuxAlgo's Pure Price Action boxes the body by default.

The other seven draw something else. pmk07's runs from a swing high's wick down to the higher of two candles' lows. TradingFinder's four build the zone with their OrderBlockRefiner library, on by default. BigBeluga's hangs one ATR(200) from the swing. ProjectSyndicate's draws a band 0.75 ATR(14) tall around the candle's middle, so every zone is the same height ("Normalize All Zone Heights", on by default).

For a breaker the range decides twice: its far edge is the line a close must cross to make the breaker, and its other edge is the line a close back through ends it at. In the drill, the wick-to-wick top sits 0.10 above the body's.

What ends a breaker?

A close back through it ends it in eight. LuxAlgo's three, Flux Charts' (on "Close", its default), VEGAlgo's with "Chop Control" on (its default) and BigBeluga's end a breaker on one close beyond its far edge; AlgoAlpha's wants two in a row, and AGProLabs' a close 0.12 ATR(14) beyond it.

A touch ends it in TradingFinder's four. Their library stops a breaker when a wick reaches its near edge ("Mitigation Level BB": Proximal), or when the next order block of its kind is first touched, so a breaker lasts no longer than price's first return to it. The library sets that touch level at the top of each candle, before a new breaker updates it, so on the candle that makes a breaker it tests the previous breaker's level, and can clear the new one at once. And the scripts' "50 % BB" choice doesn't match the name the library checks ("50 % OB"), so in our read that setting turns the touch off and leaves the 500-candle limit and the next order block's touch.

pmk07's waits for a swing: a 3-candle swing high forming below a bullish breaker deletes it. ProjectSyndicate's never ends one by default; it keeps the newest 5, and "Enable Mitigation" stops a zone at the first close inside it.

The film's rule ends a breaker on a close back through, as eight of the 14 do.

When does it decide?

Four decide on closed candles: pmk07's, Flux Charts', BigBeluga's and AGProLabs'. The other ten decide on the live bar, so a breaker can print mid-candle and vanish before the candle closes: LuxAlgo's three, TradingFinder's four, AlgoAlpha's, VEGAlgo's and ProjectSyndicate's.

A swing is late by the candles on its right. LuxAlgo's Order Blocks & Breaker Blocks, Flux Charts' and ProjectSyndicate's use 10-candle swings, known 10 candles after they print; TradingFinder's main two use 9, the Unicorn 7 and Setup 02 2; BigBeluga's, VEGAlgo's and AGProLabs' 5. LuxAlgo's Breaker Blocks with Signals needs 5 candles on a swing's left and 1 on its right, and pmk07's 1 on each side. AlgoAlpha's finds no swing at all: its block comes from the displacement.

Alerts and licences

Nine have alerts. Four send them from closed candles: LuxAlgo's Breaker Blocks with Signals (its alert() calls fire once per bar close, except the take-profit ones, off by default, which fire once per bar; its 22 alert conditions fire as you set them), pmk07's (one message per closed candle, breaker tests included), Flux Charts' (a new breaker) and AGProLabs' (new, READY, retest held, invalidated). TradingFinder's three send theirs once per bar by default, on the live candle; their "Per Bar Close" choice doesn't match the name their alert library checks ("Once Per Bar Close"), so in our read it sends nothing. AlgoAlpha's (breaker formed, rejection) and VEGAlgo's (price touching a zone) use alert conditions, so you pick the frequency in TradingView's alert dialog. LuxAlgo's Order Blocks & Breaker Blocks and Pure Price Action, BigBeluga's, TradingFinder's Setup 02 and ProjectSyndicate's have none.

Ours

None of our desks draws breaker blocks. We searched every desk's Pine source: none flips an order block or labels a breaker.

What we do sell draws the order block a breaker starts from. SMC Basics, in Pine Pro Library, $49 once with its full Pine v6 source, boxes the last opposite candle within the 20 before a close beyond a confirmed swing (10 candles each side by default), its body by default, on closed candles. A close through the block's far edge deletes it; turn on "Keep mitigated zones as ghost outlines" and it stays as a grey outline that ends at that candle. That is the first half of a breaker by our rule book, and SMC Basics stops there: it draws no break the other way and no flipped zone. The SMC AI-Scored Toolkit, $39 once, boxes order blocks at structure breaks on bar close and scores each one 0–100.

If you want breakers drawn for you, the table is the honest list: Flux Charts' for a close through on closed candles, LuxAlgo's Breaker Blocks with Signals for the lower low and the shift. The order block under each one, and when it's drawn, is in our order block indicator code read.

Check one yourself

• What makes it: find the line that sets the breaker (a breaker := true, a new box, a colour change). close, or math.max(close, open) and math.min(close, open), against the block's far edge is a close or a body through it; low or high is a wick; a pivot compared with the block is a failed swing; ta.crossover(close, …) of a swing level is a break of structure.
• Mitigation block: look for two lows (or highs) compared before the break, like Ey < Cy or l0 < l1. No such line? Then look at what the order block is born from: if it needs a close below a swing low, the lower low is built in.
• What ends it: find the line that deletes or stops the breaker's box, and read which price it compares with which edge.
• A library: if the script imports one (import TFlab/...), the rule may live there. Read that too.
• The close: look for barstate.isconfirmed, and the swing length in ta.pivothigh or ta.highest. Our repaint guide has the rest of the check.

None of the scripts here runs on MT5, MT4 or NinjaTrader 8: Pine Script runs only on TradingView. A breaker block indicator for MT5 is a new program in MQL5; check it the same way (Pine Script to MQL5 works through one port). The same flip happens to fair value gaps: a gap closed through is an inversion gap, and our IFVG indicator code read reads the scripts that draw them.

Limits

One code read, on 31 October 2026, of the versions TradingView served that day, and of the TradingFinder libraries its scripts import (OrderBlockDrawing versions 3 and 4, OrderBlockRefiner 2, AlertSender 1). We read the code; we didn't run the scripts on a live chart. Scripts change, and boosts measure popularity, not quality. The drill's and the films' candles are simulated. We haven't tested breaker blocks as a trading rule. We build and sell SMC Basics and the SMC AI-Scored Toolkit, and we have no relationship with any author named here. Nothing here is financial advice.

Use these animations on your site.Embed these animations