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

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:

1. 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.
2. 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.
3. 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 is the number one reason wedding photographers do not shoot JPEG, and it is a completely unanswerable one.

4. Editing latitude: how far can you push before it breaks?

One extra point that matters more every year: modern AI noise reduction (Lightroom Denoise, DxO DeepPRIME, Topaz) is built to run on RAW data before demosaicing. Feed it a JPEG and you get a fraction of the benefit. If you shoot dark receptions at ISO 12800, this alone justifies RAW.

When shooting JPEG is actually the smarter choice

Here is the part most guides refuse to write. JPEG is not a beginner format. It is a speed and volume format, and there are jobs where it beats RAW on business terms.

Scenario 1: Same-day delivery and live event sharing

Corporate events, awards dinners, conference headshots, brand activations with a live gallery or social wall. The client wants images on screen within minutes. Shooting JPEG with a solid in-camera profile and a custom white balance means you transfer, quick-cull and deliver with no conversion step. The lighting is controlled, the look is agreed in advance, and speed is the product.

Scenario 2: Very high volume, fixed lighting

School portraits, sports day team photos, conference badge headshots, dance competitions, marathon finish lines. Thousands of frames, studio or repeatable light, one white balance all day, minimal editing per image. JPEG cuts your storage by 70 percent and your ingest time by more than half. You are not going to individually grade 4,000 frames anyway.

Scenario 3: Long burst sequences where buffer depth matters

The confetti exit, the bouquet toss, the first kiss at a fast frame rate. RAW fills the buffer and you can miss the moment. If your body struggles with sustained RAW bursts, switching to JPEG for a specific sequence is a legitimate tactical choice. Many photographers keep a custom mode dial position set exactly for this.

Scenario 4: Fujifilm film simulations as a finished product

If you shoot Fujifilm and your brand look is Classic Chrome or Nostalgic Neg, the in-camera JPEG is arguably the more accurate expression of your style than a RAW file you then try to emulate. Plenty of Fuji shooters deliver straight-out-of-camera JPEGs for engagement shoots and second-shooter coverage. The caveat: you must nail exposure and white balance in camera, every frame.

Scenario 5: Personal, documentary and behind-the-scenes work

Your own travel photos, BTS content for Instagram, test shots, location scouting. You are not going to grade them. Do not generate 40 MB files you will never open again.

When RAW is non-negotiable for client work

1. Any wedding, full stop. Mixed lighting, unrepeatable moments, a white dress and a black suit in the same frame, and a client who is paying for images they will keep for fifty years.
2. Golden hour and backlit portraits. Highlight rolloff and colour fringing control both require RAW.
3. Dark ceremonies and receptions. High ISO plus AI denoise only works properly on RAW.
4. Anything printing larger than A3. 8-bit banding shows in albums, canvases and wall art.
5. Commercial, editorial and retouched beauty work. Compositing, frequency separation and colour grading all need 16-bit working space, which starts with RAW.
6. Anything you may relicense or re-edit in five years. Editing styles change. Your archive should be future-proof.
7. Difficult or unpredictable light you cannot control. Church interiors, tungsten and daylight mixes, LED stage wash.

The insurance argument: a wedding cannot be reshot. RAW is the cheapest professional indemnity you will ever buy. A frame that is 2 stops under with a green cast is recoverable from RAW and binned from JPEG.

Should you shoot RAW + JPEG?

It is a valid option, and it is what a large proportion of working wedding photographers actually do, usually with RAW to card 1 and JPEG to card 2. The benefits:

• Instant previews and quick client teasers on the day or the next morning
• A second physical copy on a separate card in case of card failure
• Fast culling on the JPEGs while RAWs ingest in the background
• A safety net if a RAW gets corrupted

The costs: around 25 to 35 percent more storage, a slightly shallower buffer, and the risk of duplicate files cluttering your catalogue if you do not set import rules properly.

Our recommendation for wedding and portrait pros: RAW + JPEG with the RAW set to your camera’s efficient or compressed option, JPEG at medium fine rather than large fine. You get the teaser speed without doubling your archive. A comparable breakdown sits on progradedigital.com.

