Support and resistance is the most over-used, under-defined phrase in crypto. Walk into any BTC Telegram group, ten different traders are drawing ten different "resistance" lines on the same chart, because nobody is actually computing multi-timeframe overlap. This tool does not draw lines, does not give opinions, and does not predict — it pulls live data from the Binance API across seven timeframes (5-minute up to weekly), finds candidate levels from three sources (Fibonacci levels drawn off recent swing highs and lows, high-volume price clusters, and large order-book walls), and merges them into zones scored 0-100. The score mostly reflects how many sources and timeframes land on the same price area; the rest is your call. Section 7 below compares this tool to TradingView pivot points, the charts built into exchange apps and MetaTrader plugins, and looks at how institutional desks approach the same problem.
§1 · What support and resistance actually are · why it's a zone, not a price
Support is the price band where buyers historically step in heavy enough to absorb selling pressure; resistance is the price band where sellers historically step in heavy enough to cap rallies. The common rookie mistake is reading these as single numbers — "BTC support is $107,800" — when in reality support and resistance are zones, not single prices. With BTC at $108,000, "$107,500-$108,200" is a support zone; the individual price of $107,800 is just the midpoint. This tool gives you S1/R1 as midpoint values for compactness, but every algorithm under the hood is operating on a band, not a point. If you place orders at a single isolated price level you will frequently get whipsawed by half a percent of noise and conclude "the level broke," when the band is in fact still holding. Use the score and the band width together — that's how the tool was built to be read.
Why bands rather than points? Three reasons rooted in market microstructure. First, a large order can be split into many smaller orders spread across a range of prices rather than sitting as one order at one exact price. Second, market makers' quoted spreads at any moment are inherently a band, not a price — BTC's bid-ask spread on Binance Futures is tight when liquidity is normal and widens noticeably during stress. Third, retail-driven price discovery works through round-number psychology — the "$100K psychological support" is really a zone around the round number rather than a single price, because stops, take-profits and "I'll buy if it pulls back here" limit orders cluster around it. The tool's band-width logic respects all three of these realities — single-price S/R does not.
§2 · Picking the right timeframe (15m / 1H / 4H / Daily / Weekly)
15m is for 1-2 hour scalping, day-trader perpetual contracts only. 1H is the half-day to one-day intraday rhythm, useful as a swing entry reference. 4H is a popular mid-frequency timeframe in crypto futures markets — a lot of published strategies use it as the primary axis. Daily covers 1-2 week mid-term positioning; macro turning points usually print signals here first. Weekly covers monthly trend and full bull/bear cycle structure. The larger the timeframe, the more reliable the level, but the lower the trigger frequency. Day traders should not be reading weekly levels — weekly resistance can be six months out, you cannot trade that with a 4-hour stop loss. Mid-term positioning traders should not be reading only 15m — too noisy, you'll get washed out on intraday wicks before the thesis plays out. The safest combo for a futures newcomer is 4H + Daily overlap: signals are rarer but each one deserves serious attention.
There is a deeper rule about timeframe selection that almost no one articulates: the timeframe you watch should match the half-life of your decision, not the half-life of your attention. A trader who refreshes the tool every fifteen minutes but holds positions for two weeks should still be reading 4H and Daily — checking 15m is just emotional self-harm at that horizon, because every shake-out generates noise that does not change the fundamental thesis. Conversely, a scalper holding positions for 30 minutes who watches Daily charts is calibrating off levels that may never trade during the position's lifetime. Pick the timeframe that matches your hold period, not your refresh frequency. The single biggest tactical improvement most retail traders can make is to stop watching shorter timeframes than their position holds for.
§3 · Why multi-timeframe overlap matters (1H + 4H + Daily aligned = strong support)
A level identified on a single timeframe carries limited weight — it could just be noise specific to that observation window. But when 1H computes support at $107,500, 4H also points to $107,500, and Daily also lands on $107,500, that three-way overlap is not coincidence. It means traders operating on different time horizons (intraday / mid-frequency / mid-term) are all flagging this level as structurally meaningful. To push through it, the market usually needs a heavier wave of selling. The 0-100 score in this tool leans on exactly this: a zone earns extra points for each timeframe and each separate level that lands on it, so a zone several timeframes agree on will usually outscore a level that shows up on only one. More overlap generally means a higher score — but the score describes agreement, not a promise that the level holds (§4 has the details).
A practical example from the 2024-08-05 flash crash: if you had looked at the chart with a tool like this before the BoJ-rate-hike sell-off, the support below price was an area it had already touched several times. It broke anyway. The lesson is that multi-timeframe overlap tells you something about normal market conditions, not tail-event conditions. When a global macro shock arrives (rate hike, exchange failure, geopolitical event), even 90-point supports can break. The score is a ranking, not a probability and not a guarantee. The right way to use a high-score level is "I'll size up here if it holds, and have a stop ready in case it breaks" — not "this level cannot break, I'll add leverage."
§4 · How the S1 / R1 100-point score is computed
Candidate levels come from three sources: Fibonacci retracement and extension levels drawn off the most recent swing highs and lows on each of the seven timeframes; high-volume price clusters from the 1H, 4H and Daily candles; and unusually large resting orders in the live order book near the current price. Each candidate carries its own points — higher timeframes weigh more (weekly the most, 5-minute the least), Fibonacci retracements count for more than extensions, and bigger volume clusters and order walls count for more than small ones. Candidates of the same type (support or resistance) that sit very close together are merged into one zone. The zone's 0-100 score then adds up the combined points of everything merged into it (capped), plus a bonus for how many timeframes and how many individual levels it contains (also capped), minus a penalty for sitting far from the current price and a penalty for being wide. Zones scoring under 25, or wider than 2.2% of the current price, are dropped. When you switch the timeframe buttons, the list is re-ranked to favour zones from the timeframe you're viewing and the larger ones above it (and to play down the smaller ones below it), but the score shown next to each zone doesn't change. Practically: treat low scores as reference levels for light probes at most, mid scores as places to consider measured entries, and the highest scores as the levels the most sources and timeframes agree on — which still doesn't mean they can't break. The score measures agreement between methods; it is not a measured break rate.
A subtlety worth flagging: the tool runs the same scoring on every coin in the selector. On thinner markets, a few large limit orders can look like a meaningful order-book wall when it's really just one whale's resting orders, and volume clusters are built from less trading. If you're reading scores on anything outside BTC/ETH, treat them a little more sceptically before sizing up. The levels are computed the same way — it's how much weight they deserve that changes.
§5 · Why the 1.5 / 2.5 risk-reward thresholds matter
The risk-reward ratio (RR) in the trade plan is worked out per zone. For a support zone, the entry is the zone's midpoint, the stop sits below the zone's lower edge (by 0.8 of the zone's width), and the target is the midpoint of the next resistance zone above; RR = distance to target ÷ distance to stop. Resistance zones work the same way in reverse, for shorts. RR < 1.5 means don't take the trade, the payout is too poor — at RR 1 you have to win more than half your trades just to break even, and even at a 55% win rate the math is only 0.55 × 1 − 0.45 × 1 = +0.1 per unit, which trading fees and slippage can largely wipe out. RR 1.5 to 2.5 is the workable zone. RR > 2.5 is the opportunity zone, but watch out — when something looks too good, it usually means S1 is far away and you're modeling a stop that will probably trigger before R1 does, or R1 is so far away it won't realistically hit during the trade's expected duration. Read more in the companion piece: Risk-reward ratio math.
Pair the score and the RR together for sanity: a 90-point support with RR 1.2 can be a worse trade than a 65-point support with RR 2.3 — because a higher RR can make up for a lower chance of the level holding. The score isn't a hold probability, so the numbers below are only an illustration: if the first level held 85% of the time, expected value = 0.85 × 1.2 − 0.15 × 1 = +0.87; if the second held 70% of the time, expected value = 0.70 × 2.3 − 0.30 × 1 = +1.31. In that case the lower-score, higher-RR setup is the better expected-value play. This is why "trade like an insurance company" beats "trade like a fortune-teller" over long sample sizes — you don't have to be right about every level, you just need to consistently take positive-expected-value bets.
§6 · Data source (Binance fapi live, never hardcoded)
Every candle, swing high/low, and volume number comes live from the Binance Futures API (fapi.binance.com), with computation running entirely in your browser. No price level on this page is hardcoded; refreshing the page = fetching the newest data. If the futures endpoints can't be reached, the tool falls back to Binance's spot market-data endpoint for candles and the 24-hour ticker. The tool auto-updates every 60 seconds when auto-refresh is on, and you can also force-refresh manually. During API outages the tool shows a "Failed to load data" notice rather than stale data — I'd rather show you nothing than yesterday's number relabelled as today's. If you ever see a persistent blank state, don't suspect the tool first — go check Binance's main site for API status, it's usually them, not us.
§7 · How this tool compares to TradingView, exchange charts and MetaTrader
TradingView built-in S/R drawing tools vs my algorithm. TradingView's default approach to support and resistance is the manual horizontal-line tool — you draw a line at a price you think is meaningful and TradingView remembers it. It's a brilliant interface for visualisation, but it's not an algorithm — it's storage of your own opinion. The S/R lines you see in any random TradingView chart screenshot are some trader's hand-drawn guess, not algorithmic output. TradingView does have built-in pivot point indicators (Floor Pivots, Camarilla, Woodie, Fibonacci pivots), which are algorithmic — but they only use a single timeframe's worth of data (the prior day, week or month) and they only output one set of levels at a time. My tool differs in that it merges seven timeframes and three kinds of levels into one score — TradingView users have to overlay multiple pivot indicators manually and read the convergence themselves. Both approaches work; mine is faster, theirs is more customisable. If you're a pro discretionary trader, TradingView pivot points + your own hand-drawn lines on top are probably better than any auto-computed tool. If you're a newcomer who wants the math done for you, this tool is faster.
Exchange charts. The charts inside exchange apps range from a basic candlestick view with a few moving averages to a full TradingView embed with every standard pivot type. Even the good ones don't provide multi-timeframe overlap scoring — you have to read three timeframes side by side yourself, mentally noting where pivots overlap. Seasoned discretionary traders do this in their heads; newcomers can't reliably do it. That's the gap this tool fills: the convergence math done automatically.
MetaTrader 4 / MetaTrader 5 plugins. Many forex/CFD traders cut their teeth on MetaTrader before crypto, and they bring MT4/5 habits over — installing paid third-party "Auto S/R" plugins. These plugins do much the same job as my tool, but: (a) they're closed-source and paid, (b) most are tuned for forex liquidity which is different from crypto, (c) they run on the broker's MT4/5 instance which has very different data quality than spot crypto exchanges. If you're paying a yearly fee for an MT4 Auto S/R plugin on a crypto chart, you may well be getting worse data than a free tool that talks directly to the Binance API. This is the strongest case for the "use a crypto-native tool for crypto" point.
Four misuses to avoid. (1) Watching 1H exclusively — every trade looks like the world is ending or peaking on the 1H. Force yourself to check Daily before clicking any button. (2) Treating support as a guaranteed bottom — a support level is a probability statement, not a contract. Have a stop. (3) Confusing psychological round numbers ($100K) with algorithmic S/R — round numbers are a kind of S/R via retail behaviour, but they're behavioural support, not structural; they often break harder when they break, because everyone's stop is clustered there. The algorithmic levels in this tool are structural — they're where the actual money is sitting. Both matter, neither alone is enough. (4) Ignoring volume confirmation — a level that breaks on weak volume is much more likely to be a false break than a level that breaks on heavy volume. Always glance at the volume bar at the moment of the break before reacting. This tool doesn't show a volume confirmation flag or volume bars, so check volume on your exchange's chart before reacting to a break.
The 2024-08-05 Black Monday case study. On August 5, 2024, BTC dropped hard intraday before partially recovering. The catalyst was the Bank of Japan's rate hike, which started unwinding the yen carry trade — leveraged positions across many risk assets were cut at the same time. The support just below price was an area it had tested more than once in the weeks before — exactly the kind of "should hold" level retail had been buying into. It broke anyway. A stop set a sensible distance below the support band meant a small loss you had sized in advance; buying the dip with no stop because "support held last week" meant riding the whole drop with no plan for it. The lesson is not that S/R doesn't work — it's that tail events override S/R. Every actionable level you trade off should be paired with a stop, sized for the case where the level breaks. A common rule of thumb: size the position so that if S1 breaks and you stop out, you lose no more than about 1% of your total portfolio. That habit matters more than clever entry timing.
How institutional desks actually compute S/R. Bloomberg Terminal and Refinitiv Eikon (the two dominant institutional trading workstations) both ship algorithmic pivot point and Fibonacci overlay tools — and the algorithms underneath are the same families of pivot-point and Fibonacci tools that retail charting offers (this tool uses the Fibonacci side of that). The fancy expensive terminals do not, in fact, have secret S/R algorithms that retail doesn't get. The differences are: (1) institutional desks layer order-flow data on top — real-time depth-of-book from exchanges, dark pool prints, large block trades — which retail tools can't access cheaply; (2) institutional desks have human traders looking at the screens 24/7 making override calls; (3) institutional positions sizes are large enough that getting the levels wrong by 0.5% costs millions. For a retail trader with a small account, the algorithmic S/R is much the same as the institutional version — the gap is mostly in execution, sizing, and discretion, not in the math.
Three rules I'd want every reader to leave with. (1) Use 4H + Daily as your primary framing; only zoom into shorter timeframes for execution timing, never for thesis-forming. (2) Treat S/R as a zone, not a point; leave a 1-2% buffer below your S1 for your stop, and a 1-2% buffer below R1 for your take-profit. The midpoint is for reference, not for order placement. (3) Pair every entry with the risk-reward tool — don't trade a level just because it has a high score; trade it only when the RR to the next R1 is ≥ 1.5. Score tells you how much the methods agree on the level; RR tells you whether trading it is worth your capital. Both matter.
§8 · What to read next
→ How to calculate risk-reward ratio: what's a good one and how it pairs with win rate (so you understand the RR numbers this tool gives you)
→ How to read candlestick charts · 5 patterns (read the reaction at a support to judge a real vs fake break)
→ What is leverage · 1x to 100x real meaning (size your position so the RR math actually matters)
→ BTC full-history chart + halving countdown (zoom out for the macro framing this tool gives the tactical layer)