Photography exposure stops difference calculator

It converts their combined change into a signed number of stops, so you can see whether the second setup records more or less exposure than the first. A positive result means the second setup is brighter, a negative result means it is darker, and zero means the combinations are equivalent. Separate aperture, shutter, and ISO contributions make the result easy to audit, while strict validation rejects zero, negative, missing, or non-finite values before any calculation is attempted.

How the calculator compares two exposures

A camera exposure is shaped by three settings working together. Shutter duration controls how long light reaches the sensor, ISO changes the recorded sensitivity, and aperture controls light through the square of the f-number. The calculator represents each combination with the proportional exposure value ISO multiplied by shutter seconds and divided by aperture squared. It then divides the second exposure by the first and takes the base-two logarithm of that ratio. This produces the signed stop difference photographers use when discussing exposure changes. One positive stop means the second combination records twice the relative exposure; one negative stop means it records half. Two positive stops correspond to four times as much, while two negative stops correspond to one quarter. The calculation compares settings rather than judging whether a photograph is correctly exposed, because scene luminance, filters, flash, metering, and creative intent are not part of the six supplied values. Every aperture, shutter, and ISO entry must be finite and strictly greater than zero so the ratio and logarithm remain physically meaningful.

Reading the signed result and its components

The main result, stops_difference, describes the second combination relative to the first. A positive value labels the second setting as brighter, a negative value labels it as darker, and a value of zero labels the two settings as equal. The exposure_ratio expresses the same comparison as a multiplier, which can be easier to explain to someone who does not routinely think in stops. The response also separates aperture_stops, shutter_stops, and iso_stops. These three signed contributions add to the total. Opening the lens by lowering the f-number contributes positive stops, while closing it contributes negative stops. Lengthening shutter duration contributes positive stops and shortening it contributes negative stops. Raising ISO contributes positive stops and lowering it contributes negative stops. This decomposition is useful when several controls move at once: an aperture change may reduce exposure while shutter and ISO changes add it back. Decimal results are expected when settings do not land on exact full-stop increments. Values are cleaned to stable significant precision so repeated calls and browser calculations return consistent JSON without hiding useful fractional-stop information.

Practical checks for camera planning and review

Use the calculator whenever you have two known exposure triangles and need a direct comparison rather than a recommendation for a missing setting. For example, you can compare a handheld frame with a tripod frame, check how much exposure changed between two metadata records, or verify that a planned aperture adjustment was fully offset by shutter and ISO. Enter shutter durations in seconds, so a shutter marked one over one hundred twenty-five is entered as 0.008. Enter aperture as the f-number printed by the lens and ISO as the numeric sensitivity. The order matters because the answer is directional: swapping the first and second combinations reverses the sign while preserving the magnitude. Equal results indicate equivalent relative exposure, not identical motion blur, depth of field, or noise. Those visual properties can differ substantially even when the total is zero stops. The algorithm is deterministic and runs without network access, stored state, randomness, or current-time data. That makes it suitable for interactive lessons, repeatable production checks, automated test fixtures, and metadata analysis pipelines. Successful API requests use the published base price of $0.002; the same arithmetic is available free in the browser.