The color is where you want it. The next step is a retouch, a composite or a layer that belongs in Affinity. PhotoLab 10.1 makes that trip more direct, but there is one useful question to ask before sending the photograph across: which decisions will still be editable when it arrives?

DxO’s announcement describes export to a native Affinity .af document, with the option to include the uncorrected original as a second layer. It was a free update for PhotoLab 10 owners. DIYPhotography’s October 5 account covered the integration, while DxO’s release record dates the announcement to September 29, 2026.

The file carries the developed appearance into the next stage. It does not turn PhotoLab’s individual RAW adjustments into Affinity controls. Keeping that distinction visible makes the convenience easier to use well.

Follow the appearance across the handoff

PhotoLab develops the photograph before export. Its optical corrections, denoising, local adjustments and color decisions shape the image that arrives as pixels in Affinity.

Think of the transfer as a new starting point. The decisions made in PhotoLab remain visible in the appearance. The next application can work with that result using its own pixel and layer tools.

The Photoshop Light layer article offers an example of an adjustment that remains editable inside its own document. The distinction matters because “editable file” can describe different kinds of information.

An Affinity document can retain separate layers and later editing work without also retaining the internal controls of the application that produced its starting pixels. Native format names identify a useful container. The contents determine which decisions you can revisit.

The broader idea of layers in digital image editing helps explain the relationship. A separate layer can be masked, transformed or combined with another surface. Its presence does not automatically reproduce every earlier processing step.

The second layer gives you a comparison

Imagine making a warmer rendering in PhotoLab, then exporting with the uncorrected image included. Hide the developed layer and you can compare the other version beneath it. A mask can reveal part of that lower image.

That changes the visible pixels. It does not undo an individual PhotoLab white-balance or local-adjustment choice. The distinction is small in wording and substantial when you are trying to revise a photograph.

The official PhotoLab export guide explains that the applications use different processing engines. It distinguishes sending an original RAW file into Affinity’s development mode from opening a processed image for pixel editing. The .af handoff discussed here belongs to the latter workflow.

Before export, decide which part of the rendering you want to settle in PhotoLab. Then treat the layered document as the next stage, with its own choices still ahead. If the source rendering changes, you have a relationship between versions to manage rather than a shared set of RAW controls.

Give the later document a history of its own

The guide warns that exporting again to an existing .af destination can lose layers added after the earlier handoff. A direct route does not establish an automatic merge with later retouching or compositing.

A simple version record can keep the stages understandable:

Keep track ofWhat it lets you revisit
Original capture and PhotoLab workThe source rendering
First exported .af documentThe starting appearance for Affinity
Saved Affinity version with later layersThe work added after the handoff
A separately named new exportA candidate rendering to compare deliberately

Those are roles for your files, rather than a claim that the applications assemble that record automatically. Choose names that make the relationship obvious to you.

Before a second export, ask what exists only in the layered document. A retouch may have taken time to build. A mask may depend on the first rendering. Exporting under another name gives you room to compare the new starting image before deciding how it should relate to that work.

The photograph can then develop in stages without making one stage silently stand in for all the others. A shorter trip between applications is useful precisely when you still know which file contains which decisions.

Keep version limits attached to their version

The documented 10.1 route excluded .af export on Intel-based Macs and did not display .af files in PhotoLab’s image browser. Those are version-specific limits, rather than permanent definitions of what PhotoLab can do. Check the current guide for the installed release before planning the workflow around them.

Also check the delivery properties that matter to the photograph. Color profile and embedded information deserve their own inspection. The presence of a native extension alone cannot establish that every property arrived as expected.

A small sample file can make those questions concrete before a larger job: identify the source, inspect what the layered document contains, save later work, then consider how a separately named fresh export would be handled. This is a proposed workflow check, not a measured interoperability test.

A convenient route still benefits from a deliberate pause

The earlier PhotoLab 10 depth-mask coverage concerns decisions inside RAW development. The 10.1 export concerns what happens after that stage produces an appearance. The two subjects meet at the photograph, while their controls do different work.

Use the official press lounge for the originating release record and product resources. For the next handoff, the more useful pause may be a simple one: name the layered version, keep its source relationship clear and decide what a later export would replace.

That gives the convenience of a button somewhere dependable to land.

FAQ

Can Affinity edit the original PhotoLab RAW adjustment settings in this .af export?

No. The handoff transfers developed pixels. The optional uncorrected layer gives another image to compare or mask, rather than recreating PhotoLab’s controls.

What should I do before exporting again to the same .af file?

Protect the Affinity version containing later layers. The guide warns about layer loss on repeated export, so use a distinct candidate filename before deciding what to replace.

Do the 10.1 browser limits apply to every later release?

Do not assume so. They describe the documented 10.1 route. Consult the current export guide for the installed version’s behavior and machine restrictions.