How to Read Liquidity on a Bookmap Heatmap
A practical framework for reading resting liquidity, tracking how it changes, and confirming what happened with executed order flow instead of treating bright heatmap bands as predictions.
What the Bookmap heatmap actually shows
A Bookmap liquidity heatmap visualizes resting limit orders in the order book and preserves how those orders changed through time. Brighter areas represent larger concentrations of displayed passive liquidity, while darker areas represent lower displayed size. That makes the heatmap different from a conventional price chart: it adds a history of where participants were willing to rest bids and offers before and during a move.
Displayed liquidity is not the same thing as executed volume. A bright band can remain, grow, move, shrink, or disappear before price reaches it. The first job is therefore descriptive: identify where liquidity is concentrated and how that concentration behaves relative to current price and recent market structure.
Use a four-question liquidity framework
- Where is the liquidity? Compare the band with prior highs and lows, session extremes, value areas, and nearby structure instead of reading color in isolation.
- What is the liquidity doing? Note whether size is persistent, adding, pulling, migrating, or being consumed as price approaches.
- What actually traded? Compare executed volume, aggressor direction, footprint-style pressure, and delta/CVD with the displayed order book.
- What did price do afterward? A hold, rejection, acceptance, or clean trade-through changes the interpretation. Write the invalidation condition before judging the outcome.
Persistent liquidity, pulled liquidity, and consumed liquidity
Persistence matters because a level that remains visible through repeated tests is behaviorally different from a level that disappears as soon as price approaches. Pulling also matters, but it should not automatically be labeled manipulation: orders can be modified or cancelled for many legitimate reasons, and the screen alone does not prove a participant’s intent.
Consumption is different again. When aggressive orders repeatedly execute into a resting level, the key question is whether price continues through the level or struggles to make progress. A large amount of trading with little price movement can be consistent with absorption; large trading with steady price progress can be consistent with acceptance and continuation. The same visual intensity can therefore lead to different conclusions depending on execution and response.
Connect liquidity with volume and delta
Volume bubbles, footprint-style bid/ask information, and delta help answer a different question from the heatmap: what actually traded? Positive delta indicates more aggressive buying than aggressive selling over the measured interval, while negative delta indicates the opposite. CVD accumulates that difference over time. Neither measure tells you, by itself, whether price must continue in the same direction.
For example, aggressive buying into a large resting offer may produce positive delta. If price cannot advance and the offer remains or refills, the relationship can suggest passive selling is absorbing that aggression. If the offer is consumed and price accepts above the area, the same positive delta has a different context. The evidence is the relationship between liquidity, execution, and response—not one number.
Build a repeatable review instead of a prediction
- Capture the chart before price reaches the level.
- Mark the nearest persistent liquidity above and below price.
- Record whether the band adds, pulls, migrates, or is consumed.
- Record executed volume, delta/CVD behavior, and the first price response.
- Define what would invalidate the interpretation.
- Review the same checklist after the event without changing the rules after seeing the result.
This process turns a colorful heatmap into an auditable observation workflow. It is especially useful when comparing many sessions because the wording stays consistent even when the market outcome changes.
How KS8 fits into this workflow
KS8 Heatmap is an independent third-party Bookmap add-on. Its role is to organize liquidity, market structure, Volume Profile, footprint-style pressure, delta/CVD, VWAP, absorption, and scenario context into a more disciplined advisory view. It does not convert displayed liquidity into a guaranteed signal and it does not replace the need for suitable market data.
The strongest use of any order-flow tool is to make the evidence clearer and the review process more consistent. A heatmap can show where liquidity exists and how it changes; the analyst still has to distinguish observation from assumption.