Batch Processing a Folder of Videos: When It Works
Batching pays off when one setting describes the whole job — a dozen clips compressed to 720p, a stack of recordings converted to MP3.
What batch is for
The test is simple: if one parameter set describes the task — "compress these meeting recordings to 720p", "convert these recordings to MP3" — batch it.
Tasks needing per-file judgment (different crops, different targets) do not batch well; processing individually is more reliable.
How a batch runs
Multi-select files at upload; processing runs one by one with overall progress tracked across the batch. A failing file is recorded with its reason and skipped — the batch continues and a success/failure summary appears at the end.
Everything stays local: no queue, no upload. Batch size is bounded by machine memory — keep video batches to about 10 files; images can go much higher.
Three checks before launching a batch
Spot-check two or three files: consistent orientation? similar durations? similar codecs? Set parameters for the majority and re-run outliers separately.
For quality-sensitive jobs, trial-run one file first and inspect the result before committing the whole batch.