pricingcloudinaryvideo-encoding

Cloudinary credits per video: 0.24 an HD minute, 24 per 100 clips

··9 min read
Cloudinary credits per video: 0.24 an HD minute, 24 per 100 clips

One minute of video costs 0.24 Cloudinary credits to transform at HD, 0.12 credits at SD, and 0.48 credits at 4K. Cloudinary meters video transformations per second of delivered output: 2 transformations per second for SD, 4 for HD, 8 for 4K, and 1,000 transformations to a credit.

At Plus list pricing, 225 credits for $89 a month billed annually, that HD minute works out to about 9.5 cents, and a hundred one-minute HD clips is 24 credits. Most guides quote the 250-HD-seconds-per-credit rate and then change the subject to plan tiers, leaving the division to you.

Cloudinary credits per video: one minute, ten minutes, a hundred clips

The rates below are Cloudinary's own published figures for credit conversion and transformation counting, read in November 2026. Treat the dollar columns as a working estimate and confirm the rate against your own account usage page before you size a budget, because vendors restate these. The arithmetic itself does not change: seconds of output, times the per-second rate for the resolution you deliver, divided by 1,000.

What you renderTransformationsCreditsAt $0.396/credit (Plus, annual)
1 minute, SD1200.12$0.05
1 minute, HD (1920x1080)2400.24$0.09
1 minute, 4K4800.48$0.19
10 minutes, HD2,4002.4$0.95
100 clips x 1 minute, SD12,00012$4.75
100 clips x 1 minute, HD24,00024$9.50

That last row is the one worth staring at. The Free plan grants 25 credits a month, so a hundred one-minute HD renditions consumes almost the entire month before a single byte of storage or delivery is counted. Divide the other way and you get the same answer this blog reached in Is the Cloudinary free tier enough for video? 104 HD minutes: 25 credits buys 6,250 HD seconds, or 104 minutes, if you spend the pool on nothing else.

Partial seconds are counted as full seconds, so a 6.4-second clip bills 7. Each asset upload also counts as one transformation in its own right, which means 1,000 uploads is 1 credit. Neither detail will move your bill much, but they explain why the console number never matches a clean mental estimate.

Your source file doesn't set the rate. The resolution you deliver does.

The per-second rate is keyed to the pixel count of the output, not the file you uploaded. Cloudinary's published tiers are SD at 921,600 total pixels or fewer, HD above that up to 2,073,600, and 4K above that up to 8,294,400. So 1280x720 lands at exactly 921,600 and bills as SD, while 1080x1080, a square crop people assume is small, is 1,166,400 pixels and bills as HD.

One master, two delivery resolutions, is two meters running at once. Render the same 60-second source at 720p and 1080p and you pay 2 transformations a second plus 4 a second: 360 transformations, 0.36 credits, not 0.24.

Platform variants stack the same way. A 60-second master cut to 9:16 at 1080x1920, 1:1 at 1080x1080, and 16:9 at 1920x1080 is three HD renditions at 4 transformations a second each. That's 12 a second, 720 for the minute, 0.72 credits, roughly 28 cents at Plus annual rates. Three outputs, three bills, which is the same trap Video transcoding cost is per minute. A ladder bills five times. describes on a per-minute encoder.

A derived asset is charged when it's first generated, not on every view, so the meter follows renditions produced rather than traffic. Views cost you bandwidth out of the same credit pool instead.

Where "250 HD seconds per credit" stops predicting your bill

The simple division holds for one progressive h264 rendition at a known resolution. Four common setups break it, and all four multiply rather than add.

Adaptive bitrate is the biggest one. A streaming profile generates several representations of the same source and every one of them is counted; Cloudinary's published rate for the full-HD HLS/DASH h264 profile is 14 transformations per second. That's 840 for one minute, 0.84 credits, about 33 cents a minute. The same minute delivered as a single progressive MP4 was 9 cents.

Codec choice is the second. AV1 output is published at 16, 32 and 64 transformations per second for SD, HD and 4K. One HD minute in AV1 is 1,920 transformations, 1.92 credits, roughly 76 cents, eight times the h264 figure. HDR output using dr_high with vc_h265 is charged at twice the normal rate for its resolution.

Third, f_auto on video means generating an eager transformation for each format and codec you're negotiating, and each of those is metered per second on its own. You asked for one URL and bought three renditions.

Fourth, credits are one pool shared with storage and viewing bandwidth, where 1 credit also equals 1 GB stored or 1 GB delivered. The transformation arithmetic above is a floor on your bill. Fixed plans don't auto-bill overage either: going past quota prompts an upgrade or a usage reduction, and the account can be disabled if usage stays over, which is a pipeline that stops rather than a line item you review later. The Free plan additionally caps video uploads at 100 MB per file, per a 2026 pricing walkthrough on dev.to, which bounds what those 25 credits can be spent on in the first place.

