- ✓The 2026 ESPYs took place July 15 at the David H. Koch Theater at Lincoln Center, hosted by SNL's Marcello Hernández
- ✓Musical performances came from De La Soul, Ghostface Killah, Slick Rick, and the Savannah Bananas, alongside red carpet appearances from Simone Biles, Mikaela Shiffrin, Chloe Kim, and Jalen and Ali Marks Brunson
- ✓Red carpet photographers work with fixed backdrops and hard flash lighting, shooting each attendee in a 2-3 second window rather than tracking continuous motion
- ✓Flash-lit red carpet files tend to run larger and noisier than natural-light shots, which changes how they should be compressed before filing
- ✓Wire photographers routinely bulk-compress a shoot before transfer to hit hour-long editorial deadlines, prioritizing speed over a perfectly optimized single file

The 2026 ESPY Awards landed at the David H. Koch Theater at Lincoln Center on July 15, and for a few hours the same photographers who spend most of their year shooting fast-break basketball or a downhill ski run were doing something entirely different: standing in one spot, pointing a flash at a step-and-repeat backdrop, and firing off frames in a 2-3 second window per athlete. Marcello Hernández hosted, De La Soul, Ghostface Killah, Slick Rick, and the Savannah Bananas performed, and the carpet itself pulled in Simone Biles, Mikaela Shiffrin, Chloe Kim, Jalen Brunson and Ali Marks Brunson, and a long list of other athletes who spend the rest of the year being photographed mid-motion, not mid-pose. It's worth pausing on that shift, because red carpet photography isn't a slower version of sports photography. It's a different job with different equipment logic, different file characteristics, and a different clock.
A Fixed Backdrop Changes Everything About the Shot
Sports photography is built around unpredictability — a shooter tracks a moving body through a frame that's constantly changing, adjusting focus and composition in real time because the subject won't come back to the same spot twice. A red carpet works the opposite way. The backdrop doesn't move, the lighting rig doesn't move, and the distance between camera and subject barely changes from one attendee to the next. What does change is the subject, and only for a few seconds at a time before the next name gets called up.
That predictability is why red carpet photographers lean hard on burst mode rather than the single-frame timing a sports shooter might use to catch a specific peak-action instant. With a 2-3 second window and a room full of other photographers all shooting the same angle, there's no time to chimp the LCD and re-shoot — you fire a burst, hope one frame has the right expression and hand position, and move to the next person. That approach alone produces a much higher shot count per subject than sports photography typically does, which matters later when it's time to move the files.
Why Flash-Lit Files Are Bigger and Noisier Than They Look
Hard flash lighting on a red carpet does something specific to a file that ambient or stadium lighting doesn't: it creates high contrast between a brightly lit subject and a comparatively dark background, and that contrast edge is expensive to encode. Compression algorithms work by finding redundancy — smooth gradients and flat areas compress efficiently, sharp transitions and high-frequency detail don't. A flash-lit portrait against a dim background is full of exactly the kind of hard edges and shadow noise that resist easy compression, which is part of why red carpet JPEGs out of a professional body often run larger than a comparably framed shot taken in daylight.
The noise part compounds this. Flash freezes motion well, but the areas outside the flash's throw — the edges of frame, the background behind the subject — often get underexposed and pushed up in processing, and that recovery introduces visible grain. Compress a noisy file too aggressively and the noise itself starts to look blocky and artifacted, which is a different failure mode than compressing a clean, evenly lit frame. Photographers filing from events like this generally know to treat flash-heavy shoots with a slightly gentler compression pass than they'd use on a well-lit outdoor sports frame, precisely because there's less room for the algorithm to hide its work.
Speed Beats Perfection When You're Filing to an Editor
- Shoot the burst, don't chimp between attendees. With a 2-3 second window, reviewing a shot before the next subject arrives isn't realistic — the review happens later, off the carpet.
- Cull hard and fast. A wire photographer might come away with 30-40 frames of a single athlete and file one or two. The other 90% never leaves the camera.
- Bulk-compress the selects before transfer, not one file at a time. Editorial deadlines on a night like this run about an hour from carpet close to published gallery, and processing files individually doesn't scale to that.
- Accept a slightly imperfect file over a late one. A red carpet gallery lives or dies on speed and volume — Deadline, UPI, and WDBO all ran extensive ESPYs galleries within hours of the carpet wrapping, and that turnaround only works because "good enough, fast" beats "perfect, late" in this format.
The Fan Problem: Screenshots Never Look Like the Source
None of that professional workflow reaches most people who actually see these photos. Fans encounter the ESPYs red carpet through a Getty gallery, a wire photo embedded in a Deadline or UPI writeup, or a friend's group chat — and the instinct when you want to keep one is to screenshot it. That's the point where quality actually degrades the most, and it has nothing to do with how the photographer shot it.
A screenshot captures whatever resolution your screen is rendering at that moment, not the resolution the file was delivered at — a gallery image displayed at 800 pixels wide on your phone gets screenshotted at 800 pixels wide, regardless of how much detail the original file held. Then your phone's screenshot tool re-encodes that capture as its own compressed file, on top of whatever compression the gallery site already applied on the way in. Two compression passes stacked on a downscaled capture is a worse result than either pass alone, and it's why a screenshot of a red carpet photo consistently looks softer and more artifacted than the source ever did — even when the phone taking the screenshot has a better camera than the one that shot the original.
If you're saving red carpet shots — your own event photos or a folder of favorites from the night — for a fan account, a moodboard, or just your camera roll, compressing them properly once beats screenshotting them badly. Optimage handles that free, in the browser, without a second lossy pass stacked on top of whatever compression already happened upstream.
Related reading:
- NBA Summer League 2026 Vegas Photo Sharing Guide — another live sports event and the file-sharing habits that come with it
- MLB All-Star Game 2026 Night Game Photo Tips — shooting under stadium lights instead of a step-and-repeat
- World Cup 2026 Sports Photography Tips — the action-photography side of what red carpet work is different from
Frequently asked questions
Where was the 2026 ESPY Awards held?
The 2026 ESPYs took place July 15, 2026 at the David H. Koch Theater at Lincoln Center in New York City, hosted by Saturday Night Live's Marcello Hernández, with performances from De La Soul, Ghostface Killah, Slick Rick, and the Savannah Bananas.
Why do red carpet photos look different from sports action shots?
Red carpet photography uses a fixed step-and-repeat backdrop and repeated flash bursts instead of tracking a moving subject under ambient or stadium lighting. That combination produces different file characteristics — flash tends to introduce more visible noise in shadow areas than natural light does, which changes how the files should be compressed before they're filed or shared.
Continue reading
Try Optimage — it's free
Compress, convert, and optimize images in seconds. No sign-up, no limits.
Start Optimizing Free