Volatility Compression
Understand crypto volatility compression: contracting realised range, ATR/bandwidth measures, range tightening, breakout uncertainty, false starts and regime testing.
Reading progress — saved on this device
Volatility compression is a period in which realised price movement contracts relative to a prior or historical baseline. It can precede larger movement because volatility clusters and regimes change, but compression does not tell you breakout direction or guarantee expansion on schedule.
What counts as compression?
Compression should be defined relative to a consistent baseline. Common measures include falling ATR/ATR%, Bollinger Band width, rolling standard deviation, realised volatility or narrowing high-low range.
There is no universal threshold. “Low volatility” means low relative to the asset, timeframe and regime being studied.
Quantifying a squeeze
An analyst might define compression as bandwidth falling into the lowest 10% of its trailing one-year observations. This is more reproducible than visually labelling only the narrow ranges that later produced dramatic breakouts.
| Measure | Strength | Limitation |
|---|---|---|
| ATR% | Simple range-based volatility | Does not capture distribution shape |
| Bollinger bandwidth | Easy rolling dispersion proxy | Parameter-sensitive |
| Realised volatility | Return-based statistical measure | Sampling frequency matters |
| Range width | Intuitive chart structure | Can be subjective without rules |
Compression is not direction
A compressed range can break up, break down, continue sideways or produce a false break before re-entering. The useful information is that recent realised movement is small relative to a reference—not that the market has stored a known amount of “energy”.
Low realised volatility can coexist with high implied volatility if an event is approaching, and low chart volatility can coexist with poor order-book liquidity.
Practical compression workflow
- Select one quantitative volatility measure and baseline.
- Define the percentile/threshold before reviewing outcomes.
- Record liquidity and event context separately.
- Measure subsequent realised volatility at fixed horizons regardless of breakout direction.
- Include false starts and continued compression in the dataset.
This method tests whether compression genuinely predicts higher future volatility for the chosen market and horizon rather than selecting memorable examples.
Worked example: percentile-based compression
BTC 20-day Bollinger bandwidth is 4.2%. Over the prior 365 daily observations, only 18 readings were narrower, placing the current reading around the bottom 5% of the sample.
This supports the statement: “realised dispersion is unusually compressed relative to the last year.” It does not support: “BTC will break upward tomorrow.”
A robust study would measure one-day, three-day and seven-day realised volatility after every bottom-5% observation and compare it with unconditional outcomes.
Common mistakes and misunderstandings
- Assuming compression predicts direction.
- Selecting squeeze examples only after dramatic breakouts occur.
- Confusing low realised volatility with deep liquidity.
- Using one fixed threshold across assets with very different volatility regimes.
- Ignoring continued compression and false breakouts in backtests.
Knowledge checkpoint
Q1. What information does volatility compression provide about direction?
Q2. How can you define a squeeze without hindsight?
Q3. Why can low realised volatility coexist with poor liquidity?
Q4. What outcomes must be included when testing compression systematically?
FAQ
❓ Does compression guarantee a breakout?
No. Compression can persist or produce false breaks. It only describes unusually low recent movement relative to a chosen baseline.
❓ Does compression predict direction?
No. Additional directional evidence would be required.
❓ How can compression be measured?
ATR%, Bollinger bandwidth, rolling standard deviation, realised volatility or objective range-width metrics are common approaches.
❓ Is low volatility the same as low risk?
No. Event gaps, poor liquidity and abrupt regime changes can create substantial risk after a quiet period.
Summary
- Compression means realised movement is low relative to a defined baseline.
- It should be quantified before outcomes are known.
- Compression does not identify breakout direction or timing.
- Liquidity, events and false starts must be analysed separately.
Technical analysis describes observed price, volume and volatility behaviour. It does not remove market, execution, liquidity or model risk, and its usefulness depends on data quality, timeframe and regime.
Want this in a personalised order?
Take the crypto assessment and get a custom path of 10 modules matched to what you already know. Free, no card required.
Build my path →