[Canonical article](https://algoway.trade/blog/vwma-volume-price-weighting.html)

Published: 2026-11-12. Modified: 2026-11-12.

# VWMA vs SMA: How Volume Changes the Trading Signal

![Equal price weights compared with a larger volume weight pulling the average lower](https://algoway.trade/static/img/blog-img/vwma-volume-price-weighting.jpg)

The prices are identical. The moving averages are not. That is possible when one average gives every candle an equal vote and the other lets volume decide how much each vote counts.

**VWMA is a rolling average of prices weighted by their bars' volume. SMA gives each price equal weight.** Comparing them over the same window isolates the effect of volume weighting. It does not establish that one line predicts the next trade better.

For TradingView automation, this distinction belongs in the signal definition. A price crossing VWMA and VWMA crossing SMA are different events. When using [AlgoWay to automate TradingView alerts](https://algoway.trade/blog/automate-tradingview-alerts-to-any-broker-with-algoway.html), decide which event should create the alert before configuring the execution route. A connector cannot resolve an ambiguous trading rule.

## Calculate both averages from the same prices

For a window of N bars, using closing prices:

- SMA = sum of closes / N.
- VWMA = sum of (close × volume) / sum of volume.

[TradingView's VWMA documentation](https://www.tradingview.com/support/solutions/43000592293-volume-weighted-moving-average-vwma/) describes this difference in weighting. The denominator matters: dividing the weighted price total by the number of bars would not produce VWMA.

Here is a hypothetical three-bar window. The units of volume are consistent within each example; these are arithmetic illustrations, not market observations or backtest results.

| Bar, oldest first | Close | Volume A | Close × volume A | Volume B | Close × volume B |
| --- | --- | --- | --- | --- | --- |
| 1 | 100 | 10 | 1,000 | 90 | 9,000 |
| 2 | 102 | 10 | 1,020 | 10 | 1,020 |
| 3 | 104 | 80 | 8,320 | 10 | 1,040 |
| Total | 306 | 100 | 10,340 | 110 | 11,060 |

SMA is 306 / 3 = **102** in both cases. With volume A, VWMA is 10,340 / 100 = **103.40**. With volume B, it is 11,060 / 110 = **100.55**, rounded to two decimals.

The closes rise in both examples, yet volume B puts VWMA below SMA. The oldest, lowest close carries most of the weight. Consequently, “VWMA below SMA” does not mean that the latest candle fell or that the closes in the window are declining.

## What the gap between the lines actually measures

For matching windows and price sources, subtracting SMA from the weighted average gives:

**VWMA − SMA = sum of [volume × (close − SMA)] / sum of volume.**

This identity explains the example without a story about buyers winning or sellers losing. More weight on prices above the window's ordinary mean pulls VWMA upward; more weight below it pulls VWMA downward. The gap describes how volume and price levels line up inside that window.

Two useful checks follow from the arithmetic. Equal volume on every bar makes VWMA equal SMA. Multiplying every volume in a window by the same positive constant leaves VWMA unchanged, because the numerator and denominator grow together. A larger total volume alone does not force the average higher.

With nonnegative volumes and a positive total, the weighted average also stays between the lowest and highest prices used in the calculation. If your hand calculation violates that bound, check the denominator and bar alignment before blaming the market.

## A rolling window is not a session anchor

A three-bar VWMA replaces its oldest observation when a new bar enters. That departing bar loses its entire contribution, including its volume weight. A line can therefore shift because a heavily weighted old bar leaves, not just because the latest close makes a large move.

VWAP can also weight prices by volume, but [TradingView's VWAP](https://www.tradingview.com/support/solutions/43000502018-volume-weighted-average-price-vwap/) accumulates from its selected anchor and resets according to that setting. Its default price source is HLC3. Comparing a close-based rolling VWMA with a session VWAP can change both the window and the price source. Our [VWAP reset guide](https://algoway.trade/blog/vwap-session-reset-anchor-period.html) explains that separate choice.

## Turn the comparison into one testable event

Suppose the intended rule is a bullish VWMA/SMA crossing on completed bars. Define it as VWMA at or below SMA on the previous completed bar, then strictly above SMA on the current completed bar. That is different from repeatedly entering whenever VWMA remains above SMA.

A close crossing above VWMA asks another question. It compares one price with an average, rather than comparing weighted and unweighted averages. Neither rule automatically specifies an exit, stop distance or order size. Write those decisions separately, and handle unavailable prices or volume explicitly rather than silently replacing missing values with zero.

Before comparing chart signals, hold the symbol feed, timeframe, price source, length and evaluation timing fixed. Then inspect the volume inputs and the bar that left the window. If crossings remain frequent in sideways prices, volume weighting has not repealed whipsaws; the [moving-average crossover guide](https://algoway.trade/blog/moving-average-crossover-whipsaws.html) discusses the trade-offs of filters.

The first useful test is modest: reproduce a few completed-bar values and explain every difference between the two lines. Profitability is a separate question that requires costs, exits and out-of-sample evidence.