J.Lo's Sheer Gown at Paris Couture Week Was Online Within the Hour. Here's the Photo Operation Behind That.

Jennifer Lopez showed up to Celia Kritharioti's Paris Haute Couture presentation yesterday in a sheer, sequin-dusted gown with a white feathered coat, sat front row next to her sister Lynda, and by the time most people scrolled past the headline this morning, dozens of outlets already had the photos up. That turnaround isn't luck or a publicist emailing files around. It's a photo pipeline built specifically to get a single red-carpet moment from lens to published page in under an hour, every single show, for two straight weeks of Couture Week.

The Arrivals Pit Runs on a Clock, Not a Vibe

Step-and-repeat arrivals photography looks casual from the outside — a celebrity pauses, smiles, moves on. From the photographer's side, it's a fixed rotation: each accredited shooter gets a narrow window, sometimes as short as 90 seconds, before the next name on the list arrives and attention shifts. There's no reshoot. Whatever frame gets captured in that window is the frame that exists.

That constraint is exactly why couture week photography looks the way it does — sharp, well-lit, consistent angle, because the entire setup (fixed lighting rigs, marked photographer positions, a predictable walk path) exists to remove as much variability as possible from a process that has almost no time to correct for anything going wrong.

From Camera to Getty to Every Outlet, in Under 30 Minutes

Once a photographer has their frames, the pipeline moves fast: cull to the 2-3 usable shots, basic color and exposure correction, caption with the designer, the look, the event, and transmit to the agency's editorial system. Getty and similar wire services then make those images available to subscribing outlets almost immediately — inside 20-30 minutes for a high-demand name at a headline show is typical.

That's the part that explains why a J.Lo photo from a Thursday Paris show is already embedded in an AOL or WWD post by the time most readers wake up the next morning. Nobody is waiting for a "best of the day" recap. The moment a usable frame exists, it's already moving through the system.

Why the Fashion Industry Never Uploads Raw Files

There's a specific reason wire photographers never send a RAW file straight from the camera: a single uncompressed frame from a modern press body runs 40-80MB. Transmitting that over a venue's shared press-room wifi, to an agency that then has to push it out to hundreds of subscribing outlets, would make the whole 30-minute turnaround impossible. Every step of the pipeline — the photographer's own edit, the agency's ingest, the outlet's CMS — re-encodes down to a web-appropriate JPEG, usually somewhere in the 1-3MB range at full resolution.

That's the same tradeoff anyone posting event photos faces, just compressed into a much shorter timeline. Whether it's a fashion show, a wedding, or a product shoot, the same rule holds: shoot at full quality, but the version that actually travels — over wifi, through an inbox, into a CMS — needs to be resized and compressed first, or it becomes the bottleneck instead of the story.

Why Getty's Version of the Photo Isn't the Only One Circulating

By the time a look like this has been online for a few hours, there's a second layer of image traffic happening that has nothing to do with the wire services: fans and fashion accounts screenshotting, cropping, and re-uploading the same handful of published photos across Instagram, X, and TikTok edits. Each generation of that copy-and-repost cycle degrades the image a little further — a JPEG re-saved by three different apps in a row picks up visible compression artifacts that weren't in the original wire photo at all.

That's a separate problem from the speed problem the agencies solve. Agencies optimize for getting a clean first-generation file out fast. Nobody downstream is optimizing for keeping it clean after that — every re-share, screen-record, or "here's a compilation of the best looks" video is working from a copy of a copy, and it shows. If you're the one doing the reposting, saving directly from the original source (the designer's own post, the wire photo credit, rather than a screenshot of someone else's repost) preserves noticeably more detail than grabbing whatever version has already been through five hands.

What This Means If You're Shooting Your Own Event

You don't need a press credential to run the same workflow at a smaller scale:

1. Shoot in bursts through key moments, then cull immediately rather than letting hundreds of near-duplicate frames pile up unsorted.
2. Do a fast edit pass — exposure and crop, nothing elaborate — on only the frames you're actually going to use.
3. Resize before sending anywhere. A phone or mirrorless camera easily produces 20-50MB files; nothing going into an email, a CMS, or a group chat needs that.
4. Batch-compress the full set once you've culled it, rather than exporting one photo at a time.

Optimage handles that last step for an entire shoot at once — drop in the folder, get back web-ready files, free, no account required.

Related reading:

• Taylor Swift & Travis Kelce's Wedding: A Group Chat Compression Guide — the same speed problem at wedding scale
• Social Media Image Optimization Guide 2026 — getting event photos ready for every platform
• Compress Images Without Losing Quality — the core workflow behind every guide on this site