Batch video processing
Batch processing is applying one recipe to many files in one unattended run. That sounds unglamorous, and it is the single decision that separates a workflow that scales from one that does not. This page covers what a real batch does, how it differs from an editor's export queue, what to check before buying one, and when a batch is the wrong tool.
Every video tool has a queue. Clicking Render on twelve timelines is not batch processing. Building one recipe, pointing it at a folder, and walking away without opening a single file is. The count is not the point, the unattended part is.
What a real batch does
Three properties separate a batch processor from a tool that merely accepts more than one file:
- The decision is made once. You set the recipe before the run, not during it. That is what makes it unattended.
- The settings are ranges, not values. A batch that applies the same fixed value to twelve files produces twelve identical siblings. Ranges are what make each output its own file.
- The files are never opened. If the tool expects you to review each result inside it, you have not batched anything, you have queued a chore.
Batch processor against an editor's export queue
| Editor with a queue | Batch processor | |
|---|---|---|
| What you do first | Build each edit | Build one recipe |
| Files you open | Every one | None |
| Outputs per source | One per timeline | Many, each different |
| Values | Fixed settings | Ranges drawn per copy |
| Fit for reuse at volume | Poor, it is a per-file tool | Built for exactly this |
Both are legitimate. If you need a different hook on every clip, the editor is the right tool and no batch will replace it.
What to check before you buy one
- Does it change more than metadata? Stripping metadata defeats a checksum and nothing else.
- Does every effect take a range? Fixed values make clones; ranges make distinct files.
- Does it rebuild metadata rather than blank it? An empty metadata block is its own recognisable pattern.
- Can you measure the result? A perceptual hash you can read turns a guess into a number you can act on.
- Where does the file go? A local batch costs nothing per render and needs no upload. A cloud batch pays per render and uploads your source.
- Does it scale workers to the machine? The count of outputs per hour is your hardware plus how well the tool uses it.
The arithmetic of reuse
The reason batch matters is multiplication, and it is worth doing the sum on your own operation rather than on a vendor's. Take one clip that works. If it needs to appear on ten accounts, that is ten files. If it also has to run as a vertical cut and a square cut on two other feeds, the count doubles again. If a second clip joins it next week, the whole set repeats.
A per-file workflow multiplies your hours by the same factor. A batch workflow multiplies your minutes by zero. That is the entire argument, and it is the only one that has ever mattered.
When a batch is the wrong tool
When the files need to differ in what they say. A batch repeats a decision; it cannot make one. If the second audience needs a different opening three seconds, a different claim, or a different ending, that is an edit, and it happens before the batch, not inside it. Every tool in this category is a distribution tool, and distribution is the second problem after the creative one.
Where RepurposeThis sits. One recipe, pointed at your files, producing up to 999 copies of a video per run and unlimited runs, with 51 ranged effects across frames, audio and container, worker count scaled to the machine, and a 64-bit dHash distance you can read per effect before you commit the batch.
Frequently asked
01What is batch video processing?+
It is applying the same recipe to many video files in one run, unattended, with the settings held constant across the set. It is not the same thing as an editor's export queue, where you still decide each file's edit by hand; a batch processor assumes the decision has already been made and repeats it.
02Is a batch video editor the same as a video editor?+
No, and the difference matters when you are shopping. An editor cuts and arranges; its batch feature repeats your export settings for clips you have already finished. A batch processor changes files you did not open, using ranges rather than fixed values, so each output can differ from the next.
03How many videos can one batch handle?+
That depends on the tool and on your hardware rather than on the count itself. The number that matters is outputs per hour, which is set by your CPU cores, your GPU encoder if you have one, and the length of the clips. RepurposeThis writes up to 999 copies of a video per run and scales its worker count to the machine.
04Do batch processors work on images too?+
The good ones do, and it is worth checking before you buy. The same distribution problem applies to a still: one image, several feeds, and metadata that carries the original creation record. RepurposeThis handles JPG, PNG, WebP and TIFF through the same interface.
05When is a batch the wrong tool?+
When the work is genuinely per-file creative: a different hook for each clip, a bespoke edit, a different message. A batch repeats a decision; it cannot make one. If your files need to differ in what they say rather than in how they are encoded, that is editing, and it comes first.
Sources. Perceptual hashing and Hamming distance are standard image retrieval techniques, described in the uniquification guide. Counts, worker scaling and format support describe RepurposeThis 2.x.
Related guides
Apply it to a real batch.
One video in, hundreds of unique files out — on your own machine, for $25 once.