A lookbook is not a portfolio. It is a catalog of garments, usually dozens of looks, each needing the same handful of angles, shot under one lighting setup, and delivered with colors that match the fabric on the rail. The Canon EOS R3 is a 24 megapixel stacked full-frame body with an RF mount, built for speed rather than resolution. That combination shapes a specific RAW workflow: modest files, fast bursts, and a heavy emphasis on consistency from the first frame to the last. This article walks through that workflow in the order the work actually happens.
What the R3 spec sheet means for a lookbook day
The published basics are simple. The sensor is full-frame at 24 MP, the lens mount is RF, there is in-body image stabilization, and the card slots are one CFexpress Type B and one SD UHS-II. Files are written as CR3. None of those facts is unusual on its own, but each one has a consequence on a fashion set.
- 24 MP is enough for lookbooks. Web grids, line sheets and most print catalogs do not need more pixels. Smaller files mean a full-day shoot of several hundred looks stays manageable on disk and in the editing pipeline.
- The slot pairing is asymmetric. A CFexpress card and an SD card behave differently under sustained writing, and that decides how you route files (covered below).
- IBIS is a safety margin, not a plan. On a tripod or with strobes freezing motion, stabilization contributes little. It matters for handheld, ambient-light street-style segments.
- The body is a sports and news design. Its speed and autofocus tracking suit models who move, but the controls and ergonomics reward a deliberate setup before the first look walks out.
The honest summary: the R3 does not give you the detail ceiling of a high-resolution body. It gives you speed and consistency, which is what a rack of thirty outfits needs.
Strobes, shutter choice and flicker
Studio fashion usually runs on strobes or continuous LED panels, and the shutter mode you choose interacts with both. The point to remember is that flash sync depends on how the shutter exposes the sensor. With strobes, the mechanical (or electronic first curtain) shutter is the safe default because the entire frame is exposed during the flash. A fully electronic shutter reads the sensor line by line, and a short flash can then light only part of the frame, leaving a band.
If you light with continuous sources, the trade reverses. Cheap LED panels and some modeling lights flicker at rates that interact with fast shutter speeds and produce banding or exposure drift across a burst. The R3 offers an anti-flicker shooting option in its menus; use it as a test, not as a guarantee, and run a short burst against the actual light before the model arrives. Look at the whole burst, not one frame: flicker shows up as a rhythm of brighter and darker frames.
A five-minute pre-shoot test
- Set the final lighting, the final aperture and the final white balance approach.
- Fire a burst of ten frames at the intended shutter mode against a neutral gray card.
- Check the histogram or exposure value across the burst for drift.
- Check the frame edges for banding if you are using a fully electronic shutter with any flash.
- Lock the settings and photograph the gray card once more as the first frame of the real set.
That last gray card frame matters later, because it is the anchor you will use when you check color across the batch.
Routing CR3 files across a CFexpress and an SD card
Two slots can mean redundancy or capacity, and for fashion the right answer depends on how you deliver. Redundancy (writing every frame to both cards) is the cautious option when a client is paying for a single day with a talent booking that cannot be repeated. The cost is that the slower card can set the pace for sustained bursts. Capacity (overflow) is sensible only when you will back up the first card at lunch.
| Mode | Good for | Watch out for |
|---|---|---|
| Same file to both slots | One-off bookings where a card failure would be costly | The SD card can limit how long a burst stays fast |
| Overflow to second slot | Very large looks counts with a mid-day backup | A single failed card can orphan half a day |
| RAW on one card, JPEG on the other | Instant client or art-director review from small files | JPEGs inherit camera color settings, RAW does not |
The third row has a useful trick. A small JPEG stream lets a stylist or art director review on a phone-sized file while the CR3 files stay untouched. Just keep in mind that the JPEG is a camera interpretation and should never be mistaken for the final color.
Batch structure: shoot in looks, not in frames
The most common cause of a slow fashion edit is not the editing. It is that nobody can tell where one outfit ends and the next begins. Build the structure into the capture.
- Slate frame. Photograph a small card with the look number at the start of every outfit. It costs one frame and makes the batch searchable by eye.
- Fixed angle order. Front, three-quarter, back, detail, movement. When the order never changes, a missing angle becomes obvious in a contact sheet.
- Consistent folder naming. Create one folder per rack or per day rather than one monolithic dump. CR3 filenames reset or repeat, so a folder per session avoids collisions.
With 24 MP files and a stacked sensor, burst shooting is tempting, but a lookbook rewards restraint. Bursts are for movement shots (a turn, a swing of a skirt) and for protecting against blinks. For static angles, one deliberate frame with a check is faster to cull than eight near-identical frames.
Culling for garments, not for faces
Most automated culling is designed around portraits, where a sharp eye and open eyes are the main signals. In a lookbook, the questions are different: is the hem visible, is the fabric tack-sharp where the texture matters, did a sleeve fold hide the product detail, is the model mid-blink. A garment-aware pass has three layers.
- Technical pass. Remove frames that are soft, motion-blurred, or clipped at the crop edge. This is where automated sharpness scoring saves the most time.
- Duplicate grouping. Group near-identical frames from a burst so you compare them side by side and keep one, rather than scanning them one at a time.
- Product pass. Human judgment: does the frame show the garment as the client needs to sell it, with the right drape and the right detail?
imagic runs the first two layers locally on your Windows or macOS machine: AI culling scores sharpness, closed eyes and composition, and groups duplicates and bursts. The third layer remains yours, and should. A tool cannot know that this particular collar needs to be visible because the brand is launching it. imagic reads CR3 natively through its own RAW engine, so the culling works on the camera files directly. The desktop app page describes how the culling and batch tools fit together.
Color accuracy across a rack of outfits
Clients return garments that look wrong in photos, and the most common complaint is color. Wrong color has three typical sources: inconsistent white balance across the day, a monitor that is not calibrated, and an over-enthusiastic style applied uniformly to every look.
Anchor the batch
The gray card frame from the start of the set is the reference. Set white balance from it, and then apply the same correction to the whole lighting setup. If the lights change (a new backdrop, a different strobe power), photograph another gray card and start a new color group. Never assume that a mid-day lighting change has no color consequence.
Treat saturated and reflective fabrics separately
Deep reds, royal blues and fluorescent tones tend to clip in one channel before the histogram appears to be in trouble. Satin and sequins push specular highlights past what a simple exposure change can recover. When you batch-edit, apply a base look to every frame, then review the saturated and reflective looks individually rather than assuming they came out the same.
Match to the product, not to taste
If the brand ships a physical swatch or a color code, hold the swatch beside the monitor for the critical looks. The aim is that the buyer opens the box and sees the color on the website. Moody grading belongs to editorial, not to the catalog page.
Batch editing without flattening the set
A lookbook needs consistency, which makes batch editing the right tool, but a single preset on a whole day is a blunt one. A better structure is to edit in tiers.
- Develop one hero frame per lighting setup until it looks right.
- Apply that development to every frame from the same setup as a starting point.
- Walk the contact sheet and fix exceptions: a look with a very dark garment, a look with a white dress, a look shot while the sun came out in a window.
imagic's batch editing and one-click styles support this pattern for tone, color and style adjustments across a batch of exported photos. It is not a retouching tool: skin work, wrinkle removal and garment cleanup belong in a dedicated retouching application. Plan for a handoff, exporting full-size TIFF for the hero images that need that treatment and JPEG for the rest.
Export sets and delivery
A lookbook usually has at least three consumers: the web shop, a PDF or print line sheet, and the retoucher. Define each export before the batch is finished.
| Destination | Format | Notes |
|---|---|---|
| Web shop and social | JPEG, sRGB | Long-edge size set by the platform; sharpen for screen |
| Print line sheet | JPEG high quality or TIFF | Ask the printer for color space and bleed requirements |
| Retouching handoff | TIFF | Full resolution, minimal processing, clear naming |
Name files with the look number and angle so that a retoucher in another city can find what they need without a call. imagic exports JPEG and TIFF, and a free trial of 500 exports lets you run a real shoot through the whole workflow before deciding on a license. If you only need to fix a single hero frame, the free web editor handles one photo at a time.
A worked day, start to finish
Consider a 30-look day, five frames per look in the final delivery. That is 150 final images. Shooting with deliberate frames for static angles and short bursts for movement might produce a few hundred frames per hour of set time. The edit then runs as follows: ingest by rack, run the culling pass to drop soft and blink frames and to group duplicates, review the groups to pick one per angle, develop one hero per lighting setup, apply the batch, fix the exceptions, and export three sets. Notice that nothing in this sequence relies on the camera model beyond file format and speed. The workflow is repeatable because the structure (slates, fixed angle order, anchor frames) is built at capture.
Where the R3 specifically earns its place is the front of that chain: reliable tracking on a moving model, a body that keeps up with bursts, and files small enough that a day does not strain storage. For more on camera and workflow topics, browse the AI and technology category.
Frequently asked questions
Is 24 MP enough for a fashion lookbook?
For web shops, social channels and most line sheets, yes. Very large print campaigns or heavy cropping into garment detail may justify a higher-resolution body, but a lookbook is usually limited by consistency, not pixels.
Should I shoot strobes with the electronic shutter?
Treat it with caution. A fully electronic shutter reads the sensor progressively, so a brief flash can expose only part of the frame. Test with your actual strobes and use the mechanical or electronic first curtain mode if you see banding.
Can imagic open Canon CR3 files from the R3?
Yes. CR3 is one of the supported RAW formats in imagic's built-in RAW engine, and processing happens locally on your Windows or macOS computer. It handles culling, batch editing and JPEG or TIFF export, but not retouching.