VWAP settings
Best VWAP settings for day trading: a testable starting point
Most day-trading tests can start with a session anchor, HLC3 source, zero offset, and no bands. Add a setting only when it answers a written question.
Direct answer
There is no universal best VWAP setting. For liquid US stocks and ETFs, a sensible first test is Session anchor, HLC3 source, zero offset, and a 5-minute chart. Treat 1-minute and 15-minute charts as separate tests. Add standard deviation bands only after the base VWAP rule has a clear entry and exit.
What to set before testing
Anchor
Session
Price source
HLC3
Offset
0
First chart
5-minute bars
A starting settings sheet
These values are test inputs, not claimed winning parameters. Keep each test version named and dated.
| Input | Starting value | What to compare |
|---|---|---|
| Anchor period | Session | Week or month only when the research question spans more than one session |
| Source | HLC3 | HL2 or close in a separate run with all other settings fixed |
| Chart timeframe | 5 minutes | 1 minute for more noise and fills, 15 minutes for fewer signals |
| Bands | Off at first | Then test 1 and 2 standard deviations without changing the base entry |
| Offset | 0 | A nonzero visual shift should not be used to create a trading signal |
A test workflow you can audit
- 1
Pick one market and session
Start with SPY regular trading hours. Write whether premarket volume is excluded and keep the timezone fixed.
- 2
Test the base line
Use HLC3, Session anchor, zero offset, and no bands on 5-minute bars. Define the signal on bar close.
- 3
Change one input
Compare 1-minute, 5-minute, and 15-minute charts in separate runs. Do not change the stop or exit while comparing the chart interval.
- 4
Reserve later sessions
Choose a setting on the first sample, then check it on at least 20 later SPY or QQQ sessions with costs included.
Notes from the chart review
These checks keep the rule separate from the story told after a move has already happened.
When I test SPY, I begin with the plain session VWAP. I do not add bands until I can explain what the base line is supposed to filter.
When I compare QQQ on 1-minute and 5-minute bars, I record the signal time and next tradable price. The chart close is not automatically the fill.
When I review AAPL settings, I keep the losing sessions in the sample. Removing them because news made the day unusual would rewrite the test after the fact.
Generate a settings matrix without hiding assumptions
Pineify can expose anchor, source, timeframe filter, band multiplier, commission, and slippage as inputs. You can inspect the generated code before running it.
Create a Pine Script v6 strategy for SPY with Session VWAP and HLC3 source. Use closed 5-minute bars, zero offset, and optional 1 or 2 standard deviation bands. Add inputs for commission, slippage, session hours, stop distance, and long-only or short-only tests. Show every input in the code and do not promise returns.Why the default is a starting point
TradingView documents HLC3 as the default source and Session as one available anchor period. Defaults make a clean baseline because another tester can reproduce them.
A default is not proof of an edge. The result still depends on the market, session, signal rule, exit, costs, and sample dates.
Timeframe changes the test
VWAP may calculate from the same underlying session while the strategy reads different chart bars. A 1-minute cross can appear and disappear inside a 5-minute bar. A closed 15-minute rule reacts later and produces fewer decisions.
- Name the chart timeframe in the strategy title and saved result.
- Use closed bars unless the test explicitly models intrabar execution.
- Apply the same commission and slippage assumptions to every timeframe.
Bands need their own reason
Standard deviation bands measure distance around VWAP. They do not turn the indicator into a probability forecast. A touch can continue, reverse, or stall.
Test a band as an entry filter, target, or risk boundary in separate runs. Combining all three roles at once makes it hard to tell which rule changed the outcome.
Continue the VWAP research
VWAP indicator for TradingView
Review the indicator formula, inputs, bands, and Pine Script implementation.
VWAP calculator
Calculate a volume-weighted average from price and volume rows.
VWAP trading strategy
Study rule-based VWAP entries and exits before testing a setup.
VWAP strategy optimizer
Compare VWAP parameters without hiding costs or holdout results.
Sources
- Volume Weighted Average Price (VWAP)
TradingView Help Center. Documents the VWAP formula, anchor periods, source input, bands, and timeframe behavior. Checked July 18, 2026.
Frequently asked questions
This page is an educational information tool, not investment advice or a recommendation to trade. Examples are test definitions, not live signals, historical results, or promises of returns. VWAP is based on past price and volume, and actual fills can differ from chart prices. Check current market data, costs, product rules, and your own risk limits before trading.
Tools for the next test
What Is VWAP?
Learn the VWAP formula, session reset, chart meaning, and calculation limits with a small worked example.
VWAP Reclaim Strategy
Define a closed-bar VWAP reclaim, entry, invalidation, session window, and cost assumptions before testing.
VWAP vs Anchored VWAP
Compare session VWAP and Anchored VWAP by starting point, reset, timeframe, and test use case.
VWAP Calculator
Calculate VWAP (Volume Weighted Average Price) from OHLC and volume data. Supports anchored VWAP from specific dates for institutional trading levels.
Backtesting Calculator
Analyze the historical performance of your trading strategy using win rate and risk-reward ratio.
Put the VWAP rule in writing
Pineify turns a plain-language setup into Pine Script you can read, edit, and test. The script does not predict the next price.
Build a VWAP test rule