Batch Work Without a Batch Upload

Batch usually implies a folder picker and a progress bar with forty files in it. That is not what exists here, and saying so up front is cheaper for everyone than letting people discover it after signing up. Video HD, the video tool in the OpenFilmo workspace, takes one MP4 per run at 32 credits with an estimated 1 to 4 minute wait. There is no multi-select and no folder upload. What a paid plan buys instead is concurrency: two, three or six files in flight at once, depending on tier, so a set of twenty finishes in roughly a tenth of the wall-clock time rather than in a single discounted transaction.

That distinction matters for planning. Parallel slots shorten the wait and do not lower the price, because every file still costs the same 32 credits. A batch of ten clips is 320 credits whether they run one at a time or six at a time. It also means the free tier is not a way to test a batch: Free gives 30 credits a month, which is two short of a single run, so nothing happens until a paid plan is in place. Starter at $9 for 400 credits covers twelve runs. One more boundary is worth stating before a large set goes in: the tool is described in its panel as boosting clarity and fps and publishes no output size, so a batch that needs bigger frames rather than cleaner ones belongs on the AI video upscaler page.

What it does

Built for this specific job, not a generic editor.

How it works

Four steps, no timeline to learn.

1. Normalise the set before you start

   Export every clip with the same codec settings and the same dimensions. A batch that mixes sizes and bitrates produces uneven results, and the variance gets blamed on the tool rather than on the inputs.

2. Test one file from each distinct source

   Clips that arrived from different cameras, contributors or platforms behave differently. One test from each origin costs a few runs and tells you whether the whole set is worth the spend.

3. Fill the slots and keep a simple log

   Note which files are queued and which have come back. With two or three in flight it is easy to lose track, and re-running a file is the most common way a batch quietly doubles in cost.

4. Spot-check the output rather than trusting the queue

   Open a few results at full size and play them. A batch that completed is not the same as a batch that worked, and catching a bad input early is worth more than finishing quickly.

What people use it for

The jobs this actually gets used for.

Why throughput is a plan decision, not a tool setting

Nothing you can configure changes the price of a file. Only the waiting does.

It is worth being blunt about the economics, because batch pricing is where expectations usually go wrong. The unit cost is 32 credits and it does not move with volume. There is no cheaper-per-file tier and no bundled rate, so the way to spend less on a batch is to run fewer files through it — which is exactly what the triage step is for. Testing one file from each source before committing the set is the only real discount available.

What a plan changes is the clock. One task at a time on Free, two on Starter, three on Pro with a priority queue, six on Studio with API access; against an estimated 1 to 4 minutes per file, that is the difference between an afternoon and a coffee break on a twenty-clip job. For anyone running this repeatedly, concurrency is the thing being paid for, and it is worth sizing the plan against how often batches happen rather than how large they are.

The other half of throughput is preparation. Normalising the set so every file arrives at the same size, codec and bitrate removes a category of uneven results that no amount of parallelism can fix, and keeping a log prevents the most expensive mistake in batch work, which is quietly running the same file twice.

Credits and plans

Every tool draws on one shared credit balance.

Every file costs 32 credits and takes an estimated 1 to 4 minutes, whatever the plan. Free gives 30 credits a month and one task at a time — not enough for a single run, so batch work starts on a paid plan. Starter is $9 for 400 credits and two parallel tasks, twelve runs; Pro is $19 for 1,000 credits, three tasks and a priority queue, thirty-one runs; Studio is $59 for 4,000 credits, six tasks and API access, one hundred and twenty-five runs.

Related guides

Longer reads on the same workflow, from the OpenFilmo blog.

Related tools

Closely related pages on the same problem.

Frequently asked questions