ISO is an exchange, not a quality dial

Raising ISO can exchange with shutter or aperture in a calculated exposure plan, but it does not add scene light. The useful decision is which constraint matters: motion, depth, highlight headroom, or a camera-specific output that must be tested. Treat a test frame as evidence, not as a generic ISO rule.

Electronic readout is also a test question. A declared readout time and image motion can show when you should compare shutter modes, but cannot predict the shape of distortion. Local tools can inspect decoded variation or near-maximum channels; they cannot identify sensor noise, RAW clipping, or recoverability.

Highlight headroom deserves its own caution inside this same family. A protection plan built by reducing exposure by a declared number of stops is arithmetic on a reference frame, not a measurement of the scene or the camera's actual sensor headroom. Two cameras can report the same ISO convention and still diverge in how much highlight or shadow detail their sensors and processing pipelines preserve at that setting. The only way to know how a specific camera behaves at a specific ISO, in a specific scene, is a test frame inspected on that camera, not a rule carried over from a different body or a generic guideline.

Rolling-shutter readout follows the same pattern. A row-by-row sensor read means different rows of the frame are exposed at slightly different moments while the image moves, and a declared readout time paired with an image-motion speed can flag when that gap is large enough to be worth testing. It cannot predict whether a spinning propeller will skew, whether a whip-pan will smear, or how a specific camera's electronic and mechanical shutter modes will compare, because the actual distortion shape depends on the motion path, not just its speed.

Use the ISO Noise and Dynamic-Range Tradeoff Planner to see the shutter/aperture exchange an ISO change buys. Use the Highlight Protection Planner for a declared-reduction test plan, the Electronic-Shutter Readout and Motion Planner for the rolling-shutter test-trigger question, and the local noise diagnostic or local highlight-recovery guide when the question moves from planning arithmetic to inspecting one actual decoded file.

FAQ