RAW vs JPEG for photo culling: which should you review?

When you shoot RAW+JPEG, you end up with two copies of every image. During culling, which file should you actually review? The answer affects your speed, your accuracy, and your entire workflow pipeline.

The case for culling JPEGs

JPEGs load instantly. A 20MB JPEG renders in milliseconds, while a 50MB RAW file can take seconds to decode, especially formats like Canon CR3 or Fujifilm RAF (X-Trans). For a first pass where you're making snap judgments about composition and moment, JPEG speed is a genuine advantage. Camera-processed JPEGs also show you the scene as your camera interpreted it, including the film simulation or picture style you chose in-camera.

The case for culling RAW files

RAW files contain the full sensor data with greater dynamic range and color depth. Images that look slightly dark or flat in JPEG might be perfectly usable once you adjust exposure in post. If you cull based on the JPEG, you might reject recoverable shots. Modern RAW culling tools like Selekt decode the actual sensor data (not just the embedded JPEG preview) and render it quickly using libraries like LibRaw, which supports X-Trans demosaicing and 400+ camera models.

The hybrid approach: JPG+RAW toggle

The most effective approach is culling JPEGs for speed during your first pass, then toggling to the RAW render for images you're on the fence about. This lets you move fast through obvious rejects while making informed decisions on borderline images. In Selekt, you can press R to instantly toggle between the camera JPEG and the true RAW sensor render for any paired image. This gives you the speed of JPEG culling with the accuracy of RAW evaluation when it matters.

How RAW+JPEG pairing works

When you shoot RAW+JPEG, your camera writes two files with the same base name: IMG_1234.CR3 and IMG_1234.JPG. A good culling tool detects these pairs automatically and shows you one entry in the grid (the JPEG) while keeping the RAW linked behind it. When you mark the JPEG as a Pick, the RAW file comes along for the ride. This prevents duplicate entries in your grid and keeps navigation clean even with thousands of paired files.

Performance considerations by RAW format

Not all RAW formats decode at the same speed. DNG files are generally fastest because they use a standardized structure. Canon CR2 and Nikon NEF are well-optimized in most tools. Fujifilm RAF files with X-Trans sensors are the slowest because they require a special demosaicing algorithm (Markesteijn 3-pass) instead of the standard Bayer interpolation. For Fujifilm shooters, culling JPEGs first and toggling to RAW only when needed is especially valuable.

What about embedded JPEG previews?

Every RAW file contains an embedded JPEG preview generated by the camera at capture time. Some culling tools display this embedded JPEG instead of actually decoding the RAW sensor data. This is faster, but it means you're not seeing the true RAW render—you're seeing the camera's JPEG processing applied to a lower-resolution preview. For culling purposes, this is often acceptable for the first pass, but for a final evaluation you want the actual decoded RAW data at full resolution.

Recommended workflow

1. Import your RAW+JPEG pairs into a culling tool that supports automatic pairing. 2) Do your first pass on JPEGs—they load faster and camera processing helps with quick evaluation. 3) Use the RAW toggle on maybe/borderline images to check if shadow detail, highlight recovery, or color fidelity changes your decision. 4) Export your picks (both RAW and JPEG) to Lightroom with XMP sidecar files carrying your ratings. 5) In Lightroom, work from the RAW files exclusively for developing.