Capture One's Hasselblad Support: What You Get and What Stays in Phocus

For years, Capture One's answer to Hasselblad shooters was a support article explaining why it would not open their files. As of this morning, the same article URL announces that it does.¹ Capture One 16.8.3 opens 3FR files from three Hasselblad bodies natively, the result of a formal partnership both companies announced today.²

That sentence would have been hard to believe in January. Capture One began life inside Phase One, Hasselblad's direct competitor in medium format, and the two companies spent years in what Capture One's own CEO once called a "notoriously antagonistic" relationship. The announcement is real, and it's good news. It also leaves out several things Hasselblad shooters might care about, and that's what this post covers.

Key finding: Capture One 16.8.3 (desktop) and 3.3.4 (mobile) open Hasselblad 3FR files natively from the X2D 100C, X2D II 100C, and CFV 100C. Both companies describe the rendering as Capture One's own color; HNCS is never mentioned. FFF files are not supported, there is no HDR output path, and tethering arrives later in 2026.

What Shipped on July 2

Capture One 16.8.3 for desktop and Capture One Mobile 3.3.4 add file support for three Hasselblad models: the X2D II 100C, the X2D 100C, and the CFV 100C digital back (the back half of the 907X & CFV 100C combo, so 907X shooters are covered).³ The supported format is 3FR, the RAW file your camera writes to its CFexpress card or internal SSD. Lens profiles ship for the full XCD line: 19 profiles covering all 18 XCD lenses plus the 135mm with its 1.7x converter, correcting distortion, chromatic aberration, and light falloff.⁴

Tethering is not in this release. Capture One's compatibility matrix lists tethered capture, live view, and wireless as an explicit "No" for all three bodies today; both companies say tethered support arrives "later in 2026."³ ²

What the announcement documents leave out is more informative than what they say:

The rest of this post takes those rows one at a time.

Whose Color Are You Getting?

Not Hasselblad's. Both companies say so in their own words, and neither says the letters HNCS out loud anywhere in the launch materials.

The joint press release says dedicated color profiles were created for each model "so Hasselblad files render with the same true-to-life color Capture One users know and love."² That describes Capture One's color, applied to Hasselblad files. Capture One CEO Rafael Orta put it more plainly in his DPReview interview: "We're very dedicated to making sure that when you open that file, you're seeing colors that are true to our standards."⁵ And again to PetaPixel: "Our engineers worked closely with the team at Hasselblad to ensure the files render to the standard we need."⁶

Capture One's partnership landing page muddies this with the claim that "Hasselblad's color rendering is faithful from the moment you import."⁷ But Hasselblad's own announcement email to its customer list removes the ambiguity: "With colour profiles engineered for each camera, your images will render Capture One's signature true-to-life colour."¹⁴ That is Hasselblad telling its own customers, in its own words, that the new path produces Capture One's look. Whether any of Hasselblad's color science (the matrices and LUTs behind Hasselblad Natural Colour Solution) informed the underlying profile math is stated nowhere, but both companies agree on whose rendering ends up on your screen.

Treat it, then, the way you treat Adobe's Hasselblad profiles in Lightroom: a third party's interpretation of what the files should look like. Sometimes a very good one. But if HNCS rendering is why you shoot Hasselblad, nothing changed today. HNCS still lives inside Phocus, and the Phocus-first workflow I described in What You Keep and Lose When You Skip Phocus still applies, now with one correction (already made to that post): the Capture One leg no longer requires a TIFF conversion to get files open at all.

This is testable, and I intend to test it: the same 3FR rendered in Phocus, Capture One 16.8.3, and Lightroom Classic, with measured color differences rather than vibes. That comparison is the follow-up post.

Capture One Still Has No HDR Pipeline

Nothing in the release notes, the press release, or the landing page mentions HDR, and the silence fits the record. Capture One has never supported HDR output in any form: there is no HDR color management in the application, which is why an HDR TIFF exported from Phocus opens there with blown-out highlights (C1 reads the extended-luminance encoding as ordinary SDR values).

