RAW vs JPEG: Which File Format Should You Shoot For Weddings and Portraits
RAW vs JPEG: the short answer before the long one If you are photographing a paid wedding or a portrait session that a client will hang on a wall, shoot RAW. If you are shooting a high-volume, low-margin, fast-turnaround job where the light is controlled and the look is locked in, JPEG can be the smarter business decision. That is the honest version of the answer, and most articles on this topic never get there because they treat RAW vs JPEG as a technical debate instead of a workflow decision. Below we break down the four things that actually matter in the field (dynamic range, file size, white balance recovery, editing latitude), then walk through real shooting scenarios where each format wins. What RAW and JPEG actually are RAW A RAW file is the unprocessed sensor data from your camera, usually 12-bit, 14-bit or 16-bit per channel depending on the body and drive mode. It is not really an image yet. It is a data container that needs to be interpreted (demosaiced) by software such as Lightroom, Capture One, DxO PhotoLab or your manufacturer’s own converter. Extensions vary by brand: .CR3 (Canon), .NEF (Nikon), .ARW (Sony), .RAF (Fujifilm), .ORF (OM System), .RW2 (Panasonic), plus the universal .DNG. JPEG A JPEG is a finished image. Your camera has already applied white balance, contrast, saturation, sharpening, noise reduction and a colour profile, then compressed the result to 8-bit per channel using lossy compression. It is ready to send, print or upload immediately, and it throws away the data it decided you did not need. Much the same conclusion turns up on exposure.software. The numbers side by side Attribute RAW JPEG Bit depth 12 to 16-bit (4,096 to 65,536 tonal values per channel) 8-bit (256 tonal values per channel) Compression Lossless or visually lossless Lossy, degrades on re-saves Typical file size (24MP) 25 to 35 MB 6 to 12 MB (fine quality) Typical file size (45 to 61MP) 50 to 90 MB 15 to 25 MB White balance Metadata only, fully changeable later Baked in, limited correction Usable dynamic range Roughly 12 to 15 stops on modern full frame Roughly 8 to 10 stops after the tone curve Ready to deliver No, requires conversion Yes, straight out of camera Buffer impact in burst Fills faster Fills slower, longer bursts Universal compatibility Needs supported software Opens everywhere 1. Dynamic range: the wedding dress problem This is where RAW earns its keep, and it is not theoretical. A white dress in midday sun next to a groom in a black tuxedo is one of the hardest exposure problems in commercial photography. The scene can span 11 or 12 stops. Your JPEG engine gets around 8 to 10 usable stops after its tone curve is applied, so something has to go: either the lace detail on the dress clips to pure white, or the tuxedo blocks up to pure black. With RAW you keep the sensor’s full capture. In practice, on a current full frame body: Highlight recovery: roughly 1 to 1.5 stops of clipped highlight detail can usually be pulled back from RAW. From a JPEG you get maybe 0.3 stops before it turns grey and flat. Shadow lift: 3 to 4 stops of shadow lift from RAW at base ISO is routine with acceptable noise. Lift a JPEG shadow by 2 stops and you get banding, blotchy colour and amplified compression artefacts. Gradation: 14-bit RAW gives 16,384 tonal steps per channel versus 256 in JPEG. That difference is invisible until you start stretching tones, then it becomes posterisation in skies and on skin. Field rule: any time the contrast ratio in your frame is beyond what you can control with flash, a reflector or repositioning, RAW is not optional. 2. File size and storage: the cost nobody budgets for Let us do real wedding maths. A full day, two shooters, 3,500 frames captured on 45MP bodies: RAW only at around 55 MB per file: roughly 190 GB per wedding RAW + JPEG: roughly 250 GB per wedding JPEG fine only: roughly 60 GB per wedding Shoot 25 weddings a year in RAW and you are generating close to 5 TB of originals annually, before edited exports, before backups, before the second off-site copy. That is a genuine business cost, and it is the strongest practical argument the JPEG side has. Three ways to keep RAW without drowning: Use compressed RAW. Canon C-RAW, Nikon High Efficiency RAW and Sony lossless compressed RAW cut file sizes by 30 to 60 percent with a quality difference that is invisible in normal editing. High Efficiency RAW in particular has become the sensible default for wedding shooters. Cull hard before you archive. Deleting the 60 percent of frames that will never be delivered is the single biggest storage saving available to you. Adopt a 3-2-1 backup policy and convert your archive to DNG if you want an additional size reduction and long-term format safety. 3. White balance recovery: the argument that ends the debate White balance in a RAW file is metadata. It is a note attached to the data, not a change to the data. You can set 3200K in camera, then move to 5600K in Lightroom six months later with zero quality penalty. Nothing is lost. In a JPEG, white balance is baked into the pixel values. Correcting a heavy colour cast means stretching 8-bit channels that have already been clipped. You can move it a little. You cannot rescue it. Now think about a typical reception: Tungsten uplighting at around 2800K Magenta and blue LED DJ wash cycling every few seconds Daylight spilling through a window at 6000K Your on-camera flash at 5500K Candles on every table There is no single correct white balance for that room. With RAW you split the difference on the day and fix skin tones per image or per group in post. With JPEG you are locked to whatever the camera guessed while the DJ light was green. Mixed lighting
RAW vs JPEG: Which File Format Should You Shoot For Weddings and Portraits Read More »



