EvoPdf Next and IronPDF, measured side by side
A benchmark of EvoPdf.Next.HtmlToPdf.Linux 14.60.3 against IronPdf.Linux 2026.9.2, with the same three HTML pages, the same console benchmark and the same machine, both products left on their defaults. The benchmark, the pages and the raw log of every run are available on request, so any figure on this page can be repeated on your own hardware with your own documents. EvoPdf Next is the Chromium based product, the EvoPdf.Next.HtmlToPdf packages for Windows, Linux and macOS on NuGet; EvoPdf Classic, the earlier engine with its own renderer, is still supported but is not the product measured here.
Measured on a one core Linux container. A single core measures the cost of one conversion; on a server with more cores both products scale with the number of processors.
Two Chromium versions, three years apart
Both products render with Chromium, but not the same one. The version decides which CSS and JavaScript features a page can use before the output stops matching the browser your users have.
| EvoPdf Next | IronPDF | |
|---|---|---|
| Chromium version | 142 | 109, released in January 2023 |
color-mix() | supported | not supported |
text-wrap: balance | supported | not supported |
Array.prototype.toSorted, Object.groupBy, Promise.withResolvers | supported | not supported |
IronPDF's own documentation confirms that its standard package ships Chromium 109, kept for compatibility with older Windows Server versions. A separate package, IronPdf.UpdatedChrome, ships Chromium 131 (IronPdf.UpdatedChrome for faster HTML rendering). The same documentation lists HTML and CSS features that render incorrectly under the standard package because of the older engine, overflow: hidden and subgrid among them (Rendering fixes in IronPdf.UpdatedChrome). The figures on this page were measured with the standard package, the one Install-Package IronPdf gives you. Either way, a page written against today's CSS and JavaScript renders in EvoPdf Next the way it renders in the browser your users have.
Faster on every page, most of all where the content comes from JavaScript
Sequential conversions, medians over three alternated runs.
| Page | EvoPdf Next | IronPDF |
|---|---|---|
| Simple page, 1 PDF page | 128 to 142 ms | 138 to 166 ms |
| Invoice with a 90 row table, 3 PDF pages | 191 to 204 ms | 203 to 206 ms |
| Report with JavaScript charts and a 300 row table, 7 PDF pages | 319 to 325 ms | 443 to 459 ms |
The difference is largest where it matters most: on the page whose content is produced by JavaScript, the kind of document that dashboards, generated reports and single-page applications produce, EvoPdf Next needs about 28% less time per document.
A 95th percentile that stays close to the median
Four threads converting at once, on one core, so the figures show how each engine queues work.
| Page | EvoPdf Next median / p95 | IronPDF median / p95 |
|---|---|---|
| Invoice | 840 / 913 ms | 941 / 1,505 ms |
| JavaScript report | 1,577 / 2,009 ms | 1,769 / 2,605 ms |
On real documents EvoPdf Next keeps the 95th percentile close to the median, which is what a service with a response time target cares about. On the trivial one page document IronPDF queues more evenly, because EvoPdf Next starts a fresh renderer for every document and that fixed cost shows on a page with almost nothing to render.
What a team pays
IronPDF licenses by the number of developers, locations and projects, with royalty-free redistribution sold separately. EvoPdf licenses by deployment, for any number of developers, with redistribution included in the Company License. Prices are the ones on the two pricing pages in September 2026, in USD, for the HTML to PDF product alone; both vendors also sell a wider suite.
| EvoPdf Next | IronPDF | |
|---|---|---|
| One application on one server, any number of developers | Deployment License, 450 | Lite, 999, limited to 1 developer, 1 location and 1 project |
| A team of five on several applications | Company License, 1,200 | Professional, 2,399 for up to 10 developers, 10 locations and 10 projects (list price 2,999) |
| Unlimited developers, applications and servers | Company License, 1,200 | Unlimited, 4,799 (list price 5,999) |
| Redistribution inside your own product | included in the Company License | not in Lite; sold as an extra on Plus and above, price on request |
| Updates and support | first year included, renewals optional | first year included, renewals optional |
| Both products at the same license price | the HTML to PDF license also covers EvoPdf Classic |
Licenses are perpetual on both sides. The full EvoPdf terms are on the pricing page; the IronPDF figures come from ironpdf.com/licensing and change with their promotions.
Where each product stands
| EvoPdf Next | IronPDF | |
|---|---|---|
| Rendering engine | Chromium 142 | Chromium 109 (131 in a separate package) |
| Speed on JavaScript heavy pages | 28% faster | |
| Speed on simple and table pages | faster | |
| Tail latency under load, real documents | tighter | |
| License for a team, any size | 1,200, redistribution included | 2,399 to 4,799, redistribution extra |
Product names are the property of their respective owners. Figures reflect the versions stated at the top of this page.