So a 3FR processed natively in Capture One comes out the same way everything comes out of Capture One: SDR only. If you shoot the X2D II partly for its HDR output (Ultra HDR JPEG, HDR HEIF), the new support does nothing for you. The HNCS/HDR/external-editing trilemma I wrote about in the HDR series stands exactly as it was. Phocus remains the only way to get HNCS and HDR in one file, and Lightroom Classic 14+ remains the practical gain-map path if you want HDR output with third-party editing. Capture One's new native path gives you neither; what it gives you is Capture One's toolset without the TIFF detour.

For studio, product, and portrait work, where SDR delivery is the norm and Capture One's strengths actually live, that trade may be completely fine. It just shouldn't be invisible.

3FR Only: Tethered Archives Stay in Phocus

Capture One's master compatibility list is precise about the format: "File Support: 3FR" for all three cameras.³ FFF, the container Phocus generates when it captures tethered, appears nowhere.

If your archive includes tethered sessions, those FFF files still have exactly one RAW processor. That's worth knowing before you plan a migration, and it raises a question about the tethering support promised for later this year: when Capture One tethers an X2D II directly, what file will it write? Neither company has said. (I dug into the 3FR/FFF split, and why renaming one to the other doesn't work, in the Hidden Rules post.)

The camera list will probably grow. Capture One's announcement email to customers phrases it as "Support starts with the Hasselblad X2D II 100C, X2D 100C, and CFV 100C digital back," and "starts with" seems to be doing deliberate work in that sentence. Older bodies (X1D II, H-system) are not covered today.

The Lens Correction Fine Print

One paragraph in the release notes deserves more attention than it will get. Capture One normally performs lens corrections using focus-distance information embedded in the RAW file, and Hasselblad files don't carry it in any form Capture One can read:

"Capture One performs a precise lens correction based on focus distance information from the RAW file. When the file doesn't contain this information, a default correction is applied instead, as is currently the case with Hasselblad cameras. We're working with the Hasselblad team to have this added in future firmware updates, and Capture One will automatically pick it up and apply the more precise correction."⁴

Distance-indexed correction is the industry norm, not a Capture One quirk. Adobe's lens profiles are built from calibration sets shot at combinations of focal length, aperture, and focus distance.⁸ DxO says distortion "depends firstly on the focal length" and "secondly on the focus distance," and calibrates its modules across all of those axes.⁹ Follow that one step further and it lands somewhere uncomfortable: if the file carries no focus distance, Lightroom and DxO have been applying distance-generic corrections to Hasselblad files all along too. Capture One's release note is just the first time a vendor put the gap in writing.

What does a generic correction cost? It depends on where you focus. Distortion and chromatic aberration both change with focus distance, and lens performance shifts fastest near minimum focus, which is why so many designs use floating elements to compensate.¹⁰ At ordinary working distances, a single-distance profile is probably close to right. Close work is where the difference lives.

Recording the distance is also the industry norm. Canon writes FocusDistanceUpper and FocusDistanceLower into its maker notes, Nikon, Olympus, and Panasonic have their own focus-distance fields, and EXIF has carried a standard SubjectDistance tag for decades.¹¹ What Hasselblad writes is anyone's guess: ExifTool, which documents maker-note formats for practically every manufacturer down to Phase One and Leaf digital backs, has no Hasselblad module at all.

That opens a question I didn't expect to be asking today: what is Phocus itself doing? Hasselblad's live Phocus page says the software "calculates the optical corrections for every shot at the given distance and aperture setting,"¹² and the H System manuals back this up for H lenses, describing corrections "guided by the information in the metadata included with each individual capture."¹³ But that web copy names H System and V System glass, not XCD, and I could not find any Hasselblad document making the distance claim for the X System. So either the X System 3FR carries focus distance in a proprietary block only Phocus can read, or Phocus corrects XCD lenses at a default distance like everyone else and the website is describing the H System era. Those two possibilities give different answers to "are Phocus's corrections better," and there's a straightforward way to test which is true. I'll run that test before the comparison post goes out.

Either way, the fix both companies describe is telling: Hasselblad changing what the camera writes into the file, on a shared roadmap, for a partner's software to consume. Camera firmware being modified to feed Capture One is not a press-release pleasantry. It suggests the partnership runs deeper than a file-format SDK handoff.

