Top 7 Liquidity Zone Indicators on TradingView
Liquidity-zone indicators help organize price levels, sweeps and volume-based estimates. They do not reveal every resting order or prove that institutions are buying or selling. This comparison covers seven LuxAlgo studies from the Library, including two complementary range and support/resistance tools. The order is a practical shortlist, not a measured performance ranking.
For a native workflow, begin in LuxAlgo charts, inspect the chosen study and use Quant, our coding agent, to help express a testable strategy. TradingView publications remain useful for their original descriptions and source code. Check each implementation and its timing instead of assuming that every platform version has identical settings.
Compare the Seven Indicators
| Indicator | Main question | Important limitation |
|---|---|---|
| Buyside & Sellside Liquidity | Where are price-derived levels above highs and below lows? | Estimated stop-location context, not an order-book inventory. |
| Liquidity Sweeps | Did price pierce a level or fail after a break and retest? | A sweep is an observed pattern, not a guaranteed reversal. |
| Pure Price Action Liquidity Sweeps | Which structural swing ranks were swept? | Swing significance develops as subsequent price structure appears. |
| Liquidity Pools | Which wick zones receive repeated qualifying contacts? | Volume labels allocate candle volume; they do not count resting orders. |
| Liquidity Levels/Voids (VP) | Where does the selected swing-based volume analysis mark sparse areas? | Results depend on volume data, sensitivity and thresholds. |
| Range Detector | Where is consolidation, and when was it detected? | Historical box placement can precede the detection bar. |
| Support & Resistance Dynamic | Which zones fit the detected trend? | A trend-aware support/resistance estimate, not direct liquidity measurement. |
1. Buyside & Sellside Liquidity
Buyside & Sellside Liquidity marks potential liquidity levels and configurable zones around selected price extremes. In this terminology, buy-side liquidity is above prior highs, where short-position buy stops may be located. Sell-side liquidity is below prior lows, where long-position sell stops may be located. Calling buy-side liquidity support and sell-side liquidity resistance reverses the usual placement.
The indicator also marks displacement voids. These price-derived areas can help frame a return or continuation hypothesis, but price does not have to revisit them. A breach may continue rather than reverse, and the chart cannot establish the identity or size of participants behind the move.
- Adjust: Detection Length, Margin and the displayed buy-side/sell-side zone margins.
- Check history: Present mode covers the last 500 bars in the documented version; Historical mode processes available history. Visible Levels limits the displayed objects.
- Use: mark a reference level, then specify what price must do there before considering a trade. Alerts for levels or breaches are notifications, not fills.
2. Liquidity Sweeps
Liquidity Sweeps distinguishes two patterns. One involves a wick piercing a prior level followed by a close back across it; the other involves a close through the level followed by a failed retest. The documentation distinguishes dotted and dashed annotations and draws the distance from the reference level to the relevant wick extreme as a Sweep Area.
Choose Only Wicks, Only Outbreaks & Retest, or the combined mode. The Swings setting determines the swing-detection period. Extend controls prolonging the boxes, while Max Bars limits their extension. Those are different choices from the entry, stop and expiration rules needed for a strategy.
For example, a known high at 100 followed by a bar reaching 101 and closing at 99.5 could meet a bearish wick-sweep definition. It does not prove that stop orders were exhausted or that the next bar must fall. A close above 100 that remains above it is not the same rejection pattern. Keep the selected mode explicit when reviewing examples.
3. Pure Price Action Liquidity Sweeps
Pure Price Action Liquidity Sweeps uses a hierarchy of price swings rather than a numeric swing-lookback setting. A short-term high is flanked by lower highs and a short-term low by higher lows. Intermediate swings are derived from short-term structure, and long-term swings from intermediate structure.
The Detection Settings choose the significance of swings used in sweep detection. Higher ranks create a different selection of events; they do not establish a universal improvement in accuracy. Price-only analysis also does not eliminate all noise or remove the need to check when a swing became identifiable.
Keep the structural swing time and the later detection time separate. A level drawn back to an earlier turning point must not be treated as available there before the required subsequent structure developed. Compare the live behavior with the historical display before translating annotations into entries.
4. Liquidity Pools
The original Liquidity Pools publication by LuxAlgo describes estimated zones built from high and low wick areas, repeated visits and their spacing. It monitors potential zones until the selected criteria are satisfied. This is more specific than saying that it detects institutional positions or actual order clusters.
- Zone Contact Amount: sets the required qualifying visits; the initial occurrence counts as the first contact.
- Bars Required Between Each Contact: separates contacts so adjacent candles are not necessarily counted as independent revisits.
- Confirmation Bars: delays identification after the required contact count so the subsequent price reaction can be evaluated.
- Display: boundary extensions stop when the zone is mitigated by a close beyond it; optional candle coloring applies to returns to an already displayed, unmitigated zone.
The volume label is an allocation estimate. The publication explains that a candle with 50% of its range inside a zone contributes 50% of its volume. For a candle with volume 1,000, that contribution is 500. This is not proof that exactly 500 units traded at those prices, and it is not a count of unexecuted stop orders. Check the symbol’s volume source before interpreting the label.
5. Liquidity Levels/Voids (VP)
Liquidity Levels/Voids (VP) analyzes the selected span between swing points and marks qualifying levels or voids. Its Detection Length identifies swing levels, Threshold % sets the cutoff, and Sensitivity controls how many price slices are evaluated. Filled and unfilled areas can use different colors or visibility settings.
Optional swing labels show price, change and cumulative volume between swings. Mode and the present-history bar setting also affect what is evaluated and displayed. Changing sensitivity changes the price resolution of the analysis; it is not simply a cosmetic adjustment.
Use the marked areas as candidates for a reaction, return or continuation test. Sparse historical participation does not guarantee fast future movement or a later fill. A volume profile describes the available traded-volume data and its allocation method, which is different from a live depth-of-market view. Tick volume, exchange-specific volume and consolidated volume should not be treated as interchangeable.
6. Range Detector
Range Detector is a contextual companion rather than a direct stop-location detector. It identifies sideways price ranges, their boundaries and a dotted midpoint. Blue boundaries indicate an intact range; green and red indicate upward and downward breaks in the documented display.
Minimum Range Length specifies how much consolidation is required. Range Width uses an ATR multiplier, and ATR Length sets the underlying averaging period. Overlapping new ranges can merge with existing ones and update their boundaries. Record the settings and the actual detection bar when testing a range-based condition.
The box can be anchored back to the beginning of the range, while a gray background marks its detection bar. An earlier-looking box is not permission to trade at its left edge using information found later. Once detected, the boundaries can provide context for a separate sweep rule or a breakout rule; decide which hypothesis you are testing.
7. Support & Resistance Dynamic
LuxAlgo’s Support & Resistance Dynamic estimates zones according to a detected trend. Its documented behavior shows support during an uptrend and resistance during a downtrend. It uses deviations from a central tendency to determine the trend and construct levels.
Multiplicative Factor controls how frequently new zones appear, with lower values producing more frequent levels. ATR Length affects the deviation threshold, and Extend Last selects how many recent historical levels extend to the latest bar. A significant break of a zone can motivate a separate reversal hypothesis, but it does not ensure that the trend has ended.
Use this study to ask whether a sweep aligns with a predefined trend context. It does not directly detect a liquidity pool, and agreement between two price-derived studies is not independent evidence of hidden institutional demand. Compare the combined rule with the same sweep rule on its own.
Turn a Liquidity Idea into Explicit Rules
| Decision | Illustrative rule | What to verify |
|---|---|---|
| Reference | Use a level already detected before the current bar | No future swing or later range boundaries. |
| Event | High exceeds 100, then the completed close falls below 100 | A wick sweep under the chosen definition. |
| Entry | Enter short at the next eligible price after detection | Do not assume a fill at the earlier high. |
| Exit | Use a stated stop, target and maximum holding period | Include failed sweeps and expiration. |
| Risk | Size from actual entry, stop distance and costs | Allow for gaps, slippage and instrument point value. |
Suppose an illustrative short entry is 99.5, the planned stop is 101.5, and the risk budget is $100 with $10 reserved for estimated costs. The remaining $90 divided by $2 per share allows 45 shares. Notional exposure is $4,477.50. If the exit instead gaps to 103.5, the price loss is $180 before costs. The planned stop is not a guaranteed loss ceiling; short trades also have borrowing and other instrument-specific risks.
Test all qualifying events over the stated period. Record misses, expired setups and losing trades, not only clean reversals. Keep an evaluation period outside parameter selection and compare results after fees, spread and slippage. Adding Range Detector or a trend filter changes the strategy and should be evaluated on the same underlying data.
Research the Setup in Native LuxAlgo
Open native LuxAlgo charts and use the Indicators picker to inspect the chosen study. Confirm its inputs, data source and event timing. Use multiple panels only when each answers a defined question, such as the local sweep and a completed higher-timeframe trend condition.
Ask Quant, our coding agent to implement a complete specification: “Identify a previously known swing high, detect a completed wick sweep above it, expose detection timing, then enter at the next eligible price with a defined stop, target, expiration and trading costs.” Inspect generated code and run the strategy manually. Verify individual trades before interpreting the summary statistics.
Related Video: Building Support and Resistance Tools
This official LuxAlgo tutorial demonstrates a separate support/resistance tool and introduces customization with Quant. It complements the comparison by showing how zone-based ideas can be expressed visually; the demonstrated Support & Resistance PRO Toolkit is not the Support & Resistance Dynamic script in item seven. Treat its examples as illustrations rather than a performance ranking of these seven indicators.
Choose by Function, Then Test
Use a level mapper for reference locations, a sweep detector for events, and a range or trend study only when it adds a defined contextual condition. More overlays can repeat the same price information. Check the individual publication’s access and platform details; free script availability does not make every data feed or platform feature free.
A useful workflow produces observable rules and an honest trade record. It does not require choosing a universal best indicator, assuming every void fills, or treating a colored zone as an instruction to trade.
Frequently Asked Questions
Do liquidity indicators show actual institutional orders?
No. The studies compared here estimate zones from price, swings, contacts and available volume data. They do not establish hidden stop quantities, participant identity or all resting orders.
Where are buy-side and sell-side liquidity usually marked?
In this terminology, buy-side liquidity is above prior highs and sell-side liquidity is below prior lows. These are potential order-location references, not guaranteed resistance or support.
How does Liquidity Pools calculate its volume label?
The original publication describes allocating candle volume in proportion to the candle range inside the zone. A 50% overlap contributes 50% of candle volume. That is an estimate, not exact traded volume at each price or unexecuted order size.
Are all seven indicators dedicated liquidity detectors?
No. Range Detector and Support & Resistance Dynamic are contextual companions. The former identifies consolidation and the latter estimates trend-aware support or resistance; neither directly measures resting liquidity.
Can a historical zone appear before it was actually known?
Yes. Swing-based and range-based displays can anchor drawings to earlier bars after later conditions are satisfied. Record the detection time and use only information available when the trading decision would have occurred.
How can I test a liquidity-zone strategy with LuxAlgo?
Inspect the study in native LuxAlgo charts and ask Quant, our coding agent, to express the full event, entry, exit, risk and cost rules. Inspect generated code, run the strategy manually and review individual trades. Check TradingView versions and alert compatibility separately.
Read next