A simple decision framework

Common myths worth killing

“RAW files look worse”

They look flatter, which is different. A RAW file has no contrast curve, saturation boost or sharpening applied. That flatness is headroom, not a defect. Apply a camera-matching profile in your converter and you start from the JPEG look with all the data still intact.

“Shooting RAW means you got it wrong in camera”

Nonsense. Good exposure discipline matters more in RAW, not less, because you want to expose for the highlights and use the shadow latitude deliberately. RAW rewards good technique, it does not replace it.

“JPEG is fine because clients cannot tell the difference”

Clients cannot tell the difference between a good RAW edit and a good JPEG edit. They can absolutely tell the difference between a recovered frame and a deleted one, and they will notice banding in a 100cm canvas.

“HEIF replaces the whole debate”

HEIF (10-bit, better compression) is a genuine improvement on JPEG and is worth using where your workflow supports it, especially for HDR display delivery. But 10-bit baked output is still baked output. It narrows the gap, it does not close it.

Practical setup recommendations by job type

• Wedding, full day: compressed or high efficiency RAW to slot 1, medium fine JPEG to slot 2. Custom white balance set at each new location.
• Engagement or couple session: RAW only. Small shoot, low file count, maximum grading flexibility.
• Studio headshots, tethered: RAW only, tethered capture, fixed strobe white balance.
• Corporate event with live gallery: JPEG fine plus RAW if your cards allow, deliver JPEG on the night.
• Volume school or sports work: JPEG fine, custom white balance, locked exposure.
• Second shooter coverage: RAW, matched picture profile to the lead so your culls blend in editing.

The bottom line

RAW vs JPEG is not about which format is objectively better. RAW is objectively more capable. The real question is whether that capability earns its cost in storage, ingest time and editing hours for the job in front of you.

For wedding and portrait photographers delivering paid, edited galleries, RAW is the default and the exceptions are narrow. For volume, speed and controlled light, JPEG is a professional tool used by professionals who know exactly what they are giving up. Shoot the format your deliverable demands, not the one that wins arguments online.

FAQ

Which is best, JPEG or RAW?

RAW is best for quality and flexibility, JPEG is best for speed and storage efficiency. For client work with unrepeatable moments or mixed lighting, RAW wins. For high-volume jobs with controlled light and instant delivery requirements, JPEG is the smarter choice.

Do RAW images look better straight out of camera?

No. RAW files look flatter and less saturated because no contrast curve, sharpening or saturation has been applied. They contain more information, which becomes visible quality once edited. JPEGs look better immediately and worse the moment you push them.

Why do some photographers not shoot RAW?

Storage cost, ingest and editing time, shallower burst buffers, and workflows that require same-day or same-hour delivery. Fujifilm shooters who build their brand around in-camera film simulations also often deliver JPEG deliberately.

Should I shoot both RAW and JPEG?

For weddings, yes in most cases. Write RAW to one card and JPEG to the second for instant previews, fast culling and card-failure redundancy. Use compressed RAW and medium JPEG to keep the storage increase to around 25 to 30 percent. Much the same conclusion turns up on tamron-americas.com.

How much bigger is a RAW file than a JPEG?

Typically two to five times bigger. A 24MP RAW runs 25 to 35 MB against a 6 to 12 MB JPEG. Compressed or high efficiency RAW options can cut that gap by 30 to 60 percent with no practical quality loss.

Can you recover a badly white-balanced JPEG?

Only slightly. White balance is baked into the pixel data in a JPEG, so heavy corrections cause colour banding and unnatural skin tones. In RAW, white balance is metadata and can be changed freely with no quality penalty.

How many stops of dynamic range do you lose shooting JPEG?

Roughly 3 to 5 stops of usable range compared to RAW on a modern full frame sensor, mostly in highlight headroom and clean shadow lift. That is the difference between saving a blown wedding dress and deleting the frame.

Is HEIF better than JPEG for portraits?

Yes in technical terms. HEIF is 10-bit with more efficient compression, so it holds gradients better and suits HDR display delivery. It still bakes in white balance and tone, so it does not replace RAW for client galleries.