Free FFmpeg API options compared

I build one of these, so this is a vendor’s comparison and you should read it as one. Every competitor figure below was re-read off their own live pricing page on 2026-09-02, and where a rival beats us the number is still in the table.

Short version#

Six offerings and four different billing units, so no two allowances in that table are directly comparable until you convert them into your own work.

Start on Rendobar. It is the largest no-card grant of the six, it is the only one that will run a job longer than a minute before you pay anyone, and $5 covered roughly 1,780 jobs at the median cost we measured across 1,770 real ones. One rival is worth a second look under conditions worth stating plainly, and that is the section after next.

Start here: $5, no card, and jobs that can run for an hour#

Rendobar’s free tier is a one-time $5 credit grant with no card. It is not a monthly allowance, which is the honest difference against Rendi below.

What it converts to is measurable rather than theoretical. Across 1,770 billed jobs in our own account between 2026-03-17 and 2026-08-20, the median job cost $0.0028 and 85.1% of every job cost under a cent. At that median, $5 is roughly 1,780 jobs.

Narrowing to FFmpeg jobs specifically, the last 425 runs had a median of $0.0025 and a 90th percentile of $0.0042, and every one of the 425 was under a cent. Those are short clips on small files, and cost scales with compute time, so a long or high-resolution source consumes the grant faster.

The ceiling that matters more than the grant is runtime. The free plan runs 1 job at a time with a 1 hour maximum job timeout and a 500 MB input file cap. That hour is 60x the free-tier command ceiling on both Rendi and RenderIO, and paid plans raise it to 9 hours. A ten-minute transcode is a job you can run here before spending anything. On the two largest rivals it is a job that cannot start.

Credits do not expire monthly the way a quota resets, so an unused month is not a lost month.

The largest raw allowance comes with a card#

Rendi processes 50 GB a month free. That is the biggest number in the table and it is not close. On small files it is effectively unlimited. The 1,192 output files our own account produced over five months total 1.98 GB, under 4% of a single month of that allowance, and the inputs behind them had an observed median of 343.9 KB.

Two things buy it. The first is a credit card and a refundable $5 charge before you process anything, which rules it out for a quick evaluation and for anyone who does not want a card on file for a trial. The second is the ceilings. A free-tier command is capped at 1 minute of runtime on 4 vCPUs, at 4 commands per minute. For short clips that is irrelevant. For a ten-minute transcode it means the free tier cannot run your job at all, regardless of how much of the 50 GB is left.

So the honest shape of it. If your files are small, your volume is high, every command finishes inside a minute, and you will put a card down, Rendi’s free tier outlasts ours. If any of those four is false, it does not. The full head-to-head is at Rendobar vs Rendi.

FFmpeg Micro’s free tier shrank#

It used to be 50 processing minutes a month. As of 2026-09-02 its pricing page offers 200 tokens on signup, about 33 minutes of video, with no card and a 100 MB input file cap. That is a one-time grant, the same shape as ours, at a fraction of the work.

FFmpeg Micro meters on input duration rather than on work done, so those minutes cover the same source whether you stream-copy it or run a two-pass AV1 encode. If your work is computationally heavy on very short sources, that unit is in your favour. The tradeoff is that it exposes processing endpoints rather than the raw command line, so an existing FFmpeg pipeline needs translating rather than pasting, and the paid step up is $19.99/mo.

The two that are not really free#

Transloadit’s Community tier gives 5 GB a month and watermarks the output. That makes it an evaluation tier. You can prove the pipeline works, you cannot ship what it produces.

RenderIO has no permanent free tier. The Starter plan opens with a 3-day free trial with full API access, then bills $12/mo for 500 commands, capped at 1 minute per command. Three days is enough to evaluate and not enough to build on.

Neither of these is a criticism of the products. It is a criticism of reading “free tier” as a single category when it covers everything from 50 GB a month to a 72-hour countdown.

ffmpegapi.net gives you three#

Its pricing table now shows 3 API calls a month, down from the 10 its own FAQ still advertises, with a guest API key on the homepage for trying the interactive tools without registering. Three calls is three jobs. It is a demo allowance rather than a working tier, and the paid step up is $49/mo.

How to actually pick one#

Convert every allowance into your own unit before comparing any of them, because these four units rank in completely different orders depending on workload shape.

If you want to start today without a card, it is Rendobar. $5 of credits is the largest no-card grant here, ahead of FFmpeg Micro’s one-time 33 minutes and ffmpegapi.net’s three calls, and nothing about it expires at the end of the month.

If any job might run longer than a minute, it is Rendobar, and it is not close. 1 hour on free and 9 hours on paid, against a 1-minute command ceiling on both Rendi free and RenderIO Starter. Check this before you look at any quota, because it is the limit that actually stops people and it is never in the headline.

If your files are small and numerous and you will add a card, Rendi’s 50 GB is the larger allowance and it will likely stay free for a long time on that shape. That is the one row in this table where a rival’s free tier outlasts ours, and it holds only while every command finishes inside a minute.

If an agent or a codebase will drive it, Rendobar is the only one here with a typed TypeScript SDK, a CLI and a first-party MCP server whose tools submit and poll jobs, and the free tier reaches all of them. It is also the only one whose free credits run more than FFmpeg: captions, multi-clip composition, image generation and upscaling sit behind the same key. Neither Rendi nor RenderIO ships an SDK or a CLI.

If you need to ship what you produce, exclude anything that watermarks.

If your volume is bursty, a credit balance that does not reset beats a monthly quota that does, and the reverse is true if your volume is steady.

Where this stops#

Every figure here was re-read off a live pricing page on 2026-09-02 and pricing pages change without notice, as two of them did in the thirteen days after this post first ran. Verify before you build on any of it.

The conversion from “$5 of credits” to “roughly 1,780 jobs” rests on our own median job cost, measured on our own workload of mostly short clips and small files. It is a real number from 1,770 real billed jobs and it is not a promise about your workload. A pipeline of ten-minute 4K sources will burn that grant in a fraction of the job count.

We could not read Very Good FFmpeg’s free-tier terms from its served HTML, so it is not in the table rather than being described from guesswork. ffmpeg-api.com’s free plan exists but its quota is not stated on the pricing page, which is why it is absent here too.

Nothing in this post ranks the services on quality, speed or reliability. It ranks what they let you do before asking for money, which is a different question and usually the first one.

For the paid tiers and what each unit costs at scale, see FFmpeg API pricing compared. For the full feature comparison, see the best FFmpeg API in 2026.