Formula 1 is a number-reading problem hiding behind a speed problem. Drivers carry permanent numbers between 2 and 99 (the reigning champion can run #1), but those numbers are small, styled into the livery, and easy to lose against sponsor graphics — and you are catching them at 300+ km/h. The challenge on delivery night is rarely the shooting; it is turning a card take of thousands of frames into selects that are correctly tagged by driver and team, fast enough to beat the next photographer to the agency.
- Typical event
- 3-day race weekend (4 on a Sprint round)
- Photo volume
- Thousands of frames across the weekend, hundreds in a single session
- Delivery
- Same-day for agencies, next morning for freelance
- Key challenge
- Small, livery-blended car numbers caught at 300+ km/h
The workflow, step by step
- 1
Before the weekend: import the entry list
RaceTagger · A few minutes
Load the FIA entry list as a CSV — driver, car number, team — so every detected number has a name and team to match against. In F1 you only have to do this properly once: permanent numbers stay with a driver across the season, so last round's list is usually a reserve-driver edit away from this round's.
Pro tip
Keep one master entry list per season and tweak it for reserve or rookie call-ups — the permanent-number rule means you rarely start from scratch.
- 2
On track: shoot for at least one readable number
Camera · The session
Frame each sequence so the car shows its number squarely at least once — braking-zone head-on shots reveal the nose number, and corner entry or exit catches the cockpit-side number before the car rotates away. Pure side-on apex pans look great but bury the number, so don't make them your only frame of a car.
Pro tip
Heavy-braking corners are your friend: the nose faces you, the car is slower, and the number is at its most readable.
- 3
Ingest and cull in Photo Mechanic
Photo Mechanic · Varies with your take
Pull the cards and cull the burst sequences down to keepers before anything else — Photo Mechanic is built for exactly this speed. Tagging the culled set, not the raw take, keeps your reads on the frames you'll actually deliver (1 credit = 1 photo).
Pro tip
Cull first, tag second: you only spend a credit on a frame that survived the cull, not on the 119 burst frames you threw away.
- 4
Batch-detect and match in RaceTagger
RaceTagger · One unattended batch pass
Point RaceTagger at the keeper folder. It reads the car number on each frame and matches it to the entry list you imported, so the selects come back labeled by driver and team. RAW files (Canon CR3, Sony ARW, Nikon NEF) are read through the embedded preview — no conversion step first.
Pro tip
Start the batch and go edit or eat — it runs the whole folder unattended while you do something else.
- 5
Review only the frames it flagged
RaceTagger · Minutes on the flagged set
RaceTagger flags the numbers it can't read with confidence — full motion blur, a number rotated away, a low-contrast night frame — instead of guessing. Those flagged frames are the only ones that need your eyes, so you confirm a handful rather than re-checking the whole set.
Pro tip
Night-race and spray frames cluster in the flagged pile — review them as a batch rather than hunting for them across the gallery.
- 6
Import to your editor and deliver
Lightroom · Your normal edit
Bring the tagged keepers into Lightroom or Capture One — the car number, driver name and team ride along in the EXIF/XMP/IPTC metadata your editor already reads, so there's no re-keywording. Edit your selects and deliver filtered by driver or team.
Pro tip
Deliver the agency's priority drivers first by filtering on car number — the metadata is already there, so it's a one-click filter.
Where the numbers get hard
Small, livery-blended driver numbers
Why it's hard. F1 numbers are small and styled into each team's livery, often sitting on a busy sponsor background that swallows the contrast even at close range.
How we handle it. RaceTagger reads the number from the whole frame rather than a fixed character box, so a stylized number on a busy nose still reads when it's facing the camera — and gets flagged, not guessed, when it doesn't.
300+ km/h motion blur on pans
Why it's hard. A creative panning shot prioritizes a blurred background over a crisp number; below roughly 1/250s the number softens and can smear past reading.
How we handle it. Where one frame in a sequence shows the number sharply, that read carries; frames where the blur wins are flagged for review instead of forcing a wrong number onto the photo.
Two teammates, one identical livery
Why it's hard. Both team cars wear the same colors and sponsors — visually they are the same car, and only the number tells them apart.
How we handle it. The number is exactly what RaceTagger reads and matches to the entry list, so teammates separate correctly when the number is visible; when it isn't, the frame is flagged rather than assigned to the wrong driver.
Night races under artificial light
Why it's hard. Las Vegas, Singapore, Bahrain and Jeddah run after dark, where hard track lighting throws hotspots across glossy bodywork and drops the contrast between number and livery.
How we handle it. Clean, well-lit night frames still read; the harsh-glare and low-contrast ones land in the flagged pile so you confirm them deliberately instead of trusting a shaky guess.
Pit-lane clutter and reflective wraps
Why it's hard. In the pit lane the number competes with crew, equipment and overlapping sponsor decals, and matte-or-chrome wraps can throw glare straight across it.
How we handle it. Pit and grid frames are usually closer and slower, so the number is often clean enough to read reliably — and the awkward reflective ones are flagged rather than mis-read.
By hand vs with RaceTagger
By hand
Hours after the checkered flag
Solid early, fades with fatigue late at night
- —Typing driver names and numbers frame by frame after a full shooting day
- —Cross-checking the entry list by eye to tell identical-livery teammates apart
- —Delivering tired and late, when the agency wanted the selects same-day
With RaceTagger
One unattended batch pass while you cull and edit
Reads clean numbers well; unsure ones flagged, not guessed
- →Selects arrive in the editor already labeled by driver and team
- →Only the genuinely hard frames need a human check
- →Same-day delivery becomes the normal case, not the all-nighter
A Las Vegas night-race Saturday
You've shot qualifying under the strip lights and the agency wants a driver-by-driver set before you sleep. You cull the night's take down to keepers in Photo Mechanic, point RaceTagger at the folder, and start the batch while you grab a coffee. It comes back with most frames labeled by driver and team, and a flagged pile of the glare-blown and full-blur shots. You confirm those by eye, import the lot into Lightroom, and the car numbers are already in the metadata.
The takeaway
F1 is a number-reading problem in disguise: shoot the frames where the car number faces you, cull to keepers, then let RaceTagger read and match the numbers it can see and flag the ones it can't. Your selects reach the editor already labeled by driver and team — and delivery stops being an all-nighter.
Try RaceTagger on your next F1 weekend
Import the entry list, point it at your keepers, and get selects labeled by driver. You get free credits when you sign up — 1 credit per photo after that.
Try it free →Questions photographers ask
Can AI actually read F1 car numbers when they're so small?
On frames where the number faces the camera — braking zones, corner entry and exit, the pit lane — yes, it reads them reliably. When the number is fully blurred, rotated away or lost in glare, RaceTagger flags the frame for review instead of guessing, so you confirm the hard ones by eye.
How do you tell two F1 teammates apart when the cars look identical?
By the car number, which is the only thing that distinguishes teammates in the same livery. RaceTagger reads the number and matches it to the entry list, so the two cars separate by driver automatically — and if the number isn't visible in a frame, that frame is flagged rather than assigned to the wrong driver.
Will RaceTagger read my Canon CR3, Sony ARW or Nikon NEF RAW files?
Yes. It reads those RAW formats directly through the embedded preview, so you can tag straight off your RAW files without converting them first. JPEG and RAW+JPEG folders work the same way, and the tags are written into the metadata your editor already reads.
How long does it take to tag a full F1 race weekend?
RaceTagger runs as one unattended batch over your culled keepers while you cull or edit, so it isn't time you sit and watch. Throughput depends on your file sizes and connection rather than your attention; we don't publish a fixed photos-per-minute figure because real-world speed varies too much to promise one.
Does it work for night races like Las Vegas, Singapore or Bahrain?
Yes, with an honest caveat. Clean, well-lit night frames read fine, but the harsh artificial lighting at night races creates hotspots and low contrast that make some numbers harder. Those frames are flagged for review rather than guessed, so night sets just carry a slightly larger pile to confirm by eye.
Keep reading