Most firmware updates are a yawn. You read the changelog, scroll past three bug fixes, and update the camera the next time you’re charging batteries anyway. Canon’s EOS R5 Mark II Firmware v1.3.0 isn’t that kind of update. It’s not a headline-grabber either — there’s no new burst speed, no surprise codec — but if you actually pay your bills with this body, several of the twenty changes will quietly make your week easier.
I went through Canon’s v1.3.0 release notice (released 13 May 2026) and grouped the changes by who actually feels them on a job: event and wedding shooters, sports and action shooters, hybrid photo/video creators, and people running multi-body or tethered workflows. Skip whatever doesn’t apply.
For event and wedding shooters: AF that gives up less
The single most useful change in v1.3.0 is buried in change #2 of Canon’s list: improved tracking and detection for Register people priority in challenging conditions — profile views, blurred or partially obscured faces, small subjects in the frame, and children — and this improvement applies even when the feature is set to Off.
If you’ve shot a reception or a school event, you already know the failure mode this fixes. The bride turns her head to laugh at someone three feet away from her face. A kid runs through the frame and your camera lurches to grab him. A guest’s hand crosses your subject’s chin and the box jumps to the wrong person for two frames, then comes back, then leaves again. None of those moments are catastrophic individually. Stack a thousand of them across a wedding and you’re spending an extra hour culling near-misses.
Canon doesn’t quantify the improvement, and there’s no way to A/B test it cleanly against the prior firmware on the same scene. But the language matters: “profile views, blurred or partially obscured faces, small subjects, and children.” That’s a precise list, and it covers the cases that actually cost you keepers in real venues.
A practical follow-up: if you’ve been compensating for soft AF with high shutter speeds and pushed ISO, take the win and back off slightly. Two-thirds of a stop more light at the sensor goes a long way on indoor receptions where the ceiling is the only bounce surface. If it’s been a minute since you thought about that tradeoff, SYA’s guide to ISO walks through where the safe ceiling is on modern full-frame bodies and how to think about it scene by scene.
For sports and action: the football mode is a hint, not the headline
Change #1 adds an American Football option inside Action Priority, specifically tuned for subjects wearing helmets and shoulder pads. The obvious reading: if you shoot football, turn it on.
The less-obvious reading, and the one that matters to more photographers: Canon is now publishing sport-specific AF profiles whose entire job is to recognize a human body when the face is effectively gone. Helmets, pads, masks, goggles, motorcycle visors — all of these have historically been kryptonite for face-priority systems. A profile that explicitly trains for an obscured face plus characteristic body silhouette is exactly the right architecture for that problem, and it suggests more profiles are coming.
If you shoot hockey, lacrosse, motocross, downhill skiing, or any sport where the face is gear-occluded, try the American Football mode anyway and see how it behaves on your sport’s body shape. Worst case, it’s no worse than the standard people detection. Best case, you’ve found a workaround until Canon ships the profile that’s specifically yours.
The shutter-side fundamentals do not change with firmware. You still need enough shutter speed to freeze the action you care about — or, more interestingly, you still need to choose when motion blur should be a creative tool instead of a mistake. If you haven’t deliberately reset your shutter-speed defaults in a season or two, SYA’s shutter speed guide is the fastest way to do that.
For hybrid shooters: close-up demo AF is a small change with a big payoff
Change #3: AF for close-up demos is now usable during movie recording in Movie manual exposure, Movie auto exposure, and other Creative Zone modes, and it stacks with your existing exposure and AF area settings.
If you’ve ever filmed yourself talking to camera and held something up to demonstrate it — a lens, a card reader, a print — you already know the problem. The R5 II in default movie AF locks onto your face and refuses to let go. You bring the product into frame, the camera ignores it. You move the product closer, the camera finally agrees, and then when you pull the product away it doesn’t find your face again until you wave at it like you’re flagging a taxi.
A dedicated close-up demo AF behavior is built specifically to handle that handoff. It’s the kind of thing that doesn’t matter at all until you record fifteen takes of a product walkthrough and realize the cleanest one had a soft passage right in the middle.
A small caveat worth saying out loud: AF behavior is only half of any focus problem. The other half is depth of field. If you film demos wide open at f/2.8 because that’s how the room looks “cinematic,” you’re asking the AF system to nail a focus plane an inch thick at arm’s length. That’s a hard ask for any camera. A quick sanity check on aperture and subject distance — SYA’s aperture guide is the short version — will save you from blaming firmware for what’s really a physics problem.
For run-and-gun video: false color, level, grid
Three changes belong together. Change #7 lets you turn on False Color Settings while HDR/C.Log View Assist is selected. Change #10 displays the electronic level during movie recording. Change #11 adds a grid overlay during movie recording.
The grid and level changes are quality-of-life. You’re a photographer; you already know what a level horizon looks like in the viewfinder and how a rule-of-thirds overlay reads. Having them available during video is a tiny upgrade that mostly matters because you stop reaching for your finger-on-the-screen guesswork.
False color is the one that’s genuinely useful. If you shoot C-Log and you’ve been judging exposure off a flat-looking monitor image, you’ve been guessing. False color paints exposure zones in distinct colors, so you can see at a glance whether your subject’s skin is sitting where you want it and whether your highlights are protected. It is the single fastest way to learn what a properly exposed log image actually looks like, and once you’ve shot with it for a week it’s hard to go back. Having it integrated with View Assist means you can keep a normal-looking image for framing and flip on false color to check exposure, then flip it back off.
For multi-body and team setups: AF settings on a card
Change #9: Save to card and Load from card have been added to Register/recall AF-related settings, so you can move AF setups between two bodies of the same model.
If you run a single R5 Mark II, this does nothing for you. If you run two, it changes how you operate. Anyone who has tried to keep a primary and a backup camera behaving identically — same custom AF case, same subject detection priority, same custom button assignments for focus area switching — has spent more time than they want to admit toggling menus and trying to remember which setting they changed last Tuesday.
Save your AF setup once, write it to a card, load it into the second body. From that moment forward, the two cameras respond the same way when you press the shutter, which means your muscle memory works on whichever body is in your hand. Second shooters benefit too: hand them the card, they load your settings, you’re working in the same focus language during the same job.
This also gives you a real backup of your AF configuration. If a body needs to be sent for service, you can put your AF setup back onto the loaner body in seconds rather than recreating it from memory.
For tethered and FTP workflows: thread count and the 5 GHz toggle
Two changes together: #4 adds Wi-Fi freq. band selection (5 GHz or 2.4 GHz) when transferring from Bluetooth to Wi-Fi, and #5 adds No. of connections to FTP transfer settings, letting you select the number of transfer threads.
If you shoot in venues — convention centers, hotel ballrooms, school gymnasiums, stadiums — the 2.4 GHz band is often a dumpster fire. Everyone’s phone is on it, everyone’s badge scanner is on it, and the room’s own Wi-Fi is fighting all of them. Forcing the camera to 5 GHz, where it’s allowed, can be the difference between FTP transfers that complete during the shoot and transfers that stall and have to be retried after.
The FTP thread count is more situational. More threads can mean faster transfers on a strong network. On a weak network, more threads can mean each one stalls. Most people who actually need this setting already know what their number is for their typical venue. If you don’t, leave it at the default until you have a problem.
One other workflow change worth noting: change #6 lets you store up to four Color temp values in White balance setting and assign Switch color temperature to Customize buttons for shooting. If you bounce between two distinct lighting environments on the same job — ceremony to reception, outdoors to indoors, stage to lobby — pre-loading your color temps and switching with one button is faster than spinning the dial and watching the live preview.
For everyone else: bug fixes and quiet improvements
Changes #16 through #20 are the housekeeping items: an Err49 fix during SFTP communication, a fix for interval-timer shooting being affected by auto power-off, a fix for the camera restarting when the shutter is pressed during image deletion, a fix for the body not being recognized when connected to a smartphone via USB, and a general system stability note.
If you’ve never seen any of those errors, you won’t feel these fixes. But they’re still good reasons to stay current — especially the smartphone-USB and interval-timer items, which can bite you on a job in ways that don’t show up in normal testing.
There’s also support for DPRAW shooting (change #14) and for Canon’s Software Development Assistance Kit (EDSDK/CCAPI) in change #15. If you’re shooting DPRAW you already know whether you care. If you’re not building tethering tools, EDSDK is invisible to you, but it’s relevant to the third-party apps you use — tether software, remote-capture utilities, studio automation tools. Those apps build against Canon’s SDK, and an updated SDK means future updates of those apps can take advantage of newer body behaviors.
So should you update right now?
The right answer for any firmware update is the same: yes, with a buffer. Update when you have a half day to test, not the night before a job. This release touches autofocus behavior and video overlays — both of which are areas where your specific lenses, cards, monitor, and habits matter. Run a quick test pass: a portrait with messy backgrounds, a video clip with a focus pull from face to object, an FTP transfer in a noisy Wi-Fi environment if that’s part of your day. Twenty minutes of testing tells you whether anything weird is going to bite you on Saturday.
If you’ve been losing keepers to crowded-scene AF, or you shoot any kind of talking-head video where you hand-hold a product in front of the lens, v1.3.0 is one of the few updates worth doing soon rather than eventually.
The firmware file is R5213000.FIR; the official download and instructions are on Canon’s EOS R5 Mark II Firmware Update v1.3.0 page. Grab the updated user manual at the same time — Canon updates it alongside the firmware, and the AF section is the part most likely to matter to you.
