For a cloud flow that converts HTML or a URL directly to JPG, use the HTML to JPG/JPEG action in the Power2Apps Converter connector. Its Microsoft Learn reference lists HTML as required input, width and height controls that default to 500 pixels, and response modes including Base64 String and Bytes. If you need a picture of a page as it appears in a browser, use Power Automate Desktop’s browser screenshot action instead; that captures a displayed page or element rather than treating HTML or a URL as conversion input.
Choose the right conversion route
Start by deciding what the image must represent. A cloud conversion action is appropriate when the flow has HTML content or a URL to submit. A desktop screenshot is appropriate when the page is open in a browser and you need to capture its rendered appearance.
| Route | Use it when | What is documented |
|---|---|---|
| Power2Apps Converter cloud action | Your cloud flow has HTML or a URL and needs JPG/JPEG output. | Microsoft Learn lists the HTML-to-JPG/JPEG action, width and height inputs, 500-pixel defaults, and response modes. Detailed rendering behavior and commercial terms are not established by the connector reference. |
| Power Automate Desktop browser screenshot | You need an image of a page or element currently displayed in a browser. | Microsoft documents saving a screenshot to a file or clipboard. It is browser automation, not the same input path as a cloud HTML conversion action. |
| Encodian Convert connector | You want to investigate another third-party HTML-to-image connector. | Microsoft Learn lists an HTML-to-image action, but its index does not establish exact formats or detailed behavior. |
Do not select a connector merely because its name includes “convert.” OneDrive’s Convert file action is listed as a general preview conversion action, and Microsoft’s Content Conversion connector converts HTML to plain text, not JPG. The OneDrive timing workaround documented for HTML-to-PDF errors is not a JPG solution.
Convert HTML or a URL in a cloud flow
Find the current connector action
- In Power Automate, create or open a cloud flow.
- Add an action and search the connector list for Power2Apps Converter.
- Choose its current HTML to JPG/JPEG action. The Microsoft Learn connector reference marks older HTML-to-image actions as deprecated, so do not follow an old flow example without checking its action name against the current connector and designer.
- Provide the HTML input required by the action. If your workflow starts with a URL, use the URL input supported by the action’s current designer rather than assuming a separate browser-capture behavior.
The connector reference is the basis for this cloud route: Power2Apps Converter connector documentation. The exact input and output field labels can change in the designer; use the current action schema when wiring later steps.
Recommended Free Tools
#1 Best Overall
Set dimensions and response format
Set the width and height in pixels for the downstream use. The documented default for each is 500 pixels. Those are defaults, not a stated maximum or a guarantee about image sharpness, page length, or CSS fidelity. The connector reference does not establish maximum dimensions, full-page behavior, or how every external resource is rendered, so validate the result using your actual HTML or URL.
For large outputs, the action reference offers response modes including Base64 String and Bytes to reduce response size. Select the mode that matches the next action’s accepted input, then inspect the current output schema to identify the returned image data. Avoid assuming a particular dynamic-content token name based on examples from another version.
Save the returned image
After conversion, pass the image output to a file-creation or storage action that accepts the chosen response representation. SharePoint has file-content actions, and OneDrive lists file creation and upload operations; these can store the result but do not perform the HTML-to-JPG conversion themselves. Confirm the output field and content format in the current flow designer before connecting the storage step. For example, a storage action expecting binary file content may require the Bytes response rather than a Base64 string.
Capture the page currently displayed in a browser
When the requirement is a screenshot of a rendered page, use Power Automate Desktop’s browser automation rather than treating the HTML as a conversion payload. Microsoft describes the browser screenshot action as taking a screenshot of the web page—or an element of it—currently displayed in the browser and saving the image to a file or clipboard.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Open or navigate to the target page in the browser through your desktop flow.
- Wait until the page or target element is in the state you intend to capture. The screenshot action captures what is currently displayed; it does not promise that asynchronous content has finished loading.
- Use the browser screenshot action and choose the page or an element, then save to a file or clipboard as needed.
- Check the saved output before passing it to later actions, especially if the page relies on content that appears after navigation.
See Microsoft’s Browser automation actions reference. This route requires browser automation in Power Automate Desktop; it is distinct from a cloud action that receives HTML or a URL.
Know which limits apply to which connector
Microsoft’s Content Conversion connector documentation describes an HTML-to-plain-text function with a 5 MB maximum content length and a maximum HTML DOM depth of 70. Those specifications apply to that connector’s text conversion action, not to Power2Apps HTML-to-JPG conversion. The same documentation says Content Conversion is no longer available in GCC/GCC High for new implementations; do not treat that as a statement about Power2Apps availability.
For the same reason, the documented Content Conversion limits should not be used as a proxy for the image action’s capacity. The available Power2Apps connector reference does not establish a maximum HTML size, a maximum output dimension, or a particular data-handling or pricing term.
Troubleshoot common problems
The action is missing or an older action is shown
- Cause: You may be searching a different connector or following an example that uses a deprecated HTML-to-image action.
- Fix: Search for Power2Apps Converter and select the currently listed HTML-to-JPG/JPEG action. Compare the action name with the live connector reference and designer.
The flow succeeds but the file step fails
- Cause: The file action may expect binary bytes while the conversion response is configured as Base64 String, or the wrong dynamic output field may be mapped.
- Fix: Check the conversion action’s current output schema and set its response mode to match the receiving action. Re-select the dynamic-content field in the designer rather than copying a token name from an old example.
The JPG has unexpected dimensions or missing content
- Cause: The width and height control the requested output dimensions, but the connector reference does not document full-page capture, rendering details, or how external assets are handled.
- Fix: Test with the actual HTML or URL and adjust the pixel dimensions for your use case. If the need is specifically to capture what is displayed in a browser, use the desktop screenshot route.
The screenshot is blank or incomplete
- Cause: A desktop screenshot captures the current browser state; the page may not yet display the content you expect.
- Fix: Ensure the browser has navigated to the intended page and that the relevant content is visible before invoking the screenshot action. The cited action reference does not promise a particular page-load or dynamic-content wait behavior.
A OneDrive or Content Conversion action does not produce JPG
- Cause: OneDrive’s Convert file is a general conversion preview, while Content Conversion’s described HTML function returns text.
- Fix: Use the Power2Apps HTML-to-JPG/JPEG action for cloud conversion, or Power Automate Desktop browser automation for a screenshot. Do not apply the OneDrive HTML-to-PDF delay workaround to JPG conversion.
Performance, reliability, and service checks
For a cloud flow, response representation matters: the Power2Apps reference offers Base64 String and Bytes modes intended to reduce response size for large files. Choose according to the receiving step, and test the end-to-end flow with representative inputs so that conversion output and storage agree. The available connector reference does not establish a rendering speed, maximum dimensions, or service-level guarantee.
For browser screenshots, the image reflects what the browser currently displays. Page readiness and external content can affect what is visible at capture time, so flows should make the desired page state explicit before calling the screenshot action. Treat the captured result as a browser screenshot, not as proof that a supplied HTML document would render identically through a cloud conversion service.
Before adopting any connector, check whether it is available for your Power Automate environment and whether its access, licensing, and data-handling terms fit the flow. Pricing and licensing comparisons for the listed conversion routes are not established by the cited connector pages. Microsoft’s separate Content Conversion regional availability note applies only to that connector.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If your input is a public page URL and you want an image without setting up browser automation, ScreenshotNeo offers a screenshot API and MCP server for developers. It can accept a URL in one GET request; before capture it accepts the cookie or consent banner as a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets. You can turn each cleanup step off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status.
For example, replace the target URL with the page you want to capture:
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for setup and response details. Its MCP server exposes take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. One thousand screenshots per month are free with no card; paid plans start at $5 for 3,000. ScreenshotNeo also offers browser-rendered PNG, JPEG, or WebP images and PDFs, with options including full-page capture, element selection, custom CSS and JavaScript, device and viewport settings, and async jobs.
Sign up for ScreenshotNeo and get 1,000 screenshots a month free, with no card required.
Other routes to investigate
Microsoft Learn also lists an Encodian Convert HTML-to-image action. The connector index is enough to identify it as a possible option to investigate, but it does not settle the supported output formats, detailed behavior, pricing, or data handling. Verify those points in the live connector and vendor documentation before building a flow around it.
For a short decision rule: use Power2Apps Converter when a cloud flow needs HTML/URL-to-JPG conversion; use Power Automate Desktop when the target is the page or element currently displayed in a browser; investigate Encodian only if its current action details and terms meet your requirements.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsQuick 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.
