IronPDF Pricing and IronPDF License Cost: Tiers, Renewals, Add-ons and IronPDF Alternatives

The four tiers are labelled by developers, and that is the count most buyers size against. It is the least dangerous of the three. IronPDF defines a developer as "the count of INDIVIDUALS or DEVELOPMENT MACHINES that will use, compile, or run, any Iron Product code with a debugger attached over a rolling 30-day window", and then answers its own follow-ups: an employee with a home machine and an office machine counts as two developers, contract developers count, work-from-home developers count, and development build machines count. A four person team with a CI agent and one engineer on two laptops is six developers, which is past the Plus cap of three and into Professional.

Projects are the count that catches people. The licensing page defines one project as each IDE project, "each live production server (development and staging servers not counted)", "each website, domain or subdomain" and "each microservice (including Azure and Lambda functions)", and the total is the historical count of projects created with the key, not the current one. A Lite license covers one of those. The moment your app runs on two instances behind a load balancer it is two production servers, and you are on a Plus license at minimum. Split the rendering into a separate Azure Function and that is another project. Add a customer-facing subdomain and that is one more. Professional covers ten, which a modest containerized platform reaches without trying, and beyond ten the only option is Unlimited at $4,799 today or $5,999 at list.

Locations are cities where development happens, one per city, and a remote team spread across four cities needs four, which again pushes a small team from Plus to Professional. The page offers one escape from the location count: "Add Royalty-free OEM Redistribution addon to unlock Unlimited Locations". That add-on has a price of its own, and it is the subject of the next section.

This is the same shape we found on the SelectPdf, HiQPdf and EvoPdf pricing page, where the three vendors count developers, servers, or both, and the cheapest one flips with the shape of your team. IronPDF counts all three at once, so it flips more often.

Every perpetual tier below Unlimited lists OEM royalty-free redistribution as "available at extra cost". The licensing FAQ then divides the world into four cases. No coverage required if the product is "used internally within your organization without redistribution or public API exposure". OEM coverage if you ship end-user software with IronPDF inside it. SaaS coverage, which "permits the use of our products within SaaS platforms to deliver backend features and services to end-users". And SDK coverage, a separate contract, if your product exposes a public API that passes IronPDF functionality through to other developers.

The add-on that covers OEM and SaaS is priced at $1,999 on the license builder, with the page noting "Buying later costs more. Now $1,999 vs Later $3,999". So if the thing you are building is a paid product where customers download the PDFs your servers generate, which describes most of the people reading this page, the arithmetic is:

Shape B is the one the headline price hides. The license page leads with "Licenses from $999", and for a SaaS the smallest compliant purchase is three times that. Shape D shows the other side: at Unlimited the add-on is included, so a large team pays less per developer than shape C and gains unlimited locations and projects, which is why the page steers multi-city teams there. The right move for anyone between shapes B and D is to price Unlimited early rather than climbing one tier at a time, since the add-on plus Professional already reaches $4,398, within $401 of Unlimited today.

The comparison table on ironpdf.com says "Perpetual license. Grants indefinite use of a product version at time of purchase without expiration or renewal fees", and separately that Support and Updates are "1 year free" on every tier and "Paid per year" after that. Both statements are true, and together they mean that the license price is the price of the version on your purchase date. Chromium moves, .NET moves, and the security patches that come with new IronPDF releases are behind the renewal.

The renewal ladder is not printed in the comparison table; it sits inside the license builder further down the page, which is where we read it. It is a clean percentage of list price: standard support renews at 60 percent ($599 Lite, $899 Plus, $1,799 Professional, $3,599 Unlimited) and premium support at 80 percent ($799, $1,199, $2,399, $4,799). The default selection on the page is premium, billed "Yearly. 1st year free. $2,399 next year. Auto renewal, cancel anytime." for Professional. Measured against the discounted price you actually paid, that premium renewal is 100 percent of the license, every year. Over three years a Professional buyer on premium spends $2,399 on the license and $4,798 on staying current.

