Encodian Pricing vs Plumsail Pricing and Muhimbi PDF Converter Cost: Power Automate PDF Connectors Priced by Volume

The three vendors use three words for their meter, and the words hide the same rule. Encodian says a single use of a standard action "will consume 1 credit", and its own worked example is a flow that splits a PDF once and watermarks it nine times inside an Apply to each loop: 10 credits. Plumsail says "a process run in the Plumsail account, an action execution on integration platforms, or a call to the REST API counts for one document", so the word document is misleading: in Power Automate it is one action execution. Nutrient defines monthly operations as "the number of individual operations, for example, convert, watermark, secure, and OCR per page".

So the unit is the action, not the finished file. A typical invoice flow converts HTML to PDF, stamps a watermark or a PAID mark, and applies a password: three actions, three units, one PDF. The cost per PDF is the cost per unit multiplied by the number of connector actions in your flow, and that multiplier is the first thing to count before you pick a tier. Encodian has a partial exception: its Utility actions cost 0.05 credits each on paid plans, which is why text and array helpers from Encodian are close to free, while Merge documents to PDF costs one credit plus one per document converted, and OCR costs one credit per page on both Encodian and Nutrient.

Two more differences matter at the edge of a tier. Unused allowance: Encodian states that the monthly credit allowance "renews on the 1st of every month. Unused credits do not roll over." Plumsail sells reserve packs at $15 per 100 documents that roll to the next month. File size: Nutrient caps a single operation at 5 MB on Basic, 25 MB on Professional and 100 MB on Enterprise, and the Basic cap is lower than the 25 MB its own trial allows, so a trial that works on your real scanned files can fail after you buy the cheapest plan.

Every connector in Power Automate is either Standard or Premium, and that label decides whether you pay Microsoft on top of the vendor. Microsoft's licensing FAQ is direct: "Users with the free plan or one of the Microsoft 365 license plans can only access standard connectors." A Premium connector needs Power Automate Premium at $15.00 per user per month, paid yearly, or Power Automate Process at $150.00 per flow (bot) per month, both read from Microsoft's pricing page on 21 September 2026.

This is the most useful fact on the page for a Microsoft 365 shop without Premium seats: Encodian, Plumsail and Nutrient all run on the license you already have. Their price is the whole price. Adobe, Cloudmersive and any direct API call add a Microsoft license, and who needs it depends on the trigger. Microsoft's rule: "Automated and scheduled flows always run in the context of the flow owner", so only the owner needs Premium, but "if an instant flow has premium connectors, every user who runs the flow needs a Power Automate Premium license". A button flow that twelve people click with a Premium action inside is $180 a month in Microsoft seats before the connector bill, or one $150 Process license on the flow.

Many enterprise tenants already hold Premium through Dynamics 365 or a Power Platform agreement, in which case this section costs you nothing. Check before you let it decide the vendor. The Power Automate HTML to PDF cost breakdown prices one real flow both ways, button trigger and automated trigger, to show how much of the bill the trigger design moves.

Rate cards only mean something against a volume. These four shapes cover most of what we see Power Automate teams building. Each price is the cheapest published way to cover the volume for a year on annual billing, using each vendor's own top-up rules, read 21 September 2026. Units are PDFs multiplied by the connector actions per PDF.

Three things fall out of this. At small volume Plumsail is the cheapest connector, $300 a year against $499 for Encodian and $1,308 for Nutrient, whose Basic tier is priced for 1,250 operations whether you use them or not. From the middle up, Encodian wins among connectors, because its top-up credits are priced at your tier's own per-credit rate plus 20 percent, while Plumsail's reserve documents are a flat $0.15, more than any Plumsail tier charges per document. At shape D that difference is $12,097.80 against $39,888, and both vendors will quote a custom plan well before you get there. The action multiplier moves the answer more than the vendor does: shape B makes 1,000 PDFs and pays for 2,000 units, and the only reason the rendering API column stays flat is that a watermark or a PAID stamp can be part of the HTML, so there is nothing to do after the render.

For the Sitepdf column we added $180 a year, one Premium seat for the flow owner, because the API is called through the HTTP action. That assumes an automated or scheduled trigger. If your tenant already has Premium, subtract it.

