CloudConvert Pricing: Document Conversion API Rates at ConvertAPI, Zamzar, PDF.co and Adobe

Put the six rate cards side by side and they look like they are selling the same thing at different markups. They are not. Cloudmersive meters API calls. ConvertAPI meters conversions. Zamzar and CloudConvert meter credits that a conversion consumes. Adobe meters Document Transactions. PDF.co meters credits too, but it multiplies them by the page count, and its own documentation is explicit about it: "total credits = endpoint credits × pages processed", with a worked example that converting 5,000 one page PDFs to JPG "uses 5,000 × 12 = 60,000 credits".

For a three page memo that difference is invisible. Change one variable and it stops being invisible. Keep the job at 10,000 documents a month but make them 60 page contracts instead of 3 page memos:

• Cloudmersive still bills 10,000 API calls. The bill stays at $19.99.
• ConvertAPI still bills 10,000 conversions. The bill stays at $175.
• CloudConvert still charges 2 base credits for Office to PDF, and only adds credits if a single conversion runs past a minute. The bill stays near $200.
• Zamzar still charges at least 1 credit a conversion, and its size rule bites on megabytes rather than pages: "The first 50 MB of any input file is included in your conversion cost." The bill stays near $299.
• Adobe crosses its own page cap. A Create operation covers "up to 50 pages", so a 60 page file is 2 transactions and the transaction count doubles to 20,000 a month.
• PDF.co goes from 63 credits a document to 1,260. Ten thousand of those is 12.6 million credits a month, which is twenty six times its largest published plan.

Four vendors did not move, one doubled, and one went up twentyfold, from the same change to the same input. This is why a per conversion price comparison of this category tells you almost nothing on its own. Before you compare any two numbers here, find out what the vendor is counting.

Almost every metered API in this market rewards volume. PDF.co does not, and the arithmetic is easy to check because the plan cards publish both the price and the credit allowance.

• Basic, $8.99 a month for 16,500 credits, is $0.000545 a credit.
• Personal, $22.49 a month for 37,000 credits, is $0.000608 a credit.
• Business 1, $44.99 for 80,500, is $0.000559.
• Business 2, $89.99 for 159,850, is $0.000563.
• Business 3, $270.00 for 483,000, is $0.000559.

The cheapest credit on the entire ladder is on the $8.99 entry plan. The second rung is the worst value on the ladder, 11.6 percent more per credit than the plan below it, and nothing above it ever wins the entry rate back. Spending thirty times more a month buys you credits at a very slightly worse unit price than the cheapest plan on the page.

That is not a criticism of the product, and PDF.co does far more than convert files. It is a warning about a habit. Buyers upgrade metered plans expecting the unit rate to fall, because on most APIs it does. Here it does not, so the only reason to move up the ladder is the credit ceiling itself.

Cloudmersive publishes eight rungs on its small business ladder. Divide each price by its call allowance and the answer is the same every time: $0.002. $19.99 for 10,000, $49.99 for 25,000, $99.99 for 50,000, $199.99 for 100,000, $499.99 for 250,000, $699.99 for 350,000 and $999.99 for 500,000 all land on two tenths of a cent a call.

It is the only vendor in this comparison with a completely flat unit price, and it is a genuinely useful property. You do not have to model tier boundaries, you do not lose money by sitting just under a rung, and a capacity forecast is just calls multiplied by $0.002. Against that, the ladder is a hard ceiling rather than a soft one, and Cloudmersive notes that "Available API call capacity per month, and call rate is limited by vCore compute capacity", so throughput is a separate question from allowance.

Update, 9 September 2026: this rate card is no longer published. On a re-read today the Cloudmersive pricing page returned HTTP 200 with no API rate card on it at all. The plan tiles carried placeholder content, and the only dollar figure in the document was a repeated $540,000 next to the text "3500 Sq Ft 3 Beds 3.5 Baths 2 Garages". Four URLs were checked, including the API subdomain, which showed the same placeholder. The $0.002 figures above were accurate when read on 4 September 2026 and are left here as a record, but treat them as historical and ask Cloudmersive for a written rate card before shortlisting it. We track the current state of the field on our CloudConvert alternative comparison.

ConvertAPI's comparison table publishes an overage line, and the number in it is the same across the whole ladder: $0.05 per conversion on Developer, Startup, Growth, Business and Enterprise alike.

Compare that with the in plan rates on the same table, which fall from $0.035 on Developer to $0.007 on Business. Overrun the Business plan and every extra conversion costs 7.1 times what the conversions inside the plan cost. Overrun Developer and it costs 1.4 times. The penalty for a bad forecast therefore grows the more you spend, which is the opposite of what most buyers assume when they size a plan.

