A 24-bit container may hold only 16-bit content — verify via bit scope before mastering

When a mix is delivered as a 24-bit WAV file, the mastering engineer cannot assume all 24 bit-planes carry real information. A common error (or deliberate down-conversion left in a 24-bit wrapper) results in a file where only 16 bits are active, with the lower 8 bits set to zero. This is audible as reduced resolution — more quantization noise — but is not obvious from file metadata alone. A bit scope (a visualizer showing which bit planes are active) immediately reveals this: if only the top 16 bit-planes show activity, the file is a 16-bit recording in a 24-bit container. Knowing this before processing prevents treating a 16-bit file as if it has 24-bit headroom, which affects noise floor expectations and dithering decisions.

Examples

Load the delivered file in a metering app with a bit scope (e.g. iZotope RX, Ozone Insight). If only bits 1–16 are active out of bits 1–24, the file’s effective resolution is 16-bit. Dither to 16 bits on final export; do not expect sub-16-bit detail.

Assessment

You receive a WAV file labeled ‘24-bit’. The bit scope shows no activity below bit 17. What does this indicate, and how does it affect your dithering decision on export?