WEC and Le Mans 24h photography is endurance shooting at its most extreme. You're shooting continuously for 6, 12, or 24 hours, watching cars return many times each, managing extreme lighting transitions from sunset to pitch black to dawn, and covering drivers who switch seats mid-race. The cars are grouped in three classes (Hypercar, LMDh, LMGT3) with distinct appearance but similar numbering schemes. Battery, storage, and mental fatigue management are as critical as the tagging workflow itself. RaceTagger's role here is narrow and honest: it detects car numbers in your photos and matches them to the entry list you upload, writing the result into each file's metadata so the repetitive identification work doesn't eat the hours you need for shooting and curation.
- Typical event
- 24 hours continuous (typically a mid-afternoon Saturday start to mid-afternoon Sunday), with pre-race practice and qualifying adding more sessions across the days before
- Photo volume
- Several thousand photos across the full 24-hour race, with additional images from practice and qualifying
- Delivery
- Often continuous during the race (interim batch deliveries between stints), with the full archive expected soon after the checkered flag
- Key challenge
- Lighting transitions and driver changes. A Hypercar passes the camera many times under different lighting conditions (day, twilight, night with headlights, dawn). Different drivers sit in the same car at different times, so the car number alone doesn't tell you who is driving — you have to correlate your shooting time with the team's stint schedule.
The workflow, step by step
- 1
Pre-Race: Build Your Entry List + Driver Schedule Reference
RaceTagger · A few minutes to import the entry list, plus the time to assemble your stint reference
Export the official WEC entry list (car numbers, teams, classes) into a CSV and upload it to RaceTagger as your start-list — this is what detected numbers get matched against. Separately, get the team-provided driver schedules (who drives which stint in which car at what time) and keep them in a reference sheet. RaceTagger matches numbers to the entry list; the driver-per-stint mapping stays in your own reference because it depends on timestamps, not on what's visible in the photo.
Pro tip
Build a simple spreadsheet with columns: Car#, Driver1, Driver2, Driver3, and the start/end time of each stint. At Le Mans especially, driver changes happen through the night. You'll reference this constantly when you decide which stint a batch of photos belongs to.
- 2
Shoot Continuously + Ingest in Stint-Sized Batches
Camera · Allow time for ingest and a quick cull at the end of each stint
Don't try to tag everything at the end. At the end of each driver stint, offload your cards to a laptop in the paddock. Cull the batch quickly, back up to both local and cloud drives (a 24h race means you can't afford to lose footage to a card failure), then stage that batch for tagging.
Pro tip
Use dual-card bodies in overflow mode so you can pull a full card while the other keeps filling — you never run out of storage mid-race. Bring several spare cards to Le Mans; you'll use them.
- 3
Batch Tag Each Stint Against the Entry List
RaceTagger · Batch processing runs unattended; the time scales with the size of the stint batch
Run RaceTagger on each stint's batch. It detects car numbers and matches them to your uploaded entry list, then writes the match into each photo's EXIF/XMP/IPTC metadata. RaceTagger does not infer which driver was in the seat — that's not visible in the frame — so you add the driver-stint context yourself using the timestamp and your stint reference. The benefit is that the number identification, the part that's slow and repetitive by hand, is already done before you start filtering.
Pro tip
Tag stint by stint rather than in one post-race dump. Smaller batches mean you can deliver interim packages and spread the review work out instead of facing one enormous review at the end.
- 4
Review Low-Confidence Reads — Concentrated at the Lighting Edges
RaceTagger · Scales with how many photos get flagged; night and twilight batches flag more than clean daylight
RaceTagger flags low-confidence detections rather than guessing at them, so your review effort goes where the reads are genuinely hard. In WEC, expect more flags at transition moments: sunset (mixed color temperature, dramatic shadows), the darkest hours before dawn, and the rapidly changing contrast right at sunrise. Night shots under headlights also tend to flag more often. Confirm or correct the flagged reads, and check the driver-stint context you assigned.
Pro tip
Night shots under headlights tend to flag more — budget review time for them. They're often the most visually striking photos of the whole race, so the manual confirmation is worth the effort.
- 5
Deliver Interim Batches to Teams + Sponsors
RaceTagger · A short filter-and-export per batch once the stint is tagged and reviewed
At the end of each stint, export the tagged photos as a separate delivery (for example, 'Car #63 — evening stint'). Teams and sponsors want to see their content continuously, not in one dump at the end. Export to a shared folder, notify the team, and move on to the next stint.
Pro tip
Set up a shared Dropbox or OneDrive folder with the team before the race and agree on a delivery rhythm. Predictable interim deliveries are something teams genuinely value during a long race.
- 6
Final Archive + Class-Separated Galleries
Lightroom · Allow a solid block of time for the final import and curation
After the checkered flag, import all of the race's photos into your editor in one master catalog. Because each file already carries its car number and class in the metadata, you can filter by class — Hypercar, LMDh, LMGT3 — and build separate galleries for each. Deliver the comprehensive archive alongside class-specific highlights, and keep everything for long-term archiving; Le Mans photos hold commercial value for years.
Pro tip
Hypercar (the prestige class) photos tend to sell best. A separate 'Hypercar highlights' gallery doubles as portfolio material and helps attract future WEC contract work.
Where the numbers get hard
Extreme lighting variation (day → dusk → night → dawn) on the same car over 24 hours
Why it's hard. Car #63 photographed at 2 PM has bright sidepod lighting; at 2 AM under headlights it's silhouette plus glare; at 6 AM pre-dawn it's gray-blue twilight with reduced contrast. The same number reads completely differently under each lighting regime.
How we handle it. RaceTagger detects numbers across varied lighting and matches them to your entry list. Where a read is genuinely ambiguous — and night and twilight frames are where that happens most — it flags the photo for your review instead of forcing a confident-but-wrong guess.
Multiple classes with overlapping numbers and distinct class-colored door plates
Why it's hard. Hypercar, LMDh, and LMGT3 cars can carry similar-looking numbers, and at distance or under night lighting the class color-coding on the door plate is easy to lose. You need to identify both the number and the class to match a photo to the right entry.
How we handle it. Because you import all three classes in the entry list with their car numbers, RaceTagger matches each detected number to its correct entry. For the photos where the class isn't separable in the frame, the low-confidence flag lets you make the call by hand rather than risk a mis-match.
Driver changes mid-race — same car number, different driver in the seat
Why it's hard. A photo of car #63 at 11 PM shows one driver; the same car at 3 AM shows another after a pit stop. You can't tell from the car alone who's driving — you have to correlate your shooting time with the team's stint schedule.
How we handle it. RaceTagger detects and matches the car number, and writes it into the file's metadata. It does not guess at driver identity, because that isn't visible in the frame — you assign the driver from the timestamp and your stint reference, and that context rides along in the metadata so deliveries can be driver-specific.
Headlight glare and spotlight reflections on the car number door
Why it's hard. At night, cars blast through the frame with headlights at full intensity. Light reflects off the door panel, creating hotspots that overexpose the number area or wash the number into the bright reflection.
How we handle it. Some glare-affected frames still read fine; the ones that don't get flagged for review rather than mis-tagged. Knowing that the hard cases are surfaced — instead of silently guessed — is what lets you trust the rest of the batch.
Fatigue and concentration drift during 24-hour continuous shooting
Why it's hard. This isn't a technical challenge — it's human. After many hours of shooting and tagging, attention lapses. Manual reviews get sloppy, flags get missed, deliveries slip.
How we handle it. Moving the repetitive number-identification step to RaceTagger means you're not hand-tagging every frame at the point in the night when your concentration is worst. Your manual attention goes to the smaller set of flagged reads and to composition, positioning, and curation.
By hand vs with RaceTagger
By hand
Hours of manual tagging spread across the 24h race, typically concentrated into post-stint and post-race review
Depends entirely on conditions and fatigue — clean daylight numbers are straightforward by hand, but night sequences and driver-change cross-referencing are where manual errors creep in
- —Fatigue-driven errors grow as the night wears on — wrong driver context, missed cars, duplicate tags
- —Hard to deliver interim batches because the review is never finished; teams end up waiting until the end of the race
- —Cross-referencing driver changes and stint times by hand is slow and error-prone
With RaceTagger
Batch processing runs unattended per stint, with manual effort focused on the flagged reads and on assigning driver-stint context
Strong on clean shots; harder night and twilight reads are flagged for your review rather than guessed, so the errors that do happen are surfaced instead of buried
- →Interim deliveries per stint — teams and sponsors see content during the race, not only after it
- →Review effort is distributed across the day and concentrated on flagged reads, instead of one long grind at the end
- →You stay fresher for the final stint, when the tension is highest and the photos are most dramatic
Le Mans 24h — a typical Saturday into Sunday
It's race week at Le Mans. You shoot practice and qualifying, cull, and tag against the entry list with RaceTagger so those sessions are already organized before the race even starts. The race goes green in the afternoon and you work your first positions. At the end of the opening stint you retreat to the paddock, offload your cards, cull, and run RaceTagger on the batch. The Hypercars from that stint are detected, matched to the entry list, and written into the files' metadata; you add the driver-stint context from your reference sheet, export the 'Hypercar — opening stint' folder, and drop it in the shared Dropbox so the team sees their content during the race rather than after it. You repeat through the evening and into the night. Night shots under headlights flag more often, but because RaceTagger surfaces the uncertain reads instead of guessing, you catch and fix them quickly rather than discovering mis-tags later. At sunrise the light shifts to dawn blue-hour and the twilight frames flag more again — you review them and deliver the sunrise stint. By the time the checkered flag falls, you've sent several interim packages and you're importing the final 24-hour master archive, filtering by class for the comprehensive delivery.
Try RaceTagger on your next WEC race
Start with free monthly credits — 1 credit tags 1 photo. Upload a set of photos from a previous 24h race across day, night, and dawn sessions to see how it handles lighting transitions and flags the hard reads.
Try it free →Questions photographers ask
How do I handle driver changes when the same car swaps drivers through the night?
RaceTagger detects and matches the car number, but it does not infer the driver — who's in the seat isn't visible in the frame. You build a stint reference before the race (the team provides the schedule) and assign each batch to the correct driver stint based on the timestamp. That context is written alongside the car-number match in the file's metadata, so your deliveries can be driver-specific rather than only car-specific.
What should I expect from number reading in night shooting under headlights?
Night and headlight conditions are the hardest case. Many frames still read cleanly, but glare and darkness make others genuinely ambiguous — and rather than guess, RaceTagger flags those for your review. Plan to spend extra review time on night and twilight batches; it's where your manual attention adds the most value.
Can I deliver interim batches to teams during the race instead of waiting until the end?
Yes, and it's worth doing. Tag and deliver stint by stint so teams see their car and drivers during the race instead of waiting for a single post-race dump. Set up a shared Dropbox or OneDrive folder with an agreed delivery rhythm before the race starts.
How does RaceTagger fit alongside Lightroom, Photo Mechanic, or Capture One?
RaceTagger sits between the shoot and your editor. It detects car numbers, matches them to your uploaded entry list, and writes the result into EXIF/XMP/IPTC metadata — so when you import into Lightroom, Photo Mechanic, or Capture One, the photos already carry their car number and class. It does the tagging step; your editor still handles culling, develop, and delivery.
Does RaceTagger handle the three WEC classes (Hypercar/LMDh/LMGT3) separately?
Yes. Import all three classes in a single entry-list CSV with their car numbers, and RaceTagger matches each detected number to its correct entry. Because the class travels with the entry, your exports can be filtered by class — for example all Hypercars versus all LMGT3.
Keep reading