Explore the Volatility Surface

Read IV in two dimensions

Surfaces → IV surface displays implied volatility across strike or moneyness and expiration. It adds a third dimension to the same returned grid used by its Heat map view. Use the surface to compare neighborhoods, then inspect individual nodes for precise values. The camera can make a small difference look large, so verify a hovered value before drawing a conclusion from the apparent steepness of a ridge.

Set the selection and camera

The OTM composition selects put IV below spot and call IV at or above spot; Calls and Puts read their respective grids.

1. Open IV surface and choose the symbol, session, date and eligible minute.
2. Select OTM, Calls or Puts.
3. Set strike bounds and the number/selection of expirations.
4. Drag to rotate, right-drag to pan and use the wheel to zoom.
5. Hover a node for expiry, DTE, strike, moneyness, IV and provenance.
6. Use Reset view to restore the camera, or select Heat map for a flat comparison.

Choose axes that support the comparison

The Axes menu can show strike or percentage moneyness horizontally and evenly spaced expiries or days to scale on the other axis. Even spacing emphasizes differences between listed dates, while day scaling preserves their temporal distance. Spot and MVC overlays are references; wireframe can help locate nodes. Camera state survives ordinary data refreshes, so a changing view should not be confused with a changed source grid merely because the panel was resized.

Worked example: inspect an apparent volatility ridge

Suppose one near-expiry region looks much higher than its neighbors. Hover its nodes and check whether they are listed observations or interpolated IV. Compare Calls, Puts and OTM to see which side supplies the region. Then switch to Heat map to remove perspective. A missing side can leave a partial surface with a notice. The tallest shape is a volatility/model comparison, not the most liquid executable option or a forecast of the underlying's path.

Troubleshoot a flat fallback or missing patch

Read the footer: WebGL failure, too few strikes/expirations and missing source data are different reasons. Use Retry when offered after a renderer load failure. Widen a too-small grid or narrow a dense one before changing unrelated settings. A missing historical minute can require preparation and is not repaired by rotating the camera. Capture the chosen side, axes, date/minute, node detail and fallback reason in a support report.

Compare volatility on consistent assumptions

Implied volatility is inferred from eligible option inputs under a model; realized volatility summarizes an observed underlying-price sample. Neither is an executed underlying price or a guarantee about a future move. Expiration, strike or delta band, valuation time, calendar/trading-time convention and available quote coverage all matter. A blank or invalid IV solve should stay unavailable rather than being treated as zero volatility or replaced by an unrelated contract's value.

For comparisons, first align the underlying, trading date and session. Then match the relevant expiration or maturity convention and inspect dated source inputs. A quote snapshot delivered now can still contain older observations. A historical slider selection needs eligible historical inputs; the current chain cannot manufacture an earlier smile. Closed or partial sessions can have fewer usable points. When a curve looks unusual, inspect a specific node and neighboring inputs instead of inferring a broad market regime solely from a smooth line or a color change.

Use OTM composition as a controlled comparison

The OTM setting chooses put IV below the response's spot and call IV at or above it. A node's selected side can therefore change around the spot boundary. This is not an average of call and put IV at every strike. Compare the Calls and Puts views when you need to understand which side supplies a region, and inspect the node's provenance. If one side is unavailable, the tool can show the other with a notice rather than pretending the original OTM surface is complete.

To compare two dates, keep axis mode, strike/expiry bounds and camera comparable, then inspect exact node values rather than estimating height from perspective. Moneyness uses the response's valuation spot, so the same percentage coordinate can refer to different strikes on different dates. A pinned node helps retain an audit point while the camera moves. Use its related skew action for the specific expiration when available, then verify that the destination retained the intended date and selection before treating the two views as evidence for one smile.