A simple FFmpeg API with usage-based pricing.
High-performance infrastructure, no $0 monthly minimum.
Very Good FFmpeg is a REST API that runs your exact FFmpeg commands on high-performance cloud infrastructure - and bills you per GB processed, with volume discounts that kick in automatically as you grow.
It's usage-based like AWS. Pretty boring.
How we compare.
- Do I need to learn a new API or DSL?
- No. If your command works in `ffmpeg` on the terminal, it works here. Same flags, same filters, same syntax. Send the command, we run it.
- How is this cheaper than a subscription?
- You only pay for what you process. A $29/month plan costs $29 even if you process 1 GB. Process 1 GB with us and you pay $0.50. Process 5 TB and our volume discounts kick in automatically - you’d pay $0.08/GB at the top tier.
- What hardware do my jobs run on?
- Every CPU job runs on a dedicated 16 vCPU / 32 GB DDR5 RAM / NVMe instance with 5+ GHz cores. GPU jobs run on Nvidia RTX and A-series hardware. No shared tenants or throttling.
- What's the uptime guarantee?
- 99.99% SLA available to enterprise clients. Contact us for details.
- How long can a single job run?
- 6 hours. We don’t cap you at 15 minutes the way other platforms do.
- Are there egress or storage fees?
- No. You pay per GB processed. Output URLs and webhook delivery are included.
- How is GB processed measured?
- We bill on the size of the input and output file(s) your command reads and writes. Webhook payloads and intermediate temp files don’t add to your bill.
- Do failed jobs count toward billing?
- Yes. Failed or cancelled jobs are billed for the input and output bytes processed before they stop.
- Are there rate limits or concurrency caps?
- New accounts start with 10 requests per second rate limit. Once you add a $10 pre-paid balance, it increases to 100. There is no limit on the number of concurrent jobs.
- Which codecs and filters are supported?
- A full ffmpeg build with the standard codec set: H.264, H.265/HEVC, AV1, VP9, ProRes, AAC, Opus, and the full filter graph. If `ffmpeg -codecs` lists it on a stock build, we have it.
- Do you train models on my files or share them with anyone?
- No. We don't train on, inspect, or share your media. Files are processed on a dedicated instance and deleted after the job completes.
- Can I watch a job while it runs?
- Yes. Every job streams FFmpeg stderr in real time through the dashboard.
- Do you support GPU acceleration?
- Yes. Set machine: "nvidia" on the request to route the job to a current-generation NVIDIA GPU worker. FFmpeg uses CPU code paths by default, so a GPU instance only runs faster if your command actually uses GPU decoders, encoders, and filters. See the hardware acceleration docs at /docs#hardware-acceleration for the full caveat and the list of supported codecs.
- What happens when a command fails?
- AI analyses the FFmpeg output and tell you exactly what went wrong. We find it saves a lot of time in diagnosing problems with FFmpeg commands.
- Can I run multiple commands in one request?
- Yes. Pass an array of FFmpeg commands and they run sequentially on the same instance. One request can fan out multi-resolution transcodes, thumbnails, and HLS packaging in a single job.
- Do you have SDKs?
- Official TypeScript and Python clients are available now.
- Can I upload files instead of providing a URL?
- Yes. You can optionally use the temporary upload endpoint to upload a file into our storage for use as inputs into FFmpeg.
- Do you support teams?
- Yes. Create teams, invite members, and assign role-based permissions from the dashboard.
- What happens if I don't use it for a month?
- You pay $0. No subscription floor.
Get an API key in 30 seconds. Your first 2 GB are free. No credit card required.