I Asked Hasselblad Which Render Is the Real HNCS. Wrong Question, as it turns out.

Two weeks ago I sent Hasselblad support a question I thought had a one-line answer. I know, I know, I should know better than that by now, right?

But I digress...

Let's get back on topic: when Phocus for Mac and Phocus Mobile render the same RAW file differently, which one is the real HNCS? Twelve days, two support cases, and three engineering replies later, I have an answer of sorts. But it didn't resolve the question. It dismantled it.

Along the way, that answer proved a claim I published in early August wrong. So this post is two things: the clearest definition of HNCS Hasselblad has ever put in writing, as far as I know, and a retraction.

Key finding: According to Hasselblad engineering (August 2026), HNCS is applied to every RAW render in both Phocus for Mac and Phocus Mobile, as an internal processing stage linked to white balance. No preset or import state "is" HNCS. My 9 August claim that default Mac imports aren't HNCS is therefore retracted; the measured gap is vignetting correction.

One RAW file, two Hasselblad apps, two different pictures

The question came out of the import preset investigation. Quick recap for anyone joining late: Phocus for Mac, in its default configuration, does not apply the Adjustment preset you pick in the Import dialog. Every image lands in an as-imported state the toolbar calls "3FR" (the color processing is all there; what is missing is most of the lens vignetting correction, so the corners sit darker), and it stays that way in every export until/if you apply a preset yourself. Phocus Mobile on the iPad offers no preset choices at all, and its one and only render matches the Mac's Standard preset almost exactly, roughly fifty times closer than it sits to the Mac's default import state.

Same file, same company, two different default pictures, about ten percent of full scale apart. I naively assumed that surely one of them had to be the real HNCS rendering that the marketing promises? Hasselblad themselves describe HNCS as a color system that runs "from the initial capture to post-editing"¹ and removes the need to fiddle with profiles. Well, OK then! Which of your two renders is it then?

On 7 August I put that question to Hasselblad support, with the measurements attached.

Hasselblad's first answer: crop settings

The engineering reply arrived on 14 August:

Both are valid HNCS renderings. Phocus includes 5 factory preset adjustment templates. Users can select the appropriate template based on their scenario, then make fine adjustments. [...] "3FR" represents the embedded adjustment scheme within your 3FR file. It has the same basic settings as "Standard," but includes additional crop settings.

"Both are valid HNCS renderings" should have been the first hint of where this would end up, but I was more than a little confused by the second half. Crop settings cannot be the explanation for what I measured mostly because none of the test images was ever cropped. All three exports, Mac default, Mac Standard, and the iPad's render, are 11656 x 8742 pixels.

And a crop does not change the value of a single pixel anyway; it changes which pixels you keep, as I had to explain to Hasselblad Engineering. The difference I measured is radial, strongest in the corners, which is the signature of lens falloff correction, and it shows up on every uncropped frame I tested.

So I wrote back the same day and posed the problem as a fork. Phocus Mobile has no preset selector. It produces exactly one rendering, and that rendering matches the Mac's Standard preset. So, either Standard is the HNCS rendering and the Mac's default import state is not, or Phocus Mobile cannot produce HNCS at all, which would be its own defect. I attached the RAW file, all three exports, and checksums, and asked them to pick a branch.

The same answer came back on a different case

While that rebuttal sat with engineering, my separate bug case about the import preset behavior got its own engineering reply. It contained the same crop explanation(!!!), in slightly different words, with no sign anyone had read the rebuttal filed three days earlier on the other case.

I would like to say this surprised me. The first time I asked Hasselblad what the "Use embedded if available" checkbox actually does was last November. That reply asked me for a screen recording, and the thread went quiet. The checkbox that decides whether your chosen preset gets applied at all appears nowhere in the official Phocus manual, which still only documents the software up to version 3.8. Nine months of asking, and the closest thing to documentation is still a support thread.

Then something approximating a real answer landed.

What is HNCS, according to Hasselblad?

According to Hasselblad Engineering, HNCS is a processing stage that both Phocus apps apply to every RAW render. Always. That is the answer that arrived on 19 August, this time from their engineering team after they had "reviewed your findings and measurements again carefully." Quoted in full:

