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 six timeframes, runs three independent algorithms (Fibonacci retracement, swing high/low, pivot points), and merges everything into zones scored 0-100. The score tells you how many timeframes and how many algorithms agree on a given price level; the rest is your call. There is also a dedicated US/EU reader section below (§7) that compares this tool to TradingView pivot points, Coinbase Advanced Trade, Kraken Pro, MetaTrader plugins, and the way r/Bitcoin chart culture talks about S/R — because the gap between how American and European retail traders use S/R and how institutional desks actually compute it is enormous.
§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, typically 0.3-0.8% wide. 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, large limit orders are placed in clusters by institutional traders precisely to obscure exact intentions — a $50M buy at "$108,000" usually arrives as twenty smaller orders strung from $107,800 to $108,200. Second, market makers' quoted spreads at any moment are inherently a band, not a price — BTC's typical bid-ask spread on Binance Futures is 0.01-0.05% during normal liquidity and widens to 0.2-0.5% during stress. Third, retail-driven price discovery works through round-number psychology — the "$100K psychological support" everyone talks about is genuinely a zone from $99,500 to $100,500 because that's where retail places stops, take-profits and "I'll buy if it pulls back here" limit orders. 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 the most-used mid-frequency timeframe in crypto futures markets — most 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 break through, the market needs a consensus-level selling event, which is rare. The 100-point score in this tool is structured around exactly this: 1 timeframe hit = 0 base points, 2 timeframes aligned = 50 points, 3+ timeframes aligned = 70+ points. The more overlap, the higher the score, the harder the level is to break — full stop.
A practical example from the 2024-08-05 flash crash: in the hours before the BoJ-rate-hike sell-off, this tool would have flagged $58,000 as a multi-timeframe Daily + Weekly + Monthly support — the score would have been north of 80. It broke anyway. What this tells you is not that the tool was "wrong" but that multi-timeframe overlap measures the probability of a level holding under normal market conditions, not under 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 probability, 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
Each support / resistance band is computed by three independent algorithms — Fibonacci retracement, swing-high/low pivots, and a classical floor-trader pivot — then aggregated. The 100-point math is straightforward: number of algorithms that flag the same band (out of 3) × 30 points + number of timeframes that overlap on the band (out of 4) × 10 points. A "100-point support" means all three algorithms identified the level and all four timeframes overlap — historically this kind of level has very rarely been broken by a single candle, usually requiring macro news or a major liquidation cascade. A "40-point support" means one algorithm and two timeframes — useful as a reference, not as a primary entry. Practically: levels below 50 are positions for light probes only, not core size; 50-70 is the actionable zone for measured entries; 70+ is where you can size up with confidence; 85+ is the kind of level where you can defend a position aggressively because the historical break rate is single-digit percent.
A subtlety worth flagging: the scoring system is calibrated to BTC, ETH and the top-10 majors. For lower-liquidity altcoins (think DOGE or smaller), the scores tend to be artificially inflated because order books are thinner and a few large limit orders can create what looks like multi-algorithm convergence when it's really just one whale's resting orders. If you're reading scores on anything outside BTC/ETH, mentally discount by 10-15 points before sizing up. The S/R levels themselves are real — the score's calibration is just less reliable when the asset doesn't have the deep order book that the algorithm was tuned on.
§5 · Why the 1.5 / 2.5 risk-reward thresholds matter
The risk-reward ratio (RR) in the trade plan is "potential gain from current price to R1" divided by "potential loss from current price to S1." RR < 1.5 means don't take the trade, the payout is too poor — because almost no retail trader sustains a 60%+ win rate, and at RR 1 the expected value is negative even at 55% win rate (0.55 × 1 − 0.45 × 1 = +0.1 per unit, which is wiped out by trading fees and slippage). RR 1.5 to 2.5 is the workable zone, where most genuine signals fall. 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 is a worse trade than a 65-point support with RR 2.3 — because the higher RR compensates for the lower hold probability. The math: at 90-point hold probability ~85% × RR 1.2 → expected value = 0.85 × 1.2 − 0.15 × 1 = +0.87; at 65-point hold probability ~70% × RR 2.3 → expected value = 0.70 × 2.3 − 0.30 × 1 = +1.31. 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. BTC spot price is cross-checked against the Binance Spot endpoint for sanity (a fapi-vs-spot divergence is itself an early signal of market stress — large gaps usually precede squeezes). The tool auto-updates every 60 seconds when auto-refresh is on, and you can also force-refresh manually. During API outages or market closes, the tool will go blank rather than show stale data — that's the cost of live-data fidelity (we won't lie to you with yesterday's number relabeled 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 · For US / EU readers: how this tool compares to TradingView, Coinbase, Kraken, MetaTrader, and r/Bitcoin chart culture
This is the section US and European retail traders usually want first, so I've gone long here. The way Americans and Europeans access support/resistance differs structurally from how traders in Asia do it — different default platforms, different cultural conventions, different regulatory constraints. Worth being explicit.
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 fundamentally differs in that it merges six timeframes and three independent algorithms 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.
Coinbase Advanced Trade / Coinbase Pro charts. Coinbase's charts have improved dramatically since the 2023 rebuild but they ship with no S/R indicators at all — the chart is a candlestick view with a basic set of moving averages and RSI, and that's roughly the limit. There is no built-in pivot point overlay; you'd have to switch to a TradingView embed or pull data into a separate tool to compute support/resistance. The Coinbase consumer app (not Advanced Trade) doesn't even have full TA — just simple price lines. The implication for US retail: if you're getting your charting from the Coinbase consumer app, you have essentially zero algorithmic S/R. You're working from horizontal lines you drew yourself based on memory of where prior tops and bottoms were. That's a real disadvantage for newcomers — this tool fills that gap.
Kraken Pro. Kraken's pro charting is execution-grade and ships with TradingView under the hood — so the indicator library is the full TradingView set including all the standard pivot point types (Floor / Camarilla / Woodie / Fibonacci / DM). What Kraken Pro doesn't provide is the multi-timeframe overlap scoring my tool does — you have to read three timeframes side by side yourself, mentally noting where pivots overlap. Pro discretionary traders do this in their head; newcomers cannot reliably do it. So Kraken Pro is the right tool if you want institutional-grade execution and full TradingView TA; my tool is the right shortcut if you want the convergence math done automatically.
MetaTrader 4 / MetaTrader 5 plugins. Most American retail forex/CFD traders cut their teeth on MetaTrader before crypto, and they bring MT4/5 habits over — installing third-party "Auto S/R" plugins that cost $30-200 each. These plugins do exactly what my tool does, 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 $99 a year for an MT4 Auto S/R plugin on a crypto chart, you are getting worse data and worse computation 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.
The four misuses US/EU retail keep making. (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 "$58K support" 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 yet show a volume confirmation flag — that's on the roadmap — but the chart at the top right shows you the volume bars so you can do it manually.
The 2024-08-05 Black Monday case study. On August 5, 2024 (a Monday in US/EU hours), BTC opened around $58K and dropped to $49K by mid-day Asia time, before partially recovering. The catalyst was the Bank of Japan's unexpected rate hike, which started unwinding the yen carry trade — every leveraged risk asset on the planet sold off in sync. The $58K level had been a 4H + Daily support with score in the high 70s the prior Friday — exactly the kind of "should hold" level retail had been buying into. It broke anyway, and traders who had stops at $57,500 (a sensible distance below the support band) were saved with a 1% loss; traders who had no stop and "bought the dip" near $52K because "support held last week" took a 15-20% drawdown by Asia close. 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. The exact rule: position sizing such that if S1 breaks and you stop out, you lose ≤ 1% of total portfolio. That math has saved more traders than any clever entry timing.
r/Bitcoin chart culture vs algorithmic data. Anyone who spent time on r/Bitcoin during 2024 saw the phrase "$60K HUGE support" appear in roughly half the high-upvoted posts during pullbacks. The phrase is not algorithmically wrong — $60K was, at various points, a real support — but the way it's used in retail forums is religious rather than analytical. The data my tool produces would have said "$58.5K-$60.2K is a 65-point support, decent but not unbreakable" — which is calibrated and probabilistic. The Reddit version was "$60K SUPPORT" in caps, treated as a contract the market had signed. When $60K broke in March 2024 (and again in August), the same posters then declared "$55K is even STRONGER support." That cycle of moving certainty backward as each level breaks is not analysis; it's coping. Read the data, not the room.
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 roughly the same Floor Pivots / Camarilla / Fibonacci retracement that my tool uses. 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 using $5K-$50K of capital, the algorithmic S/R is genuinely the same as the institutional version — the gap is in execution, sizing, and discretion, not in the math.
Three rules I'd want every US/EU 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 whether the level will hold; RR tells you whether holding the level is worth your capital. Both matter.
§8 · What to read next
→ Risk-reward ratio · how to compute, what thresholds to use (so you understand the RR numbers this tool gives you)
→ How to read candlesticks · 7 key 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)