Definition: what Williams %R measures
Williams %R (often written Williams %R or %R) is an indicator that puts the latest price into context of a recent trading range. It compares the current price to the highest high and lowest low over a chosen lookback period (for example, 14 periods). The result is scaled into a bounded range (commonly shown from 0 to −100).
A useful way to interpret it is relative position, not prediction. When %R is near one end of its scale, the current price is near the corresponding extreme of the lookback window; when %R is near the other end, it is near the opposite extreme.
Simple model: how to read the scale
A basic interpretation framework is:
- If %R is closer to 0 (the “upper” end of the scale), the current price is nearer the recent highest high.
- If %R is closer to −100 (the “lower” end), the current price is nearer the recent lowest low.
This makes %R a “range position” indicator: it tells you how far price has traveled within a recent high–low corridor. Because the lookback window is part of the calculation, the indicator’s meaning depends on the time horizon you choose. A %R value computed over a short window can react quickly to recent swings; a longer window typically smooths the effect of any single move.
Assumptions for interpretation
To interpret any numerical reading, you need to know (or assume) two things:
- the lookback period used to compute the high–low range, and
- the price input used in your platform (commonly the close, but implementations can vary).
Without those assumptions, the same displayed %R value can represent different underlying ranges.
Evidence or example: what you can check on your own chart
You can verify the interpretation mechanically by checking the lookback window:
- Pick a chart setting for the %R lookback period.
- Identify the highest high and lowest low over that exact number of periods.
- Locate the current price and compare whether it is close to the recent high or close to the recent low.
- Confirm whether the displayed %R is correspondingly near the end of the scale.
If the current price is near the recent high, %R should appear near the upper end; if the current price is near the recent low, %R should appear near the lower end. This is an “interpretation consistency” check: it confirms the indicator is behaving as a range-position measure.
What you should not treat as evidence of future direction is a single %R reading or a one-time crossing of an arbitrary level. Even if %R often coincides with overextended price action in past data, that does not establish a reliable forward rule.
Limitations and risks: what cannot be inferred from %R
Williams %R has material limitations that affect what you can infer:
- It is not a standalone forecast. %R describes where price sits within a past range; it does not, by itself, specify what price will do next.
- The indicator depends on the parameter choice. Changing the lookback period changes the high–low corridor and therefore changes the indicator values.
- Market conditions vary. In different volatility regimes, the same %R level can correspond to different “real-world” move sizes.
- Historical relationships don’t guarantee future results. Patterns you notice in historical %R behavior can fail when the market structure or volatility changes.
- Data and implementation can differ. If two platforms compute %R with different price inputs or period handling, their readings may not match.
A common failure mode is treating “overbought/oversold” language as a reversal signal. Even if %R reaches an extreme, price can stay near that extreme for multiple periods during strong trends.
Verification and next question to ask
To independently verify what %R means on your own environment, document your %R settings and then check the range-position consistency described above. After that, ask a more testable question than “Will it predict a move?” For example: “Under my chosen settings, how often did extreme %R conditions coincide with meaningful subsequent changes in price in historical data—and how sensitive are those results to lookback length?”