Live. Production-ready, available on all plans.
inputs map stages source files into the working directory by name. The command references them by bare name, and inline -i URLs also work.
Timeout: 900 s max (plan-capped) · Accepts: video, audio, image
Request
Parameters
Working directory for the command. Optional, defaults to an empty map. Each key is a path-safe filename staged under that exact name. Each value is the source for that file. Omit it when every input is an inline
-i URL. A value is one of:Filters that read a file by name (subtitles=, lut3d=, drawtext fontfile=, concat lists) must get that file through inputs. They are not -i arguments. See the FFmpeg guide.Real FFmpeg command starting with
ffmpeg. Input URLs go in -i positions, or reference staged inputs files by name.Container format. Inferred from the trailing filename if omitted. One of:
mp4, mkv, webm, mov, avi, ts, gif, png, jpg, mp3, wav, flac, ogg, aac, opus, m4a, srt, vtt.Max execution time in seconds. Range 1–900. Plan caps apply (Free 5 min, Pro 15 min).
Which machine class runs the job. One of
auto, cpu, gpu.auto(default): a command using an NVENC or CUDA encoder, likeh264_nvenc, routes to a GPU. Everything else runs on CPU. You don’t set anything.gpu: force a GPU machine.cpu: force a CPU machine. A command that calls an NVENC encoder is rejected withVALIDATION_ERROR.
h264_nvenc, hevc_nvenc, and av1_nvenc on NVIDIA L4 GPUs, billed per second. gpu and auto-routed GPU jobs require the Pro plan; a GPU job on the Free plan returns 403 PLAN_LIMIT. cpu and auto work on every plan.Response
GET /jobs/{id} until status: "complete". On success the job carries an output object. On failure it carries an error object. The filenames your command writes define the output.
output is one shape for every job type, documented in full on Job output. FFmpeg jobs set output.data to null and return their files in output.file and output.files. Read output.file.url for the file to play or download, and output.files for the full list.
Present when
status is failed.See also
- Job output: the output shape every job returns
- FFmpeg guide: security model, allowed flags, examples
- CLI: same job, terminal interface
- Job lifecycle
Related
- FFmpeg guide: security layers, allowed flags, worked examples
- CLI overview: the same job from your terminal with
rb ffmpeg - Credits and billing: per-compute-second pricing detail
- Plan limits: file-size caps, timeouts, and concurrency per plan
- FFmpeg in the cloud: every operation Rendobar supports