The journal · 21 September 2026 · 8 min read
Power Automate HTML to PDF: Convert HTML to PDF in Power Automate, One Flow Priced Five Ways
The same 600 PDFs a month cost $0 to $2,334 a year in Power Automate, and the biggest line is usually the Microsoft license, not the converter. Encodian, Plumsail and Nutrient are Standard connectors; the HTTP action, Adobe and Cloudmersive are Premium, so a button flow with 12 runners needs 12 seats. Changing the trigger to automated cuts that to one.
Live demo
Runs in your browser. Nothing is uploaded. One PDF free to try, then a plan.
Your HTML
Live preview
Your PDF is downloading. That was the free one. The Starter plan converts as many as you need, for $29 a month or $174 a year.
See the planConverting HTML to PDF in Power Automate costs anywhere from $0 to about $2,300 a year for the same 600 documents a month, and the biggest line on the bill is usually not the converter. It is the Microsoft license that the converter's connector tier drags in. Encodian, Plumsail and Nutrient (the old Muhimbi converter) are Standard connectors and run on the Microsoft 365 license you already have. The HTTP action, Adobe PDF Services and Cloudmersive are Premium, and a Premium action inside a button flow means every person who presses the button needs a $15 a month seat. We priced one real flow five ways on 21 September 2026, and then priced it again after changing only the trigger.
The flow we are pricing
A US staffing firm's HR operations team sends 600 offer letters a month. Candidate details sit in a SharePoint list. A Compose action builds the letter as HTML from a template the team already uses for email, the flow converts it to PDF, saves it to the candidate's folder and emails it. Today the flow is an instant flow: 12 recruiters select the list item and press a button. Nobody in the tenant has Power Automate Premium; everyone has Microsoft 365 E3. That last detail is ordinary, and it is the one that decides most of the price.
Why the connector tier matters more than the connector price
Every Power Automate connector is Standard or Premium. Microsoft's licensing FAQ says users on Microsoft 365 plans "can only access standard connectors". For Premium, the pricing page lists Power Automate Premium at $15.00 per user per month, paid yearly, and Power Automate Process at $150.00 per bot per month, which can license a single flow for everyone who runs it.
Who needs the seat depends on the trigger. In Microsoft's words, "Automated and scheduled flows always run in the context of the flow owner", while "if an instant flow has premium connectors, every user who runs the flow needs a Power Automate Premium license". Our flow is instant, and it has 12 runners. So any route that puts a Premium action in it costs $180 a month, $2,160 a year, in Microsoft seats, or $1,800 a year if you license the flow with Process instead, before the converter has charged a cent.
Route 1: the OneDrive Convert file action
The route every forum answer suggests first: write the HTML to a .html file in OneDrive for Business, call Convert file with PDF as the target, save the result. It is a Standard connector, so the Microsoft cost is zero and there is no vendor. For a plain letter with inline styles it is often good enough.
The limits show up with layout. You get no margin, header or footer settings, and the questions on Microsoft's own Q&A forum tell the story: people asking how to put a header and footer on each page of an HTML conversion, and people reporting that the converted file comes out corrupt. For an offer letter that legal has approved down to the letterhead, "often good enough" means someone checks every PDF by eye, which at 600 a month is the cost you are trying to avoid.
Route 2: Plumsail Documents
Plumsail's Convert HTML to PDF action takes the HTML string and returns the file. The connector is Standard on Microsoft Learn, so the seat cost is zero. Plumsail counts "an action execution on integration platforms" as one document. At one action per letter we need 600 a month, which is past the Folder plan's 200, so it is Drawer at $84 a month billed annually, $1,008 a year ($99 a month if you pay monthly). If the flow also stamped or merged the PDF with a Plumsail action, each of those would count again.
Route 3: Encodian Flowr
Encodian's Convert - HTML to PDF is a standard action at one credit per run, and the Encodian Flowr connectors are Standard tier, so again no seat. 600 credits a month does not fit the Standard plan's 500, but Encodian's help center publishes a rule that makes the gap cheap: top-up credits cost your plan's per-credit rate plus 20 percent and last a year. Standard on annual billing is $499 for 6,000 credits, about $0.083 each, so a top-up credit is about $0.0998, and the 1,200 extra credits a year this flow needs cost $119.76. Total $618.76 a year, cheaper than stepping up to Midsize at $999. The side-by-side of all three connector rate cards, with four volume shapes, is on our Encodian, Plumsail and Muhimbi pricing comparison.
Route 4: a Premium converter (Adobe PDF Services or Cloudmersive)
Both have HTML to PDF actions and both are Premium connectors. Adobe's Convert Dynamic HTML to PDF action wants a zip file with an index.html at the top level, which means another step to package your Compose output. Leave the vendor fees aside for a moment (we priced Adobe PDF Services API pricing separately, and its free allowance is measured in Document Transactions rather than documents). In this flow the Microsoft seats alone are $2,160 a year for 12 recruiters, or $1,800 with a Process license on the flow. That is more than any Standard connector charges for the whole job.
Route 5: a rendering API through the HTTP action
This is our product, so weigh this section accordingly. The HTTP action posts the HTML to a PDF generator API and gets back a PDF rendered in Chromium, with margins, page size, headers and web fonts under your control, and a dated archive copy of every letter kept for later. Sitepdf's Starter API is $174 a year for 10,000 renders a month, so 600 letters use 6 percent of it. The HTTP action is Premium, though, so in the flow as built it inherits the same $2,160 a year of seats as Route 4. Priced honestly against today's button flow, it is $2,334 a year, the most expensive route here.
Now change one thing: the trigger
Nothing about this flow needs a person to press a button. The recruiter already edits the SharePoint item; add a choice column called Offer status and change the trigger to When an item is created or modified, with a trigger condition that fires only when the status becomes Ready to send. The flow is now automated, it runs in the owner's license context, and only the owner needs Premium: one seat, $180 a year.
| Route (600 PDFs a month) | Connector tier | Vendor, per year | Button flow, 12 runners | Automated flow, 1 owner |
|---|---|---|---|---|
| OneDrive Convert file | Standard | $0 | $0, limited layout control | $0 |
| Plumsail Documents, Drawer | Standard | $1,008 | $1,008 | $1,008 |
| Encodian Flowr, Standard plus top-up | Standard | $618.76 | $618.76 | $618.76 |
| Adobe PDF Services or Cloudmersive | Premium | Vendor fee | $2,160 in seats plus the vendor fee | $180 plus the vendor fee |
| Sitepdf API via the HTTP action | Premium | $174 | $2,334 | $354 |
Read the two right-hand columns together. With a Standard connector the trigger does not matter, and the choice is purely between vendors: Encodian at $618.76 beats Plumsail at $1,008 for this single-action flow. With a Premium route the trigger is worth $1,980 a year on its own, more than the price difference between any two vendors in the table. After the trigger change, the rendering API is the cheapest route that gives full layout control, at $354, and it keeps that lead as volume grows because 10,000 renders a month cost the same $174.
Two cautions before you copy the fix. First, the owner should be a named person with a Premium seat, not a shared service principal: Microsoft's FAQ lists flows running under an application user among the cases that need a Process license. Second, if your tenant already holds Premium through Dynamics 365 or a Power Platform agreement, the seat column is already paid and the vendor column is the whole comparison.
Which route to buy
If the letter is simple, nobody has Premium and volume stays in the hundreds, start with Encodian or Plumsail; both are honest, published and Standard. Plumsail is the better fit if you are also filling Word templates and collecting signatures, Encodian if you need many different document actions from one credit pool. If the document has to look exactly like the approved design, if the same flow will soon run thousands of times a month, or if you need to prove later exactly what a candidate received, use the rendering API with an automated trigger. The same logic applies outside Microsoft's stack; our guide to generating PDFs from Zapier, Make and n8n prices the equivalent step on those platforms.
One last point for HR teams specifically. The offer letter is the first document in an onboarding sequence that usually continues with policy acknowledgments and required training, and it is worth building the flow so the signed letter's date is the one that starts that clock. If new-hire courses are still tracked in a spreadsheet, a corporate LMS that assigns and tracks onboarding training can pick up where the PDF leaves off. The Sitepdf API tiers are listed by monthly render volume, so you can check the economics for your own numbers before you change a single trigger.
Written by the team behind SitePDF, an HTML to PDF API that archives every page it renders. The in-browser converter is free to try, and API plans start at $29 a month.