When Nikon released its first CFexpress Type B cards alongside the Z 9, many photographers discovered that the XQD cards they’d used for years in D5 and D850 bodies were now sitting in a gray area: same slot, same connector, same physical card — yet the two formats are not interchangeable in both directions, and the differences underneath that shared shell matter considerably once you start moving files around.
This article isn’t about which card to buy. It’s about understanding what changed between XQD and CFexpress at the format level, what that means for your data in transit, and how to approach a migration without losing anything.
Same Slot, Different Standard
The physical similarity between XQD and CFexpress Type B cards is deliberate — CFexpress was engineered to use the same form factor, which is why Nikon and Sony were able to offer firmware updates that added CFexpress compatibility to cameras that previously read only XQD. The connector and slot dimensions are identical.
The underlying protocol, however, is not the same. XQD uses the PCIe 2.0 interface with a single lane (x1). CFexpress Type B also uses PCIe but stepped up to the Gen 3 specification and added the NVMe (Non-Volatile Memory Express) command set on top of that. NVMe replaced the older command layer that XQD relied on, and that replacement is significant — NVMe was originally designed for enterprise SSDs, and it introduces a much lower-latency command queue structure than what XQD’s host interface logic expected.
What this means practically: a camera that shipped with XQD firmware is not automatically capable of parsing NVMe commands. The firmware update Nikon pushed for the D850 and D5 bodies effectively rewrote the card controller handshake logic — it is not a minor patch. Bodies that never received that update genuinely cannot read CFexpress cards, regardless of what the slot looks like. Check the firmware notes for your specific body before assuming compatibility.
What Changes at the File Level (Nothing, Actually)
Here’s the part that surprises photographers: the card format migration does not touch your files. NEF, RAF, CR3, ARW — whatever RAW format your camera writes — is stored on the card’s NAND memory the same way a file sits on an SSD. The card is a storage medium, not a codec. XQD and CFexpress use different controller protocols, but neither encodes or reencodes image data on the way in or out.
Copying files from an XQD card to a CFexpress card, or ingesting them into a workstation, produces bit-for-bit identical files provided the transfer completes without error. There is no transcoding step, no quality change, no metadata modification introduced by the card swap itself. The risk during migration is not format corruption — it’s interrupted transfers, card reader incompatibility, or skipping verification steps.
That said, the card reader situation deserves attention. Many USB 3.0 XQD readers marketed before CFexpress became mainstream will not reliably read CFexpress cards even when they fit physically, because the USB-to-PCIe bridge chip in older readers wasn’t provisioned for Gen 3 speeds or NVMe traffic. Some readers with the XQD form factor were simply never validated against CFexpress firmware. If a card reader predates CFexpress availability in the market — check the reader’s own documentation, not just the slot shape.
The Three Situations That Actually Cause Problems
Most migration headaches fall into one of three patterns:
-
Shared-card environments — A body that received a CFexpress firmware update can write to a CFexpress card that an un-updated second body then can’t read. This comes up in production environments where two operators share cards across a Z6 and a D850, for example. Confirm that every body in the chain has been updated before mixing card types.
-
Archive ingest from old cards — Photographers upgrading bodies often have a stack of XQD cards with archived shoots. The cards are still readable by the old body and by XQD-compatible readers, but over time XQD readers will become rarer as the ecosystem moves on. Ingest those archives sooner rather than later, and verify checksums after copying — don’t rely on file-size matching alone.
-
Reader bottlenecks masking write failures — CFexpress Type B cards can sustain sequential write speeds that older USB 3.0 card readers throttle heavily. When a reader can’t keep up, some implementations will silently drop the connection mid-transfer rather than throwing an error. The resulting partial files look intact in the directory listing until you try to open them. Use a reader that explicitly lists CFexpress Type B support and connect it to a USB 3.1 Gen 2 or Thunderbolt port.
CFexpress Type A: A Different Animal Entirely
Sony introduced CFexpress Type A as a smaller variant, used in the A1 and A7 IV among others. Type A uses the same NVMe + PCIe Gen 3 protocol as Type B but in a smaller physical form factor — and it shares a slot design with Sony’s SD card slot in dual-slot bodies that accept either. Type A and Type B cards are not physically interchangeable, despite sharing the same underlying interface spec.
If you are migrating from Sony’s UHS-II SD workflow into CFexpress territory, Type A is the relevant variant to research — not Type B. The two types are part of the same CFexpress 2.0 specification, published by the CompactFlash Association, but implemented in different physical packages targeting different body categories.
Migration Checklist Before You Retire Your XQD Cards
Run through these steps before treating XQD as legacy storage:
- Confirm body firmware — Verify that any camera body expected to read CFexpress has received the relevant firmware update. Don’t assume; check the manufacturer’s firmware release notes for your specific model number.
- Update your card reader — Confirm the reader explicitly supports CFexpress Type B (or Type A if applicable). Check the manufacturer’s compatibility page, not the physical slot shape.
- Ingest and verify archives — Copy existing XQD cards to at least two locations and verify file integrity with a checksum utility before reformatting.
- Don’t reformat until you’ve opened files — File count and folder structure surviving a copy doesn’t confirm file integrity. Open a representative sample from RAW files you care about before wiping the source card.
- Label your remaining XQD cards clearly — Once your primary body is CFexpress-only, XQD cards should be marked accordingly so they don’t accidentally surface in a slot that accepts them physically but won’t write to them reliably.
How This Fits Into a Broader RAW Workflow
The card swap is one node in a longer chain. Once files are off the card and on a workstation, the format questions shift from storage protocols to RAW codec compatibility — which software version can decode which camera’s RAW variant, whether a DNG conversion step makes sense for long-term archival, and how export settings affect what downstream recipients receive. Those questions sit in a different layer than card hardware, and our File Formats coverage addresses the codec and container side in more depth.
The immediate action: if you have XQD cards with unreplicated archives on them, that’s the task with a deadline. Card readers for older formats don’t get manufactured indefinitely, and a format that’s physically intact but unreadable is functionally the same as data loss. Copy first, verify, then migrate your hardware.