Help · Knowledge base · Concept

IV rank and IV percentile

From the platform knowledge base — the same entry the platform's AI agent cites in its answers. Educational reference, not advice.

IV rank and IV percentile

Definition

IV rank and IV percentile normalize an underlying’s current implied volatility against its own history, answering “is IV high or low for THIS instrument?” — raw IV levels are incomparable across names. IV rank locates today’s IV within the past year’s range; IV percentile counts how much of the past year traded below today’s IV. Both are practitioner conventions, not academic constructs; their definitions matter more than their names, which vendors sometimes swap.

How it works / structure

  • IV rank = (IV_now − IV_52w_low) / (IV_52w_high − IV_52w_low) × 100. Range-based: one extreme spike stretches the denominator and pins rank low for months afterward.
  • IV percentile = share of the past N trading days (typically 252) with IV below IV_now, × 100. Distribution-based: robust to single spikes, blind to how extreme the current level is.
  • Parameters: lookback window (252d standard), IV tenor used (30-day constant-maturity is common), rank vs percentile choice. The platform binds these to catalog concepts iv_rank and iv_percentile; vrp_percentile normalizes the volatility risk premium the same way.
  • Divergence reading: after a vol spike decays, rank can read ~10 while percentile reads ~60 — the pair together describes the year’s shape, which is why the platform carries both.
  • Simulation parameters: entry filters expressed as rank/ percentile thresholds are directly replayable (the concepts read stored computed fields).

When it applies

Normalizing any IV-conditional decision: premium-selling entries gated on “IV high for this name”, long-premium entries on “IV low”, cross-sectional screens ranking names by relative IV, and event positioning (pre-earnings IV inflation reads differently at the 20th vs 90th percentile).

Risk profile & failure modes

  • High can go higher: rank/percentile are backward-looking normalizations, not mean-reversion guarantees; IV percentile 95 before a crisis was followed by IV several times higher.
  • Regime resets: a volatility-regime shift (regime-volatility) makes the trailing year’s range the wrong yardstick — post-shift readings are systematically distorted for months.
  • Vendor inconsistency: rank vs percentile naming and tenor choices differ across platforms; unstated definitions make thresholds non-comparable.
  • Cheap-for-a-reason / rich-for-a-reason: low IV before known quiet periods and high IV before scheduled events are correctly priced, not mispriced; the normalization cannot see the calendar (event-earnings proximity concepts fill that gap).

Evidence & limits

The definitions are practitioner conventions (documented here as the platform’s binding definitions). Evidence that high-IV-rank entries improve premium-selling outcomes is broadly consistent with the volatility-risk-premium literature (Bakshi and Kapadia 2003 for the index premium) but specific rank thresholds (“sell above 50”) are unproven folklore — the platform treats thresholds as strategy parameters to be tested per instrument, not as facts.

Falsifiable-thesis examples

Illustrations only, not signals:

  • “X’s IV percentile, at 92 today, will read below 60 within 60 days” — falsified if the daily series never drops below 60.
  • “Premium-selling strategy S on Y, gated at IV rank ≥ 50, will show a higher replay Sharpe than the ungated variant over the same two-year window” — falsified by the paired replay.

Cross-references

  • The quantity normalized: opt-implied-volatility
  • The premium being harvested (or not): indicator-realized-vs-implied-vol
  • Regime distortions: regime-volatility
  • Strategy consumers: strategy-iron-condor, strategy-cash-secured-put, strategy-strangle

Sources

The agent cites this page.

Inside the platform, this entry is live context. A signed-in citation opens the in-app view of the same id.

Inquire about founding membership