Volume Profile is a histogram of traded volume at each price over a chosen period. It is useful for describing where activity occurred; it does not, by itself, tell anyone what price will do next.
That distinction is the whole article. A profile can be calculated exactly once its data, price rows, session, and time range are fixed. The jump from a calculated map to a trade is still a hypothesis.
What Volume Profile actually measures
Volume Profile groups trading activity by price, rather than putting volume underneath each time bar. Sierra Chart describes its Volume by Price study as horizontal bars showing cumulative volume at each price increment over a specified period; TradingView likewise describes Volume Profile as activity at specified price levels over a selected period (Sierra Chart: Volume by Price, TradingView: Volume Profile basics).
Price volume traded at that price
101.00 ||
100.75 ||||||
100.50 ||||||||||| <- most volume in the chosen period
100.25 ||||
100.00 |
The horizontal bars are volume-at-price, not a forecast.The period is a modelling choice. A profile can cover a session, a fixed range, visible bars, or another defined window; platform documentation exposes those choices rather than treating one window as universal (Sierra Chart: Volume by Price settings, TradingView: Volume Profile types). Change the window and the profile can change. That is not a defect. It is why the window belongs in any rule.
POC, value area, and nodes
The Point of Control (POC) is the price row with the greatest volume in the profile. Both Sierra Chart and TradingView define it that way (Sierra Chart: Volume by Price, TradingView: Volume Profile basics).
The value area is the range of rows chosen to contain a selected share of the profile's volume. TradingView documents 70% as its typical default, while also stating that the percentage is configurable; Sierra Chart exposes a Value Area Percentage setting in the same spirit (TradingView: Volume Profile basics, Sierra Chart: Volume by Price settings). The number is a convention set by a platform or a trader, not a natural law of markets.
| Term | What it is | What it does not prove |
|---|---|---|
| POC | The highest-volume price row in the selected profile | Automatic support or resistance |
| VAH / VAL | The high and low boundaries of the chosen value area | A mandatory breakout or reversal point |
| High-volume node | A local concentration of volume | That price will attract price again |
| Low-volume node | A local thin area of volume | That price will be crossed quickly |
High- and low-volume nodes are descriptive labels for the shape. They can make a chart easier to read, but they should not be promoted into signals by vocabulary alone. MotiveWave explicitly notes that its Volume Profile study calculates no trading signals; TradingView calls the tool reactive because it shows activity that has already occurred (MotiveWave: Volume Profile, TradingView: Volume Profile basics).
Why the data source is part of the method
Volume Profile is only as specific as the data used to build it. Sierra Chart says accurate intraday Volume by Price work needs tick-by-tick data and warns that higher-timeframe historical bars can require an estimation of volume at price; TradingView says its profiles are calculated from lower-timeframe data and that the calculation logic varies by indicator (Sierra Chart: Volume by Price, TradingView: Volume Profile basics).
That matters especially when people move the idea from exchange-traded futures to spot FX or CFDs. The Bank for International Settlements classifies foreign-exchange turnover as an over-the-counter market, rather than a single central exchange record (BIS: Triennial FX and OTC derivatives survey). A platform's profile can therefore describe the activity in its feed without representing all global FX activity. Sierra Chart's own troubleshooting guide also notes that session times, timezone, tick size, and data completeness can produce different profiles (Sierra Chart: Volume by Price differences).
This is not an argument against using a profile. It is an argument against pretending that a broker's tick-volume picture is the entire market. For a cTrader trader, the feed, server time, session definition, and row size should be written down before results are compared.
What the evidence and the critics say
The arithmetic is objective: total the volume in each price row, identify the maximum, and apply the stated value-area method. The interpretation is not objective. “Acceptance”, “rejection”, and “fair value” are trader descriptions layered on top of a histogram.
The most common weak claim is hindsight. After price leaves a high-volume area, it is easy to call that area important. A usable methodology must say in advance which prior profile is used, when the reference becomes available, what counts as a touch or break, and what invalidates the idea. Otherwise every bar after the fact is a tidy explanation.
There is also a category error worth avoiding: Volume Profile is not Market Profile TPO. TPO maps time at price, while Volume Profile maps volume at price. Sierra Chart documents the two as separate studies, and TradingView defines the latter from traded volume at price (Sierra Chart: TPO Profile Charts, TradingView: Volume Profile basics). They may agree on a level. They do not measure the same thing.
How you'd actually test it
Start by freezing the map. Specify the instrument, data feed, timezone, session boundary, profile window, price-row size, and value-area percentage. Then write a rule that uses only information available at the time.
| Hypothesis | Rule that can be tested |
|---|---|
| Prior POC is a useful reference | At each session open, compare a pre-defined reaction rule at the prior POC with the same rule at matched random price offsets |
| Value-area exit carries information | Define a close outside VAH or VAL, a return condition, an entry, a stop, and a time-based exit before testing |
| Low-volume nodes change travel | Measure time and adverse excursion through pre-defined low-volume nodes against comparable non-node ranges |
The test needs costs, including spread, commission, slippage, and realistic session handling. Split the work into an in-sample period for rule design and an out-of-sample period for judgement. Then inspect results by instrument and regime rather than keeping only the best-looking window. Out-of-sample testing and how to verify a cTrader backtest explain why that separation matters; real trading costs explain why a frictionless profile rule is not enough.
realbacktesting is a trading-software studio for cTrader built around verifiable work: its published cBot figures are cTrader-native backtests that readers can reproduce in their own cTrader. The relevant standard here is modest: define the profile before the outcome, then see whether the rule survives unseen data and costs.
Frequently asked
Is Volume Profile the same as Market Profile?
No. Volume Profile groups volume by price, while Market Profile TPO groups time by price. They can be displayed together, but they answer different descriptive questions.
Is the POC support or resistance?
The POC is the highest-volume row in a selected profile. Whether it behaves as support, resistance, or neither is a separate hypothesis that needs a precise rule and a test.
Does Volume Profile work in forex?
It can describe the data feed used to create it. Because spot FX is over the counter, a profile from one broker or platform should not be treated as a complete record of global FX volume.
What is the best Volume Profile setting?
There is no universal setting. The range, session, row size, and value-area percentage are part of the strategy specification and should be fixed before testing.
The stubborn takeaway
Volume Profile can make past trading activity legible. It earns its place in a method only when the level, the rule, and the data source are all specified before the result is known.