Skip to main content

A Simple Browser-Based Alternative to FFmpeg for Batch Video Conversion

For when the right answer to 'how do I convert ten MOVs to MP4' is not 'memorize a shell loop'.

  • Common FFmpeg jobs (convert, compress, resize) in a UI
  • No install, no command line, no shell loop
  • Bulk-friendly batch queue
  • MP4, MOV, MKV, and WebM in and out
  • Use FFmpeg separately for filtergraphs, two-pass, or scripting

Overview

FFmpeg is the right tool for almost any video task, eventually. The cost is the learning curve. Doing 'convert these ten MOV files to MP4 at decent quality' on the command line means knowing the input flag, the output codec flag, the CRF or bitrate flag, the preset flag, and a shell loop to apply it across the folder. None of that is hard, but none of it is fast the first time either.

This tool covers the conversions and compressions that most people actually want from FFmpeg, but as a UI: pick the files, pick the output format, set quality and width, click convert. The mapping below shows the common FFmpeg one-liners and the equivalent thing in this tool.

It is not a replacement for everything FFmpeg can do. Codec-level controls, audio filters, complex filtergraphs, hardware-specific encoders, and scripting all stay on the FFmpeg side. For day-to-day batch jobs, the browser path is faster to set up.

Technical notes

Convert MOV to MP4

FFmpeg: ffmpeg -i in.mov -c:v libx264 -crf 23 out.mp4. Here: drop MOV files in, output preset is MP4, click convert.

Compress a folder

FFmpeg: a shell loop wrapping the command above with -crf 28 or a target bitrate. Here: drop the folder in, pick the balanced (or smaller) quality preset, click convert.

Resize to 1280 wide

FFmpeg: -vf "scale=1280:-2". Here: enter 1280 in the width field, click convert. Aspect ratio is preserved automatically.

When to stay on FFmpeg

Custom filtergraphs, two-pass encoding, codec-level tuning, audio filters, ProRes, HLS packaging, hardware-specific encoders, and any kind of scripting or automation. The browser is faster for the common case; FFmpeg is still right for the edge cases.

Good to know

No filtergraphs or two-pass encoding

There is no UI for FFmpeg-style filter chains, two-pass bitrate targeting, or per-codec tuning. Those workflows belong on FFmpeg itself.

No ProRes, HLS, or scripting

ProRes intermediates, HLS packaging, and any kind of scripted pipeline (CI jobs, batch automation) are out of scope.

Codec coverage is narrower

FFmpeg supports an enormous codec list. This tool covers the common consumer codecs (H.264, H.265 where the browser supports it, VP9, AV1 decode). Exotic codecs may not work in the browser at all.

Sources: W3C: WebCodecs specification · MDN: Web video codec guide · Reviewed 2026-10-12

How to do common FFmpeg conversion jobs in a browser

Run the convert, compress, and resize jobs people usually reach for FFmpeg for, as a browser UI instead of a shell loop.

01

Add your videos

Drag and drop your video files into the converter, or click to pick them.

02

Choose your settings

Pick the output format, quality, optional width, and whether to remove audio.

03

Start the batch

Click Convert files. Each file is processed locally on your device.

04

Download

Download files individually, or grab the whole batch as a ZIP.

Frequently Asked Questions

When should I still reach for FFmpeg?

Anything involving filtergraphs, two-pass encoding, custom codec tuning, audio filters, ProRes, HLS packaging, or scripting. Also anything where you need the result to be reproducible from a CLI command.

Are my files uploaded anywhere?

No. The conversion runs in your browser; nothing is sent to a server.

Does this use FFmpeg under the hood?

No. It uses WebCodecs, the browser's built-in video encode/decode API. WebCodecs lets the browser run the encode directly rather than wrapping FFmpeg.

Is it as fast as FFmpeg?

For common browser-supported workflows, performance can be very good. For exotic codecs, deeper tuning, or scripted pipelines, FFmpeg is usually the better tool.

Which browsers does this work in?

Conversion requires WebCodecs video encoding and decoding, but each browser and device supports a different codec subset. MP4, MOV, and MKV output use H.264 video with AAC audio; Firefox and desktop Linux browsers do not natively encode AAC. Safari 16.4 added video WebCodecs, while Safari 26 added audio encoding and decoding. WebM output uses VP9 with Opus and may work where AAC output does not. For the widest support, use a recent desktop Chrome or Edge release, or Safari 26+. The converter still validates the actual source and output codec configuration when a job starts.

Sources: MDN: WebCodecs API · MDN: WebCodecs codec selection · WebKit: WebCodecs video support in Safari 16.4 · WebKit: WebCodecs audio support in Safari 26 · Mediabunny: supported formats and codecs · Reviewed 2026-10-12

Related tools