Phocus 4.1.2 Has a Critical Color Preview Regression

If you have a Hasselblad X2D II (or any modern Hasselblad body) and edit your 3FR files in Phocus 4.1.2 on Mac, your previews have been lying to you since the 4.1.2 update shipped. Every file you open shows up in the main viewer with flat, desaturated colors that do not reflect what the Hasselblad color pipeline should be producing. The colors you see in Phocus are not the colors in your image.

This bug was first spotted publicly by u/freddiew88 on r/hasselblad on 2026-04-09, the morning after they updated to 4.1.2. They compared them to their own TIFF exports, and noticed that something was very wrong with the default RGB rendering. They described it as "pretty much a debilitating bug" in the thread. I saw their post, reproduced the bug on my own machines, and spent far too many hours going deeper to figure out what changed between Phocus 4.1.1 and 4.1.2. Everything that follows in this post is built on their original observation. The credit for spotting the bug in the first place is entirely theirs.

This is not a display calibration issue. It is not a macOS color management quirk. It is not Apple's True Tone doing something weird. I have reproduced it on a MacBook Pro Liquid Retina XDR, an Apple Studio Display, and a Pro Display XDR, all with True Tone disabled. The bug is inside Phocus itself, and it affects every Mac user of 4.1.2 on every 3FR file, at default settings, with no user interaction required.

See the Phocus 4.1.2 color bug for yourself

If you want to see the bug with your own eyes in the next 30 seconds, there is a direct way to demonstrate it inside Phocus itself without exporting anything. The key is a hidden tool called "Reproduction" that ships with Phocus but is not enabled in the default tool layout. Most Phocus users have never seen it, which is part of why this bug has been quietly affecting people without them realising. Adding it temporarily is the quickest way to show yourself the difference.

1. Open a bright, saturated 3FR file in Phocus 4.1.2. Fall foliage, a vivid sunset, an autumn forest scene, or anything with rich orange, red, or deep blue content works best. The more saturated the subject, the more obvious the bug.
2. Right-click on the tool panel area at the right side of the viewer and select "Reproduction" from the popup menu. This adds the Reproduction tool to your tool stack.
3. In the Reproduction tool, look at the Working Space dropdown. It will be set to "Hasselblad RGB". This is the default state for every file in Phocus 4.1.2 on Mac. What you are looking at in the main viewer right now is the state every 4.1.2 user sees by default on every file they open.
4. Now toggle Working Space to "Hasselblad L* RGB".

Watch the preview.

The change should be immediate and dramatic. Colors that looked muted and flat a second ago now show up with the full Hasselblad color pipeline. Oranges pop. Reds deepen. Contrast comes back. The whole frame wakes up. On a bright foliage or sunset image the difference is not subtle. It is night and day.

That second state, the Hasselblad L RGB rendering, is what your image actually looks like when Phocus does its job correctly. The first state, the Hasselblad RGB default, is the bug. If you cross-check by exporting a 16-bit TIFF with the factory output preset and opening it in macOS Preview, you will see that the TIFF matches the Hasselblad L RGB preview, not the default Hasselblad RGB preview. The export pipeline still produces correct pixels, but the default preview pipeline does not. (This is covered in detail in the technical section later in the post.)

Toggling Working Space to Hasselblad L* RGB is not a practical fix for this bug (more on why later), but it is the clearest demonstration you can do inside Phocus of exactly how much the default 4.1.2 preview is hiding from you.

What is actually happening

I went digging to figure out what changed between the two versions, and the picture that emerged is clear at the level of observable behavior. I will cover the code-level details later in this post for anyone interested, but here is the plain-language version:

Phocus internally has two different rendering paths for Hasselblad files. One produces the preview you see in the main viewer. The other produces the pixels that get written when you export a TIFF. In Phocus 4.1.1, both paths produced the same correct HNCS-rendered output. In Phocus 4.1.2, the export path is still correct, but the preview path has regressed. It no longer applies the full Hasselblad color pipeline the way it used to. The result is a flat, desaturated preview that does not match the file's actual rendered color.

