Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Short answer: Power Apps does not provide a general HTML-to-PDF renderer. Choose one of three routes: use the experimental PDF() function when your content already exists on a canvas screen, populate a Word template and convert it with Word Online (Business), or send HTML/URL input to a connector that explicitly supports HTML-to-PDF. The first two are Microsoft-documented paths; direct HTML conversion depends on a third-party connector and its current licensing and action names.
Choose the route that matches your input
| Route | Input | Best for | Important limitation |
|---|---|---|---|
Power Apps PDF() |
Canvas screen or supported controls | A form or report already laid out in Power Apps | Experimental and not documented as a general HTML/CSS renderer |
| Word Online (Business) | Word template with named content controls | Invoices, letters and repeatable reports | Premium connector availability and Word-layout constraints |
| HTML-to-PDF connector | HTML string, HTML file or URL | Existing HTML/CSS that must be rendered directly | Connector licensing, fidelity and action status vary |
Method 1: Power Apps PDF() for a canvas screen
Microsoft describes the function as generating a PDF “from the contents of a screen or certain types of controls.” It is experimental and disabled by default, so treat it as a feature to validate in your tenant rather than a production guarantee.
Enable the function
- Open the canvas app in Power Apps Studio.
- Select Settings.
- Open Upcoming features, then Experimental.
- Enable the PDF feature and save the app.
Add a capture button
Put the following formula in a button’s OnSelect property, replacing the screen name with your own:
PDF(SubmitInspectionScreen);The screen should contain the labels, galleries, forms and other controls you want printed. An HTML string sitting in a variable is not automatically interpreted as a browser document. To use this route, represent the needed content with app controls first, or choose a connector that accepts HTML directly.
#1 Best Overall
Deliver the generated file
The PDF result must be passed to an action connector or a Power Automate flow for storage or delivery. A typical flow receives the file from the app, creates a file in SharePoint or OneDrive, and optionally sends it by email. Define the file name and destination in the flow so users can retrieve the binary even when the app closes after the button is pressed.
Method 2: Populate a Word template, then convert to PDF
This is the most predictable Microsoft route for business documents. Instead of trying to reproduce arbitrary HTML, you design a .docx template once and fill named content controls on each run.
Create the template
- Create a Word document in Word desktop or Word for the web.
- Enable the Developer controls if needed and insert named content controls for fields such as customer name, invoice number, line items and totals.
- Save the template in OneDrive for Business, a SharePoint Online site or an Office 365 Group document library supported by Microsoft Graph.
Build the Power Automate flow
- Start the flow from Power Apps, a button, or another trigger.
- Add Word Online (Business) – Populate a Microsoft Word template.
- Select the template and map each content control to dynamic values from Power Apps or your data source.
- Add Word Online (Business) – Convert Word Document to PDF.
- Use the returned PDF binary in Create file, an email attachment, or another approved destination.
The connector reference labels Word Online (Business) Premium for Power Apps and Power Automate in supported regions. Confirm that your tenant, region and license expose both actions before designing the app around them.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
When Word is preferable
- You need stable pagination, corporate branding and repeatable fields.
- Users edit or approve the source document in Word.
- Your source data is structured rather than a complete HTML page.
Word templates are not a drop-in browser engine: complex CSS, JavaScript interactions and web-only layouts must be redesigned as Word content controls and document formatting.
Method 3: Convert HTML directly with a connector
If you already have an HTML string or a URL, use a connector whose action explicitly accepts HTML content or an HTML URL. The Microsoft connector catalog lists Power2Apps operations with options including landscape mode, image quality, headers, footers, paper format, margins, page ranges and scale. The catalog marks the shown Convert HTML to PDF operations as deprecated, so check the replacement action and connector version in your tenant before production deployment.
Connector alternatives
- LatinShare: catalogued with a “Convert HTML to PDF” action.
- PDF4me: offers HTML conversion and template actions.
- Plumsail: provides HTML-to-PDF settings for engine, paper size, orientation, margins, header and footer.
- Muhimbi: can convert a URL or HTML fragment and documents authentication, viewport, media type and conversion-delay options.
These are third-party services. They may require premium licensing or a separate account; verify current terms and data-processing requirements with your maker tenant and the vendor.
Pass HTML safely
Keep the HTML in a Power Apps variable, a file, or a data source, then map it to the connector’s HTML or URL field. If the connector accepts a URL, ensure the service can reach it without an interactive login. For inline HTML, include complete markup and absolute URLs for images and stylesheets when the service does not share your browser session.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesSet layout controls deliberately
- Paper and orientation: choose A4, Letter or the required format before testing page breaks.
- Margins: leave room for printer-safe areas and headers.
- Headers and footers: verify whether the connector expects HTML, plain text or a template.
- Scale and image quality: increase quality for diagrams, but expect larger files or slower runs.
- Page ranges: confirm whether numbering is zero- or one-based.
How to decide
| Question | Use this route |
|---|---|
| Is the desired document already a canvas screen? | PDF(), after enabling the experimental feature |
| Do you need a controlled business document with repeatable fields? | Word template plus Word Online (Business) |
| Must existing HTML/CSS be rendered without rebuilding it? | An HTML-to-PDF connector that explicitly supports your input |
| Do you need URL authentication, viewport or media-type controls? | Compare connector capabilities; Muhimbi documents these controls in the catalog |
Reliability, security and cost checks
- Release status:
PDF()is experimental, while the listed Power2Apps HTML actions are marked deprecated. - Licensing: Word Online (Business) is Premium in supported regions; third-party actions can add premium or vendor fees.
- Data exposure: HTML and generated PDFs may leave Microsoft 365 when a third-party service renders them. Check retention, residency and authentication terms.
- Assets: inaccessible fonts, images or CSS produce different output from your local browser. Prefer absolute, reachable asset URLs or inline critical styles.
- Testing: test long tables, missing images, special characters, right-to-left text, page breaks and large files before enabling user-wide flows.
Troubleshooting common failures
The PDF function is unavailable
Confirm the app is a canvas app, then check Settings > Upcoming features > Experimental. If your organization blocks experimental features, use Word or an approved connector.
The PDF is blank or missing controls
Make sure the target screen is fully populated before calling PDF(). Controls hidden by formulas, galleries that have not loaded, and content outside the captured screen can be absent. Move required content onto the target screen and test with representative data.
Word fields are not offered for mapping
Reopen the template picker after saving the file, verify that controls have names, and store the document in OneDrive for Business or SharePoint Online. Avoid duplicate or unsupported control types.
HTML conversion returns an authentication or network error
A connector rendering a URL may not possess your browser cookies or Microsoft 365 login. Supply the connector’s documented authentication settings, expose the page to its service where permitted, or send inline HTML instead.
Free tools Windows power users keep installed
One-click scans. No signup required.
Images, fonts or CSS do not appear
Use absolute HTTPS asset URLs, allow the renderer to fetch them, and wait for resources when the connector provides a delay or network-idle setting. Inline critical CSS when external stylesheets are unreliable.
Best Value
The action cannot be found
Search the current connector catalog rather than copying an old flow. Deprecated actions can disappear or be replaced, and names differ by connector version and region.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If your source is a public webpage and you need a PDF rather than a Power Apps-rendered screen, ScreenshotNeo provides a single-request capture API. It accepts the page as a visitor would, removes cookie banners, newsletter popups and chat widgets before capture, and can return a PDF. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed; the response identifies the page verdict and billing status in headers. Its MCP server gives Claude, Cursor and other MCP clients take_screenshot, get_page_info and capture_pdf tools.
See the ScreenshotNeo documentation for parameters and authentication. The following cURL request captures a page as a PDF:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.pdfPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.pdf", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);Every plan includes the same features, including PDF paper size, margins, landscape and page ranges. The Free plan includes 1,000 screenshots per month without a card; paid plans start at $5 for 3,000 shots. Sign up free when this URL-to-PDF workflow fits your app.
Frequently Asked Questions
Can Power Apps convert an arbitrary HTML string with PDF() alone?
No. PDF() is documented for a screen or certain controls, so arbitrary HTML normally needs to be rendered into controls or sent to an HTML-capable connector.
Does Word Online (Business) preserve CSS from an HTML page?
No. It converts a populated Word document; recreate the design with Word formatting and content controls.
Are third-party HTML-to-PDF connectors included with every Power Apps license?
Not necessarily. Premium licensing, regional availability and separate vendor accounts can apply.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
