Is the Cloudinary free tier enough for video? 104 HD minutes

The Cloudinary free tier is enough for video only if you process roughly 100 minutes of 1080p a month and put almost nothing else through the same 25 credits, because processing, storage and delivery all draw on one pool.

Every Cloudinary number below comes from Cloudinary's published plan comparison and billing documentation, read on November 2, 2026. Vendors restate these meters quietly, so check their pricing page against these figures before you build.

What 25 Cloudinary credits convert to in minutes of video

Cloudinary never publishes a minutes figure for its free tier, so you derive it. The docs define one credit as 1,000 transformations, 1 GB of managed storage, 1 GB of viewing bandwidth, 500 SD video seconds, or 250 HD video processing seconds. Twenty-five credits at the HD rate is 6,250 seconds, about 104 minutes of 1080p output in a 30-day window. At the SD rate it's 12,500 seconds, about 208 minutes.

The per-second counting is where video stops behaving like images. A derived SD video is counted at 2 transformations per second of output and a derived HD video at 4 per second for h264, h265 and vp9, and the initial upload counts as one transformation. The ratios line up: 1,000 transformations divided by 4 per second is the same 250 HD seconds per credit.

Resolution is defined by pixel count, not by label. SD means an output of 921,600 total pixels or fewer, HD means more than that and up to 2,073,600. A 1280x720 render is exactly 921,600 pixels and bills as SD; 1080x1920 is exactly 2,073,600 and bills as HD at double the rate. Rendering your vertical cuts at 720x1280 instead of 1080x1920 doubles the minutes the free pool gives you. HDR output using dr_high with vc_h265 is charged at twice the rate for its resolution.

So one minute of 1080p output costs 240 transformations, or 0.24 credits. One minute of 720p output costs 0.12.

Why 104 minutes is a ceiling and not an allowance

The 104 minutes assumes you process video and then do nothing with it, which no pipeline does. Cloudinary's derived assets, the transformed outputs it caches and serves, count against the storage quota alongside your originals and any backed-up revisions. Upload a 10-minute 1080p master at 8 Mbps and that single file is 0.6 GB against the quota, 0.6 credits, before you transform anything. The four cuts you render from it are charged per second of output, then stored as their own assets.

Delivery is the meter that ends the conversation. A 45-second 1080p vertical clip at 5 Mbps is about 28 MB. A thousand plays from Cloudinary's CDN is roughly 28 GB of video bandwidth, which at 1 GB per credit on Free is 28 credits: more than the whole monthly allocation, for one clip that did modestly well. The same traffic on a self-service paid plan costs 14 credits, because paid plans meter video bandwidth at 2 GB per credit.

On Free and the self-service paid plans, transformations and bandwidth are counted over a rolling last-30-days window rather than resetting on a billing date; storage is a snapshot of what you hold now. There's no monthly reset to plan a batch around, and nothing to roll over: usage ages out of the window. Uploads on Free are capped at 100 MB per video and 10 MB per image, with a 25-megapixel image limit, and files over 100 MB need Cloudinary's upload_large chunked method with its default 20 MB chunks.

Cloudinary's support documentation describes warnings at roughly 90% of quota and repeated upgrade notifications rather than instant overage billing, but an account left over quota is eventually disabled and delivery can stop.

What one repurposing month costs in credits, line by line

Take a month one of our users runs: 20 masters, each 10 minutes of 1080p, each cut into four 45-second vertical shorts at 1080x1920 for TikTok, Reels and YouTube Shorts. No views yet, no delivery, just processing and the files sitting there.

That month is 28.66 credits against an allowance of 25, and it blew the budget before a single viewer watched anything. Processing was half of it. The other half was rent on storage for files most builders already keep in Amazon S3 or Cloudflare R2. Same pattern as why your Mux invoice is mostly delivery: the transform is the cheap line, the recurring meters are the bill.

Delete the originals after each run and the month lands at 16.66 credits, inside the free pool. Render the cuts at 720x1280 instead and processing halves to 7.2 credits. Both of those are real answers, and neither is in the credit table.

The same month on a processing-only meter

FFmpeg Micro prices one thing, so the arithmetic has one line. Processing costs 1 token per 10 seconds of input, metered per second with no rounding up to the minute, and billed on the input duration, not how long the servers take. Trim 45 seconds out of a 10-minute master and you're billed for 45 seconds, not 10 minutes. Status checks, job listing and downloads are free, and failed jobs are never billed.

