Batch queue
Upload the pile and walk away.
Queue a whole shoot at once. iPhone HEIC files are converted on the way in, each job reports the stage it has reached, and a failure never takes the rest of the batch down with it.
Every job reports the stage it reached, so a stall is visible rather than mysterious
The ceiling
Listing one item at a time is what caps your week.
Upload, wait, save, upload, wait. The waiting is short each time and enormous in aggregate, and it forces you to sit with the tool instead of doing anything else. Queue the whole shoot and the sequence collapses into one step you are not present for.
Photos straight off an iPhone are converted on upload. No exporting to JPEG first.
Each job reports where it is, from building the prompt through to the finished image.
One bad photo fails on its own. The rest of the batch finishes without you intervening.
Pro jobs are claimed ahead of the general queue when the drop is large and the day is busy.
FAQ
Questions, answered.
Can I upload iPhone photos directly?
Yes. HEIC files are converted on the way in, so you do not have to export anything to JPEG first.
Do I have to keep the tab open?
Jobs are processed server side, so progress continues rather than depending on your browser doing the work. Come back to the workspace and the finished images are there.
What happens if one photo fails?
Only that job fails. The rest of the batch keeps going, the failed one is flagged in the queue, and retrying it does not restart anything else.
What does priority processing mean?
On the Pro plan your jobs are claimed ahead of the general queue. It matters when you are processing a large drop at a busy time, and not much otherwise.
How many photos can I queue at once?
A batch can hold as many projects as your monthly project allowance covers, at up to eight photos each. The queue works through them in order.
Batch queue
Process the shoot while you do something else.
The queue keeps running whether you watch it or not.