Rally is one of the least forgiving disciplines for a camera. You hike to a spot, you get one pass per car, and the light is whatever the forest gives you — often four stops of it in the same frame. Both bodies offer Canon's vehicle subject detection for cars and motorcycles, which holds a car that's sideways rather than drifting onto the trees behind it — on the R5 that arrived with firmware 1.5.0, so check you're current before you rely on it. Canon is upfront that detection can drop out on subjects kicking up dirt and dust, which on a gravel stage is most of them, so it's an assist and not autopilot. The R3's stacked sensor and 30fps electronic burst let you hold through a whole slide with no blackout, and its sealing is the more rally-proof of the two bodies. The R5 answers a different rally problem: 45 megapixels means you can shoot from the safe side of a hillside and still crop into a door number that was fifty meters away. Both write CR3 to a CFexpress card fast enough that the buffer isn't what stops you.
- →Vehicle subject detection that holds a crossed-up car instead of the treeline — with the honest caveat, Canon's own, that dust and thrown dirt can break the lock.
- →Deep, fast bursts (R3 30fps electronic, R5 20fps) for a pass you only get once — enough to open the shutter early and still be running when the car is square to you.
- →Serious weather sealing and dual cards (CFexpress Type B + SD UHS-II) for gravel, rain and a day away from base camp where nothing can be re-shot.
RAW format. CR3 — size varies with the body (24 MP R3, 45 MP R5), the compression you pick and how much detail is in the frame; budget generously rather than planning around an exact figure. · Three or four days of stages, every car worth a burst, and no way to go back means you keep more than you would on a circuit — the card take grows much faster than the keeper count.
Settings by scenario
Gravel stage — car sliding through dust
- Shutter
- 1/640 – 1/1250
- Aperture
- f/4 – f/5.6
- ISO
- Auto ISO 400–6400
- AF mode
- Servo AF, Vehicle detection on, expanded AF area
- Burst
- R3 electronic 30fps · R5 electronic 20fps
Dust is the enemy of the number, not of the photo — the frame that looks best is often the one where the door is already buried. Start the burst before the car fills the viewfinder and keep it running past you; the readable number is usually two frames earlier or later than the pretty one. f/4–f/5.6 leaves enough depth to survive an AF point that lands on airborne gravel instead of the door.
Forest stage — deep shade with dappled backlight
- Shutter
- 1/500 – 1/1000
- Aperture
- f/2.8 – f/4
- ISO
- Auto ISO, cap raised to 12800
- AF mode
- Servo AF, Vehicle detection on, single point on the windscreen
- Burst
- Mechanical 12fps for consistent exposure
A forest stage can hold four stops between the shaded road and a sunlit gap. Expose for the car, not the scene, and accept blown highlights in the trees — a correctly exposed door panel is what keeps the number readable later, by you or by anything reading it for you. On the R5, watch for skew on fast pans and banding under artificial light; mechanical is the safer default here.
Jump, crest or water splash — anticipated action
- Shutter
- 1/1600 – 1/2500
- Aperture
- f/4 – f/5.6
- ISO
- Auto ISO 400–6400
- AF mode
- Servo AF prefocused on the landing zone, Vehicle detection on
- Burst
- R3 electronic 30fps · R5 electronic 20fps, prefocused
You can't react to a crest, so don't try — prefocus on the landing zone, switch to back-button or manual focus so the camera doesn't hunt at the last moment, and open the burst before the car appears rather than when it does. Assume the frames you get are only the ones you were already shooting, and give yourself a second of margin at both ends of the pass.
Service park and podium — static cars, mixed light
- Shutter
- 1/250 – 1/500
- Aperture
- f/2.8 – f/4
- ISO
- Auto ISO 100–6400
- AF mode
- Servo AF, Eye detection for crew portraits, single point
- Burst
- Short bursts, 5fps
These are the easiest frames of the whole event and worth shooting deliberately: numbers clean, sponsor decals readable, crew faces visible under the awning. They're also your own reference for the rest of the week — when stage six hands you a car with a caked-over door, the service shot is how you remember which livery belonged to which crew.
From card to delivery
- 1
Back at the service park or base camp: card reader → Photo Mechanic to ingest the day's stages and cull the bursts down to keepers. Cull generously, but keep the soft frame where the number is readable — it may be the only one.
- 2
Load the event entry list as a CSV, then run the keepers through RaceTagger. Rally is its own sport profile in the app: it reads the race number, driver and co-driver names, team, class, sponsor text and — since rally cars are road-legal — the license plate. The match against the entry list is scored on the race number, the crew names, the team and the sponsor text; the class is read and written into the file's metadata, while the plate is read but not written to the file — and neither feeds the match today.
- 3
Import into Lightroom or Capture One. The EXIF/XMP/IPTC tags travel with the files, so the crew is already on the frame before you touch a slider.
- 4
Edit your selects and deliver by crew number, team or class — or have the day's take split into those folders first.
- Files / event
- Rally frame counts scale with how many stages you can physically reach in a day and how long you hold each burst, so size it from your own take at a comparable event rather than a generic figure.
- Storage
- Size the cards and the drive from your own CR3 count — a rally day is burst-heavy, and you want to hold a full multi-day event without dumping mid-stage.
- Card strategy
- CFexpress Type B for the buffer, SD UHS-II as an in-camera backup — and more cards than you think, because there's no going back to base to dump mid-stage.
- Tagging time
- one unattended batch pass with RaceTagger · typing crew numbers into captions by hand, frame by frame by hand
The takeaway
Rally gives you one pass per car, so the camera work is anticipation — prefocus the crest, burst through the whole slide, and keep the frames where the number squares up to you even when they aren't the prettiest. The naming happens later: cull at the service park, load the entry list, and let the tagging step match on the numbers, crew names and sponsors it can actually read — and flag the caked-over doors instead of guessing at them.
Come off the stage with the crews already named
RaceTagger reads the race numbers, crew names and sponsors off your CR3 files and matches them against the event entry list, so the day's stages reach your editor already tagged. 500 free credits when you sign up — 1 credit per photo after that.
Try it free →Pro tips for this camera
Shoot the approach and the exit, not just the money frame.
A rally car is crossed up through most of a corner, and the door number swings away with it. The frames either side of the slide are where the number squares up to you — that's what makes the pass identifiable afterwards, and you only get the one pass.
Load the entry list before the day's tagging, not after it.
Reading a number off a muddy door is only half the job — turning '14' into a crew, a team and a class needs the event's entry list. Import it as a CSV once and every frame from every stage matches against it; without it you're back to typing names off a results sheet.
Don't plan to tag at the stage — plan to tag when you're back on a connection.
The number reading runs in the cloud, one credit per photo, so a forest with no signal is a place to shoot and back up, not a place to tag. Rally's rhythm suits this anyway: ingest and cull between stages, then run the whole day's keepers as one batch at the service park or the hotel.
Keep the frames where the number is gone — the rest of the car still identifies it.
Rally is a discipline where the number is unreadable more often than not, so the match leans on more than digits: the crew and co-driver names above the door, the team name and the sponsor decals all carry weight, and crew names carry the most. A frame with a caked door and a clean sponsor stripe can still land on the right crew. The class gets read and written to the file too, and on a road-legal car the plate is read but not written into it — neither counts toward the match — and where nothing usable is left, the frame is flagged for review rather than guessed at.
Watch the R5's electronic shutter on hard pans and under rally light pods.
The R5's non-stacked sensor skews fast horizontal movement and can band under LED and pulsed lighting — both of which erode a number that was already marginal. The R3's stacked sensor mostly shrugs it off; on the R5, mechanical is the safer choice for panning and night stages.
Questions photographers ask
What shutter speed should I use for rally photography with a Canon R5 or R3?
Around 1/640–1/1250 for a car sliding through a gravel stage: fast enough to hold the car, slow enough to leave movement in the dust and wheels. Go to 1/1600 or faster for jumps and water splashes. Drop below 1/250 only if you're deliberately panning for a blurred background — the door number softens along with everything else, which costs you the identification later.
R5 or R3 for rally?
The R3 is the more natural stage body: a stacked sensor at 30fps with no blackout, better sealing, and Eye Control AF for grabbing a subject fast when a car appears over a crest. The R5's advantage is resolution — 45 megapixels lets you shoot from a safe vantage point and still crop into a door number, at the cost of visible rolling shutter on the electronic shutter. (These R5 figures are for the original EOS R5; the R5 Mark II uses a faster sensor.) Plenty of rally shooters carry an R3 for the stage and an R5 for reach.
Can AI read a rally car's number when it's covered in mud?
Sometimes — and it tells you when it can't. Rally is one of the harder disciplines for number reading: gravel, mud and spray erase door panels for whole stages at a time. RaceTagger's rally profile scores the match on more than the digits — driver and co-driver names, team name and sponsor text all count, with the crew names weighted most heavily, so a car with a caked door and a readable sponsor stripe can still land on the right crew. The class gets read and saved into the file as well; the license plate is read during analysis but isn't written into the file. Neither is part of the match score today. When nothing usable is left, the frame is flagged for review instead of being assigned a guess.
Does RaceTagger work at a rally stage with no mobile signal?
Not for the tagging step — the number reading runs in the cloud, so it needs a connection. Shoot and back up at the stage, then tag the day's keepers in one batch once you're back at the service park, base camp or hotel. It's 1 credit per photo and the batch runs unattended, so it fits the end-of-day slot rally already has.
Will RaceTagger read Canon CR3 files from the R5 or R3?
Yes. It reads CR3 directly from the embedded preview, so you can point it at a folder of R5 or R3 RAW files without converting first — JPEG and RAW+JPEG folders work the same way. Point it at the day's keeper folder rather than the whole card: the rally profile doesn't use the local scene-skip step, so the spectator and scenery frames you'd never deliver are cheapest to drop in your culling tool first.
Keep reading