Batch File Conversion: Browser, CLI, or Daemon
Batch is a loop. The loop can run in a tab, in a shell, or on a daemon you start yourself.
Read on 2026-10-29 from the pages named in Sources. We did not upload a test file, time a conversion, or audit a deletion job.
A batch is a loop with a place to run
Converting one file and converting a folder are the same job repeated. The limit is wherever the bytes sit while the loop runs: browser memory, a disk on a machine you administer, or a queue on someone else's account.
The VERT README says there is no file-count limit and no file-size limit. That is their claim about the product, not a measurement of your tab. A large video still follows the video rules: some conversions leave the browser and use the daemon.
Browser, shell, and a hosted queue
| Loop | Where it runs | What the source says |
|---|---|---|
| Drop many images, audio files, or documents | The browser | VERT's FAQ says non-video work stays on the device. |
| The same image command for a folder | Your shell | The ImageMagick homepage shows a magick command and calls the suite scripting-first for batch jobs. |
| The same media command for a folder | Your shell | FFmpeg's about page describes ffmpeg as a command-line tool that converts multimedia files between formats. |
| Video the browser will not finish | vertd, locally or on their server | The video doc says the UI can call a daemon, including one you run. |
A free upload queue has numbers on the pricing page
On 2026-10-29 the CloudConvert pricing page listed a free package at 10 conversion credits per day, a 1 GB maximum file size, 5 minutes of processing, and 5 concurrent tasks. Paid packages on that page change the caps. Those numbers are a price-page reading, not a FrontierDot load test.
An upload queue is the wrong loop for a file you cannot send off the machine. Use the browser path or a local daemon, then read upload or on-device. For one-off choice, start at how to choose an online file converter. The command-line tools are in FFmpeg, ImageMagick, and Pandoc. The directory entry is VERT, and every note is on the Front blog index.
What a batch page cannot tell you
- How many files your browser tab will hold. That depends on the machine, and we did not fill one.
- Whether a vendor's no-limit sentence survives a hostile file. We did not fuzz one.
- A winner. Throughput without a dated run and a harness is not a benchmark. Labels for real runs are on how FrontierDot labels benchmarks.
Keep reading on Front
Every post, newest first, is on the Front blog index.
- How to choose an online file converter: where the file goes, before which logo you pick.
- FFmpeg, ImageMagick, and Pandoc: when the shell is the right worker.
- Upload or on-device: what VERT, CloudConvert, and Convertio say about the bytes.
- Format matrix by family: image, audio, document, and video, by the library named.
FAQ
Can I batch convert without uploading?
Yes for the jobs VERT's FAQ puts on the device, and yes with ImageMagick or FFmpeg on your own computer. Video that the browser will not finish needs a daemon, which you can run locally.
Does no file-size limit mean any video stays in the tab?
The README states no file-size limit. The video doc still says some video is server-side when the browser path is unsupported or too slow. Both sentences are theirs.
Is the CloudConvert free package 10 credits a day?
That is what the pricing page showed on 2026-10-29, along with a 1 GB file cap, 5 minutes, and 5 concurrent tasks. Check the page again before you plan a queue around it.