PC 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 & 11Outdated 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 matchUse UiPath’s Take Screenshot activity. Choose the Classic activity when your workflow uses the Classic design and an Image variable; choose the Modern activity when you need explicit control over whether to capture an element, an application window, or the desktop. Before following any property path, confirm your Studio project type and installed UI Automation package, because the two activity generations expose different controls.
Choose the right UiPath screenshot activity
Classic: UiPath.Core.Activities.TakeScreenshot
Classic Take Screenshot captures a specified UI element and returns a Screenshot field that can be used with Image variables. If you do not provide a selector, it captures the entire screen. You can also pass a UiElement produced by another activity. A clipping region lets you crop relative to that element.
Classic is a practical choice for existing Classic workflows or projects that already pass Image values between activities. Its principal target and timing properties are exposed on the activity itself.
Modern: UiPath.UIAutomationNext.Activities.NTakeScreenshot
Modern Take Screenshot can run inside or outside a Use Application/Browser card. Inside an application card it captures the targeted application; outside the card, with no target, it captures the whole desktop. UiPath lists it as compatible with Windows – Legacy, Windows, and cross-platform projects.
#1 Best Overall
- Robotic Process Automation using UiPath StudioX: A Citizen Developer’s Guide to Hyperautomation
- ABIS BOOK
- Apress
In Windows and cross-platform projects, open the activity’s Screenshot container and choose one of these scopes:
- Main window: the main active window of the attached application. This is the default.
- Element: an indicated UI element.
- Desktop: the entire desktop.
UiPath documents the Desktop option inside an Application Card starting with UIAutomation version 25.10.32. If Desktop is missing, inspect the installed package version before changing the workflow.
A complete workflow for saving a screenshot
- Add the activity. In Studio, search the Activities panel for Take Screenshot under UI Automation and place it after the application has opened or reached the state you need to document.
- Select the capture scope. For Modern, set Screenshot to Element, Main window, or Desktop. For Classic, indicate an element or provide its selector; leave the selector empty only when a whole-screen capture is intended.
- Indicate the target. Use the indication wizard on the visible control, or pass a
UiElementfrom an earlier activity. Review the generated selector rather than assuming it remains stable when the application changes. - Choose the output. Modern can output to File, Image, or Clipboard where that selector is available. File is the default. Classic exposes a Screenshot result suitable for an Image variable.
- Set a path and naming policy. For Modern File output, specify a writable filename and configure auto-increment if repeated runs must preserve earlier captures. Use an absolute, access-controlled folder for unattended jobs.
- Run and verify. Open the saved file or inspect the Image variable during debugging. Confirm that the application, element bounds, and visual state are the ones your process requires.
Classic activity settings that affect capture
Target and selector
Target.Selector identifies the element. Supplying no selector means full-screen capture. A UiElement from another activity is useful when the target is discovered dynamically. Use clipping when only a region inside that element belongs in the evidence.
Readiness and delay
WaitBefore defaults to 300 milliseconds. It can help with a known, short rendering lag, but it is not a substitute for selecting the right readiness condition. Target.WaitForReady supports None, Interactive, and Complete; choose the least permissive setting that reliably indicates the control is ready. Target.TimeoutMS defaults to 30,000 milliseconds.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Error behavior
ContinueOnError defaults to False. Set it deliberately when a missing screenshot is recoverable. UiPath notes that when ContinueOnError is True inside a Try Catch, the error is not caught, so do not enable it if your recovery branch depends on catching that exception.
Modern output, targeting, and visibility
File, Image, or Clipboard
Use File when the screenshot must survive after the workflow or be attached to a case. Use Image when later activities will inspect, resize, or compose it in memory. Use Clipboard only when a following step consumes clipboard data. UiPath qualifies the output selector as Windows-project-only where that setting is available; project type can therefore change which choices appear.
Element targeting methods
Modern element capture can expose strict and fuzzy selectors and, depending on project conditions, image, native-text, Computer Vision, and semantic-selector methods. Some are Windows-only. Computer Vision availability depends on its server configuration, and semantic selectors use an LLM-generated human-readable description. Treat the methods shown by your installed package and project as authoritative rather than assuming every method is portable to cross-platform execution.
Visibility and page readiness
For a web page or dynamic desktop app, configure the activity’s page-load and visibility checks for the state you need. A screenshot taken before a panel is visible can be technically successful yet operationally useless. Prefer a selector, visibility condition, or application readiness signal over a large fixed sleep.
Capturing a control, window, or desktop
One element
Choose Element in Modern or indicate a Classic target. This produces focused evidence such as an invoice total, error dialog, or form section and avoids unrelated information elsewhere on the screen.
The attached application’s main window
Inside Use Application/Browser, choose Main window in Modern. This is appropriate for a complete application view while excluding other open programs.
The entire desktop
Choose Desktop in Modern, or omit the Classic selector. Desktop capture can include taskbars, notifications, and other windows, so use it only when those pixels are part of the diagnostic record. In an Application Card, the Desktop choice requires UIAutomation 25.10.32 or later according to UiPath’s documentation.
Recording screenshots are not runtime screenshots
Studio’s recorder can add informative PNG screenshots while recording user actions. UiPath describes these files as being stored in a project screenshot folder; one page calls it .screenshots while an earlier sentence uses .screenshot, so confirm the actual folder in your project. Recording is not a replacement for a deliberate runtime capture: keyboard shortcuts, modifier keys, right-click, and mouse hover are listed as non-recordable actions. Use Take Screenshot when the process itself must save evidence at a defined checkpoint.
Free tools Windows power users keep installed
One-click scans. No signup required.
Unattended execution and interactive displays
A screenshot activity needs an interactive session. UiPath’s maintained error-handling guidance warns that an unattended Robot with no display may fail or silently write nothing. For reliable unattended post-mortem evidence, it recommends Orchestrator session recording for Robot 2023.2 and later; validate that recommendation against the Robot and Orchestrator versions and execution mode you operate.
Before deployment, test the exact account, Windows session, screen resolution, locked/unlocked state, and application launch method used by the Robot. A workflow that works in an attended Studio run is not proof that a headless or disconnected session can render pixels.
Privacy, storage, and naming
- Assume a capture can contain personal information, credentials, invoices, or an open authenticated session.
- Write files to access-controlled storage, not a broadly shared temporary folder.
- Set retention and cleanup rules for diagnostic images.
- Use names containing a process or case identifier, timestamp, and checkpoint so operators can trace an image without opening it.
- Avoid attaching raw screenshots to widely distributed logs; provide a restricted link or sanitized derivative where possible.
Troubleshooting checklist
The activity captures a blank or old screen
- Confirm the Robot has an interactive display.
- Check that the application is in the intended state before capture.
- Replace a fixed delay with a visibility or readiness condition; for Classic, review WaitBefore and WaitForReady.
- For Modern, verify the selected Application Card and page-load settings.
The wrong element or region is captured
- Re-indicate the target and inspect its selector.
- Ensure you selected Element rather than Main window or Desktop.
- Remove or correct a Classic clipping region that is offset relative to the target.
- Check that the target is visible and not covered by another window.
The Desktop option is unavailable
Check the UI Automation package and project type. UiPath documents Desktop inside an Application Card from version 25.10.32; older packages may not show it.
No file is produced
- Confirm File output is selected and the filename is valid.
- Use a folder where the Robot identity has write permission.
- Check auto-increment behavior when a file already exists.
- Review ContinueOnError and surrounding Try Catch logic so a failed write is not hidden.
Modern Clipboard or targeting choices are missing
Some output and targeting methods depend on Windows projects, package generation, or Computer Vision configuration. Compare the options in the activity with the project’s compatibility and installed dependencies instead of copying settings from another project.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesOr skip the browser setup
If your goal is a URL screenshot rather than a screenshot of the UiPath desktop itself, ScreenshotNeo provides a single HTTP request. It removes cookie or consent banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and whether it was billed. Its MCP server lets Claude, Cursor, and other MCP clients use take_screenshot, get_page_info, and capture_pdf.
See the full parameter reference in the ScreenshotNeo documentation. A basic cURL request is:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
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.webp", "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}`);ScreenshotNeo supports PNG, JPEG, WebP, and PDF output plus full-page lazy-image loading, CSS-selector element capture, device presets, custom viewports, retina scale, waits, custom CSS or JavaScript, clicks, hidden selectors, request blocking, headers, cookies, user agents, authorization, timezone, geolocation, transparent backgrounds, resizing, chosen cache TTLs, signed links, asynchronous webhooks, bulk capture of up to 100 URLs per call, a usage API, and an OpenAPI specification. Its parameter names are compatible with those used by other screenshot APIs, which can simplify migration.
The Free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 screenshots; every feature is on every plan, and yearly billing gives two months free. Sign up free for ScreenshotNeo to start without a card.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →FAQ
Can I capture a screenshot without Use Application/Browser?
Yes. Modern can run outside the card; with no target it captures the desktop. Classic can capture the full screen when no selector is supplied.
Best Value
Which activity should a new cross-platform project use?
Use Modern Take Screenshot, because UiPath lists it for cross-platform projects. Confirm the output and targeting options exposed by your installed package.
Can a screenshot be kept only in memory?
Yes. Use the Classic Screenshot result with an Image variable or choose Modern Image output where that option is available.
Frequently Asked Questions
Does Take Screenshot capture a browser page as a PDF?
No. The UiPath activity captures an image. Use a separate PDF-generation approach when a document rather than an image is required.
Why is my selector valid but the screenshot still misses the control?
A selector can resolve before the control is visible or fully rendered. Add an appropriate visibility or readiness condition, then verify the application scope and target bounds.
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.
