The right culling source depends on the decision. A camera JPEG or embedded RAW preview is usually fast enough for composition, timing, and expression. A rendered RAW view is more useful when a decision depends on recoverable highlights, shadows, white balance, or fine detail. Keep the original RAW files until the final selection and backup are complete.
Camera JPEGs and embedded previews
Camera JPEGs include the selected picture style, sharpening, noise reduction, and white balance. RAW files also commonly contain camera-generated previews, but preview size and quality vary by camera and settings. A preview can therefore be quick and visually useful without representing the full editing latitude of the sensor data.
When to inspect RAW data
Check a RAW-capable editor when a frame looks marginal because of exposure, colour, noise, or critical focus. RAW data can provide more adjustment latitude than an in-camera JPEG, but it cannot repair missed focus or all clipped detail. Avoid rejecting a required moment solely from an automated score or a small preview.
Handle RAW+JPEG pairs deliberately
Pairing behaviour differs by application. Confirm whether ratings apply to both files, whether export includes one or both, and whether duplicate filenames remain unambiguous. Selekt provides a JPG/RAW preview-source control for paired files, but the active source should be read from the interface; do not assume every displayed RAW view is a fresh full-resolution demosaic.
Recommended workflow
Use fast previews for the broad pass, inspect borderline and final candidates at a useful zoom, and open exposure-critical frames in the editor that will develop them. Export or transfer a small test set first and verify ratings, sidecars, pair handling, and filenames in the destination. This preserves speed without pretending every preview answers the same question.
