The RAW+JPEG rush workflow: fast now, master intact

A same-day promise is not a reason to gamble with the only copy of someone's wedding. RAW+JPEG gives you a middle path: small files that move fast for the rush, RAW files kept whole for the real edit. It works when you decide in advance which file does which job, and how the two find each other again afterward.

What dual capture actually buys you

Switch on RAW+JPEG and the camera writes two files for every exposure: the RAW, which is the sensor data with all its latitude intact, and a JPEG the camera has already processed using your picture profile and white balance. The JPEG is small enough to copy, browse and send in the time you have between a ceremony and a dinner. The RAW is the file you will still want in five years when someone asks for a print.

The trade is worth stating plainly. You get speed at the front of the job in exchange for more cards, more copying and one more decision at ingest. What you do not get is a workflow that is twice as fast. Import both file types into one pile and edit whatever you click on, and you have doubled the clutter for no gain.

The mental model that makes it work: the JPEG is a fast proof of the scene, and the RAW is the negative. A same-day JPEG can be a completely valid delivery. It just cannot be the only file you keep, or quietly become the master because it was convenient.

It applies to any job with a deadline inside the day: a wedding with a sneak peek promise, a conference, sports, editorial. If nothing has to leave the building tonight, RAW only is simpler.

Set the camera so the JPEG is usable, not just present

The JPEG inherits every in camera decision you make, and you cannot undo those choices the way you can on a RAW. So set the second file up as if it were the deliverable, because on rush days it is.

• Use the largest JPEG size and the highest quality setting your camera offers. The storage a small JPEG saves is not worth a file you cannot crop.
• Choose sRGB when the files are going to phones, press desks and social platforms. It is the least surprising color space in a hurry.
• Pick a neutral or familiar picture profile. A heavy creative look bakes in on the JPEG and then clashes with the gallery you deliver three weeks later.
• Think about white balance rather than defaulting to auto. Auto is fine in changing light outdoors. A fixed Kelvin value usually gives a cleaner set in one ballroom under one set of lights, which means less correction in the rush window.

None of this rescues a badly exposed frame. RAW gives you room to recover highlights and fix a cast, the JPEG gives you far less, and a rush window spent on corrections is a window you could have saved with the camera in your hands.

One gotcha to test before you rely on it: on some bodies, writing two files affects buffer behavior during long bursts, and on some it changes how many frames you get before the camera slows. Test with the card, burst mode and settings you actually use. Find that out at home, not during a first dance.

Do the card math before the day, not at the reception

Dual capture changes card planning materially, and the arithmetic is worth doing once with your own camera's real file sizes rather than assuming. Shoot fifty frames at your intended settings, look at the folder, and work from those averages.

As an illustration of the shape of it, using round numbers you should replace with your own:

A typical wedding day runs 2,000 to 4,000 frames, so a high resolution body can push those numbers a long way past the example. Size your cards and your backup drive for the combined total plus room for a reception that goes longer than planned, and take the spare card you would normally leave in the bag.

Two rules that cost nothing and save whole evenings. Do not switch to RAW+JPEG halfway through a day because you suddenly want rush files: mixed capture settings make coverage hard to count and confuse the ingest. And agree the setting across the team, so whoever runs the rush lane knows which cards will feed it.

Two destinations, decided before the first card goes in

Make two folders before you touch a card reader: JPEG_RUSH and RAW_MASTER. The rush lane is a working folder with a short life. The master lane is the archive, and it gets the full backup treatment before anything else happens to it. Our post shoot ingest checklist has the order of operations, and the 3-2-1 backup workflow covers the copies that matter.

Keep the camera's original folder structure on the backup copy. It is the least clever option and the one that survives a bad night, because a file can always be found by card and time.

Here is the gotcha that catches people once and only once. Lightroom Classic can either treat a RAW+JPEG pair as one photo or as two separate files, depending on a preference. If it treats them as one, the JPEGs you were planning to send are effectively invisible in the catalog, and you will lose ten minutes of a thirty minute window finding out why. Test that setting on a small job before a real deadline. Photo Mechanic and other fast browsers have their own pairing behavior worth knowing in advance too, and our Photo Mechanic review covers where its speed genuinely comes from.

Keep the rush JPEGs until the full gallery has shipped and been checked. They are a precise record of what the client saw on the night, which matters when someone asks for that picture again in a different size.

