Concept
HTF-level Proximity Filters
HTF-level Proximity Filters, also known as LTF confirmation at HTF levels, are Meta & Composition concepts. The Library holds 3 implementations, each one a working definition you can pull into Quant.
Top HTF-level Proximity Filters indicators
3 total
What are HTF-level Proximity Filters?
An HTF-level proximity filter gates lower-timeframe signals by their distance to higher-timeframe levels. The mechanics are simple: maintain a set of levels computed on a higher timeframe, such as prior period levels, pivots, or untested zones; measure current price's distance to the nearest one, usually normalized in ATR multiples or percent; and allow or suppress the signal based on that distance. It runs in two modes: require proximity, so entries only count when they fire at a level, or require clearance, so a long triggered directly beneath higher-timeframe resistance is discarded because its room to run may be capped before it starts.
The filter turns the top-down habit, trade the lower timeframe only where the higher timeframe agrees, into checkable arithmetic. Its output is only as good as its level set: feed it too many levels and everything is near one, feed it too few and valid locations are missed. Implementations therefore tend to cap the number of active levels per side and prefer fresh, untested ones.
How traders use it
- As a veto: suppress longs within a set distance below higher-timeframe resistance and shorts just above higher-timeframe support, removing trades whose first obstacle arrives almost immediately.
- As entry qualification: the inverse mode accepts lower-timeframe reversal triggers only when they print at a higher-timeframe level, the familiar pattern of dropping down a timeframe to confirm a location before committing.
- As target logic: the same distance calculation ranks which level sits first in the trade's path, informing where targets or partial exits belong rather than whether to enter.
Related concepts · Multi-timeframe
Concept family
Meta & Composition
28 concepts mapped · 23 in the Library
HTF-level Proximity Filters FAQ
How close does price need to be to a higher-timeframe level to count?
There is no universal number. Common practice normalizes distance by volatility, for example within a fraction of the daily ATR, or by a percentage of price, because a fixed tick distance means completely different things on different instruments and timeframes. The threshold is a tunable parameter: tighter thresholds select fewer, cleaner interactions, while looser ones catch more but dilute the meaning of being at the level.
Are signals taken at higher-timeframe levels more reliable?
They are differently located, not guaranteed. Higher-timeframe levels attract attention and order flow, which is why traders filter for them, but levels break regularly and a filter cannot know in advance which will hold. Treat proximity filtering as trade selection whose value should be measured: compare the filtered and unfiltered signal streams over the same data and confirm the filter is actually earning its rejections.
Build HTF-level Proximity Filters your way.
Quant writes, tests, and refines it with you — then it runs on LuxAlgo charting or ports to TradingView.


![L1 Proximal Filter [MTF & Alerts] Maxxed Edition preview](/_next/image/?url=https%3A%2F%2Fs3.tradingview.com%2Fo%2Fo6awMfe0_mid.webp%3Fv%3D1771027945&w=3840&q=75)