PSPDFKit Pricing and PSPDFKit Cost: What Nutrient Charges to Generate 8,000 PDFs a Month

PSPDFKit, now sold as Nutrient, does not publish a price for its SDKs: every SDK license is an annual subscription quoted by sales, priced on the components you use and how your app uses them. Nutrient does publish one price list that covers PDF generation, the DWS Processor API: $75, $275 or $445 a month for 1,000, 5,000 or 10,000 credits, or $67, $247 and $399 a month billed yearly, with one HTML to PDF conversion costing half a credit. Both were read from nutrient.io on 25 September 2026. For a team that mainly needs to turn HTML into PDFs on a server, that published card is the realistic number to plan with, and it depends heavily on how many operations each document goes through.

The team we are pricing

A US payroll and HR platform serving mid-size employers. Every month it produces about 8,000 total compensation statements, one per employee, from an HTML template the employee already sees in the portal. Each statement is followed by a two page benefits summary that HR uploads once a year. The engineering lead shortlisted PSPDFKit because the name came up in every PDF SDK comparison, and was asked a simple question by finance: what will it cost?

There are two ways to buy from Nutrient for this job, and they are priced completely differently.

PSPDFKit SDK pricing: quote only

Nutrient's SDK pricing page says licenses "are sold as annual subscriptions, including access, updates, and support, with multiyear terms available at the best yearly rate," and that price depends on "the products and components you require, and how your application uses the technology and the value it delivers." There is no figure on the page, only a contact form, and the response promise is one business day. The Web, mobile and server SDKs are all sold this way.

Directory sites print estimates for PSPDFKit, some per developer and some per month, and they disagree with each other by an order of magnitude. We could not tie any of them to a Nutrient document, so we are not repeating them. What we can say is where the category sits: across the ten commercial PDF SDKs we priced on PDF SDK pricing, the vendors that do publish a figure put a single platform, single product license at roughly $1,000 to $6,000 a year, and redistribution or OEM rights are priced separately. A component based quote with a server deployment and several modules tends to land above a starting price, not at it.

The SDK is the right purchase when the product itself needs PDF features in front of users: a viewer embedded in your web app, annotation, form filling, redaction, signing, mobile editing. Nutrient is very good at that, and a render API is not a substitute for it. Our payroll team does not need any of it. It needs 8,000 files a month produced on a server, which is the job the cloud API is priced for.

Nutrient DWS Processor API pricing, as published

The credit costs per operation are fixed and printed on the same page: HTML to PDF 0.5, image to PDF 0.5, PDF to image 0.5, PDF merge 1, compress 1, watermark 1, redaction 1, Office to PDF 1, OCR 2, text extraction 3 and digital signatures 10. Nutrient notes that "most operations are priced per use, not per page," which is good news for multi page statements.

Two rules decide what happens at the edge. Free plan output carries a "For Evaluation Purposes Only" watermark until you enable pay as you go. And overage is capped: on paid plans the default monthly spending cap is "half your monthly subscription value," and Nutrient says "we never charge beyond the cap," so a busy month can hit the cap unless someone raises it in advance.

What 8,000 statements a month cost on the Nutrient API

Render only. 8,000 HTML to PDF conversions at half a credit each is 4,000 credits. Starter plus pay as you go would be $67 plus 3,000 credits at $0.09, or $337 a month, so Growth at $247 a month billed yearly ($2,964 a year) is the cheaper fit. That is about $0.031 a statement.

Render, then merge in the benefits summary. This is how most teams would first build it: render the statement, then merge the static summary PDF onto the end. The merge is a second operation at one credit, so each statement now costs 1.5 credits and the month needs 12,000. That is past the Pro allowance: $399 plus 2,000 credits at $0.0534, or $505.80 a month, $6,069.60 a year, and the $106.80 of overage sits inside Pro's default cap of $199.50 only because volume is steady. Add a "Confidential" watermark as a third step and it becomes 2.5 credits a statement, 20,000 credits a month, which is Custom pricing territory.

That is the pattern worth knowing before any Nutrient call. The API meters operations, not documents, so the price of a document is the sum of the steps your pipeline puts it through. We found the same thing on Nutrient's Power Automate connector and on its low code competitors in Encodian, Plumsail and Muhimbi pricing: every vendor in that camp counts actions, and a two step flow doubles the bill.

The cheapest fix inside Nutrient is also the obvious one: put the benefits summary into the HTML template as extra pages, so one conversion produces the whole document. The bill falls back to the 4,000 credit case.

The same job on a render API

A rendering API that counts documents rather than operations prices this more simply. On SitePDF the 8,000 statements, with the summary pages included in the template, are 8,000 renders on the Starter API tier: $29 a month, or $174 a year billed yearly, with 10,000 renders of headroom for open enrollment months. Each render returns a hosted PDF, and with the archive option a dated copy of the statement is kept for 90 days on that tier, one year on Growth and three years on Scale.

That retention question matters more for payroll than the per document price. Federal wage and hour rules expect payroll records to be kept for years, and each state adds its own requirements. Most HR platforms end up maintaining a list of what must be kept, for how long and where, and a register that tracks each obligation against the control that meets it is the tidy way to show an auditor that the statement archive actually covers the requirement.

When PSPDFKit is worth its price

If the PDF is something your users work in rather than something your server hands them, the SDK is the product and the quote is the cost of doing it properly. Viewing large files in the browser, annotating, filling forms, redacting, signing, comparing versions, running the same features on iOS and Android: those are years of engineering, and Nutrient sells them with support. The DWS API is also a sensible buy when a pipeline really does need OCR, Office conversion, redaction and signatures in one place, since a single vendor for all of them is worth something.

If the job is producing documents from HTML you already have, you are paying for a toolkit to use one tool. Before you book the sales call, put one real statement through the converter at the top of this page and count the steps your pipeline actually needs. If it is one step, the PDF API pricing comparison shows every per document and per credit vendor on one table, and the C# PDF library comparison covers the self hosted side if you would rather keep rendering in house.