FFmpeg command explainer
Paste an FFmpeg or ffprobe command and read what it does, in the order FFmpeg does it. Point at a phrase to see its part of the command.
FFmpeg jumps to 1:18 in in.mp4, reads 3 seconds, keeps 10 frames a second, resizes each frame to 480 px wide, picks the best 256 colours for this clip, redraws every frame with that palette and writes out.gif. A GIF has no sound, so any audio in the input is left out.
-ss 78- With a re-encode it is exact as well as fast: the first frame written is the one asked for. Trim a video recipe
palettegen- The same 3 seconds without a palette came out grainy and off-colour. MP4 to GIF recipe
Runs on Rendobar as written.
Run it
Run it on Rendobar
Send the same command from your code. The job fetches each input from its URL and returns the output file's URL when it finishes. The code follows the command box above.
import { createClient } from "@rendobar/sdk";
const rb = createClient({ apiKey: process.env.RENDOBAR_API_KEY });
const job = await rb.jobs.run({ type: "ffmpeg", inputs: { "in.mp4": "https://cdn.rendobar.com/examples/mp4-to-gif/in.mp4", }, params: { command: "ffmpeg -ss 78 -t 3 -i in.mp4 -vf \"fps=10,scale=480:-1:flags=lanczos,split[a][b];[a]palettegen[p];[b][p]paletteuse\" out.gif", },});
console.log(job.output.file.url);Install with npm i @rendobar/sdk. jobs.run() submits and waits, so it returns the finished job in one call.
curl https://api.rendobar.com/jobs \ -H "Authorization: Bearer $RENDOBAR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "type": "ffmpeg", "inputs": { "in.mp4": "https://cdn.rendobar.com/examples/mp4-to-gif/in.mp4" }, "params": { "command": "ffmpeg -ss 78 -t 3 -i in.mp4 -vf \"fps=10,scale=480:-1:flags=lanczos,split[a][b];[a]palettegen[p];[b][p]paletteuse\" out.gif" }}'Returns immediately with a job id. Poll GET /jobs/{id} or register a webhook rather than blocking on the request.
FAQ
Frequently asked questions
Is the FFmpeg command explainer free?
Yes. It runs in your browser and sends the command nowhere. Running a command on your own file needs a Rendobar account, and new accounts get $5 of free credit with no card.
Why is the sentence in a different order from my command?
It follows the order FFmpeg works in, not the order the flags were typed. FFmpeg opens each input and seeks, runs the filters, encodes, and stops at any limit such as -t before it writes the file. So -c:v libx264 typed before -vf still reads as filter first, then encode.
Can the explainer see what is inside my file?
No. It reads the command, not the file, so it never guesses what the file holds. When an output cannot carry a stream, such as audio in a GIF, it says any audio is left out. For the streams, codecs and size of a real file, use the video info recipe, which reads a file in your browser.
Where do the flag explanations come from?
From FFmpeg's own documentation. Where a recipe measured how a flag behaves on real footage, the explainer quotes that finding under the sentence and links the recipe.
Why does the explainer say a command would be refused?
It runs the same check Rendobar's FFmpeg API runs before a job starts. A path outside the job folder, a pipe or redirect, or a protocol flag gets refused there, and the explainer shows the same message so you can fix it first.
Your command. Our infrastructure.
Bring your own commands. Run them on scalable CPU and GPU infrastructure, and pay only for compute time.
