Hardware and software requirements

The following hardware and software specifications list the minimum and recommended resources for a single robot to execute jobs.

Important:

These requirements only consider the resources needed for the automation, and do not include the resources used by other applications involved in the automations.

Hardware requirements

Resource	Minimum	Recommended
CPU (*)	For Intel x64: 2 x 1.8GHz 64-bit For ARM64: Apple M1	For Intel x64: 4 x 2.4GHz 64-bit For ARM64: Apple M1
RAM (**)	4 GB	8 GB
Disk Space (***)	UiPathStudio.msi: 3.4 GB for new silent installations. 1 GB of additional space is required for UI-based installations. 3.4 - 3.8 GB for automatic updates (varies depending on the version you are updating from). 1 GB of additional space is required for UI-based updates. UiPathRobot.msi: 1.6 GB for new silent installations and updates. 1.9 GB for UI-based installations and updates.

(*) UiPath does not support the ARM architecture on Windows.

(**) Automations that use Document Understanding frameworks might need additional RAM.

(***) The disk space requirements do not include the space for the automation dependencies, such as packages and libraries.

Hardware requirements for High-Density Robots

For a High-Density setup, where multiple robots concurrently execute jobs on the same Windows Server machine, you must multiply the minimum and recommended hardware requirements with the number of runtimes set for the machine template in Orchestrator.

For example, with three users concurrently executing jobs, the minimum requirements are:

• For Intel x64, you need six cores of 1.8GHz 64-bit (two cores of 1.8GHz 64-bit per runtime), and a RAM of 12 GB (4 cores per runtime).

Hardware requirements for the live streaming and recording features

For scenarios where the live streaming and recording features are required, you must apply the recommended hardware requirements:

• CPU

  • For Intel x64: 4 x 2.4GHz 64-bit

  • For ARM64: Apple M1

• RAM

  • 8 GB

Software requirements

Resource	Supported versions	Details
Operating System	Windows 10 Windows 10 N
	Windows 11
	Microsoft Azure Windows 10 Enterprise Multi-Session	Works with Azure Virtual Desktops (AVD). 1 Supports Windows 365 machines.
	Microsoft Azure Windows 11 Enterprise Multi-Session	Supports Windows 365 machines.
	Windows Server 2016 Windows Server 2019 Windows Server 2022
	Windows Server Core 2016 Windows Server Core 2019 Windows Server Core 2022	Can only run background unattended jobs. By default, jobs run under the local system account. To use a specific user, set their credentials in Orchestrator. Then, on the robot machine, set the UIPATH_HEADLESS_WITH_USER environment variable to True.
	MacOS version 10.15 (Catalina) or greater.	Required by the Assistant for Mac.
Citrix environments	XenApp v6.5 or greater
	XenDesktop v7.0 or greater
.NET Framework	Version 4.6.1 or greater	To run Studio in any of the available languages, install the matching language pack version for your .NET framework, and remove conflicting .Net versions.
Web Browsers (for browser automation)	Microsoft Edge 78 or greater with Internet Explorer (IE) mode	Internet Explorer as a desktop application is out of support starting June 15 2022, Internet Explorer 11 being the last major version. We continue to provide the support for Microsoft Edge with Internet Explorer (IE) mode, which offers built-in legacy browser support for sites requiring Internet Explorer. Automated with the extension for Microsoft Edge.
	Google Chrome version 64 or greater	Automated with the extension for Chrome or the Webdriver protocol.
	Mozilla Firefox version 52.0 or greater	Automated with the extension for Firefox or the Webdriver protocol.
	Microsoft Edge on Windows 10 version 1803 or greater	Automated with the extension for Microsoft Edge.
Web browsers (for interactive sign in)
Microsoft Office (for projects created with StudioX)	Office 2013
	Office 2016
	Office 2019
	Office 2021
	Office 365
IP	IPv4
	IPv6	Assistant can be installed on IPv6-compatible operating systems.

Important:

We advise keeping Azure Virtual Desktop (AVD) sessions active when running unattended automations on Virtual Machines. Disconnected AVD sessions can prevent the creation of new robot sessions, resulting in job timeouts.