The Tour de France opened in Barcelona with a team time trial won by Jonas Vingegaard and Visma-Lease a Bike. Whether you're at the roadside with a camera or collecting screenshots and press photos over the next three weeks, the practical problem is volume: burst mode and daily stage coverage pile up fast. Cull hard, keep your picks in a shared album, and compress before you send — not after your phone tells you storage is full in week two.
- ✓Stage 1 was a 19.56km team time trial through Barcelona, finishing on the Côte de Montjuïc climb
- ✓Jonas Vingegaard and Visma-Lease a Bike won the stage; a rule change now gives every rider an individual GC time instead of one blanket team time
- ✓Burst-mode panning shots of a peloton generate 15-30 near-identical frames per attempt — most of them redundant
- ✓A three-week Grand Tour followed at 10-20 photos per stage adds up to 300-600 images by Paris — WhatsApp and Instagram will compress them anyway, so you should control that first
- ✓WebP at quality 80 holds up fine for cycling action shots; you don't need to keep the JPEG originals once you've picked your keepers
Jonas Vingegaard is wearing yellow after stage 1. Visma-Lease a Bike won the opening team time trial through Barcelona — 19.56km along the seafront and through the city center before finishing on the Côte de Montjuïc, a 1km climb averaging 5.2% that turned a fast, flat run into a real selection. Tadej Pogačar and Remco Evenepoel both lost time there. It's exactly the kind of stage 1 gut-punch the Tour has been missing since it dropped the classic team time trial format from recent editions.
There's also a rules change worth knowing if you're following the GC race: instead of every rider on a team getting the same blanket time, each rider now gets an individual time based on when they personally cross the line — the team's stage result is set by whoever's first rider finishes. That gave teams the option to let a fading domestique drop off the pace in the final kilometer without wrecking the leader's real GC gap. It's a small tweak that changed how conservatively teams could ride into that Montjuïc kick.
If you're one of the people who actually stood on the Barcelona seafront with a camera, or you're the person in your group chat who ends up curating three weeks of stage photos for everyone else, the next 21 days have a real, boring, entirely solvable problem: photo volume.
The Burst-Mode Problem Nobody Warns You About
Cycling is one of the worst sports for storage bloat, and it's not because the photos are large individually — it's because getting one good shot requires shooting dozens of bad ones first.
A panning shot, where you track a moving rider so the bike stays sharp while the background blurs into speed lines, has maybe a 1-in-15 hit rate even for someone who does this regularly. So the standard technique is burst mode: hold the shutter, fire 10-20 frames a second, and sort through them afterward. A three-second burst at 12fps is 36 frames. For a fast-moving team time trial where riders pass in under two seconds, you might fire three or four bursts trying to catch one team formation cleanly — that's 100+ frames for one photo you'll ever use again.
Now extend that across three weeks. Even someone who's not shooting bursts — just saving press photos, screenshots of the broadcast, and phone snaps of the roadside crowd — realistically accumulates 10-20 images per stage. By the Champs-Élysées finish, that's 300-600 photos sitting in a camera roll, most of them full-resolution originals nobody's ever going to print.
What Actually Works for a Three-Week Race
The fix isn't complicated, but it only works if you do it daily instead of promising yourself a "big cleanup" after the race ends (you won't do it).
- Cull the same day, not later. After each stage, pick your 3-5 keepers immediately while you remember which shot was actually sharp. Delete the burst rejects on the spot — don't archive "just in case," because you won't look at frame 14 of 36 again.
- Compress before you send, not after. WhatsApp and Instagram both re-compress every image you upload anyway, and they do it worse than you would if you controlled the settings yourself. Convert your keepers to WebP at quality 80 before sharing — file size drops 60-70% from a typical 8-12MP JPEG with no visible difference in a group chat or on a phone screen.
- One running album, not one message per stage. Set up a single shared gallery link at the start of the race and drop each day's picks into it. Twenty-one separate WhatsApp messages spread across three weeks is unfindable by the time someone wants to look back at stage 4's photos in week three.
For anyone actually shooting the race — team photographers, credentialed press, or serious amateurs with a long lens by the barriers — the discipline matters even more, because your originals are almost certainly RAW files or large JPEGs in the 20-40MB range. Filing to an editor or a client on a deadline from a hotel Wi-Fi connection in a random French town is a different problem than sharing to a group chat, and it's one where getting your export settings right in advance saves you from missing a filing window because a 200MB batch won't upload over a weak connection.
Getting Your Keepers Down to Size
Whatever you're shooting on, the workflow is the same: pick your keepers, then run them through a bulk image compressor before you distribute them anywhere. WebP or AVIF at quality 75-82 is the right target for anything that's going to be viewed on a screen — a phone, a laptop, a shared gallery — rather than printed. That's a 60-75% size reduction from a typical out-of-camera JPEG with no perceptible quality loss at normal viewing sizes, and it means you're not the reason the group chat's storage warning goes off in week two.
If you're running a running gallery for a group following the race together — friends, a cycling club, a fan community — a free client gallery does the job better than a chat thread: one link, photos organized by stage, no re-compression damage every time someone forwards an image to someone else.
Related reading:
- Best Image Format for Sports Photography — format and settings guide across different lighting and motion conditions
- Wimbledon Day 4: Centre Court Roof and LED Lighting Photos — another live-event photography problem this summer
- Cloud Storage Costs of Unoptimized Images — what unculled burst folders actually cost you over time
Last updated: July 2026 · Compress your race-day photos free →
Frequently asked questions
Why do panning shots of cyclists take up so much storage?
A panning shot — tracking a moving rider while the background blurs — almost never works on the first try. Serious cycling photographers shoot in continuous burst mode, firing 10-20 frames per second, to get the one frame where the rider is sharp and the background streak is clean. A single 3-second burst at 10fps produces 30 frames, and most phones and mirrorless cameras are shooting these at 12-24MP each. That's 30 full-size images for one final photo you'll actually keep. Multiply that across a whole stage and you understand why cycling photographers' memory cards fill up faster than almost any other sport.
What's the best way to share Tour de France photos with a group chat over three weeks?
Set up one shared album or gallery at the start of the race, not one chat message per stage. Pick your best 3-5 photos per stage, compress them to WebP or high-quality JPEG before uploading, and drop them into the same running collection. This avoids the two failure modes: WhatsApp destroying quality through repeated re-compression on forwarded images, and 21 separate chat threads that nobody can find a specific photo in by stage 15.
Continue reading
Try Optimage — it's free
Compress, convert, and optimize images in seconds. No sign-up, no limits.
Start Optimizing Free