FFmpeg API: multi-file output and inline inputs
Commands that write many files like HLS, DASH, and image sequences now come back as ready-to-use URLs, inputs accept inline text and uploaded files, and failed jobs return the real ffmpeg error.
The FFmpeg API now handles commands that produce more than one file. Run an HLS or DASH ladder, or write an image sequence, and the job returns a playable URL plus the full file list, each at its own link. The stream plays as-is. No zip to unpack, no rehosting.
More flexible inputs
Inputs got more flexible. Alongside a URL, you can pass a file’s contents inline, which is handy for an SRT subtitle, a concat list, or a .cube LUT with nothing to host. You can also point at a file you already uploaded. Files land in the working directory under the exact name your command uses, so subtitles=subs.srt and lut3d=look.cube work the way they do on your own machine.
Real ffmpeg errors
When a command fails, the job now returns the actual ffmpeg error output instead of a status code alone, so you can see what went wrong and fix the command.
- Multi-file outputs (HLS, DASH,
-f segment, image sequences) return a playable URL plus the full file list. - Inputs accept a URL, inline text, or a reference to an uploaded file.
- Failed jobs include the real ffmpeg error output.
- The SDK returns the typed output shape, with
outputUrl()andjobData()helpers for the headline file and structured results.
See the FFmpeg job reference for the full input and output shapes.
Outputs above 100 MB were unblocked separately, see outputs larger than 100 MB.