Crypto anchored volume profile groups traded volume into price bands from a chosen starting point to a declared endpoint. It shows where activity was concentrated within that market and window, while anchored VWAP compresses the same history into an average. Fix the anchor, price-bin size, volume units and venue before reading a point of control or comparing profiles.
A longer horizontal histogram row means that more recorded volume was assigned to that price band. It does not show an inventory of resting orders, prove that buyers are still holding, or guarantee a reaction when price returns. The useful starting question is specific: where did this instrument trade after the event I selected?
The anchor selects history; the bins retain its shape
An anchored profile needs both a time window and a price grid. The start can be a timestamped event, a declared daily boundary or a pivot that has already been confirmed. The endpoint is the latest observation included in the calculation. TradingView's anchored volume profile documentation describes its drawing tool as accumulating from a manually chosen start through the available bars.
Within that window, a trade-based profile assigns each execution's quantity to the band containing its price, then sums quantities within each band. Declare how boundaries work: for example, a band from 100 inclusive to 101 exclusive contains a trade at 100.50 but assigns a trade at exactly 101 to the next band.
Anchored VWAP instead divides total price-times-quantity by total quantity. It can describe the weighted center without retaining whether volume formed one cluster or several separated clusters. The VWAP anchor worksheet explains that average and its window choices. A volume profile adds a distribution, rather than supplying a better version of the same line.
Neither calculation is the order book. Volume records completed activity; available depth concerns orders currently offered. Review the slippage and order-book depth worksheet before treating a broad historical node as liquidity available to an order now.
Read the labels without adding a forecast
The point of control, or POC, is the row with the largest recorded volume. A high-volume node is a local concentration; a low-volume node is a relatively thin area between concentrations. Their appearance depends on the grid as well as the observations.
A value area highlights a selected portion of volume. TradingView describes 70% as a common setting, with its own procedure for choosing rows around the POC. Record the target and implementation rather than assuming every tool produces identical boundaries. Its volume profile concepts guide defines these labels and the calculation approach.
The percentage is a share of historical volume, not a probability that future price will remain inside the area. Nor does the highest-volume row identify a guaranteed support level. A candidate price zone still needs a separately defined visit and failure rule, as in the support and resistance worksheet.
Worked example: one trade set, two different grids
The following hypothetical TOKEN/USDT spot data contains five executions after a predeclared 13:00 UTC event and before a 14:00 snapshot. Quantities are base-token units. Each execution occurs at the exact price shown; this is deliberately simpler than reconstructing a profile from candles.
Use one-USDT bands aligned at 98, with lower boundaries included and upper boundaries excluded.
| Execution price, USDT | Base quantity | Assigned band | Price × quantity, USDT |
|---|---|---|---|
| 98.50 | 2 | 98–99 | 197.00 |
| 99.50 | 8 | 99–100 | 796.00 |
| 100.50 | 18 | 100–101 | 1,809.00 |
| 101.50 | 12 | 101–102 | 1,218.00 |
| 102.50 | 5 | 102–103 | 512.50 |
| Total | 45 | All five bands | 4,532.50 |
The POC is the 100–101 band, with 18 of 45 units, or 40% of volume. The exact trade-weighted average is 4,532.50 ÷ 45 = approximately 100.72 USDT. The POC is a band; assigning its midpoint as a displayed label does not establish that every execution happened at the midpoint.
Now merge adjacent rows into two-USDT bands, keeping the grid aligned at 98:
| New band | Included quantities | Total base volume |
|---|---|---|
| 98–100 | 2 + 8 | 10 |
| 100–102 | 18 + 12 | 30 |
| 102–104 | 5 | 5 |
The largest row now covers 100–102 and contains 66.67% of volume. No trades changed. The grid broadened the apparent concentration, while the trade-weighted average stayed at 100.72. A rule using “within 0.10 of the POC” is therefore incomplete unless it defines the row boundaries and which representative price it uses.
TradingView offers row-count and ticks-per-row settings, with tick rounding affecting the resulting rows. That implementation detail is documented in its anchored profile inputs. Save the actual grid, not just a screenshot or requested row count.
A moving POC can be a legitimate update
Continue the first example with another hypothetical 30 units trading at 102.50 after the snapshot. The 102–103 band rises from 5 to 35 units and becomes the POC. Total volume is now 75 units; total traded value is 7,607.50 USDT. The average rises to approximately 101.43.
That update does not mean the earlier snapshot was wrong. The developing window contains new evidence. In a historical test, preserve the profile available at each decision time. Using the final day's POC for a morning decision borrows future trades.
If the event anchor comes from a breakout, specify when the breakout was observable. The Donchian breakout guide addresses prior-window boundaries; its price observation can define an event without making subsequent volume available in advance. Do not keep moving the anchor to whichever later swing creates a more convincing profile.
The feed determines what the profile can claim
A profile from one spot pair describes that dataset. A perpetual contract, another venue or a different quote asset supplies different observations. Do not add base units, quote turnover and contract counts as if they were equivalent. The volume confirmation guide provides the unit and venue checks.
For a concrete raw-data example, Binance's Spot market-data API exposes execution price, quantity and time in trade responses. Its aggregate-trade endpoint compresses qualifying executions. A custom reconstruction must preserve the chosen instrument, interval coverage and quantity definition; those fields do not establish global crypto volume.
Chart profiles may approximate price allocation using lower-timeframe bars. TradingView documents lower-timeframe selection and a fallback to chart resolution when older detailed data is unavailable. A long anchor can therefore have different detail from a recent one. Check the anchored profile calculation limits before comparing narrow nodes across histories.
An up/down color split also needs its own definition. TradingView's general profile guide describes bar-direction classification rather than direct buyer/seller identification. Synthetic chart prices add another problem: its guide warns that nonstandard charts can distort profile data. The Heikin Ashi execution-price guide explains why a smoothed candle should not silently replace the underlying traded series.
Keep a profile specification beside the observation
| Field | Record before interpreting the profile |
|---|---|
| Instrument | Venue, exact symbol, spot or derivative, volume unit |
| Window | Anchor timestamp and reason, endpoint, inclusion rule |
| Availability | When the anchor and each input became observable |
| Grid | Band width, grid origin, boundary convention, tick rounding |
| Method | Trade-based allocation or documented bar approximation |
| Labels | POC tie rule, value-area target and selection algorithm |
| Failure policy | Pause comparisons when coverage or units cannot be reconciled |
If two profiles disagree, compare this record before inventing a market explanation. Missing trades, a changed grid or a different instrument can alter the shape without any new trading insight. Any entry or exit rule based on that shape still needs separate testing with costs and executable prices.
This AI-assisted educational article follows the editorial policy. The examples teach distribution and data checks; they do not establish a profitable strategy or a particular KLINEO volume-profile implementation.