Rally photography is a completely different beast from circuit racing. Cars pass your position once and never again — you get one chance to nail the shot. Numbers are painted on the car, so mud, dirt, gravel, and racing damage progressively obscure them through the day. You're often positioned far from base, shooting multiple stages, then doing your ingest, culling, and tagging end-of-day when you return to base camp and have connectivity. The multi-day event structure means your evening workflow must be efficient, because next morning you're shooting again, not managing deliveries.
- Typical event
- 3-4 day rally (e.g., Rallye Monte-Carlo: Fri morning → Mon afternoon), typically 13-15 stages total
- Photo volume
- 1,000-2,000 photos per day across multiple cars and shooting positions over the day's stages
- Delivery
- End-of-day from base camp (accumulated from all field stages), next morning at the latest
- Key challenge
- No reshoot — cars don't repeat stages. If your shot is blurry or the number is mud-covered, that's the only image of that car on that stage. You have to maximize clarity in tough conditions (dust, gravel spray, mud splatter).
The workflow, step by step
- 1
Pre-Rally: Build Your Start List + Note the Stage Schedule
RaceTagger · A few minutes
Take the official WRC entry list (car numbers, drivers, teams) and save it as a CSV — that's the start-list RaceTagger matches detected numbers against. Also note the stage sequence and approximate timing, so you can organize photos chronologically at the end of the day.
Pro tip
Print a stage schedule and time references. In the field you'll often rely on your watch and notes. Knowing 'SS1 ends at 8:45' helps you organize a big day into logical batches when you ingest in the evening.
- 2
Shoot Multiple Stages (Field Work)
Camera · Full day of field shooting and logistics
Position yourself at several stage locations through the day and shoot cars as they pass. Cards fill quickly. Don't ingest yet — you're still in remote positions, often without reliable power or connectivity. Save the processing for base camp.
Pro tip
Shoot RAW where you can. Gravel spray creates variable lighting, and a car may be dust-covered from earlier stages, cutting reflectivity. RAW gives you latitude that JPEG doesn't — and RaceTagger reads RAW via the embedded preview, so you don't have to convert first.
- 3
Return to Base Camp + Back Up Your Cards
Manual · Short — but never skip it
Evening: get back to base camp (hotel, RV, media center). Immediately back up all cards to two external drives, and to the cloud if you have connectivity. Never rely on single-copy field work.
Pro tip
Bring a portable SSD (no moving parts) and a USB-C hub. Cards take a beating in dust and gravel environments. Redundancy is non-negotiable.
- 4
Batch Cull the Day's Photos
Photo Mechanic · Depends on volume and your culling speed
Ingest the full day's photos into your culler (Photo Mechanic, Lightroom, or your tool of choice) and cull heavily — reject obvious misses, blurs, and repeats. Rally is one-pass, so you get fewer variations of each car, which makes the keeper decision matter more.
Pro tip
Sort by stage and capture time from the metadata. That groups all SS1 photos together, then SS2, and so on — so you're not making edit decisions in a random order.
- 5
Tag the Culled Photos with RaceTagger (at Base Camp)
RaceTagger · Batch runs unattended while you do other evening tasks
Once you're back on connection at base camp, run RaceTagger on the culled set. It reads each car number — including ones partly obscured by mud, dirt, and gravel spray — and matches it against your entry-list CSV. When more than one car is visible in a frame, it handles the multiple detections rather than picking one at random.
Pro tip
Dirt on a number is more readable than you'd expect — the AI works from the structure that's still visible rather than needing a perfectly clean number. Clean numbers tag with high confidence; heavily mud-covered or motion-blurred ones get flagged for you to check rather than guessed.
- 6
Review Flagged Reads + Deliver
RaceTagger · Scales with how many reads got flagged
Review the photos RaceTagger flagged as low-confidence — typically the extreme-mud or motion-blur cases. Confirm or correct them, then let RaceTagger write the numbers into the files (EXIF/XMP/IPTC) and organize the set. Upload to your cloud or client server that evening if bandwidth allows; otherwise queue it for the morning.
Pro tip
Upload before you sleep if you can. Next morning you're shooting early again, and a delivery already posted is one less thing to manage.
Where the numbers get hard
Mud and dirt progressively covering car numbers through the day
Why it's hard. As the rally goes on, cars accumulate mud, dirt, and gravel dust. A crisp white #47 at 8 AM is gray-brown splatter by mid-afternoon. By day three some numbers are barely legible even to the human eye.
How we handle it. The AI reads numbers from whatever structure is still visible rather than needing perfect clarity. It doesn't need a clean number — just enough of the digits to identify them. Where coverage is too heavy, it flags the read for you to confirm instead of guessing.
Gravel spray and dust obscuring the number in the moment
Why it's hard. As a car accelerates away, or another follows closely, gravel spray fills the frame. Those dust particles create a real visual obstruction in the shot — your shutter captures the spray, not the clean number.
How we handle it. The AI looks for number structure underneath the dust and works from partial visibility. Some gravel-spray frames will come back flagged as low-confidence; many still resolve to a confident read.
Racing damage — bent panels and crumpled fenders distorting the number
Why it's hard. Rally cars hit curbs, rocks, and each other. A number painted on a flat door becomes warped when the door is crumpled inward. The digits aren't hidden; they're geometrically distorted.
How we handle it. Vision-based recognition handles a warped number better than rigid character matching, reading the digits through the deformation the way a person reads numbers on a curved surface. Severe distortion still gets flagged for review.
One-pass-only shooting — no reshoot if the number is unclear
Why it's hard. Unlike circuit racing where cars loop the track, a stage happens once. If your shot has the number obscured by dust, that's your only frame of that car from that position. No second chance.
How we handle it. Confidence flagging matters most here. On a blurry or mud-covered shot, RaceTagger flags it as low-confidence rather than committing to a guess. You can verify the ambiguous shots immediately and decide whether it's your only usable image of that stage, or whether a cleaner frame exists from another position.
Remote field positions with no time to process during the day
Why it's hard. Rally stages are often in mountains or rural areas, with no power or connection at your shooting spot. You can't process in real time — you batch everything at end-of-day, back at base camp.
How we handle it. The workflow is built around that reality: shoot in the field, then ingest, cull, and tag at base camp once you're back on connection. RaceTagger's batch processing runs the whole day's set unattended while you handle other evening tasks, so the field/base split doesn't slow delivery.
By hand vs with RaceTagger
By hand
A long evening of culling plus reading and typing every number by hand, on top of a full day already spent in the field
Reading mud-covered numbers by eye is error-prone, and damage and gravel spray make it worse
- —Reading muddy numbers manually is exhausting — squinting at thumbnails under poor lighting, second-guessing yourself constantly
- —One-pass-only pressure is psychological — knowing you have just one image of a muddy #47, you stress over getting the tag right
- —Everything is batched at base camp, so there's no interim quality check during the shooting day
With RaceTagger
A batch run that processes the day's set unattended, plus a focused review of only the reads RaceTagger flagged
Strong on clean numbers; honest flagging on muddy, damaged, or blurred ones so you check those rather than trust a guess
- →Mud handling is consistent — the AI works from the visible structure of the number, so you're not relying solely on your own tired eyes at the end of a long day
- →Low-confidence reads are surfaced for you — you verify just those, not the whole set
- →A faster evening means delivering that night is realistic, so you start the next morning's shoot without a backlog
A typical Rallye Monte-Carlo day (Friday, SS3-SS5 in Provence)
Friday morning you position at Col du Logis for SS3, frost on the ground, cars kicking up gravel. Car #47 is clean, white number clearly visible. By early afternoon you're at SS5; the cars are now caked in dirt from earlier stages, and #47 has a muddy gray-brown film across it — your shot shows maybe two-thirds of the number. By evening you're back at the hotel in Sisteron. You offload cards, back them up to an SSD, and connect to the hotel wifi. You open your culler and cut the day's set down to your keepers, sorted by stage. Then you run RaceTagger over that set. It reads and matches the bulk of them against your entry-list CSV with high confidence, and flags the handful it isn't sure about — some motion blur, some dust spray, a few where the mud is too heavy. You review just those flagged frames, resolving the ambiguous ones by checking another position's shot or referencing the driver list. RaceTagger writes the numbers into the files and organizes them, and you post the set to the team server that evening. Saturday morning you're ready to shoot SS6-SS8 without playing catch-up on Friday's work.
Try RaceTagger on your next rally event
Start with free monthly credits — 1 credit tags 1 photo, no credit card required. Run a previous rally's keepers through it across clean, muddy, and damaged numbers to see how it handles off-road conditions.
Try it free →Questions photographers ask
How does RaceTagger handle car numbers that are covered in mud by mid-day?
It reads the number from whatever structure is still visible, rather than needing a clean surface, and matches it against your start-list CSV. Clean numbers read with high confidence; heavily mud-covered ones are harder, so RaceTagger flags those for you to confirm instead of guessing. You still get the benefit on the readable majority and a short review list for the rest.
Since cars only pass once per stage, what happens if I miss the shot?
That's the brutal truth of rally photography — one-pass-only. If your shot is blurred or the number is obscured, that stage has no image of that car from your position. This is why you shoot from multiple positions through the day. RaceTagger's confidence flagging helps you spot immediately whether your only frame of a car is usable or needs a closer look.
Do I tag in the field or back at base camp?
Back at base camp. RaceTagger's number recognition runs in the cloud, so it needs a connection — you shoot in the field, then ingest, cull, and tag in the evening once you're back on wifi at the hotel or media center. The batch runs unattended while you handle other evening tasks, so the field/base split doesn't hold up delivery.
What's the typical daily volume for a rally photographer?
Roughly 1,000-2,000 photos per day across the stages you cover, shooting many cars from several positions. You cull down to your keepers in the evening, then run that set through RaceTagger as one batch.
How do I handle delivery with unreliable base-camp wifi?
Tag in the evening, then queue uploads for when bandwidth is available — many base camps have better wifi later at night once casual traffic drops. A phone hotspot works as a backup. Worst case, deliver next morning, but staggering uploads through the evening is ideal.
Keep reading