The practical consequence is worse than it sounds. You are editing against a preview that is lying to you, and then exporting correct pixels that reflect edits you made to compensate for the lie. Every saturation, white balance, contrast, shadow, or highlight decision you make in 4.1.2 is being made against the wrong reference image. When the export comes out looking over-saturated or over-corrected compared to what you intended, that is why.

The only confirmed fix: downgrade to 4.1.1

There is no in-app workaround for this in 4.1.2. The only fix that has been verified to resolve the bug is to downgrade to Phocus 4.1.1. Hasselblad publishes previous version installers on their support site, so the downgrade itself is straightforward.

The practical tradeoff is small. Phocus 4.1.2 was a minor point release and its user-facing additions were modest. You are not giving up significant new features by dropping back one version. You are giving up a broken default preview in exchange for working default behavior. If you depend on Phocus for editing, this is worth doing now rather than waiting for Hasselblad to ship a fix.

Alternatively, if you cannot downgrade for some reason, a partial mitigation is to export a TIFF of anything you are editing and use a color-managed viewer (Preview.app, Capture One, Photoshop) as your actual reference while Phocus handles the adjustments. It is clunky, but it gets you back to correct colors for judgement purposes.

A note on the Reproduction tool workaround

If you have already gone looking for a fix and found the hidden Reproduction tool, you may have noticed that toggling its Working Space from Hasselblad RGB to Hasselblad L* RGB does reveal the correct rendering. This is how u/freddiew88 first confirmed the bug existed, and it is how I confirmed it on my own machines. It is a useful diagnostic. It is not a practical workaround.

The Reproduction tool is not enabled in the default Phocus layout and has to be manually added via the tool panel popup menu. Even once added, the Working Space toggle applies per image, not globally, so you would be toggling it manually on every file you open. There is also a secondary bug where toggling back from Hasselblad L* RGB to Hasselblad RGB fails to revert the preview (the state gets stuck in memory and survives Phocus restart). Between the per-image friction and the stuck-state secondary bug, the Reproduction tool is not a real answer. Downgrading to Phocus 4.1.1 is the real answer.

What I found in the code

I also spent time comparing the Phocus 4.1.1 and 4.1.2 binaries to narrow down what changed between the two. Two of Hasselblad's internal frameworks show significant churn in 4.1.2, and one specific method that previously handled syncing the preview's color state with the current image correction data was removed in 4.1.2 with no like-for-like replacement. The export path in 4.1.2 got a corresponding refactor that kept it working correctly; the preview path did not. The detailed binary analysis is in the bug report that went to Hasselblad engineering as a suggested starting point. I will write it up as a standalone technical post for anyone who wants the full reverse-engineering breakdown.

Status with Hasselblad

I filed a detailed bug report with Hasselblad support on 2026-04-09 with a complete evidence package: screen recording, side-by-side screenshots, histogram captures, a sample 3FR file, and the symbol-level diffs of the affected frameworks. The report walks through the reproduction steps, the observed behavior, the code-level analysis above, and suggested starting points for investigation.

I have not yet received a substantive response. Hasselblad support typically sends an automated acknowledgment within a few hours and a substantive engineering response within several days to weeks, depending on the issue. I will update this post when there is meaningful news. If you are affected and want to add weight to the report, filing your own ticket with Hasselblad support is the most direct way to signal how widespread this is. Reference the "default Hasselblad RGB preview rendering regression" so they can match it to the existing report.

What you should do now

If you shoot Hasselblad and edit in Phocus 4.1.2 on Mac:

1. Stop making color decisions against the current Phocus 4.1.2 preview. It is not showing you your actual file.
2. Downgrade to Phocus 4.1.1. This is the only confirmed fix. Hasselblad's support site has the previous version installer.
3. If you want to use 4.1.2 anyway, export to TIFF and use a color-managed viewer as your color reference while editing.
4. Consider filing a ticket with Hasselblad support. The more users who report this, the faster it gets fixed.

I will update this post when/if Hasselblad ships the fix.

References

1. u/freddiew88 on r/hasselblad, "PHOCUS COLOR BUG? anyone else experiencing this?"
2. Hasselblad Phocus download page
3. Hasselblad customer support