ReelSDK runs FFmpeg 5.1 in your browser with x264, x265, VP9, LAME and Opus built in: free, no install, nothing uploaded. From code, the API runs ffmpeg 8.1 on a fresh machine for $0.02 per compute minute.

Run FFmpeg online for free: no install, no upload

Type what you would put after ffmpeg, pick your files and run, or start from one of 4 examples like turning the first 3 s into a GIF. On the ReelSDK API, one job takes up to 50 inputs and 20 outputs.

ToolsUpdated

or drop them here

MP4, MOV, WebM or MKV. It stays on your device.

No video at hand?

Runs on your device with the ffmpeg.wasm core 0.12.10 (FFmpeg 5.1.4), GPL-2.0-or-later: source code, our mirror

At a glance

This page or the API

Both run your arguments as you wrote them. The timings are for the resize example on our 11-second vertical sample, on our test PC in Chromium.

This page or the API
This pageReelSDK API
ffmpeg version5.1, as WebAssembly8.1
Runs onYour device, one CPU coreA fresh machine per job
File sizeUp to 2 GB in totalUp to 500 MB per input, 1 GB per job
PriceFree$0.02 per compute minute
Resize example36 to 42 sAbout 5 s

Sources: our runs of the sample clip, ReelSDK ffmpeg docs, checked November 2026.

How to use it

Write the arguments exactly as on the command line, without the word ffmpeg; quotes work as in a shell. Your files sit in a folder named in, so a file called clip.mp4 is in/clip.mp4. Name the output at the end, like out.mp4, and every file the command writes shows up below as a preview or a download.

The 4 examples are a good start. On our 11-second sample, the GIF, the audio and the PNG each took under 3 seconds, while resizing the whole clip to 720 wide took 36 to 42 seconds, because it re-encodes every frame. If the command fails, the tool shows ffmpeg's own log so you can see why.

What differs from ffmpeg on your computer

The engine is ffmpeg.wasm: FFmpeg 5.1 compiled to WebAssembly, built with x264, x265, libvpx, LAME, Opus, Vorbis, Theora, libwebp, libass, freetype, fribidi and zimg. Hardware encoders such as NVENC or VideoToolbox are not there, and ffprobe and ffplay are not included.

It runs on a single thread, so -threads changes nothing and heavy encodes take a while. It cannot read from URLs or write to your disk directly: pick inputs from your device and download the outputs. The tab can hold up to 2 GB of files in total.

Nothing is uploaded

Your files are read inside this tab. In our network log, the page fetched the 2 engine files and no request carried any part of your files. The engine is a 10.3 MB download (32.2 MB unpacked) that your browser keeps for 7 days.

Once a command works here, the API below runs it on ffmpeg 8.1 with your files given as links: the resize example finished in about 5 seconds. Args outside our allowlist get a 400 answer before any job starts. See the ffmpeg API and pricing.

From your code

The same job as one API call

Run your own ffmpeg command on your files in the browser, free and without installing or uploading anything.

terminalTry it
curl "https://api.reelsdk.com/v1/ffmpeg?wait=60" \
  -H "Authorization: Bearer $REELSDK_KEY" \
  --json '{
    "inputs": {
      "clip.mp4": "https://api.reelsdk.com/f/lib/demo/clip.mp4"
    },
    "args": [
      "-i", "clip.mp4", "-vf", "scale=720:-2", "-c:v", "libx264", "-preset",
      "veryfast", "-crf", "23", "-c:a", "copy", "out.mp4"
    ],
    "outputs": ["out.mp4"]
  }'
The API ran the resize example on ffmpeg 8.1: a 2 MB, 720x1280 MP4 in about 5 seconds.Input: 10.7-second sample clip

FAQ

Questions, answered

Is FFmpeg online free?

Yes. There is no signup and no cap on how many commands you run, because your own device does the work. Running commands from your own code with the API costs $0.02 per compute minute.

Are my files uploaded?

No. They are read inside your browser and ffmpeg runs there. In our network log, the page fetched the 2 engine files and no request carried any part of your files.

Which codecs and filters can I use?

Everything FFmpeg 5.1 ships with, plus x264, x265, libvpx for VP8 and VP9, LAME for MP3, Opus, Vorbis, Theora and libwebp, and libass for burning in subtitles. -filter_complex works as on the command line.

Why is my command slower than on my computer?

The browser runs ffmpeg on one thread and without hardware encoders. Short jobs like cutting, extracting audio or grabbing a frame stay quick; long encodes are faster on the API.

Ready to build?

Ship video from your app today

Your first $0.50 is free, and one key covers every endpoint.

Moonlit lake with a lit cabin under the mountains