Order-Book Heatmap vs Liquidation Heatmap: Which Data Do You Need?
An order-book heatmap shows orders that actually rested in the book. A liquidation heatmap shows where leveraged positions might be liquidated, usually estimated by a model. They answer different questions.
Short answer
Use an order-book (liquidity) heatmap when you need to know where real limit orders rested and whether they were pulled or filled. Use a liquidation heatmap when you want an estimate of where leveraged positions could be forced to close; such maps are typically modelled from open interest, leverage assumptions and price history, not observed orders. Liquidations themselves trigger on mark price under each exchange's margin rules. ChartsPod shows a liquidity heatmap, the live L2 book and recorded liquidations.
Observed orders versus modelled levels
| Question | Use |
|---|---|
| Was there a large bid at this level before the drop? | Order-book heatmap |
| Was it filled or pulled? | Order-book heatmap plus footprint |
| Where might leveraged longs be forced out? | Liquidation estimate |
| Did liquidations actually happen? | Recorded liquidation events |
How liquidations actually trigger
Exchanges liquidate positions based on mark price and margin requirements, not the last traded price on your chart. Bybit's liquidation process, for example, depends on margin mode and uses mark price as the trigger. A liquidation estimate that ignores margin mode and leverage mix can place levels in the wrong place.
Worked example: reading both maps around one drop
Illustrative case on a BTC perpetual. Before a fall, an estimated liquidation map shows a cluster of long liquidations roughly 2% below price. The order-book heatmap shows a band of resting bids about 1.5% below price that has been persistent for several hours.
Price drops 1.5% and reaches the bid band. The footprint shows heavy aggressive selling into it; the band shrinks but does not disappear, and price pauses. Then the band is pulled, price falls another 0.6%, and recorded liquidations spike. Open interest falls sharply in the same minutes.
What happened is visible only by combining the views: the resting bids absorbed the first wave, their withdrawal let price reach the area where leveraged longs were exposed, and forced selling followed. The liquidation map estimated the area roughly; the recorded events confirmed it; the order-book heatmap explained why price paused first. Write all three observations, with venue and timestamps, rather than crediting the outcome to one map.
Using both without confusing them
- Mark estimated liquidation zones as hypotheses, labelled with the model and time.
- Check the order-book heatmap for real liquidity near those zones.
- When price arrives, read the footprint and recorded liquidations.
- Record whether estimated levels matched actual liquidations.
Watch the liquidity heatmap, footprint and recorded liquidations together on a perpetual.
Open the live chart in ChartsPodRelated: TensorCharts vs ChartsPod: Compare Crypto Heatmap Coverage, Aggr.trade Liquidation Prints: Check Venue Coverage and Event Timing, ChartsPod Heatmap History: Live Sessions and Missing Depth.
Treat order-book heatmaps as evidence of past liquidity and liquidation heatmaps as estimates. Confirm both against what traded.
See Order-Book Heatmap vs Liquidation Heatmap on live data in the free ChartsPod terminal.
Open the ChartsPod terminalQuestions readers ask
Is a liquidation heatmap real data?
Usually it is an estimate based on open interest and leverage assumptions. Actual liquidations are separate recorded events.
Does ChartsPod have a liquidation heatmap?
ChartsPod lists a liquidity (order-book) heatmap and liquidation data among its derivatives tools. Check the terminal for the exact views available.
Why didn't price reverse at a liquidation cluster?
Estimated levels can be wrong, and even real cascades can be absorbed or extended depending on book liquidity.
Sources and methodology
ChartsPod capabilities were checked against ChartsPod's public pages (home, docs, markets and indicators) on 17 October 2026. Third-party facts come only from the official sources listed. Venue availability inside ChartsPod is shown per tool, so confirm the exact exchange and contract in the terminal before relying on a feature. Worked examples use clearly labelled illustrative numbers, not recorded market data.
- Bybit: Liquidation process — mark price and margin modes.
- Binance: USD-M Futures market data API — trades, depth, funding and open interest.
- ChartsPod: product overview, pricing and FAQ — free terminal, venues, modules, no order placement; checked 17 Oct 2026.
This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.
CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.