- 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
Chromium Automation support for browser automation in UI Automation, how it works, which browsers it supports, and what it requires.
Chromium Automation is a browser automation method that controls Chrome, Edge, and other Chromium-based browsers through the Chrome DevTools Protocol (CDP) — the same protocol the browser's built-in Developer Tools use. Common automation tasks such as opening the browser, navigating, clicking elements, typing text, and exploring the DOM are performed by sending CDP commands to the browser.
Unlike the Browser Extension method, Chromium Automation does not require the UiPath browser extension to be installed. Unlike the WebDriver protocol, it does not require a browser-specific driver binary (such as chromedriver or msedgedriver) to be downloaded and kept in sync with the browser version. UiPath launches and manages the browser session internally, so Chromium Automation works out of the box on any machine that has a supported browser installed.
How UiPath implements it
When a workflow uses Chromium Automation, UiPath starts the target browser with remote debugging enabled (the --remote-debugging-port=0 launch flag) and connects to it over CDP. All subsequent automation — element lookup, interaction, and DOM inspection — is carried out through that connection.
Chromium Automation introduces support for headless browser automation, where the browser runs without a visible window. It can also run with a visible browser window for development, debugging, and attended-style scenarios. Both are exposed as separate modes (see Configuration Steps).
Supported browsers
Chromium Automation supports Chromium-based browsers:
- Google Chrome
- Microsoft Edge
- Other Chromium-based browsers
Mozilla Firefox and Apple Safari are not supported by this method, because CDP is specific to Chromium. For those browsers, the Browser Extension and the WebDriver protocol are the available automation methods.
Requirements
- A supported Chromium-based browser installed on the machine.
- No UiPath browser extension.
- No WebDriver executable.
The browser must be able to start with the --remote-debugging-port=0 flag. This is blocked when the DeveloperToolsAvailability Group Policy is set to 2 (Disallow usage of the Developer Tools) — see Known Issues and Limitations.
Sessions and selectors
- New session per run — Chromium Automation opens a new, isolated browser session with its own
user-data-dir. It cannot attach to a browser instance already open on the user's desktop. Extensions, saved passwords, and session cookies from the default browser profile are not available in the session. - Incognito — private (Incognito) mode is supported without additional configuration.
- Selectors — selectors generated for Chromium Automation are compatible with those used by the other browser automation methods, so you can build and validate your automation the same way. Chromium Automation activities can execute inside and outside Use Application/Browser containers.
Because Chromium Automation always starts a fresh session and does not reuse the user's profile, it is best suited to unattended automation. The Browser Extension method is the recommended option for attended automation where you need to work with the user's already-open browser. See Browser Automation Mode for a full comparison of methods.