- Overview
- UI Automation
- About the UI Automation activity package
- Applications and technologies automated with UI Automation
- Project compatibility
- UI-ANA-016 - Pull Open Browser URL
- UI-ANA-017 - ContinueOnError True
- UI-ANA-018 - List OCR/Image Activities
- UI-DBP-006 - Container Usage
- UI-DBP-013 - Excel Automation Misuse
- UI-DBP-030 - Forbidden Variables Usage In Selectors
- UI-DBP-031 - Activity verification
- UI-PRR-001 - Simulate Click
- UI-PRR-002 - Simulate Type
- UI-PRR-003 - Open Application Misuse
- UI-PRR-004 - Hardcoded Delays
- UI-REL-001 - Large Idx in Selectors
- UI-SEC-004 - Selector Email Data
- UI-SEC-010 - App/Url Restrictions
- UI-USG-011 - Non Allowed Attributes
- UX-SEC-010 - App/Url Restrictions
- UX-DBP-029 - Insecure Password Use
- UI-PST-001 - Audit Log Level in Project Settings
- UiPath Browser Migration Tool
- Clipping region
- Computer Vision Recorder
- Activities index
- Activate
- Anchor Base
- Attach Browser
- Attach Window
- Block User Input
- Callout
- Check
- Click
- Click Image
- Click Image Trigger
- Click OCR Text
- Click Text
- Click Trigger
- Close Application
- Close Tab
- Close Window
- Context Aware Anchor
- Copy Selected Text
- Element Attribute Change Trigger
- Element Exists
- Element Scope
- Element State Change Trigger
- Export UI Tree
- Extract Structured Data
- Find Children
- Find Element
- Find Image
- Find Image Matches
- Find OCR Text Position
- Find Relative Element
- Find Text Position
- Get Active Window
- Get Ancestor
- Get Attribute
- Get Event Info
- Get From Clipboard
- Get Full Text
- Get OCR Text
- Get Password
- Get Position
- Get Source Element
- Get Text
- Get Visible Text
- Go Back
- Go Forward
- Go Home
- Google Cloud Vision OCR
- Hide Window
- Highlight
- Hotkey Trigger
- Hover
- Hover Image
- Hover OCR Text
- Hover Text
- Image Exists
- Indicate On Screen
- Inject .NET Code
- Inject Js Script
- Invoke ActiveX Method
- Key Press Trigger
- Load Image
- Maximize Window
- Microsoft Azure Computer Vision OCR
- Microsoft OCR
- Microsoft Project Oxford Online OCR
- Minimize Window
- Monitor Events
- Mouse Trigger
- Move Window
- Navigate To
- OCR Text Exists
- On Element Appear
- On Element Vanish
- On Image Appear
- On Image Vanish
- Open Application
- Open Browser
- Refresh Browser
- Replay User Event
- Restore Window
- Save Image
- Select Item
- Select Multiple Items
- Send Hotkey
- Set Clipping Region
- Set Focus
- Set Text
- Set To Clipboard
- Set Web Attribute
- Show Window
- Start Process
- System Trigger
- Take Screenshot
- Tesseract OCR
- Text Exists
- Tooltip
- Type Into
- Type Secure Text
- Use Foreground
- Wait Attribute
- Wait Element Vanish
- Wait Image Vanish
- Accessibility Check
- Application Event Trigger
- Block User Input
- Check/Uncheck
- Check App State
- Check Element
- Click
- Click Event Trigger
- Drag and Drop
- Element Scope
- Extract Table Data
- Find Elements
- For Each UI Element
- Get Browser Data
- Get Clipboard
- Get Text
- Get URL
- Go to URL
- Highlight
- Hover
- Inject Js Script
- Keyboard Shortcuts
- Keypress Event Trigger
- Mouse Scroll
- Navigate Browser
- Save Image
- Select Item
- Set Browser Data
- Set Clipboard
- Set CV Server
- Set Runtime Browser
- Set Focus
- Set Project Setting
- Set Text
- Take Screenshot
- Type Into
- Unblock User Input
- Window Operation
- Perform browser search and retrieve results using UI Automation APIs
- Web Browsing
- Find Images
- Click Images
- Trigger and Monitor Events
- Create and Override Files
- HTML Pages: Extract and Manipulate Information
- Window Manipulation
- Automated List Selection
- Find and Manipulate Window Elements
- Manage Text Automation
- Load and Process Images
- Manage Mouse Activated Actions
- Automate Application Runtime
- Automated Run of a Local Application
- Browser Navigation
- Web Automation
- Trigger Scope Example
- Enable UI Automation support in DevExpress
- Computer Vision Local Server
- Mobile Automation
- Release notes
- About the mobile device automation architecture
- Project compatibility
- Get Log Types
- Get Logs
- Get Page Source
- Get Device Orientation
- Get Session Identifier
- Install App
- Manage Current App
- Manage Other App
- Open DeepLink
- Open URL
- Mobile Device Connection
- Directional Swipe
- Draw Pattern
- Positional Swipe
- Press Hardware Button
- Set Device Orientation
- Take Screenshot
- Take Screenshot Part
- Element Exists
- Execute Command
- Get Attribute
- Get Selected Item
- Get Text
- Set Selected Item
- Set Text
- Swipe
- Tap
- Type Text
- Terminal
- Release notes
- About the Terminal activity package
- Project compatibility
- Best practices
- Find Text
- Get Color at Position
- Get Cursor Position
- Get Field
- Get Field at Position
- Get Screen Area
- Get Text
- Get Text at Position
- Move Cursor
- Move Cursor to Text
- Send Control Key
- Send Keys
- Send Keys Secure
- Set Field
- Set Field at Position
- Terminal Session
- Wait Field Text
- Wait Screen Ready
- Wait Screen Text
- Wait Text at Position
- Terminal coded automation APIs
UI Automation activities
Semantic selectors let you indicate UI elements based on their meaning, not only on traditional selector attributes. You describe the element you want to interact with, and UiPath uses AI to identify the best matching target.
Semantic selectors support two find methods:
- DOM (Document Object Model) — the default find method for web applications. It uses information extracted from the application DOM.
- Image — the default find method for non-web applications. It uses the visible screen image and the image grounding capabilities of modern multimodal models.
DOM mode
In DOM mode, UiPath searches the DOM to find the target element. This mode uses UiPath's DOM Extractor to collect structured information about the page, then sends that information to a large language model (LLM) to match UI elements based on their semantic description.
DOM mode is recommended when the target can be identified through information available in the DOM, such as:
- visible text;
- labels;
- roles;
- attributes;
- element hierarchy;
- structural relationships between elements.
DOM mode can reach any element available in the DOM, including elements that are off-screen. This makes it useful for web applications where the target element exists in the page structure even when it is not visible in the viewport.
DOM mode is less precise when the most important identifying characteristics are visual, such as a specific icon shape, color, style, or visual position. DOM mode is also not available for non-web applications.
The in-product tooltip summarizes DOM mode as: "Searches the DOM. Reaches any element, including off-screen. Less precise on visual details. Not available on non-web applications."
Image mode
In Image mode, Semantic selectors search the visible screen image instead of the DOM. Image mode can detect and reason over objects that are visible on the screen, including icons, colors, styles, layout, and visual relationships.
This mode uses the image grounding capabilities of the latest multimodal models. These models can understand not only that an element exists, but also where it appears on the screen and how it looks in relation to the surrounding UI.
Image mode is the better choice when the target is described more reliably by how it looks than by its structure, for example:
- an icon with a specific shape or color;
- a button that is visually distinct but poorly described in the DOM;
- a tile or card identified by its color, position, or style;
- a warning, status, or action icon;
- a control in a non-web application;
- a screen where DOM information is incomplete, noisy, or unavailable.
For example, Image mode can target "the green Sales Opportunities tile," "the blue icon next to the search field," or "the warning icon in the top-right corner."
Because Image mode works from the screen image, it is limited to what is visible. If an element is off-screen, hidden, or not visually rendered at targeting time, Image mode cannot identify it from the current screenshot.
For off-screen targets, a Mouse Scroll activity with the To element property, placed before the Semantic selector action, brings the element into view before the action executes.
The in-product tooltip summarizes Image mode as: "Searches the screen image. Detects any object on the screen, including icons, colors, and styles. Limited to what's visible."
Relationship with Computer Vision
Image mode is the natural evolution of UiPath's Computer Vision technology.
Computer Vision uses AI-based object detection to identify UI elements on the screen. It remains available in Unified Target and continues to be an important targeting method. Because Computer Vision is based on a dedicated object detector, it is more stable and deterministic in scenarios that require predictable visual element detection.
Image mode builds on the same direction — using visual understanding to interact with applications when traditional selectors are not enough — but introduces a more flexible approach. It uses modern multimodal models that reason over the full screen image and match elements based on natural language descriptions. The following table summarizes when to use each method:
| Method | Use it when |
|---|---|
| Computer Vision | You need stable, deterministic visual object detection. |
| Image mode | You want flexible semantic targeting based on visible visual attributes. |
| DOM mode | The element can be reliably identified from DOM information. |
Computer Vision remains part of Unified Target and is not replaced by the Image find method of Semantic selectors.
Model selection
Semantic selectors include a Model drop-down in Project Settings > UI Automation > Semantic Selector that lets you choose the underlying model used for semantic targeting for each available find method.
For DOM mode, two models are available:
| Model | Description |
|---|---|
| Gemini 2.5 Flash | A model for semantic understanding over DOM-extracted information. Suitable when the target can be described through the information available in the DOM. |
| PathMini | UiPath's fast and compact model, designed for strong performance while optimizing for speed and efficiency. PathMini supports both Computer Use capabilities and image grounding for Semantic selectors. |
For transparency, PathMini is based on a fine-tuned Qwen model.
For Image mode, Semantic selectors can use only PathMini, because it supports image grounding and can reason over the visible screen image.
Usage guidance
DOM mode is the default option for web applications when the target can be identified through text, labels, roles, attributes, or structure available in the DOM. DOM mode is also useful when the target exists in the DOM but is not visible on screen.
Image mode is the better option when the target is described by how it looks, when color, icon shape, style, visual position, or surrounding layout are more relevant than DOM attributes. Image mode is also useful for non-web applications, or when the DOM does not provide enough reliable information.
When using Image mode, the target must be visible on the screen at targeting time. For off-screen targets, a Mouse Scroll activity with the To element property, placed before the Semantic selector action, brings the element into view before the action executes.
Related content
For more information about Semantic selectors, refer to About Semantic selectors.