Encodian documents its top-up rule in its own help center: additional credits are "valid for 1 year from the date of purchase", are only spent once the monthly allowance is gone, and are priced at "your chosen subscription plan plus 20% (on a per credit basis)", with a minimum of 250 credits self-serve or 4,000 through the sales desk. Its worked example, a Midsize plan plus 9,600 top-up credits for a year of 1,200 to 3,000 credits a month, comes to $1,798.20, which is the figure we used for shape B. The same page says it is often cheaper to upgrade than to top up, and that it does not offer "Custom pricing below 12,000 credits per month".

The Dedicated tiers are priced for isolation, not volume. Dedicated is $10,999 a year for 18,000 credits a month, which is $0.051 a credit, more than the $0.038 of Enterprise on annual billing. What you buy is processing inside your own Azure tenant, a requirement some regulated buyers have, and Encodian lists two actions (PDF Sign and image OCR) as unavailable on dedicated subscriptions. Dedicated+ at $39,900 a year removes the credit meter entirely. If you are not required to keep processing in your tenant, Enterprise plus top-ups is cheaper per credit all the way up to about 895,000 credits a year (roughly 75,000 a month), the point where Dedicated+ starts to win.

Nutrient does not publish a top-up. Above 12,500 operations a month the page says to contact sales, which is the same opacity we recorded on the Salesforce document generation pricing audit, where four of the five leading vendors publish no number at all. Among Power Automate connectors the market is more honest: two of three publish every rung.

Choose Plumsail Documents if you are filling Word, Excel or PowerPoint templates from SharePoint list data at a few hundred documents a month. It is the cheapest entry, the connector has the highest throttle of the three at 1,200 calls a minute, its reserve documents roll over, and e-signature collection is part of the same product. It is priced least well for a flow that runs several connector actions per document at volume.

Choose Encodian Flowr if you need breadth inside Power Automate: more than 230 actions across nine connectors, from Office conversion to barcode reading, OCR, PDF/A and regex utilities that cost a twentieth of a credit. Its per-credit price falls fastest with volume, and it lets you pick the processing region (US, Canada, Germany, Australia, UK or Switzerland) on every paid plan. It is also the one vendor with a published plan that removes the meter, at $39,900 a year.

Choose Nutrient (the Muhimbi PDF Converter) if you already run it on SharePoint on-premises or in Nintex workflows. Nutrient sells the same converter as an on-premises deployment with unlimited users, developers and locations for a single legal entity, quoted by sales, and it converts formats the others treat as edge cases: Visio, CAD, MSG and EML email, and InfoPath on the Extended input tiers. As a pure cloud connector bought from scratch it is the most expensive of the three at every volume we priced.

Choose none of them for a flow whose only job is turning HTML or a live URL into a PDF at thousands a month. Every connector here meters that job at 4 to 15 cents a unit, and a rendering API meters it at a fraction of a cent. That is the next section.

If your documents start life as HTML, either an email body, a SharePoint page, a Power Apps screen you have rebuilt as a template, or a report page with a URL, you do not need a document connector for the conversion step. One HTTP action posts the HTML to a rendering API and gets a PDF back. Sitepdf renders in managed Chromium, so CSS, web fonts and page breaks come out as they look in the browser, which is the control the OneDrive Convert file route does not give you, and every render is kept as a dated archive copy you can retrieve later. Starter API is $29 a month or $174 a year for 10,000 renders, Growth $99 or $594 for 50,000, and a render is a render regardless of page count. The PDF generator API page shows the request options and the PDF API pricing comparison puts the per-render price against the other hosted APIs.

Be clear about what this does not replace. Sitepdf renders HTML and URLs to PDF. It does not fill Word templates, convert Excel, merge or split existing PDFs, OCR scans or collect signatures, and a flow that needs those still needs a connector for those steps. The honest design for a lot of teams is both: a Standard connector for the Office-file steps it is good at, and one HTTP call for the high-volume HTML rendering that would otherwise eat the credit allowance. If you are deciding between template merge and HTML rendering more broadly, the document generation API guide lays out when each engine wins.