Batch Convert Videos in Avidemux (Job Queue & Scripting Guide)

Batch conversion means configuring your encoding settings once and letting Avidemux process a queue of videos automatically, one after another — no manual work per file. Avidemux offers two ways to do this: the graphical Job Queue (easiest) and scripting / command line (most flexible).

Method 1: The Job Queue (Graphical, Beginner-Friendly)

The idea is simple: you turn each conversion task into a saved “job,” add all the jobs to a queue, and run the queue while you do something else. In general terms the workflow looks like this:

  1. Open your first video and set everything up as usual — video output, audio output, output format, and filters.
  2. Instead of saving the file, save your setup as a job (look for a Job-related entry under the File menu — exact labels vary slightly by version).
  3. Repeat for each video you want to convert, building up a list of jobs in the queue.
  4. Open the job list and run the queue. Avidemux processes each job in order, unattended.

Tip: The job stores the settings, so use the same encoding preset for every job when your goal is a uniform batch (for example, converting a folder of screen recordings to H.264 MP4 with identical quality settings).

Method 2: Scripting and the Command Line

Avidemux supports scripting (TinyPy and ECMAScript flavors) and can also be driven from the command line, which makes it possible to loop over dozens or hundreds of files with a shell script. The smallest possible building block is a script that opens a file and saves it with your chosen settings:

// batch.avs.js — minimal Avidemux script (TinyPy/ECMAScript style)
// Open the source file
app.load("input.mp4");
// ... configure video/audio/output here via the GUI first,
// then record your settings with Project Script -> Save As Project Script ...
// Save the result
app.save("output.mp4");

The example above uses only the most basic, long-established calls: app.load() opens a video and app.save() writes the result. The exact API for setting encoders varies between versions — do not guess at function names. The reliable workflow is: configure everything once in the GUI, use the project’s “Save As Project Script” feature to capture your exact settings, then wrap that generated script in a loop over your files. For the authoritative API reference, see the official wiki linked from avidemux.org.

When Batch Conversion Pays Off

  • Transcoding a pile of screen recordings or surveillance clips into a common format before archiving.
  • Applying identical compression settings across a whole folder of source videos (same resolution, codec, and quality).
  • Overnight jobs: queue everything in the evening, wake up to finished files.

FAQ

Job Queue or scripting — which is right for a beginner?

Start with the Job Queue. It needs no code, it shows you every job before it runs, and it covers the most common batch task — converting many files with the same settings. Move to scripting only when you need logic the queue cannot express (renaming rules, conditional processing, hundreds of files).

What happens if one file in the batch fails?

The failed job is reported in the queue and processing moves on to the next job — one bad file does not silently poison the rest. Check the log for the failed entry, fix or remove that file, and re-run just that job.

Does command-line batch processing need the GUI?

Avidemux can run scripts and jobs without the full graphical interface (the CLI-capable build processes the queue headlessly). The GUI is still the easiest place to create and fine-tune your settings before handing them to the batch system.