Blog · Workflow ·
The Embedded JPEG: Why Photo Mechanic Is Fast at Culling
Every raw file carries a JPEG the camera already made. What's inside a Canon CR3, why showing that JPEG beats developing the raw, and what it means for your cull.
Open a folder of raw files in Photo Mechanic and they're just there. Open the same folder in a raw developer and you wait. The difference isn't magic and it isn't a faster computer. It's what each program chooses to show you.
What's inside a raw file
A raw file is mostly sensor data: the unprocessed values from the sensor, before demosaicing, white balance, color, noise reduction and sharpening. Turning that into a picture is called developing, or rendering, and it's real work.
But a raw file also carries finished JPEGs, made by the camera the moment you pressed the shutter. That's what you see on the back of the camera, and that's what Photo Mechanic shows you.
A Canon CR3 from an EOS R5 Mark II contains, among other things:
- a full-size JPEG of 8192 x 5464 pixels, about 3 MB, made by the camera
- a smaller preview of 1620 x 1080 pixels
Reading a JPEG out of a file and decoding it is quick. Developing 45 megapixels of raw data is not. That's the whole trick.
What that means in milliseconds
When I built my own culling app, Snelkeus, I measured it. On a Mac mini M4 Pro with real concert files, showing the camera's JPEG at screen size takes about 35-50 ms, and a 100% view for a focus check about 85 ms. Grid thumbnails come from the smaller preview and take 3-6 ms.
One more lesson from building it: on the Mac, decoding JPEGs didn't get faster when I threw more threads at it. So the trick isn't decoding in parallel, it's decoding in the right order: the current photo first, then the next ones in the direction you're browsing. In tests at 4 and 8 photos a second, every frame was already sharp when it appeared; at 15 a second, 31 of 33 were.
What you see is the camera's opinion
The embedded JPEG is the camera's rendering, not yours. That has consequences for how you cull:
- Color and contrast come from your camera settings: picture style, white balance, in-camera corrections. Under LED light that can look very different from your final edit. Judge the moment, not the color.
- Focus checks are honest. On a CR3 the embedded JPEG is full size, so 100% really is 100%. In-camera sharpening and noise reduction are baked in, though, so judge focus, not grain.
- The raw has more room than the JPEG shows. A frame that looks too dark or too hot on the preview may be fine in the raw. If the moment is right and the exposure is borderline, keep it and decide in the edit.
Not every camera embeds the same thing
How big the embedded preview is depends on the camera and the format. Canon's CR3 is generous, with a full-size JPEG. Other formats can carry a smaller one. Snelkeus uses its fast path for CR3 and reads other raw formats through macOS, using the embedded previews where the camera provides them.
Lightroom can do part of this
Lightroom Classic has an Embedded & Sidecar preview option on import, which shows the camera's previews first instead of rendering them. It helps. But you're still importing into a catalog before you can start, and that's exactly the step a dedicated culling app skips.
The short version
- Developing raws is slow. Showing the embedded JPEG is fast.
- Cull on the camera's JPEG, edit the raw.
- While culling, judge moment and focus, not color.
That's how Photo Mechanic does it, and how I built Snelkeus. Why I built it is here, and how I use it on a festival day is in how to cull 2,000 festival photos fast.