Both Phocus and Phocus Mobile apply HNCS when processing RAW images. HNCS takes effect during the intermediate stages of image processing and is strongly linked to white balance parameters. Since different presets utilize different white balance parameters, this is the primary factor influencing the visual outcome of HNCS. Other post-processing adjustments, such as vignetting or tone curves, do not affect the HNCS processing currently applied to the photo.

Read that twice, because it quietly redefines the thing photographers argue about in forum threads. HNCS is a stage inside the rendering engine. Every RAW file passes through it, in both apps, every time. You cannot turn it off, you cannot select it, and you cannot point at a render and say "that one is HNCS." The as-imported state? HNCS. Standard? HNCS. The iPad's render? HNCS. Asking which render is the real HNCS turns out to be like asking which cup of coffee is the real water.

The presets sit on top of that stage, and per Hasselblad the main way they influence its visible outcome is through white balance. Vignetting and tone curves sit outside it entirely.

And to give credit where credit is due, this definition agrees with my own measurements better than my original interpretation of them did. When I isolated the mechanism on 11 August, the as-imported state and Standard turned out to share one identical color pipeline. The entire visible difference between them, byte for byte, is the Lens Corrections Vignetting slider moving to 100. A lens correction. The exact category Hasselblad now says lives outside HNCS. Their definition and my toggle test are two independent descriptions of the same pipeline, and they fit.

The crop explanation from the earlier replies was not mentioned again because I requested they refrain from diversionary tactics.

The retraction

On 9 August I published a post titled "Phocus for Mac Imports Aren't HNCS by Default. Neither Are Your Exports." Under Hasselblad's definition, that title was wrong, and so was the claim it stood on: that a render without the preset applied is a render without Hasselblad's color science. Every one of those exports carried HNCS. Every render Phocus has ever shown me carried HNCS. What the default import flow withholds is a lens falloff correction.

The measurements in that post were right, and every one of them still stands. The interpretation was mine, and it overreached. The post has been corrected in place with dated updates, and its title no longer makes the HNCS claim. I am also re-checking the wording in the HNCS explainer and the .phos teardown against this definition, and will note any corrections there the same way.

The lesson is one I have preached here before and then failed to follow myself: pixels beat labels. I proved with checksums that the pixels differed, then reached for a label the pixels never claimed. In my defense, if they'd just have documented all this in the first place we wouldn't be here.

For completeness, Hasselblad also confirmed the behavior that started all this. The default import flow skipping your selected preset is, in their words, "expected behavior." As is the checkbox re-ticking itself every time Phocus restarts. None of it is a bug in their eyes, which makes the practical advice below permanent rather than a workaround.

What does this settle, and what stays open?

Settled: the community had the shape of this right years ago. A Luminous Landscape analysis from 2015² modeled HNCS as white-balance-driven color transforms selected per illuminant, and "strongly linked to white balance parameters" is the first time Hasselblad has confirmed that link in writing, as far as I know. Settled too: preset differences are adjustments layered on one shared color pipeline, which is exactly what the .phos sidecar teardown found when it diffed the factory presets.

Open: one detail of Hasselblad's answer does not, however, line up with that same teardown. They say different presets "utilize different white balance parameters" as the primary factor. The sidecar diffs across all five factory presets found sharpening and tone curve changes, and no white balance delta at all. Maybe presets pass the as-shot white balance through rather than setting their own. Maybe the answer describes a layer the sidecar never records?

The practical rule survives every redefinition unchanged: untick "Use embedded if available" when you import, or apply your preset afterwards with the Adjustments dropdown or Modify. That gets your Mac the same corrected render the iPad produces without being asked.

Which leaves the question I should have sent on 7 August, and which is now sitting with Hasselblad on the still-open bug case: if every render is HNCS, why does Phocus for Mac default to withholding a lens correction that Phocus Mobile applies to every single image? When that answer arrives, I'll be sure to update you all right here.

References

1. Hasselblad, "Hasselblad Natural Colour Solution": hasselblad.com/learn/hasselblad-natural-colour-solution
2. Luminous Landscape Forums, "Hasselblad Natural Color Solution (HNCS) - how it works (probably)": forum.luminous-landscape.com