The Problem With Modern File Converter Pricing
Open the pricing page of almost any cloud file converter and you will see numbers that look reasonable. $8 a month here. $12.99 a month there. A "free tier" of 10 daily uses or 20 daily minutes.
What those pages do not tell you is what those numbers actually buy.
We spent a week reading customer reviews, billing complaints, and our competitors' own help articles to figure out what people actually pay versus what they expect to pay. Two patterns came up over and over.
This guide walks through both. It is not a takedown. FreeConvert and CloudConvert are mature products that serve real customers well. But their billing models obscure the real cost of a conversion, and most people only figure that out after they have already paid.
We use a different model. We will explain that too, with the same level of detail.
Pattern One: Minutes That Are Not Minutes (FreeConvert)
FreeConvert advertises a free tier of "20 conversion minutes per day." That sounds like 20 minutes of wall-clock time. It is not.
Each conversion has a base cost in "minutes" plus an additional charge for actual processing time. A small image conversion that takes two seconds of real time still counts as roughly one minute. So 20 daily "minutes" works out to about 10 operations per day for most casual users.
The mismatch shows up on review sites. On Trustpilot, FreeConvert reviewers regularly complain that they thought they had 20 free minutes and discovered after a handful of files that they had hit the daily cap. MConverter, a direct competitor, documents the gap in their own blog: 20 minutes equals roughly 10 operations.
The same logic continues on paid plans. The $12.99 a month Basic tier ships with "1,500 conversion minutes per month." If you convert ten 200 MB videos a week, you might find that the actual processing time eats your quota in the first ten days. The published number is fine. The unit it counts in is the problem.
A worked example
Say you want to convert a one hour 1080p video from MOV to MP4. The video itself is one hour long. The actual conversion runtime depends on the encoding settings and the server load, but a CPU encode of a one hour video typically takes between 5 and 15 minutes.
On FreeConvert's free tier, that single file will not finish. The free tier has a "5 conversion minutes per file" cap. The file gets stopped partway through with an error message about exceeding the free minutes.
On FreeConvert's $12.99 Basic plan, you have 1,500 monthly conversion minutes. The same one hour video might consume 8 to 15 of those minutes. Convert 100 similar videos in a month and you have used the entire monthly quota. The "1,500" number on the pricing page makes it sound like a much bigger budget than it actually is for video work.
What the pricing page does say
To FreeConvert's credit, their pricing FAQ does state that "large files or advanced codecs consume more conversion minutes." It is the unit that is misleading, not the disclosure. They tell you minutes vary by file. They just do not give you a per-format table, so you cannot pre-compute how much of your monthly allocation a specific job will burn until you try it.
Pattern Two: Credits That Vary By Format (CloudConvert)
CloudConvert uses a different model. They sell credits.
The free tier is 10 credits per day. Pay-as-you-go starts at $8 for 500 minutes. Subscriptions start at $8 a month for 1,000 minutes. The catch is the conversion cost in credits depends on what you are converting.
Per CloudConvert's published pricing:
- General format conversions cost 1 credit minimum
- Office to PDF or iWork to PDF costs 2 credits minimum
- PDF to Office costs 4 credits minimum, because they use a paid third-party engine (Apryse) for that route
Then there is an additional credit per minute of actual processing time on top of the base.
So the same 10 credit free tier buys 10 image conversions, or 5 Office to PDF conversions, or 2 PDF to Office conversions per day. Same advertised allowance. Wildly different real allowance depending on what files you happen to work with.
A worked example
Say you bought the $8 a month subscription plan with 1,000 credits. You spend a month converting PDFs back to editable Word documents because you are migrating a stack of old client deliverables.
PDF to Office is 4 credits minimum, plus 1 credit per minute of processing. A 50 page PDF might burn 8 credits. Convert 125 of those and you have used your entire monthly subscription.
If instead you spent the same month doing simple image conversions, you would get 1,000 of them.
Both customers paid $8. Both stayed within their published quota. The second customer got 8x the work done. The credit model does not lie, but it makes the real cost-per-job depend on which file types you happen to work with, which is hard to predict in advance.
Credits expire on subscriptions
There is one more wrinkle. CloudConvert subscription credits expire at the end of each billing period. They do not roll over. If you bought 1,000 monthly credits and used 600, the remaining 400 disappear when the month ends. The pay-as-you-go credits never expire. The monthly subscription credits do.
CloudConvert is upfront about this in their terms. It is still a surprise to most customers who buy the subscription assuming it works like a phone plan.
How We Price (And Why)
We sell two things. A free tier and a flat subscription.
Free tier: 20 conversions per day with a free account, or 5 per day with no signup. One conversion equals one file successfully converted into the format you asked for. The size of the file does not change the count. The processing time does not change the count. The source format and target format do not change the count. Twenty files per day equals twenty conversions, regardless of what those files are.
Pro plan: $9.99 a month. 100 conversions per day (2,000 per month). Files up to 2 GB. Same definition of "conversion" applies. We do not throttle by minutes. We do not charge more for harder formats. We do not expire your credits at month-end because there are no credits.
That is the entire model.
Why we picked this model
When we started building, we did the same exercise we just walked you through. We looked at what existing converters charged and tried to predict what a real customer would actually pay. The answer was always "it depends." That made sense to us as the operators, because our compute cost really does depend on file size and processing time. But it made the pricing page useless to most customers, because they could not predict their monthly bill without doing math we did not give them tools to do.
We decided to absorb the variability on our side. A 10 second image conversion and a one hour video conversion both count as one conversion in your bill. Some files cost us more compute than others. We average that out and price the subscription so the average covers it. People who convert mostly small files subsidize people who convert mostly large files, the same way an "all you can eat" buffet works.
It is not the cheapest way to price. If you only ever convert tiny images, you would pay less elsewhere. But for the median user, the prediction error is zero. You see $9.99 on the page. You pay $9.99 at the end of the month. You can plan your team budget without a per-format calculator.
What we give up
To be fair, here is what this model costs us.
We have to enforce file size limits, because we cannot afford a flat-rate model with 50 GB uploads. 2 GB on Pro, 10 GB on Business. That covers everything most users do but it is an honest cap, not a "we let you try and then bill you" surprise.
We do not have a usage-based, pay-per-call API tier. API access comes with the standard plans instead: the full REST API, all 9 SDKs, webhooks, presigned uploads and OAuth2 are included on Free, Pro, and Business, billed at the same flat monthly price as the rest of the product. The upside is a predictable bill with no metering. The honest downside is that if you need true per-call pricing at very high volume, we are not the right fit yet, and if you are in that spot we would rather you reach out so we can quote something fair than push you onto a plan that does not match how you actually use it.
What This Means For You
If you are evaluating converters for personal or small team use, the question is what model fits how you actually work.
Use FreeConvert if your conversions are uniformly small and short. Their per-minute model rewards you when each job takes seconds. Their GPU encoding tier is genuinely fast for video.
Use CloudConvert if your conversions are mostly identical-format, mostly small, and you want never-expiring credits. Their pay-as-you-go is competitive for buy-once project work.
Use us if your work is unpredictable in file size, you do not want to think about per-format cost, and you want a flat monthly bill you can plan around. Or if you just want a free tier where 5 daily conversions actually means 5 daily conversions of anything you want.
We are not the right tool for every customer. We are the right tool for customers who want the bill to match the pricing page.
Try Both Models Side By Side
The fastest way to verify any of this is to try the free tiers and convert the files you actually convert. Note how many you can do before you hit the cap. That is the real free-tier limit, not the advertised one.
Then look at what you paid this month somewhere else, look at what you would pay us, and decide whether flat rate beats variable rate for your specific workflow.
Start with our free 5 daily conversions. No credit card. No account required. No minute counter watching you.
Sources Cited
- FreeConvert pricing: freeconvert.com/pricing
- FreeConvert "20 minutes equals 10 operations" analysis: MConverter blog
- CloudConvert pricing and credit math: cloudconvert.com/pricing
- CloudConvert credit expiry terms: cloudconvert.com/terms
- Customer reviews of both services: Trustpilot FreeConvert, Trustpilot CloudConvert, Capterra CloudConvert