There is a cheaper way to buy time. The 5 year Support and Updates option is a one-time purchase at a stated 40 percent saving: $5,397 standard or $7,197 premium for Professional, against $8,995 or $11,995 for five yearly renewals. If you know the library is staying in the product for five years, that is the option to take at checkout, because the yearly plan is the default and the saving is not offered retroactively.

For comparison, HiQPdf renews at a flat 50 percent and SelectPdf at 60 to 67 percent, both priced on our .NET converter comparison. QuestPDF, priced below, renews at 100 percent of its own $1,999 because its license is a yearly renewal by design, with the version kept if you stop.

Alongside the perpetual ladder IronPDF sells two subscriptions, both for one developer, one location and one project. Monthly at $99 includes 1,000 API calls a month and charges $0.04 a call after. Yearly at $708 ($59 a month billed annually) includes 15,000 calls a year and charges $0.03 after. Both include ongoing updates while you pay, and both say "No lock-in contract, cancel any time". The tooltip defines usage as "tracked by the number of load/export calls in all environments. Each call consumes 1 API credit."

That definition deserves a question before you buy, because loading HTML and exporting a PDF are two operations in the IronPDF API, and the wording does not say whether one rendered document consumes one credit or two. If it is two, the 1,000 included calls cover 500 documents and the overage is effectively $0.08 a PDF. We could not settle that from the published page, so we have priced the subscription on the generous reading of one credit per document and you should confirm the strict one with sales in writing.

Two things fall out of that table. The monthly subscription passes the price of a Lite perpetual license in its eleventh month at the minimum volume, and at 10,000 renders a month it costs more in ten weeks. It exists for a short project, not for a product. And against a hosted per-render API the gap is the meter itself: the subscription meters calls on top of a seat, the perpetual license meters developers, servers and cities, and a rendering API meters renders only. At 10,000 renders a month the subscription is about 16 times the Sitepdf Starter API, which is documented on the PDF API pricing page with the same normalization applied to nine hosted vendors.

The published alternatives lists for this query are not usable. G2 names Adobe Acrobat, Visual Studio, pdfFiller and Zoom Workplace as IronPDF alternatives. None of those is a .NET PDF library, and one of them is video conferencing. Below are the five options a .NET team actually chooses between, read from each vendor on 18 September 2026, with the one thing each is good at and the one thing that rules it out.

Notice that two of the five cheapest looking alternatives do not render HTML at all. That is the most common mistake in this comparison: QuestPDF and PDFsharp are excellent libraries that solve a different problem, and a team that migrates to them from IronPDF is rewriting its templates, not swapping a package. If your PDFs start life as HTML, the real field is IronPDF, iText with pdfHTML, Syncfusion, and a hosted rendering API. The C# PDF library comparison goes through the engines one by one.

IronPDF earns its place. It ships a Chromium based renderer inside the NuGet package, so a C# team gets browser-accurate output without running a browser, and it does far more than convert: it edits, merges, signs, stamps, redacts and reads PDFs with one dependency. It runs on Windows, Linux and macOS, in Docker, in Azure Functions and in AWS Lambda, which is more than SelectPdf can say. The rate card is public, the definitions of every counted thing are published with worked examples, there is a 30 day money-back guarantee, and the company sells through Enterprise with EULA redlines for procurement teams that need them. Among self-hosted .NET options only QuestPDF is more transparent, and QuestPDF does not render HTML.

Buy IronPDF when the work is PDF manipulation as much as generation, when rendering has to stay inside your network, or when a compliance regime forbids sending document content to a third party. In those cases the Unlimited tier with the add-on included is the version to price, and the 5 year updates bundle is the way to buy it.

Do not buy it for the single job of turning HTML into PDF on a server you also have to scale. That job is a metered commodity, and every count in the IronPDF model, developers, cities, production servers, microservices, the SaaS add-on and the yearly updates, is a count that a rendering API does not have. Send the HTML, get the PDF and a dated archive copy back, and the invoice is a function of one number you already track. The PDF generator API page shows the request shape, and the code sheet below is the whole migration for a typical ChromePdfRenderer call.