Guide
Bitcoin Liquidation Heatmap, Explained
A liquidation heatmap estimates where leveraged positions would be force-closed if price reached those levels, and paints the dense zones as bright bands. This guide explains how the map is built, how to read it, why price so often travels toward the brightest zones — and how to tell a magnet from a mirage.
What a liquidation heatmap actually shows
Every leveraged position has a price at which the exchange force-closes it. A liquidation heatmap takes what is known about open positions — open interest, typical leverage tiers, entry zones — and estimates where those forced closes stack up. Price levels with many estimated liquidations render as bright bands; quiet levels stay dark.
The key word is estimates. Exchanges do not publish every trader's liquidation price, so heatmaps model them from aggregate data. Different tools make different assumptions, which is why two heatmaps of the same market rarely agree exactly.
Read it as a map of potential forced flow: if price reaches a bright band, a burst of involuntary market orders is likely to fire there. That is information about future fuel, not a promise of direction.
How to read the map
Bright zones above current price are mostly short liquidations: traders betting on a fall get squeezed if price rises into them, and their forced buy-backs push price further up. Bright zones below price are long liquidations: forced selling that accelerates a drop.
The often-quoted magnet effect comes from this mechanic. Dense liquidation clusters are pools of forced orders waiting to fire, and markets tend to travel toward liquidity. When BTC grinds upward just below a bright band, sweeps it, and reverses — that is the classic liquidity run: the cluster was fuel for the last leg, and once burned, the move had nothing left.
Cascades are the second pattern. When one cluster fires, the forced orders can push price into the next cluster, chaining liquidations into a violent single-direction move. The huge wicks on crypto charts during volatile days are usually cascades, not considered selling or buying.
Timing matters too: clusters build up over days as positions accumulate, and the map redraws as open interest changes. A band that sat untouched for a week is heavier than one that appeared an hour ago.
Liquidation heatmap vs order-book heatmap
These two get confused constantly. An order-book heatmap (the Bookmap or TradingLite style) shows real resting limit orders — liquidity that exists right now and can be pulled at any moment. A liquidation heatmap shows estimated forced market orders that would fire only if price reaches the level.
One is displayed intent, the other is modeled obligation. Resting orders can vanish; liquidations, once triggered, cannot be cancelled. That makes liquidation clusters more reliable as fuel, but less precise in location, since they are estimates rather than displayed orders.
| Order-book heatmap | Liquidation heatmap | |
|---|---|---|
| What it shows | Real resting limit orders | Estimated forced closes |
| Can it disappear? | Yes — orders get pulled | No — fires if price arrives |
| Precision | Exact prices, live | Modeled zones, approximate |
| Best use | Spotting defense and spoofing | Mapping fuel for the next move |
How traders actually use it
The practical workflow has three steps. First, mark the dense clusters above and below price at the start of the session — these are the candidate destinations. Second, when price approaches a cluster, switch attention to executed flow: footprint and delta tell you whether the move into the zone is being absorbed or accelerating. Third, judge what happens after the sweep: exhaustion and a delta flip right after a cluster fires is one of the cleaner reversal contexts crypto offers.
The mistake to avoid is trading the map alone. A bright band is a hypothesis about fuel; the footprint at the level is the evidence. Liquidation data also differs by venue — a cascade can start on one exchange before the rest react — so a multi-venue read is materially safer than a single feed.
Used this way, the heatmap answers where to pay attention, and order flow answers what to do when you get there.
Limits and honest caveats
Heatmaps are built from assumptions about leverage that are sometimes wrong, they cannot see positions hedged elsewhere, and they say nothing about whether large players will defend a level before price ever reaches the cluster. Treat the brightness as relative, not absolute: the value is in comparing zones against each other, not in any single number.
They are also least useful in quiet, low-leverage regimes — when open interest is thin, the map is mostly noise. Their edge concentrates exactly where crypto is most dangerous: crowded, over-leveraged markets.
Frequently asked questions
Are liquidation heatmaps accurate? They are estimates modeled from open interest and typical leverage, not exact data. Zones are directionally useful — dense vs quiet — but individual prices are approximate, and different tools disagree.
Why does price move toward liquidation clusters? Clusters are pools of forced orders. Markets seek liquidity, and a dense cluster offers fuel: sweeping it fires involuntary market orders that pay the other side. That is the magnet effect.
What is a liquidation cascade? A chain reaction: one cluster fires, the forced orders push price into the next cluster, and so on. Cascades produce the violent wicks typical of leveraged crypto sell-offs and short squeezes.
What is the difference from a Bookmap-style heatmap? Bookmap-style maps show real resting limit orders that can be cancelled. Liquidation heatmaps show estimated forced market orders that cannot be cancelled once triggered — fuel rather than displayed intent.
Do liquidation heatmaps work for altcoins? Best on liquid perpetuals like BTC and ETH, where open interest is deep and models have data to work with. On thin alts the estimates get noisy and a single whale can invalidate the picture.
Should I trade reversals off every bright band? No. The band tells you where forced flow may fire, not which way price resolves. Confirm with executed order flow at the level — absorption and delta behavior after the sweep — before acting.