Batch Upscayl stops after 11-16 images

[AdamAnon]

Hi, I have 91 images in the input folder but Batch Upscayl stops after anywhere between 11 and 16 images. Different number every time but never seems to go over 16 images. I'm not running out of VRAM nor RAM, I have 16GB and 64GB respectively. Is this a bug? By design? Some settings needed to be changed? Thanks!

Windows 11 Pro
RTX 4080

[dosubot[bot]]

Hi @AdamAnon! I'm Dosu and I’m helping the upscayl team.

There’s no hardcoded limit on the number of images Upscayl processes in a batch. Instead, the batch process stops if it encounters any error with an image—there’s no retry or skip, so a single problematic file or transient issue will halt the entire batch, which explains why you see it stop after a variable number of images each time. This isn’t by design as a batch size limit, but rather a result of strict error handling in the current implementation.

On Windows 11 with NVIDIA GPUs, there are also known issues that can cause Upscayl to hang or stop during batch processing, sometimes related to folder paths or environmental quirks. Workarounds include running upscayl-bin.exe directly from the command line or moving your images to a different folder before processing. These approaches have helped other users with similar setups and issues [source 1].

If you want to try the command line workaround, you can run something like:

upscayl-bin.exe -i [input_folder] -o [output_folder] -s 2 -m [models_path] -n upscayl-standard-4x

Replace the bracketed values with your actual paths and settings.

If you want to dig deeper, check the Upscayl logs for any error messages when the batch stops—these can help pinpoint if a specific image or file type is causing the failure.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[AdamAnon]

Thank you AI bot.

Posting this for the benefit of anyone else who may run into this issue.

Yes, I looked into the paths already because I thought it might be the spaces but it seems that the spaces are fine and it's the source path length that may be the culprit. Or maybe this happened because the source images were inside a Nextcloud folder, so maybe nextcloud.exe was touching them? Though this was never an issue with any other batch editing programs.

The directory path was 109 plus file name , so around 130 characters long, still within Windows limits, but it looks like it might have been throwing Upscayl off. When I copied my source images to a short path on a scratch disk, under 30 chars, it works fine now.

Problem solved.