Stacked Footprint Imbalances: Row Size and Minimum-Volume Effects
Stacked imbalances look like strong signals, but their count depends on row size and on whether a minimum volume is required. Change either and the stack changes.
Short answer
A stacked imbalance is several consecutive price rows where one side exceeds the other by the imbalance ratio (TradingView's default is 300%). Smaller rows create more rows and more chances for small-number ratios to exceed the threshold; without a minimum-volume filter, a row with 3 versus 1 contract counts the same as 300 versus 100. Fix row size, set a minimum volume per row and keep the ratio constant before counting stacks.
How settings create or remove stacks
| Setting | Effect on stacks |
|---|---|
| Smaller rows | More rows, more imbalances, more stacks |
| Larger rows | Fewer, larger rows; stacks merge or vanish |
| No minimum volume | Tiny rows can qualify |
| Higher ratio | Fewer imbalances |
Worked example
Illustrative rows near a low: buy 3 / sell 1 (300%), buy 6 / sell 2 (300%), buy 9 / sell 3 (300%): a stack of three buy imbalances totalling 18 BTC of buying. On the same candle, with a 20 BTC minimum per row, none qualify. A trader using the first setting sees a strong signal; with the second, nothing.
Building a stack log
Log each stack you consider meaningful with the settings, the market, the location (at a level, at an extreme, mid-range) and what price did over the next N bars. After 50 entries, compare outcomes by location. Many traders find stacks at the extremes of a move behave differently from stacks in the middle of a range.
Keep settings fixed for the whole log. If you change row size halfway, start a new log; mixing settings makes the comparison meaningless.
Definitions differ
Tools differ on whether they compare bid and ask at the same price or diagonally (ask at one row versus bid at the row below). TradingView describes its comparison and the default 300% threshold; check your tool's definition before comparing stack counts across platforms. See TradingView Footprint vs Trade-Based Footprint: Data Differences and ChartsPod Footprint Setup: Row Size, Imbalance and Coverage Checks.
Set fixed rows and a minimum volume, then count stacks on a perpetual.
Open the live chart in ChartsPodCount stacked imbalances only with fixed row size, ratio and minimum volume, and record those settings.
Review Stacked Footprint Imbalances with bar replay before using it live.
Open ChartsPod replayQuestions readers ask
What is a stacked imbalance?
Consecutive rows where one side exceeds the other by the imbalance ratio.
Why do I see so many stacks?
Small rows and no minimum volume let tiny rows qualify.
What minimum volume should I use?
One that excludes rows too small to matter on that market; fix it once chosen.
Sources and methodology
Order-flow concepts are explained from first principles and from TradingView's documented footprint and CVD methods; ChartsPod features were checked on its public pages on 17 October 2026. All numbers in examples are illustrative, not recorded market data.
- TradingView: Volume footprint charts, a complete guide — intrabar method, row size, imbalance, repainting.
- 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.