The cheapest credit is the second you never sent

Trimming belongs before the transform. Every meter in this category, output seconds or input seconds, charges for duration, so the decision that moves your bill most is how long the thing you generate actually is. A 12-minute webinar recording rendered in full "so we have it" is 2.88 HD credits. The 30-second pull quote that anyone will actually watch is 0.12.

That is the same method as RunPod FFmpeg at $0.33/hr isn't cheap. Price it per video.: take whatever unit the vendor meters in, convert it into cost per finished video, then attack the input. Vendors price the pool because the pool is theirs. You price the job because the job is yours.

The same hundred clips on a per-input-second meter

FFmpeg Micro meters the other side of the job, and the rate is published and resolution-blind: 1 token per 10 seconds of input, counted per second. A 60-second input is 6 tokens whether the output lands at 720p, 1080p, 4K or AV1. A 10-second video costs 10 seconds. Failed jobs are never billed.

Run the same comparison honestly, because each rendition here is also its own job billed on its own input seconds. Three platform variants from one 60-second master is three jobs, 18 tokens. The difference is that the rate never changes with what comes out the far end.

WorkloadCloudinaryFFmpeg Micro
1 minute, one HD rendition0.24 credits (~$0.09)6 tokens (~$0.05 on Starter)
1 minute, three HD variants0.72 credits (~$0.28)18 tokens (~$0.14)
1 minute, AV1 HD1.92 credits (~$0.76)6 tokens (~$0.05)
100 clips x 1 minute, HD24 credits (~$9.50)600 tokens (~$4.80)
30-second trim from a 1-hour recordingbills the 30 seconds of outputbills 30 seconds, 3 tokens

Starter is $19.99 a month for 2,500 tokens, which is where that $0.008 per token comes from; top-ups run 500 tokens for $5 on any plan, including Free, and purchased tokens don't expire while the account is open. Full rates are on pricing.

The trim above is one request:

curl -X POST https://api.ffmpeg-micro.com/v1/transcodes \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "inputs": [{"url": "gs://YOUR_BUCKET/webinar-full.mp4"}],
    "outputFormat": "mp4",
    "options": [
      {"option": "-ss", "argument": "00:12:30"},
      {"option": "-t",  "argument": "30"}
    ]
  }'

Where this comparison isn't fair: a Cloudinary credit also buys managed storage, CDN delivery and URL-based image transforms, and if you want all four things from one vendor, the pooled credit is doing four jobs. If you only want the file processed and handed back, you're paying for the other three. That split is the whole argument in Cloudinary alternative for video: which ones hand the file back.

FAQ about Cloudinary credits for video

How many Cloudinary credits is a 30-second video?

A 30-second HD rendition is 120 transformations, or 0.12 Cloudinary credits, at the published rate of 4 transformations per second of HD output. The same 30 seconds delivered at SD is 60 transformations, or 0.06 credits.

Does Cloudinary charge credits every time someone watches the video?

Cloudinary charges a derived asset when it's first generated, not on each view. Playback draws on the viewing-bandwidth side of the credit pool instead, where 1 credit covers 1 GB delivered, so a popular video still costs you credits, just on a different meter.

Do I get charged twice if I render the same video at two sizes?

Two sizes means two per-second meters on Cloudinary, charged at each output's own resolution rate. One 60-second source delivered at both 720p and 1080p is 2 plus 4 transformations a second, 360 total, 0.36 credits rather than 0.24.

Does a 7-second clip cost 7 seconds or round up to 10?

Cloudinary counts a part of a second as a full second, so a 7-second clip bills 7 seconds of output at the rate for its resolution. FFmpeg Micro bills per second with no rounding to the minute, so that same 7-second input is metered as 7 seconds against the 10-seconds-per-token rate.

What happens if I run out of Cloudinary credits mid-month?

Fixed Cloudinary plans don't automatically bill overage. Passing 100% of quota prompts an upgrade or a reduction in usage, and the account can be disabled if usage stays over, while pay-as-you-go accounts are billed for usage above quota instead.

The 24-credit figure is the one to carry into your own planning: a hundred one-minute HD clips, one rendition each, is roughly an entire 25-credit free month on an output-second meter, and the same hundred clips is 600 tokens on an input-second meter no matter what resolution or codec comes out. Sign up free opens an account with 200 tokens, about 33 minutes of video, no card required. Spend a few of them on the 12-minute webinar you've been meaning to cut down, then put the token count next to the 0.24-credits-a-minute math above and see which meter matches the work you actually do.

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.

Software EngineeringVideo ProcessingFFmpegCloud ArchitectureAPI DesignAutomation

Ready to process videos at scale?

Start using FFmpeg Micro's simple API today. No infrastructure required.

Get Started Free