Free planning tools · Plan an imaging night

Imaging-session storage calculator

Budget raw image storage, calibration frames and backup copies before a night of imaging.

No account needed. Results update here as you change the inputs. Measurements stay in this tab unless you choose to share a link; shared links contain the inputs, including any location coordinates.

Your inputs

The starting values are examples. Replace them with your own measurements, prices or documented requirements.

What to have ready
  • The stored image dimensions and bits per pixel across all channels.
  • Counts for lights and each calibration category.
  • Available working-drive GB, expected file overhead and processing allowance.
Measurements for Imaging-session storage calculator

Calculated from your inputs

Your plan

The example will calculate here when JavaScript is ready.

What to do next

    Calculation details

    Inputs used in this result

    Compare a change before committing

    Keep this plan, change the inputs and see the difference. The comparison stays in this tab.

    Is there enough working-drive space for the session and processing?

    An imaging session leaves more than light frames. Include darks, flats and bias or dark-flats, then distinguish the working drive from the additional raw copies you plan to keep elsewhere. This storage calculator shows that separation explicitly.

    The processing allowance is your estimate. Comparing a plan before and after changing frame count or stored bit depth can help avoid filling a field computer while still retaining the backup plan.

    How to use this planner

    1. Enter recorded image dimensions and actual stored bit depth.
    2. Add the planned raw frames and total copies, including the working copy.
    3. Check the working budget separately from other backup destinations and revise the allowance after a trial.

    The calculation

    Bytes per frame = width × height × stored bits per pixel ÷ 8 × (1 + overhead). Total = bytes per frame × all frame counts × copies.

    A worked example

    6,248 × 4,176 pixels at stored 16-bit depth use 52.18 MB per frame before overhead. With 210 frames, 5% overhead and two copies, budget about 23.01 GB.

    Example inputs are demonstrations. Replace them with your own measurements, prices or documented requirements.

    Assumptions and limits

    Use stored bit depth, not ADC bit depth: 12-bit camera data often occupies a 16-bit container. For RGB 16-bit-per-channel files use 48 bits per pixel. All frames here use the same dimensions and depth. Compression, padded rows, video, processing intermediates and stacked floating-point files can change demand. GB is decimal; GiB is binary.

    Questions about this calculation

    Should I use the sensor ADC bit depth or the file’s bit depth?

    Use how the image is stored. A camera’s ADC specification can differ from the container used by the capture software. For multi-channel files, include the combined bits across those channels.

    Why are GB and GiB different in the detail?

    The calculator uses decimal GB of one billion bytes for drive-budget inputs. GiB divides by 2 to the power of 30. Operating systems can label capacity differently, so compare the same units.

    Put the result in context