The same 80 cuts at 45 input seconds each is 3,600 input seconds, or 360 tokens. The 200 free tokens that land at sign-up cover the first 33 minutes of that, and the remaining 160 are inside a $5 top-up of 500 tokens. At Starter's rate of 2,500 tokens for $19.99, each 45-second cut costs about 3.6 cents. Storage isn't metered, delivery isn't metered, and there's no second pool to watch, because there's no CDN and no player: you get the file back and put it where it already lives. The pricing comparison has the token tables for your own footage.

The request is one call, from code, from n8n, Make or Zapier, or from an AI agent over MCP:

curl -X POST https://api.ffmpeg-micro.com/v1/transcodes \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "inputs": [{"url": "https://storage.example.com/input.mp4"}],
    "outputFormat": "mp4"
  }'

Submit the job, poll for status, download the output. Free accounts cap input files at 100 MB, the same ceiling Cloudinary's Free plan puts on video uploads, and paid plans raise it to 1,024 MB on Starter and 2,048 MB on Pro.

Which free tier is right for which reader

Cloudinary's free tier is the better deal if you want a whole media platform for a small catalogue, and it isn't close. For $0 and no card you get the upload widget, the upload API and search, remote fetch, automatic backup with revision tracking, image and video transformations, video transcoding with adaptive streaming, CDN delivery, and 3 users on 1 account. For a small team shipping a site with a few hundred assets and modest traffic, 25 credits is a real product and the per-second video rate won't stop you. Nothing on FFmpeg Micro's free tier replaces that.

Cloudinary's free tier is the wrong shape when all you want is the file back. Two of those features are the ones charging you: storage you're paying for in S3 anyway, and bandwidth for views that TikTok and YouTube serve from their own infrastructure once you've uploaded. Processing was 14.4 of the 28.66 credits above, so half the bill bought capability the pipeline didn't use. That's the same accounting error as paying one blended rate for editing work when half of it is machine work.

FFmpeg Micro's free tier is right for the builder with a video step inside an n8n, Make or Zapier workflow who needs 33 minutes of transcoding, reframing, watermarking or caption burn-in to prove the pipeline works, with unlimited storage, unlimited API keys and nothing else to budget. What it doesn't include is customer support, token management, automatic top-up or token banking: those start at Starter, at $19.99 a month. Cloudinary's free tier gives 3 users; ours gives 1 user and 1 organization, and Starter raises that to 10 users across 2 organizations. If you want a team on the free plan, Cloudinary wins that line.

FAQ about the Cloudinary free tier for video

Does the Cloudinary free tier include video transcoding?

Yes. Cloudinary's own plan comparison lists video transformations and video transcoding with adaptive streaming as Free plan features, along with the upload API, remote fetch and CDN delivery. Third-party pricing guides that call transcoding paid-only are wrong: the limit on Free is the 25-credit pool and the 100 MB per-video upload cap, not feature gating.

How many minutes of 1080p video do 25 Cloudinary credits process?

Twenty-five Cloudinary credits process about 104 minutes of 1080p output, derived from 250 HD video processing seconds per credit. At 720p the same 25 credits cover about 208 minutes, because an output of 921,600 pixels or fewer bills at the SD rate of 2 transformations per second instead of the HD rate of 4.

Do unused Cloudinary credits roll over to the next month?

Unused Cloudinary credits don't roll over, and there's nothing to roll over: transformations and bandwidth on the Free and self-service paid plans are counted over a rolling last-30-days window rather than a calendar month, and storage is measured as a current snapshot. FFmpeg Micro works the other way: purchased tokens don't expire while the account is open, and a subscription's monthly grant rolls over up to three times the grant while you stay subscribed.

What happens when a video transformation fails?

Cloudinary doesn't publish a clear statement on credits consumed by a failed derived asset, so test it on your own account before you trust a retry loop with your quota. FFmpeg Micro's rule is published: failed jobs are never billed, and status checks and downloads don't cost tokens either.

Which Cloudinary features aren't covered by the 25 credits at all?

Add-ons sit outside the credit pool entirely, AI video transcription being the obvious one for anyone generating captions. Add-on usage is billed separately, its quota resets monthly on the billing date rather than on a rolling window, and it stops hard when exhausted rather than drawing down your credits.

The comparison that decides this isn't Cloudinary against us, it's your own footage against both meters: total the minutes you process, the gigabytes you store, and who serves the views, then price the processing half at FFmpeg Micro's pricing page. Sign up free and 200 tokens land without a card, about 33 minutes of video, with no servers to run, callable from your code, from n8n, Make and Zapier, or from your AI agents.