We are investigating an issue where batch processing is stalling or crashing the app. Sometimes it’s necessary to force quit the application.
Anyone experiencing this issue should revert to the previous version:
Topaz Gigapixel v1.3.1
Windows: Download
Snapdragon: Download
Apple Silicon Mac: Download
Intel Mac: Download
We will update this thread once a fix is released
Thank you
Great to get a heads up notification like that - thank you all in Support and Devs very much.
Here in Thailand I’ve had just a few hiccups with Gigapixel v1.3.2 and a handful more with web based Bloom +Autopilot +Wonder 3 +Upscale. But I’m really enjoying v1.3.2 and Blooms family and staying cool and re-running things works for me provided the servers are up !
For me it’s too much fun being in the heat of the battle with v1.3.2 and Bloom to consider a tactical withdrawal to v1.3.1 So I’m happy dodging any bullets and keeping my head down when I can just at the moment. Of course I’m retired and not in business or facing a deadline so taking a risk is not life threatening for me ! 
Windows 11 - Gigapixel now freezing during batch upscaling since last update.
We will release a fix for this soon
Thank you
keeps crahing after processing about 5 to 10 images and i unistall and reinstall going to try going back to old version
so unistalling the new versiona nd going back to old version worked for me just to let you all know and hopefully they get it fix and ill update
@marcelo.gutierrez_ca
I added you to the thread for your issue. This will be fixed in the next version we will release this week.
Hi everyone,
We released last night v1.3.3 that includes a fix for that issue:
Released June 27th, 2026
Windows: Download
Snapdragon: Download
Apple Silicon Mac: Download
Intel Mac: Download
Let us know if you have issues after updating 
I am on MacStudio M4 128gb UM Sequoia latest update. I have had it fail at least three times today. Images are around 17xx x25xx AND UPSCALE Set to 2x. It is getting quite tiresome.
@bildad-22363
Pretty sure this is your issue, please update to v1.3.3 to resolve this
