Photo AI appears to add XMP data to TIFF output files if the XMP file is in the same directory

If there is an XMP file in the same directory and with the same root name as a TIFF that is brought into PhotoAI, PhotoAI will add the data to the TIFF metadata even if that XMP data is already cooked into the TIFF. Editing software will now read the XMP edits and reapply them to the TIFF file.

Steps to reproduce issue:

  1. Using Adobe Bridge, edit a RAW file in Adobe Camera Raw, producing an XMP file. For illustration, make a very visible change such as significantly changing the white balance.
  2. Using Bridge, create a TIFF from the edited Raw file for use in Photo AI. This applies the existing photo edits. If you re-open this file in Adobe Camera Raw, there will be no preset adjustments to any of the sliders.
  3. Import the TIFF into PhotoAI and apply noise reduction
  4. Save the result as a TIFF
  5. Open the new TIFF file in Adobe Camera Raw. You will see that the sliders are now positioned to be consistent with the XMP profile from which the original TIFF File was created, essentially re-applying the XMP data.

I have only seen this in Photo AI. Topaz Denoise, Sharpen or Gigapixel do not do this.

I tried applying Photo AI to the same TIFF with and without the XMP file present. Comparing metadata, it looks as if the “Already Applied” flag in the embedded TIFF metadata is switched from True to False when the XMP file is present and Photo AI executes. With that flag false, the editing software reapplies the edits.


If the already applied metadata is not included in the input file, but the XMP with the same name is present, PhotoAI reads the XMP data and includes it in the output TIFF file, with the already applied flag set to false.

If the input file is a DNG and the output is also a DNG, there is no problem. But, if the output is set to TIFF the same thing happens. The XMP data is somehow included in the output TIFF file with the already applied flag set to false.

Topaz Photo AI [v1.3.3] on [Mac] 13.3.1 (a) (22E772610a)

Thanks for reporting this. I was able to reproduce this issue and shared it with my team.

We have a fix for this which will go in the update next Thursday on May 18th.

Please reach out if I can help with anything else.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.