Help
Why does the tool recommend limits for batch size and file size?
The tool does not lock you to a fixed number of files. The recommendations are there because larger jobs are more likely to slow down, fail partway through, or make the later download step less reliable.
If you can add the files to the page, that only means the browser accepted them. It does not guarantee that the same device will finish the whole batch comfortably in one pass.
Why does the page show batch and file-size guidance?
A batch job is more than Add Files. The browser still has to convert the files, keep the results organized, and prepare the later download step. The guidance is there because that whole job gets harder to finish cleanly as the workload grows.
What signs usually mean the batch is already too heavy?
If you see one or more of the signs below, split the batch before you keep going:
- Conversion has clearly slowed down
- Some files have started to fail
- The batch feels heavy on a phone
- Individual files are large
- Downloading the converted results becomes harder to finish
Why do larger batches slow down more easily?
More files means more work in sequence. Larger files mean more work per file. Either way, the browser and device have more to carry through conversion, result handling, and download prep.
Both can slow the process down, even if the files were added without trouble at the start.
Why does the tool mention 200 files, 30 MB per file, and 1 GB total?
These numbers are guidelines, not hard limits.
- Around 200 files per batch: a practical range for many common batch jobs without making the full process too heavy
- Around 30 MB per file: large files can become heavy even when the file count is not very high
- Around 1 GB total: helps keep the full batch from becoming so heavy that later steps start to break down
Treat those numbers as a practical guide, not as a hard stop.
Why can the same batch feel fine on one device and rough on another?
Because the tool runs in the browser, the device matters. The same batch may feel fine on a desktop and noticeably heavier on a phone.
That is normal. The guidance is there to keep the tool usable across different devices, not to imply that every device can handle the same load.
What if I need to process a very large batch anyway?
If you need to work through a large number of HEIC files, this approach is usually more stable:
- Use a desktop if you can
- Split the work into smaller batches from the start
- Keep the successful results first, then move on to the next batch
- If you need fuller EXIF preservation or long continuous runs, use a local tool
Next steps
If the batch has clearly slowed down, or some files have started to fail, split it and try again.
If the problem looks less like batch size and more like a file-level issue, check: Why do some HEIC files fail to convert?