Liquidity Heatmap Trading: How to Read It
A liquidity heatmap turns the order book into a picture: it paints the resting limit orders sitting at every price over time, so you can see the walls of liquidity the market is leaning on — before they get hit. Here is how to read one, and how heatmap trading actually works.
Senzoukria · Learn · Updated 13 September 2026
Most charts show you price. A liquidity heatmap shows you the orders behind the price — the resting limit orders stacked at each level, painted as a heat-coloured map that scrolls through time. Where a footprint chart tells you what aggressive traders already did, the heatmap tells you what passive traders are waiting to do. If you are deciding which of the three order-flow views answers your question, compare them in heatmap vs footprint vs DOM.
What the colours mean
Each horizontal row is a price level; the colour at any point is the amount of resting limit-order size sitting there at that moment:
- Hot / bright cells — a lot of resting liquidity. A bright horizontal streak is a liquidity wall: a large block of limit orders.
- Cool / dark cells — thin liquidity. Price tends to travel fast through empty zones because there is little to slow it down.
Because it scrolls with time, you do not just see the wall — you see how long it has been there and how it reacts when price approaches. That last part is the whole skill, and it comes down to how a band ends.
The three behaviours to read
1. Walls that hold (real liquidity)
Price drives into a bright band, heavy aggression hits it, and the band stays lit while price stalls. That is a large passive player absorbing the flow — the same event you would see as heavy volume with no progress on the footprint. These levels become meaningful support or resistance. See absorption in trading for how to confirm it.
2. Walls that disappear
Displayed size may be executed, cancelled or replaced. Compare book updates with trade records before attributing the change. Missing updates and aggregation also matter. A disappearing band alone does not establish spoofing or intent.
3. Replenishment
Repeated executions with renewed displayed size can suggest replenishment. That is not proof of a native iceberg or of a single participant. Several orders can contribute to the same level. Order-level data adds detail, but its available fields determine what can actually be established.
Trading with a liquidity heatmap
Heatmap trading is not about the wall itself — it is about how the wall behaves when price finally reaches it. The heatmap does not tell you a level will hold; it lets you watch, in real time, whether it holds, pulls or refills, and that behaviour is the read you act on:
- Into a wall that holds — resting size absorbs the aggression and price stalls: the level is being defended, a reference for support or resistance.
- Into a wall that pulls — the band vanishes as price approaches: the brake everyone was watching is gone, and the move often accelerates through the vacated zone.
- Through thin, dark zones — little resting liquidity means little to slow price down; these are where the fast moves travel.
In practice, heatmap trading is done next to the tape, not instead of it — the heatmap shows where the size is waiting, the footprint shows whether aggressors are eating through it. Neither is a signal on its own.
Heatmap + footprint: displayed size vs executions
The two views answer different questions, which is exactly why they pair well:
- Heatmap = resting, passive, displayed liquidity. Where is the size waiting?
- Footprint = executed, aggressive, action. Who is hitting that size, and is it holding?
A wall on the heatmap plus heavy bid volume and stalling delta on the footprint at the same price is consistent with absorption; confidence depends on the data and repeated observations.
Key takeaway: a liquidity heatmap is a map of where the market keeps its fuel. Bright walls are decisions waiting to be made — your job is to watch whether they defend (absorb), pull (displayed size removed), or refill (replenishment) when price finally tests them.
How to read a heatmap: a worked observation
Hypothetical example: 120 contracts are displayed at one ask price. During the next interval, 80 contracts trade there and 100 remain displayed. These totals are consistent with net additions of 60 contracts if coverage is complete. They do not identify a single hidden order: cancellations, additions and several participants can coexist.
- Record source, instrument, depth coverage and color scale.
- Mark a persistent band before price reaches it.
- Match executions to book changes at the same price and time.
- Record whether price stalls or continues, including counterexamples.
- Test a written rule with realistic costs before using it as a strategy.
CME explains Market by Order and Market by Price: order-level and aggregated data expose different details. Neither a trade-only archive nor ordinary OHLC candles recreates missing book history.
A liquidity heatmap also differs from a liquidation heatmap, which models possible liquidation levels. Keep the source and estimation method explicit. For a research protocol, see futures backtesting.
Common mistakes
- Trading a wall the moment you see it, before price has tested how it behaves.
- Ignoring pulled liquidity — a vanished wall is a signal, not a non-event.
- Reading the heatmap without the tape. Resting size only matters once aggression meets it.
See it on live data
Senzoukria renders a native liquidity heatmap next to the footprint from your NinjaTrader, Apex / Rithmic or crypto feed, so you can watch walls form, hold and pull in real time on the market you actually trade. Start with a $9 first month, then $29.
Frequently asked questions
- What is a liquidity heatmap?
- A liquidity heatmap is a time-based visualization of the order book (DOM). For every price level it colors how much resting limit-order size is waiting there — brighter or hotter means more liquidity. It shows displayed liquidity, unlike a footprint, which shows executed aggressive volume.
- What is the difference between a heatmap and a footprint chart?
- A footprint shows what already traded — aggressive market orders that executed. A heatmap shows what is resting and waiting — passive limit orders that have not been hit yet. One records executions; the other records displayed liquidity. Reading them together tells you where big orders sit and whether aggressors are eating through them.
- What does a bright wall on the heatmap mean?
- A bright horizontal band is a large block of resting limit orders at one price — a liquidity wall. If it sits below price it often acts as support; above price, resistance. The key question is whether it holds and absorbs incoming aggression, or gets pulled (cancelled) as price approaches.
- Can you trust liquidity walls — what about spoofing?
- Not blindly. No. Compare disappearing size with executions, cancellations and data coverage. The image alone does not prove intent or spoofing. A persistent level with executions and little price progress is consistent with absorption, not a guarantee of a reversal.
- What is a heatmap in trading, in plain terms?
- It is the order book (DOM) painted over time instead of read at a single instant: every resting limit order, at every price, colored by size, scrolling forward. An order-book snapshot shows you liquidity right now; a heatmap shows you where it has been sitting, growing or draining — which is what lets you tell a real wall from one that just appeared.
- How do you read a liquidity heatmap, step by step?
- Five steps. 1. Read the colour scale and the unit it encodes — contracts, lots or notional — together with the depth coverage the feed provides. 2. Locate the bands that persist across several minutes, rather than the size that flickers in and out. 3. Compare each band with the executions printed beside it at the same price and time. 4. Watch what the band does as price arrives: size consumed by trades that print, or withdrawn before they print. 5. State what the available data cannot separate — a band that vanishes without matching executions may have been cancelled, and displayed size never includes hidden orders.