This is for Topaz Photo Tech Support.
Pixel 10 Pro DNGs are opened in green color. Please fix.
Thanks.
CC
CVC Productions
I placed this thread in the forum because this was the first option presented to me by the Topaz Help system. I know the community cannot fix this, but I think the community should know about these program failures and how they are addressed by the Topaz Labs staff.
After posting this, I also sent a similar Tech Support request using the ticket system. Keep in mind that my device (Pixel 10 Pro) is mentioned twice (in the subject line and in the body).
I was entirely underwhelmed with the Tech Support response received. Please note that the response was not generated by an AI robot, but by a human being. I will quote below both, the response I received and my rebuttal, without any further editorializing.
RESPONSE RECEIVED:
Hello Cristian, John here for the Topaz Photo team 
Thanks for reaching out.
Currently, Topaz Photo does not support the Google Pixel 8 Pro, but we do have an open ticket with our development team to support this camera model fully in the future. I’ve added your information to this ongoing support ticket, and the team will keep you updated as we work on adding support for it.
While we don’t have an exact timeline for when this will be available, I can assure you that our team is hard at work on getting this camera model supported 
In the meantime, the workaround is to convert your RAW DNG files to TIFF or another non-RAW format.
For more information about the cameras currently supported, you can check out our Topaz Labs Documentation page below 
Topaz Photo | Supported Cameras & Files
Also, could you send some more example RAW files for our development team to have on hand for further investigation? You can securely submit your image(s) to my Dropbox using the link below
Dropbox File Request
Please send me a note to let me know you sent something.
I’ll keep an eye out for your reply. If you have any other questions in the meantime, feel free to contact me here.
MY REBUTTAL
Hello Mr. Sloan,
Dear Mr. Yang,
As you requested, DNGT file
PXL_20251208_224546369.RAW-02.ORIGINAL.dng
sent.
Please note that I take issue with your response.
I have also sent a copy of this email to your CEO, Eric Yang.
Mr. Yang, please provide your feedback.
1. The inaccuracy in referring to the wrong device type is troubling. How could you possibly provide any meaningful technical assistance for my specific situation if you have the wrong device? Would you submit a request to your developers to speed up the DNG compatibility for a Pixel 8?
2. Sending me to view your list of supported devices is useless and rather insulting. Yes, it does CYA (“cover your ass”), but how is that technically helpful to my use case? Yes, I know how to read docs. Do you actually expect that I will now go to your doc, read the list, discard my Pixel 10 Pro and purchase another phone? I do own tens of thousands of dollars of professional photo equipment (which, yes, appears on your list), but for some specific use cases I prefer to use a Pixel 10 Pro, if that is OK with you. And I expect a popular device launched in August 2025 to be compatible with a photo program I am paying a hundred-dollar-plus subscription on. Of course, at my next renewal date I will seriously consider dropping this subscription.
3. As I indicated, I am not using some niche off-brand device imported from AliExpress. I am using a flagship USA device, with 8 to 11 million devices in existence, produced by the developer of the Android ecosystem, a device used by many Android ecosystem professionals and developers.
4. There is nothing voodoo about the DNG files produced by the Pixel 10 family of products. I have many other photo processing software, and without exception, 100%, they all work perfectly with the DNG files from the Pixel 10 Pro. If there is some minor difference with this specific model, it appears all other companies that produce all the other software I am using have made the necessary minuscule adjustment and have propagated it to their current versions. But not Topaz Labs. Topaz Labs “team is hard at work” to fix this, has been for the past 7 months and was not able to this date (middle March 2026) to come up with a solution. Not very reassuring.
5. Your response “we don’t have an exact timeline for when this will be available”, again, CYA (“covers your ass”), but provides zero information and zero confidence that this will be addressed and remedied in the quickest way possible. Nobody really expects that you would give a fixed date ETA. May I suggest you skip this “we don’t have an exact timeline for when this will be available” as it is terrible Customer Support and Public Relations and replace it with something more intelligent and more reassuring to your customers. Other companies have learned how to do that while skipping the CYA part.
Your response, Mr. Sloan, in its inaccurate, non-informative and noncommittal grandeur, is a typical case study for why Artificial Intelligence Agents (which do not make device errors) will soon replace such asinine “human response”. If you and your Customer Service management would like to preserve the “human touch” in your company and not let your Customer Service staff be replaced by AI, may I suggest seriously revising your Customer Service standard responses with something better (other companies have already done that), that will present a compelling case to keeping your job (as opposed to being replaced by AI.
Respectfully,
Cristian Coban, Ph.D.
CVC Productions
**********************
If anyone wishes to comment or add their 2 cents, please do so.
Topaz Photo raw support is based on a third party library called LibRaw.
Based on the notes in the link, it appears that Topaz raw support is currently about two years out of date. The latest version of LibRaw was released in January this year (it doesn’t include the Pixel 10, but it does have 8 and 9)
1 Like
As stated in my follow-up email, I’m sorry for the typo; it was simply an error on my part. However, all information other than the camera model provided to you was accurate. Thanks again for sharing your input and thoughts, on the Support side we will be sure to share this information with the developers.
Happy Editing 
