Video API pricing: which meters keep billing after the job ends

You compared six video APIs on features, picked the one advertising free encoding, and the bill still grows every month. Nothing in the pipeline changed. The meter did.
Quick answer: Video API pricing comes in four units: stored and delivered minutes (Cloudflare Stream, Mux), pooled credits (Cloudinary), per minute of rendered output (Shotstack, JSON2Video, Creatomate), and per second of input processed. Which of those meters keep billing after the job ends? Three of the four do, charging every month a file exists on the vendor's disk, so the honest comparison prices one library across twelve months instead of comparing headline rates. FFmpeg Micro bills the fourth unit: 1 token per 10 seconds of input, metered per second with no rounding up to the minute, status checks and downloads free, failed jobs never billed, and nothing at all after the job finishes.
The four units behind every video API price list
Every video API bills on one of four units, and the unit decides the shape of your bill far more than the rate does. Feature comparisons line up players, codecs and SDKs, never the meters. The meter is the part of the decision that still costs you money in month eighteen.
| Unit | Vendors that bill this way | When it charges | When it stops |
|---|---|---|---|
| Stored + delivered minutes | Cloudflare Stream, Mux, api.video | Every month the file exists, plus every minute watched | When you delete the file |
| Pooled credits | Cloudinary | On the transformation, on the stored derivative, and again on delivery | When you delete the derivative and stop serving it |
| Per minute of rendered output | Shotstack, JSON2Video, Creatomate | Once per render, scaled by output length and sometimes by pixels | When the render finishes |
| Per second of input processed | FFmpeg Micro | Once, on the length of the file you sent | When the job finishes |
A stored-minute meter is a subscription to the existence of a file. That's a fair deal when the vendor also serves that file to an audience through a player and a CDN. It's a strange deal when you processed the clip once, already keep the master in S3, and the platform copy exists only because that's where the encode landed.
What free encoding costs after the encode is done
Free encoding on Mux Basic, api.video and Cloudflare Stream is real and worth real money. Encoding the same 1,000 source minutes as a five-rung H.264 ladder runs about $53 on AWS MediaConvert at Basic tier list prices, per Forasoft's encoding API comparison. Against $53, a $0 encode line looks like the obvious pick.
Then the file sits there. The list prices below come from each vendor's published pricing in November 2026. I'm not linking them, because price pages move and a stale link is worse than a dated number. Read the live page before you budget.
- Cloudflare Stream bills on two meters only, roughly $5 per month per 1,000 minutes of storage capacity and roughly $1 per 1,000 minutes delivered, with ingest, encoding and egress included.
- Mux encodes free at Basic quality, then charges storage from about $0.0024 per minute per month with a one-month minimum on Basic assets, and delivery after a free allowance of 100,000 minutes.
- api.video encodes free at any volume and recovers it on hosting, roughly $0.00285 per stored minute, plus delivery per minute watched.
Before you trust a third-party calculator: a widely linked video API cost comparison prints Cloudflare Stream's two meters the wrong way round, listing $1 per 1,000 stored and $5 per 1,000 delivered. The orientation matters by a factor of five in opposite directions depending on whether your catalog is big and quiet or small and busy. Check the vendor's page yourself, always. Third-party pages get our own numbers wrong too: a few still quote FFmpeg Micro plans that never existed, including a "Scale" tier and per-minute rounding we don't do.
A 5,000-clip library, priced over three years
Take 5,000 clips averaging two minutes each: 10,000 minutes, 600,000 seconds, roughly 190 GB at a normal 1080p social bitrate. You processed them once, and you keep the masters in your own bucket, where S3 Standard charges $0.023 per GB per month for the first 50 TB (AWS S3 pricing), about $4.31 a month.
Here's the same library under each meter, cumulative, delivery left out of all three columns because you pay egress somewhere either way.
| Year 1 | Year 2 | Year 3 | |
|---|---|---|---|
| Stored minutes at $5 per 1,000 per month | $600 | $1,200 | $1,800 |
| Stored minutes at $0.0024 per minute per month | $288 | $576 | $864 |
| Per input second, plus your own S3 | $552 | $604 | $656 |
The per-input-second column is 60,000 tokens of processing, which at the $25 top-up rate of 3,000 tokens is about $500 paid once, plus the $51.75 a year of S3 you were already paying. Year one it's the middle option. Year two it stops moving, and the hosting meters don't.
Pooled credits behave the same way with an extra turn of the handle. One Cloudinary credit buys roughly 250 seconds of HD video processing, so 600,000 seconds draws about 2,400 credits for a single pass, and the stored derivative and every delivered gigabyte draw from the same pool afterward. We walked that math in what a Cloudinary credit actually buys for video, and the three-meter version in Mux pricing in 2026.
Render meters at least stop. Shotstack's pay-as-you-go rate is around 20 cents per output minute, JSON2Video charges a credit per second of rendered output, and a Creatomate credit is 100 million output pixels, so the same sixty-second edit costs roughly 37 credits at 1080p30 and roughly 149 at 4K30 for identical work. You pay once per render, but on the thing you got back rather than the thing you sent, and the resolution multiplier is real.
Which meter fits which pipeline
The right meter follows from who ends up holding the file and who is watching it. A hosting meter is correctly priced when the vendor does the hosting: if you need adaptive bitrate streaming, a player, signed playback, per-viewer analytics and a CDN, stored and delivered minutes buy all of that, and building the equivalent yourself costs more than the meter does. Pay it without flinching.
A per-output-minute render meter is correctly priced when you want a JSON timeline, a template system and a scene graph you don't maintain. That is a composition product, not a transcode, and 20 cents a minute for something you'd otherwise build is cheap. It goes wrong when teams route plain work through it: a watermark, a reframe to 9:16, a format conversion. Paying template-render rates for a one-filter job is the most common way to overspend in this category, and we broke it down in video transcoding cost is per minute.
A per-input-second meter fits when you already own storage and delivery, the operation is a step inside a larger pipeline, and you want the file handed back. Transcode an upload to house spec, burn captions, pull thumbnails, cut clips out of a long recording, watermark UGC. The job happens, the charge happens, both end.
FFmpeg Micro is the wrong call in three situations. If you need a hosted player and streaming delivery, we have none, so you'd bolt a platform on anyway. If you want a drag-and-drop editor or a visual timeline, this is an API, not an editor. And if your sources exceed the input cap on your plan, 100 MB on Free, 1,024 MB on Starter and 2,048 MB on Pro, you'll need to split or downscale before sending.
Our meter, stated exactly
FFmpeg Micro charges 1 token per 10 seconds of input video, metered per second. There's no rounding up to the nearest minute, so a 10 second video costs 10 seconds. Checking job status, listing jobs and downloading outputs are free. Failed jobs are never billed. There's no storage meter and no delivery meter, because the output goes back to you.
The trim case diverges most from everything above. Pull a 30 second highlight out of a one-hour webinar and you're billed for 30 seconds, 3 tokens, not the 360 tokens the full hour would cost:
curl -X POST https://api.ffmpeg-micro.com/v1/transcodes \
-H "Authorization: Bearer $FFMPEG_MICRO_KEY" \
-H "Content-Type: application/json" \
-d '{
"inputs": [{ "url": "gs://<YOUR_BUCKET>/1763212800-webinar.mp4" }],
"outputFormat": "mp4",
"options": [
{ "option": "-ss", "argument": "00:41:12" },
{ "option": "-t", "argument": "30" }
]
}'
Plans are $0, $19.99 and $49.99 a month, and those are the only three. A new account gets 200 tokens, about 33 minutes of video, with no card. Paid grants are 2,500 and 7,000 tokens a month, grant tokens roll over while you stay subscribed up to three times the monthly grant, and top-ups (500 for $5, 1,200 for $10, 3,000 for $25) work on any plan including Free and don't expire while the account is open. Full table on the pricing page.
FAQ about video API pricing
Which video API meters stop when the job finishes?
Per-output-minute render meters and per-second-of-input processing meters both stop when the job finishes. Stored-minute and delivered-minute meters keep charging as long as the file exists on the vendor's storage and anyone is watching it, and pooled credit systems like Cloudinary's draw on the same pool for processing, for the stored derivative and for delivery.
Does rendering at 4K or 60fps make a video API cost more?
On a pixel-based credit meter, yes, dramatically. A Creatomate credit is 100 million output pixels, width times height times frame rate times duration, so a sixty-second edit costs roughly 37 credits at 1080p30 and roughly 149 at 4K30 for identical composition. On an input-duration meter like FFmpeg Micro's, output resolution and frame rate make no difference to the charge: a minute of input is 6 tokens whatever comes out the other end.
Am I billed for a video processing job that failed?
FFmpeg Micro never bills failed jobs. Several render-based vendors state the same policy, including Shotstack and JSON2Video, but hosting platforms charge storage from the moment an asset exists, and at least one applies a one-month minimum even to assets you delete immediately. Read the storage minimum, not just the encoding line.
Do unused video API credits or minutes roll over?
Rollover varies by vendor, and it's the detail most comparison pages skip. FFmpeg Micro rolls unused monthly grant tokens over while you stay subscribed, up to three times the monthly grant, and purchased top-ups never expire while the account is open. Creatomate's monthly credits reportedly don't carry over, and Shotstack rolls plan minutes for three months, so a seasonal workload can forfeit a large share of what it paid for.
Is there a video API free tier that doesn't need a credit card?
FFmpeg Micro's free tier is 200 tokens at sign-up, about 33 minutes of video, with API access, unlimited API keys and unlimited storage, and no card. It leaves out customer support, token management, automatic top-up and token banking, which start at the $19.99 Starter plan. Mux, api.video and Cloudflare Stream offer free allowances too, but there the free portion is the encode, and the storage meter starts the moment the asset lands.
Run the arithmetic on your own numbers before you pick a meter: total minutes of footage, how many months you keep them, and whether anyone is watching. The side-by-side version is on compare pricing, and checking our half of it costs nothing. Sign up free gets you 200 tokens, roughly 33 minutes of video, with no card, no servers to run and no FFmpeg to install. Send a one-hour webinar, get billed for the 30 seconds you trimmed.
About Javid Jamae
Founder & CEO at FFmpeg Micro
Javid is a software engineer, author, and entrepreneur with over 25 years of professional software development experience across enterprise, startup, and consulting environments. He founded FFmpeg Micro to make video processing accessible to developers through a simple, automation-first REST API.
You might also like

Is the Cloudinary free tier enough for video? 104 HD minutes
Is the Cloudinary free tier enough for video? 25 credits is about 104 minutes of 1080p output, measured, and only if you store and deliver nothing else.

Getting an MP4 back out of Mux: what static renditions cost
Mux static renditions cost $0 to prepare as standard, but storage and download-as-delivery keep billing. The real math for 500 clips fetched once a month.

Most Cloudinary alternatives for video are hosts, not processors
Cloudinary alternatives for video mostly sell hosting: Gumlet, ImageKit and FastPix take the file, deliver it, and keep billing long after the transform.
Ready to process videos at scale?
Start using FFmpeg Micro's simple API today. No infrastructure required.
Get Started Free