The practical reading is that on ConvertAPI you want headroom, and you want more of it the higher up the ladder you go. Our 10,000 conversion job fits Growth at 15,000 with 50 percent spare, and that spare is the point rather than waste. Buying Startup at 5,000 and paying overage on the other 5,000 would cost $95 plus $250, which is $345, against $175 for simply buying the right plan.

Adobe publishes no price for the paid tier of Acrobat Services, which makes the free allowance the only Adobe number a buyer can actually plan against. It reads simply enough: "500 free Document Transactions per month". What it buys is not simple at all, because the transaction table in Adobe's own licensing documentation prices operations differently by a factor of five hundred.

• Create, which is the DOCX to PDF operation, is "1 Document Transaction for up to 50 pages". 500 transactions is up to 25,000 pages a month.
• Export, PDF back to Office, and OCR, Compress and Combine follow the same 50 page rule.
• Extract and PDF To Markdown is "1 Document Transaction for up to 5 pages", ten times denser. 500 transactions is 2,500 pages.
• Accessibility Auto-Tag is "10 Document Transactions (per page)". 500 transactions is 50 pages, and a single 60 page report would need 600 transactions, more than the entire monthly free allowance.
• Electronic Seal is "10 Document Transactions (per PDF)", so 500 transactions seals 50 documents.

Two operations, both inside one vendor, both counted in the same unit, and the same 500 transactions buy 25,000 pages of one and 50 pages of the other. If you are evaluating Adobe on the free tier, the number that matters is not 500. It is 500 divided by whatever your specific operation costs. Our comparison of Adobe PDF Services API alternatives goes further into what the paid tier does and does not include.

CloudConvert is the only vendor here that varies the base cost by what you are converting. Its published table is short and worth memorizing if you use the service:

• General conversions: 1 credit
• Office to PDF: 2 credits
• iWork to PDF: 2 credits
• PDF to Office: 4 credits

Turning a Word file into a PDF costs twice a general conversion. Turning a PDF back into Word costs four times a general conversion, and twice what the outbound trip cost. On top of that, "conversions consume at least one credit, with additional credits charged for every extra minute if the conversion takes longer than one minute", so a slow file costs more than a fast one of the same type.

There is one trap on the pricing page itself that is easy to walk into. CloudConvert renders its prices inclusive of the viewer's local VAT. Our read on 4 September 2026 returned "$12.30 incl. 23% VAT" for the 1,000 credit subscription and "$22.14 incl. 23% VAT" for the equivalent package, with a cost per credit of $0.0123 and $0.0221. A US buyer does not pay that 23 percent, so the figures that belong in a US budget are $10.00 and $18.00, at $0.0100 and $0.0180 a credit. If you are comparing CloudConvert against a US vendor, check whether the number you copied was tax inclusive before you put it in a spreadsheet.

One figure we will not publish is CloudConvert's rate at 20,000 credits. The pricing page sets volume with a browser slider that we could not drive outside an interactive session, and it defaults to the 1,000 credit rung on every automated read. CloudConvert states that subscriptions "can be up to 50% cheaper than packages" and that the rate improves with volume, so the $200 a month in our table is a ceiling for this job rather than a quote. We would rather publish a bound we can defend than a number we guessed.

On published prices for short documents the order is not close. Cloudmersive at $19.99 is roughly a ninth of ConvertAPI and a fifteenth of Zamzar for the same 10,000 conversions, and its flat $0.002 makes forecasting trivial. If cost per short conversion is the only axis you care about, that is the answer and the rest of this page is detail. One caveat added 9 September 2026: Cloudmersive has since stopped publishing that rate card, so you can no longer verify the $0.002 figure yourself. If you are actively shortlisting rather than reading, start from the CloudConvert alternative routing guide, which is kept current and picks by job direction rather than by headline price.

Cost is rarely the only axis. ConvertAPI publishes the clearest plan structure of the six, with concurrency and maximum file size stated per tier, 200 MB on Developer rising to 1 GB on Business, which matters if you convert large files. Zamzar is the format generalist, and if your inbound files include the long tail of formats rather than Office documents, breadth is worth paying for. CloudConvert is the one to look at when conversions are mixed and occasional, because a package of credits "never expire" and there is no monthly floor to carry. PDF.co is priced for short documents and manipulation work rather than long ones, and its 42 credit document parser suggests where its real value sits. Adobe is the choice when the requirement is Acrobat fidelity or Auto-Tag accessibility output specifically, and when a procurement process can absorb a sales cycle.

And a limit of all six worth saying plainly: these are file format converters. They take a document that already exists and change its container. If the document does not exist yet, because it is a rendered invoice, statement, report or notice built from your own HTML and data, a conversion API is the wrong tool and you want a rendering API instead. That is what we build, our PDF API pricing comparison covers that side of the market, and the demo above will render a page for you right now without an account.