I get an image I’m happy with on preview and then the export is different, I assume the model re-runs on export changing the image
Hi.
You’re comparing a smaller lower resolution screen preview to a fully processed high resolution image. It’s not recommended to use Redefine on large Images
Here’s a Topaz tip
It is recommended to use images that are 1024px and smaller to get the most optimized result.
Make the most of Redefine when you come across the following type of images:
- Low resolution images (either from crop or otherwise)
- Blurry images
- AI-Generated images
For higher resolution images, try using our Basic models.
Hope this helps
alright, thanks. hopefully there’s an option to have the model regenerate the same as the preview for export in the future
Well, that’s not true on the Mac (or at least wasn’t until 8.2.2).
After „preview the whole image“ was ready you could then save without further delay.
Deleted by author
Same on my Windows 11 PC - if you preview the entire image then the export is almost instantaneous (using v8.3.3).
1 Like
It’s an instant thing - and on the Mac you for sure would notice if the image was reprocessed for saving (as the rendering can take several minutes up to hours there).
Hi Sikboy1029
Apologies Jo.vo has pointed out I incorrectly stated that Redefine is rerun on Export
Apologies once again
1 Like
You are absolutely correct and thank you for pointing this out
1 Like
so it is a bug, alright I guess it’s not solved
Hi all,
I’m having a strange issue with Gigapixel. In the preview window, everything looks great — especially areas with people. The faces and details look refined and acceptable. But when I export the final image, it looks very different. The people appear oddly deformed — not just softer, but with strange artifacts or changes that don’t resemble what I saw in the preview.
It feels like the final render is using a completely different model or settings than the preview. I’ve tried various models (Standard, High Fidelity, etc.), toggled face recovery, experimented with scaling, and tested different export formats, but nothing seems to help.
As a very hacky workaround, I’ve resorted to taking a screenshot of the preview area, then pasting that into Affinity Photo to composite over the original image. It’s obviously far from ideal, but it shows how much better the preview looks compared to the export.
Has anyone else seen this or figured out a way to fix it?
I’m on Win11, RTX5080 and GP 8.3.3.
Thanks in advance!
Deformed heads and faces …
Yes I’ve seen it in the last few days with old monochrome postcards and could not find any options in Gigapixel AI 8.3.3 or Photo AI 3.6.0 to get close to the OK Previews.
My system is Windows 10 PC RTX 4070 Super
I will look for some examples later this evening
At least I’m not the only one on this boat 
Here’s one example — in theory, we should expect a 1:1 match between the preview and the final output, but as you can see, that’s definitely not happening here.
Preview:
Output image:
1 Like
It looks like they’ve finally resolved making everyone look like Topaz Girl.
I’ve never had that issue with the non-generative models, only with the newer generative models (Recover and Redefine). With non-generative models, preview matches output. If your having problems with the non-generative models, then you’ll need raise a ticket with support, so they can work through it with you.
1 Like
Thank you for your insights!
Being new in this forum, do you know if the moderators open the ticket or I have to do something for it?
The link for the contact form is https://docs.topazlabs.com/#contact-us
Or the email address is support@topazlabs.com
1 Like
Thank you, I sent them an email. If possible I will keep things updated here if something comes.
Hi mate, I’ve the same problem in any image. When I do small previews everything is ok, when I calculate full preview I got a lot of deformations. Did you find a solution?
Hi,
I reached out to support and got this response:
The issue is that the preview uses one seed, and another seed is generated when the export is run. This can result in an unexpected output.
I will submit your ticket to the engineers and email you back when we have an update that addresses this.
So it’s definitely a known issue now — hopefully we’ll see a resolution soon.
In the meantime, my workaround is to generate a bigger preview, take a screenshot, and do some compositing. 
