Skip to main content
Edit Videos

Free · private · in your browser

Process several videos in one batch

Add videos, choose compress or convert, and run the queue.

How it works
  1. ImportChoose source
  2. EditSet the change
  3. PreviewReview result
  4. ExportCreate file
InputMP4, WebM, MOV and M4V videoOutputMP4 or WebM video

Doing the same thing to twenty files by hand is where an afternoon goes. Add a set of videos, choose one operation — compress or convert — configure it once, and the queue applies it to every file in turn, reporting progress as it goes. Each finished video downloads separately, and nothing is uploaded anywhere.

One setting across a mixed set

The strength of batching is also its constraint: every file gets the same treatment. That is fine when the inputs are consistent — a folder of clips from one camera, a set of screen recordings at the same resolution. It goes wrong on mixed sets, where a quality setting tuned for 4K footage is wasteful on a 720p clip and a size target sensible for a short clip starves a long one. Group similar files and run several batches rather than forcing one configuration onto everything.

Why the queue is sequential

Files are processed one after another rather than in parallel. Encoding already saturates the CPU and the available memory, so running four at once on one machine mostly makes all four slower and raises the chance of running out of memory on large files. Sequential processing also makes the progress report meaningful and a failure easy to attribute. Plan for total time to be roughly the sum of the individual jobs, and start a large batch when you can leave the tab open.

Questions, answered

How many files can I process at once?

There is no fixed limit. Since files are processed one after another, total time is roughly the sum of the individual jobs — plan accordingly for large batches.

Can I use different settings for different files?

No — one configuration applies to the whole queue. Group similar files and run separate batches when the sources vary a lot in resolution or length.

What happens if one file fails?

The queue reports which file had the problem and continues with the rest, so a single unsupported input does not lose the whole run.

Do I need to keep the tab open?

Yes. All the work happens in the page, so closing the tab or letting the device sleep interrupts the queue.

Should I use this or the dedicated batch tools?

This one covers both compressing and converting in a single place. The dedicated batch compress and batch convert tools present only the settings relevant to that one job, which is quicker when you already know which you need.