FFmpeg in the cloud, billed by compute seconds
Run arbitrary FFmpeg commands in the cloud. Pay only for successful encodes, metered by compute seconds. No servers to manage. One endpoint, arbitrary FFmpeg commands.
Example request
POST /v2/run with your API key
curl -X POST https://ffmpego.com/v2/run \
-H "Authorization: Bearer ffc_live_..." \
-H "Content-Type: application/json" \
-d '{
"inputs": [{ "url": "https://example.com/video.mp4" }],
"args": ["-c:v", "libx264", "-c:a", "aac", "-f", "mp4"],
"outputFilename": "out.mp4"
}' \
--output out.mp4How it works
Three steps from signup to encoded output. Same predictable API you know from server-side FFmpeg.
Create an account
Sign up free, pick a plan, and generate an API key from your dashboard.
POST /v2/run
Send inputs and FFmpeg args as JSON. inputs[i] maps to FFmpeg input i.
Pay per compute second
Successful encodes return X-Compute-Seconds. Failed jobs are not billed.
Transparent, usage-based pricing
Start free with 2,000 compute seconds on Pro for $9/mo. Hard monthly caps — no surprise overages in v1.
View all plansPro plan snapshot
Most popular for indie apps and automation
FAQ
What counts as a compute second?
Wall-clock FFmpeg execution time on our containers, rounded up to a minimum of 1 second per successful request.
Do failed encodes consume quota?
No. Only successful 2xx responses increment your compute and request counters.
Can I run filter_complex and multi-input jobs?
Yes. /v2/run is designed for predictable input ordering and complex filter graphs.