UiPath Studio

The UiPath Studio Guide

Chrome Extension

This topic presents the most frequent reasons for which the UiPath Extension for Chrome might not work properly, and how to solve these issues.

Please note that browser automations with the extension for Chrome are currently possible on a single Chrome window.


You need to use at least Google Chrome version 64 to perform browser automations.

Checking if the Extension for Chrome is Installed and Enabled

  1. In Google Chrome, navigate to chrome://extensions/.
  2. If the extension is not present, install it as explained here.
  3. Make sure the extension is updated to the latest version.


Selecting the Developer mode check box at the top of the 'chrome://extensions/' page displays the Update button on the extension Details page.

Preventing Possible Issues

A. Enable access to files and incognito mode:

  1. In Google Chrome, navigate to chrome://extensions/.
  2. Select the UiPath extension.
  3. Make sure the Allow in incognito and Allow access to file URLs options are selected.

B. Check if the Chrome extension process is running:

  1. Open Task Manager.
  2. Check if the ChromeNativeMessaging.exe process is running.

C. Check the extension version and ID:

  1. Open the Registry Editor.
  2. Navigate to the HKEY_CURRENT_USER\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.uipath.chromenativemsg_v2 key.
  3. Check if the Default REG_SZ value is C:\Users\YOUR_USER_NAME\AppData\Local\UiPath\manifest.json.
  4. Open the manifest.json file with a text editor such as Notepad.
  5. Check if the path property leads to the ChromeNativeMessaging.exe file.
  6. Check if the allowed_origins field contains the correct extension ID (ex: chrome-extension://dkgencfabioofgdmhhjljpkbbchbikbh/).

ChromeNativeMessaging is Not Running

  1. In Google Chrome, navigate to chrome://extensions/.
  2. Remove the UiPath extension manually by clicking the Remove button.
  3. Reinstall it from UiPath Studio as explained here.

If the information above did not solve your issue, you can try getting additional information by viewing traces and analyzing the errors thrown by the UiPath extension. The following are types of traces you can collect and analyze.

Enabling Traces

General Extension Traces in Google Chrome

  1. In Google Chrome, go to chrome://extensions/.
  2. Select the Developer Mode checkbox at the top of the web page.
  3. Go to the UiPath extension and click background page. The Developer Tools page is displayed.
  4. Navigate to the Console tab. All the traces generated by the extension are displayed here.


Errors are marked in red.

Traces Generated by the Web Page you Want to Automate

  1. On the webpage you want to automate, go to Side Navigation Bar > More tools > Developer tools (or press Ctrl+Shift+I). The traces generated by the UiPath extension for the current page are displayed.


Errors are marked in red.

Full traces

  1. Open the Registry Editor.
  2. Navigate to the HKEY_CURRENT_USER\SOFTWARE\UiPath key.
  3. Double-click the WebExtensionTrace DWORD value. The Edit DWORD Value window is displayed.
  4. In the Value Data field, change the value to 1, and click OK. The value is saved.


If the WebExtensionTrace DWORD value does not exist, you have to create it, by right-clicking the right panel, selecting New > DWORD (32-bit) Value, and providing the values mentioned above.

If the extension for Chrome is still not working then remove the extension from chrome://extensions/ and reinstall it as explained here.

Updated 4 months ago

Chrome Extension

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.