The rush pass, on a timer

A rush lane needs a time budget or it eats the night. For a thirty minute promise: ten minutes to copy and open, ten to select, seven to batch correct and export, three to verify what arrived. The split becomes yours after two jobs. The point of writing it down is that it gives you a moment where you stop improving one image and send the set.

Run the JPEG pass in stages rather than trying to do everything on each frame:

1. Set aside accidental frames, blinks, obvious motion blur and burst near duplicates.
2. Mark the frames that cover the required moments, people, sponsors or story beats.
3. Zoom to 100 percent only where focus is genuinely in doubt.
4. Apply one restrained batch correction for exposure, white balance and crop.
5. Export to a folder called READY_TO_SEND and open three files before anything goes out.

For a twenty five image event set, aim for range rather than volume: a wide, a few interactions, the key people, two details, one action frame and a closing image. Speed should let you send a better small set, not a spray of a hundred loose proofs. The count argument for weddings is in how many sneak peeks to send, and if the delivery has to happen from the venue rather than from a hotel room, the full on-site loop is in card to social before you leave.

Getting from a rush pick to its RAW without guessing

The paired files normally share a base filename, which is the whole trick. If DSC_4321.JPG was the frame the client loved, its master is DSC_4321 with the RAW extension your camera uses. Leave original filenames alone until matching is done, or rename both files together in one controlled step. Renaming only the rush lane at eleven at night is how a pick becomes unfindable. The naming system worth adopting is in renaming and keywording after the pass.

At the full edit, collect the rush picks, find their RAW counterparts by name and capture time, and do the finished work there. Print files, album spreads and anything shot in mixed light come off the RAW. The JPEG stays valid for what it was: a timely file, sent when it was worth the most.

Watch for a mismatch that surprises people. Some cameras bake a crop, a lens correction or a profile into the JPEG that the RAW does not show by default, so the two versions of the same frame can differ in framing and in distortion. Compare two or three hero images rather than assuming they match. If the client fell in love with the in camera crop, reproduce it on a virtual copy of the RAW rather than trying to talk them out of it.

Lightroom's Assisted Culling can help the second half of this job. It scores subject focus, eye focus and eyes open, and since version 15.4 it can run at import, so the RAW folder can be scored while you are still working the rush lane. Adobe labels it early access and says it is optimized for portraits and headshots. Setup is covered in our Assisted Culling guide.

The four ways this goes wrong

The failures are predictable, which means they are avoidable. Clearing the JPEGs off the drive before delivery has been confirmed. Treating them as the master because they were convenient, and never going back to the RAW. Sending a heavily stylized in camera look on the night, then delivering a different gallery a month later. And silence: the client cannot tell whether they are looking at finished work or a preview.

A short ruleset covers all four:

• JPEGs are for speed, previews and promises you made in writing.
• RAW files and original cards stay protected until a verified second copy exists.
• Matching filenames and named folders, so a rush pick can be found in a year.
• Edit the rush files lightly unless the client has approved a specific look.
• Say in one sentence whether these are finished files or early previews.
• Every high resolution and print export comes from the RAW.

That last piece is client expectation work as much as file management. "Here are twenty polished web images from today, your full gallery follows with the complete edit" is a sentence that prevents a month of confused messages. If the rush lane is becoming a standard request, it is a deliverable, and it belongs in the package rather than in your evenings. The pricing side is in what to charge for a rush turnaround.

When RAW only is the better call

Dual capture is a tool for a deadline, not a default. For a personal project, an unhurried portrait session or any job where the first delivery is a week away, RAW only is less storage, less copying and one less thing to get wrong.

High frame rate sports is the interesting exception: the rush case is strongest there and so is the volume problem, so the answer depends on your buffer, your card speed and whether someone else handles transmission. Some shooters instead rate in camera during play and send a few JPEGs from the body.

JPEG only can work if you trust your in camera look and the client needs small web files, but it leaves no margin for a white balance you got wrong in a room you had never seen.

The test is four questions. How hard is the deadline, how difficult is the light, what usage did you promise in writing, and is anyone else free to run the rush lane. Two or more pointing at speed, shoot both files. Otherwise keep it simple, because RAW+JPEG is a way to hit a deadline safely, not a substitute for a backup plan or a good exposure.

FAQ