FFmpeg in the cloud, billed by compute seconds
Pay only for the time FFmpeg actually runs — from $0.0036 per compute second. Failed encodes are never billed, there are no servers to manage, and hard monthly caps mean no surprise overages.
Need a clip from a YouTube video? Paste a link and cut it by timestamp — no full download.
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 75 compute seconds. Pro is $9/mo for 2,000 compute seconds — about $0.0045 per second of successful encoding, and as little as $0.21 per minute of encoding on Mega. Hard monthly caps mean no surprise overages.
Compare all plansPro plan snapshot
Most popular for indie apps and automation
FAQ
How cheap is it, really?
The free tier costs $0. Paid plans start at $9/mo for 2,000 compute seconds — about $0.0045 per second of successful encoding. Failed encodes are never billed, and hard monthly caps mean your bill cannot exceed your plan price.
Why is this cheaper than running my own FFmpeg servers?
You only pay while FFmpeg is executing. There are no idle VMs, no storage or egress markups, and nothing to patch, scale, or babysit. Successful encodes are the only thing that counts against your quota.
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.
Ready to encode for less?
Create a free account and get your API key in minutes. Failed encodes stay free, and you only upgrade when you need more compute.
Start free — 75 compute seconds