Does This Replace Phocus?

Hasselblad says no, on the record. "This partnership isn't a replacement for Phocus," the company told PetaPixel, adding that Phocus will be developed alongside the Capture One support.⁶ Orta, for his part, told DPReview the RAW support and tethering "won't be the extent" of the partnership: "Tomorrow is the start line."⁵

My read, clearly labeled as a read: Phocus isn't going anywhere soon, because too much of what makes a Hasselblad a Hasselblad only exists there. HNCS rendering, the HDR output pipeline, HNNR noise reduction, firmware updates, and now FFF compatibility are all Phocus-only. What today's announcement does change is Phocus's job description. Hasselblad no longer needs Phocus to be the studio workflow answer; Capture One can be that, and it's better at it than Phocus was ever going to be. A Phocus that concentrates on being the reference renderer and camera companion, while Capture One handles high-volume commercial work, is a coherent division of labor.

That said, launch-day statements are launch-day statements. Companies discontinue software they promised to maintain, and the honest answer to "what does this mean for Phocus in five years" is that nobody outside Gothenburg knows.

What I'd Do Today

If Capture One is already your editor for other systems, update to 16.8.3 and bring some 3FRs in. You get native files, layers, masks, and the workflow you know. Go in understanding that the color is Capture One's interpretation and everything renders SDR.

If you're on the Phocus-to-Capture One TIFF workflow for HNCS reasons, nothing about today's release forces a change. The TIFF handoff remains the only way to carry Hasselblad's rendering into C1. Native 3FR support is an alternative, not an upgrade, and which one you want depends on whether the color or the convenience matters more. My Phocus Histogram vs Capture One Levels comparison covers one corner of what moving between the two actually feels like.

If HDR output is part of your workflow, skip this entirely. Nothing here is for you yet.

The follow-up post will put numbers on the open questions: measured color differences between Phocus, Capture One, and Lightroom renders of identical 3FRs, how Capture One's denoising compares with HNNR above ISO 6400, and whether Capture One handles files that Phocus 4.2's importer has touched, since that importer rewrites the EXIF camera-model tag in ways that already break DxO PureRaw's model detection. It will also chase the focus-distance question. 16.8.3 is in the in-app updater now.

References

1. Hasselblad camera and lens support in Capture One - Capture One support article; this article ID previously hosted "Why Capture One does not currently support Hasselblad cameras"
2. Hasselblad and Capture One Partner to Bring Native Hasselblad RAW Support - joint press release, July 2, 2026
3. Camera Models and RAW Files Supported by Capture One - Capture One's master compatibility list
4. Capture One 16.8.3 release notes - camera support, lens profiles, and the focus-distance correction caveat
5. Capture One and Hasselblad partner up - DPReview, July 2, 2026, with the Rafael Orta interview
6. Why Capture One is Finally Supporting Hasselblad, and What It Means for Phocus - PetaPixel, July 2, 2026, with Hasselblad's Phocus statement
7. Capture One x Hasselblad partnership page - Capture One's landing page
8. Adobe Lens Profile Creator User Guide - profiles are built from "shooting iterations" at fixed focal length, aperture, and focus distance
9. Geometric Lens Distortion: How DxO corrects optical flaws - DxO on distortion's dependence on focal length and focus distance
10. Things You Should Know About Your Lenses, But May Not - Roger Cicala on close-focus performance and floating elements
11. ExifTool Tag Names index - per-brand maker-note tag tables (Canon, Nikon, Olympus, Panasonic focus-distance tags; no Hasselblad module exists)
12. Phocus for PC/Mac - Hasselblad's Digital Lens Correction description, "at the given distance and aperture setting"
13. H4D range user manual - DAC corrections guided by per-capture metadata
14. "Hasselblad × Capture One: A Refined Workflow" - Hasselblad's customer announcement email, July 2, 2026; publicly reproduced in this r/hasselblad thread

[BUY ME A COFFEE - replace with HTML card]

[SIGNUP BLOCK - add manually]