CloudConvert API Pricing and Cost Per Credit: the Full Ladder Behind the Slider

Entry is $10.00 a month for 1,000 credits on a subscription, or $18.00 once for 1,000 package credits that never expire. There is a free tier of 10 credits a day, which is a testing allowance rather than a plan: it is capped at a 1 GB file size, 5 minutes of processing time, 5 concurrent tasks and low processing priority. Paid plans lift all four of those to unlimited.

The two paid shapes answer different questions. A package suits irregular work, because unused credits sit in the account indefinitely and an auto-refill option tops it up when it empties. A subscription is cheaper per credit at every volume we measured, but the credits reset each month, and CloudConvert warns that if you switch subscription "any remaining conversion credits will expire". If your volume swings by a factor of three between months, the cheaper per credit rate can still lose to the package, because you pay the subscription for a peak you only hit twice a year.

Above the published ladder there is an Enterprise tier with custom credits and pricing, which adds dedicated capacity, priority support, a 99.9 percent SLA, SSO and SAML, custom contracts and metered invoicing. Team billing is available on the standard plans too, so one billing account can cover an organization while conversions stay private per user.

A conversion costs a base credit determined by its type, plus time. CloudConvert states it plainly: "The longer a conversion takes, the more resources it consumes and the more expensive it becomes. Our packages and subscriptions typically consume one credit per minute of conversion time." The base costs are published as a short table.

So an HTML to PDF render starts at the cheapest base cost on the card. That sounds like good news, and for a simple document it is. The catch is the second half of the formula. CloudConvert adds that "By default, conversions consume at least one credit, with additional credits charged for every extra minute if the conversion takes longer than one minute."

HTML to PDF is the conversion type where that clause bites hardest, because render time is not a property of the file size. It is a property of the page. A plain invoice built from server-rendered markup finishes in a second or two. A report that pulls a web font, waits on a charting library, lazy-loads images and settles a layout can run past sixty seconds, and at that point it costs two credits instead of one. Nothing in the rate card tells you which of those you have.

Run the arithmetic on a real workload. Ten thousand renders a month that all finish inside a minute need 10,000 credits and cost $74.00 on a subscription. If those same ten thousand documents average just over a minute, you need 20,000 credits, which sits between the 19,000 rung at $131.00 and the 25,000 rung at $168.00. The document count did not change, the invoice nearly doubled, and the only thing that moved was how long your own pages take to paint.

CloudConvert is fair about the typical case: "Ninety-five percent of our conversions take only a few seconds, and we already account for that." That is true across their whole mix, which is dominated by media and Office files. It is a weaker guarantee for the specific job of rendering a modern web page, which is the slowest thing on the menu. Before you commit, time your ten worst templates, not your best one. Two credits on your heaviest report is the number that sets your budget.

One genuinely good clause: "only successful conversions are charged". A failed render is free, which is not true of every metered API and is worth having when you are rendering pages you do not control.

Those two volumes are worth pricing because they are where most document workloads actually sit, and because they line up with published tiers on both sides. The CloudConvert column assumes the good case of one credit per render.

At ten thousand renders CloudConvert is about 2.6 times our monthly price, and at fifty thousand about 3.1 times. Those multiples widen if any of your pages cross the one minute line, and they widen again against our yearly billing, which costs the same as six months. They narrow to nothing if you also need the other 200 formats, which is the honest qualifier and the subject of the next section.

The structural difference is what you are buying. CloudConvert sells you a bucket of compute time measured in credits, and your bill moves with how hard your documents are. A per render tier sells you a document count, and the heavy report costs the same as the light one. Which is better depends entirely on whether your render times are predictable. If they are, and they are short, credits can be excellent value. If your slowest template is ten times your fastest, a flat count removes a variable you cannot control.

This page exists because we sell a competing API, so it is worth being specific about where CloudConvert wins, because on several counts it does.

Format breadth. CloudConvert converts roughly two hundred formats: video, audio, images, ebooks, CAD, archives, Office documents in both directions. We render HTML to PDF and archive the source page, and that is the whole product. If your application needs to accept whatever a customer uploads and normalize it, that is a different job and a single-format API is the wrong tool for it. Buying two vendors to avoid one is usually a false economy.

Concurrency. CloudConvert gives paid plans unlimited concurrent tasks. Our tiers cap concurrency at 3, 10 and 30 renders. If you generate a year-end batch of fifty thousand statements in one overnight window, unlimited concurrency is a real advantage and our queue is a real constraint you should plan around.

Credits that never expire. The package model genuinely fits seasonal work better than any monthly tier, ours included. A business that renders almost nothing for nine months and then produces a quarter of a million documents in tax season is better served buying credits once than paying twelve months for two months of use.

No file size or processing time ceiling on paid plans, and a free daily allowance you can test against without a card. Our free try is a single PDF in the browser converter.

Where we are the better fit is narrower and it is about shape rather than quality: a steady monthly volume of HTML to PDF where you want a document count rather than a compute meter, and where a timestamped archive of the source page has value. If that is not your job, the table above should send you to CloudConvert with clear eyes.

The mistakes below are the ones that make published comparisons of this category disagree with each other, and they are all avoidable in about twenty minutes.

Find out whether the displayed price includes tax. CloudConvert renders prices inclusive of the viewer local VAT. A European reader sees $22.14 and a United States buyer pays $18.00 for the same thing. Any comparison that copies the displayed figure without saying which it used is 23 percent out for somebody.

Establish what one credit buys before comparing credit prices. A credit is not a unit, it is a token whose value each vendor defines. Here it is a base cost by format plus a minute of compute. Elsewhere it is a page, a megabyte, or a single API call. Two vendors at a cent a credit can differ by a factor of five on the same work.

Ask whether the meter is per document or per unit of work. This is the distinction that decides whether your bill is predictable. Per document scales with output and you can forecast it from your own database. Per minute scales with how hard the work turns out to be, which you discover after you integrate.

Price the peak month, not the average. Subscription credits that do not roll over mean the average month is the wrong number. You size the plan for the peak and pay for that headroom all year, or you overflow and pay overage rates.

Check whether failures are billed. CloudConvert does not charge for them. Several competitors do, and when you render third-party URLs your failure rate is not a rounding error.

We applied exactly these rules across the market in the PDF API pricing comparison, which puts twelve vendors on one 10,000 document workload, and in the HTML to image API pricing breakdown for the rendering-to-PNG side of the same job.

If you are comparing CloudConvert against the rest of the market on one shared workload rather than reading its own rate card, the CloudConvert pricing comparison prices six document conversion APIs on the same 10,000 file job, weighted for Office input rather than HTML. If you are shopping rather than budgeting, the CloudConvert alternative comparison prices ConvertAPI, Zamzar, PDF.co, Adobe PDF Services and Cloudmersive against each other and routes the choice by the direction of your job. For the rendering side specifically, the HTML to PDF API roundup covers who is in that market, and the HTML to PDF converter will turn a document into a PDF right now without an account. Teams generating documents from data rather than converting files that already exist should start at the document generation API page, because a converter is the wrong category for that work. Our own rates are on the pricing page.