Changelog
New

GPU-accelerated FFmpeg encoding

The ffmpeg job type now takes a compute param. NVENC commands run on NVIDIA L4 GPUs, billed per second, on the Pro plan.

API Dashboard

The ffmpeg job type now runs on CPU-powered or GPU-powered machines. A new optional compute param picks the hardware. It defaults to auto, so a command that uses an NVENC or CUDA encoder routes to a GPU on its own. Nothing in your existing jobs changes.

Rendobar’s FFmpeg API runs h264_nvenc, hevc_nvenc and av1_nvenc on NVIDIA L4 GPUs. Billing is per second of processing. There are no instances to start or manage.

  • compute: "auto" (the default) sends NVENC and CUDA commands to a GPU and everything else to a CPU machine.
  • compute: "gpu" forces a GPU. compute: "cpu" forces a CPU and rejects an NVENC command early with a clear error.
  • Swap one flag to try it. -c:v libx264 becomes -c:v h264_nvenc in the same command you already send.
  • GPU acceleration is available on the Pro plan. CPU and auto work on every plan.

See the FFmpeg reference for the compute param and examples.

GPU compute is a Pro capability. Per-plan limits are listed under plan limits.

Share