How to Capture a Full-Page Website Screenshot with Power Automate

To capture a whole webpage with Power Automate for desktop, use the browser automation action Take screenshot of web page. Set Capture to Entire web page, choose File or Clipboard for Save mode, then run the flow with a browser instance on the page you want to capture. The separate workstation action named Take screenshot captures a screen or foreground window, not the full document page. See Microsoft’s browser automation action reference and workstation action reference.

1. Prepare a browser instance

1. Open Power Automate for desktop and create or edit a desktop flow.
2. Add a browser launch action, such as Launch new Microsoft Edge, or attach to a running browser instance that the flow can access.
3. For a new browser, set its initial URL to the page to capture, or navigate to the target using a browser action such as Go to web page.
4. Use the same Windows user account to run Power Automate and start or attach to the browser. Microsoft documents that browser automation can’t open or attach to a browser started by a different system user.

Power Automate for desktop documents web automation for the built-in Automation browser and browsers including Edge, Chrome, Firefox, and Internet Explorer; setup varies with the browser and automation method. The browser action needs a browser instance variable. Follow Microsoft’s current web automation setup guidance for the browser you use.

2. Add the full-page screenshot action

1. In the browser automation actions, add Take screenshot of web page.
2. Set Web browser instance to the instance created or attached in the previous step.
3. Set Capture to Entire web page. This is the full-page setting; Specific element captures a selected webpage element instead.
4. Set Save mode to File to write an image, or Clipboard if a later flow action will consume the image from the clipboard.
5. For File, enter the complete output path in Image file, including its directory and filename. Select a supported File format.
6. Save and run the flow. Open the resulting image and confirm it contains the page sections and state you intended to capture.

Example flow outline

Launch new Microsoft Edge (or attach to an accessible instance)
Go to web page: https://example.com/
[Optional: wait for the page state your capture requires]
Take screenshot of web page:
  Web browser instance: %Browser%
  Capture: Entire web page
  Save mode: File
  Image file: C:\Captures\example.png
  File format: PNG

This is an outline of the actions and settings to create in the Power Automate designer, not executable Power Fx or a script. The browser screenshot action does not produce an output variable.

3. Choose capture scope, destination, and format

Setting	Choices	Use it when
Capture	Entire web page; Specific element	Choose Entire web page for the full page. Choose Specific element when you only need one webpage element; select its UI element.
Save mode	File; Clipboard	Use File for a retained artifact with a known path. Use Clipboard when the next step works with clipboard content.
File format	BMP, EMF, EXIF, GIF, JPG, PNG, TIFF, WMF	Choose a format supported by the downstream tool. PNG and JPG are common choices for image workflows; the action offers the full list shown here.

Microsoft lists the format choices but does not establish format-specific quality, file-size, or compatibility guarantees for every destination. If another action or service will process the image, verify that it accepts the format you choose. A file save requires a full path, and the destination directory must be available to the flow.

4. Handle page state before capture

The action captures the webpage currently displayed in the browser. A flow should navigate to the intended URL and wait for the state it needs before taking the screenshot. For a site with delayed content, determine a suitable wait using the site’s behavior and inspect the resulting capture. Microsoft’s screenshot reference does not promise that lazy-loaded images, infinite-scroll content, animations, sticky headers, or other dynamic behavior will be handled in a particular way.

• Delayed content: add an appropriate wait step before capture, then inspect whether the needed content appeared.
• Lazy-loaded sections: test the target page. The reference does not guarantee off-screen content will load automatically.
• Infinite scroll: decide which portion of the page should exist before capture. Do not assume the screenshot action will scroll through every possible item.
• Consent prompts or overlays: check whether a banner or dialog obscures the page. The built-in action’s reference does not describe automatic banner removal.
• Repeatability: use the same URL, browser configuration, and page-ready condition for captures that need consistent results.

5. Troubleshoot common failures

Symptom	Likely cause	What to check
“Element with specified CSS selector not found”	The action is set to Specific element, but its selected webpage element or selector is absent in the current page state.	Confirm the right page and browser instance are active, wait for the element if it loads later, and reselect or repair the UI element. Use Entire web page if you need the whole document.
“Failed to save file”	The destination path cannot be written or the file save otherwise failed.	Check that the full path is valid, the directory exists and is writable, the filename is usable, and the selected format is supported.
“Failed to save in the clipboard”	The action could not put the captured image on the clipboard.	Check whether the flow can use the clipboard in its execution context. If the workflow needs a retained artifact, try File mode and inspect the destination permissions.
“Failed to take screenshot”	The browser instance, page, or capture operation failed.	Confirm the browser instance is valid and points to the intended page; retry after the page reaches the needed state. Check browser automation setup and the flow run details.
The browser cannot be attached to or controlled	The browser may have been started under another Windows user, or browser-specific automation setup may be missing.	Run Power Automate and the browser under the same user, then follow the setup guidance for the selected browser and automation method.
The image shows a screen or window instead of a long page	The workstation Take screenshot action was used rather than the browser action.	Use browser automation’s Take screenshot of web page and set Capture to Entire web page.

These action exceptions and the browser-action configuration are documented in Microsoft’s reference. For broader setup issues, see Microsoft’s browser control troubleshooting article.

6. Reliability, performance, and cost considerations

A full-page capture depends on reaching the intended page state and successfully saving or copying the output. The Microsoft action reference does not publish a capture-time benchmark, maximum page height, or a guarantee for dynamic content. Large or complex pages may take longer to become ready and may produce larger images; measure the flow with the pages and destination you actually use.

• Reliability: use a predictable browser launch or attachment path, wait for the content your task requires, and inspect representative output. A success from the screenshot action alone does not establish that every dynamic section rendered as intended.
• Performance: capture only the scope you need. A full document can involve more content than a specific element; use element capture when the task only needs one component.
• Storage: image formats and page content affect output size. Set a destination and retention policy appropriate to your workflow.
• Cost: the cited Microsoft action documentation gives no per-screenshot price. Any Power Automate licensing or hosting costs depend on your environment and plan; consult your organization’s current licensing information rather than infer a price from this capture action.

7. If you need an API instead of browser setup

ScreenshotNeo is a website screenshot API and MCP server. It can be useful when the job is to request an image or PDF from code or an AI agent instead of configuring a desktop browser flow. Its API accepts a URL and returns a screenshot or PDF. The examples below use the documented endpoint and request pattern; replace YOUR_API_KEY with your key. See the ScreenshotNeo API documentation.

Or skip the browser setup

Make a single GET request to capture a page as WebP:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webp

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://example.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before the shot. Bot checks, blank pages, and failed loads are never billed; response headers report the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. Sign up for 1,000 free screenshots a month, with no card required.

FAQ

Does “Entire web page” mean the whole document rather than the visible screen?

Yes. It is the browser action’s full-webpage capture scope. The workstation screenshot action has a different screen or window scope.

Can I capture just one part of a webpage?

Yes. Set Capture to Specific element and select the webpage element. The action can raise a missing-selector exception if that element is not found.

Can the action return the image as a flow variable?

The documented action produces no variables. Choose File or Clipboard as its destination.

Will the action always capture lazy-loaded or animated content?

Microsoft’s reference does not make that guarantee. Wait for and inspect the target page state in your own flow.

Can I use this for PDFs?

The documented browser screenshot action saves an image to a file or clipboard. For PDF output through ScreenshotNeo, use its documented PDF capability or MCP capture_pdf tool.