Hardware and Software Requirements

Note: The requirements documented on this page apply to Studio and StudioX.

Hardware Requirements

	Minimum	Recommended
CPU Cores (*)	2 x 1.8 GHz 32-bit (x86)	4 x 2.4 GHz 64-bit (x64)
RAM	8 GB of available system memory	12 GB
Disk Space	3.5 GB for new installations, 5 GB for upgrades (including temporary files required during installation)	N/A

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

Important: Resolutions below 1024x768 are not supported. Running Studio on such displays causes the Studio Backstage view to be displayed incorrectly.

Software Requirements

Supported Versions	Particularities
Operating System	Windows 8.1 Windows 8.1 N	Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022: x86 version for a 32-bit OS (required for SVN and GIT source control) x64 version for a 64-bit OS (required for GIT source control)
	Windows 10 Windows 10 N	Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022: x86 version for a 32-bit OS (required for SVN and GIT source control) x64 version for a 64-bit OS (required for GIT source control)
	Windows 11	Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022, x64 version (required for GIT source control)
	Microsoft Azure Windows 10 Enterprise Multi-Session	Works in conjunction with Azure Virtual Desktop (AVD) as well.1 Supports Windows 365 machines.
	Windows Server 2012 R2	Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022, x64 version (required for GIT source control) 2
	Windows Server 2016	Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022, x64 version (required for GIT source control) 2
	Windows Server 2019	Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022, x64 version (required for GIT source control) 2
	Windows Server 2022	Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022, x64 version (required for GIT source control) 2
Citrix environments	XenApp v6.5 or greater
	XenDesktop v7.0 or greater
.NET Framework	Version 4.6.1 or greater	.NET Framework is required for running Windows - Legacy projects and must be installed on machines. If your machine runs a Windows OS in a language other than English, install the corresponding language pack for the .NET Framework version you are using. This is required for running Studio in any of the available languages. The .NET Framework and related language pack version must correspond, and any conflicting .NET Framework versions installed on the machine should be removed. .NET (formerly .NET Core) is a newer framework required for running Windows and cross-platform projects. The appropriate .NET version (Desktop Runtime) is automatically added in the installation folder when installing or upgrading Studio.
Web Browsers (for browser automation)	Internet Explorer v8.0 or greater
	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 or the Webdriver protocol.
	Microsoft Edge in IE mode (Internet Explorer v8.0 or greater) on Windows 10 version 1803 or greater	Automated with the .
Microsoft Office (for projects created in the StudioX profile)	Office: 2013
	Office: 2016
	Office: 2019
	Office 365
File System	NTFS
IP	IPv4, IPv6	Studio can be installed on IPv6-compatible operating systems.

Important:

• Various display issues may occur in Studio if the Nahimic Service software in installed on your machine. This component is also included in other third-party applications such as Asus ROG Xonar Phoebus Sonic Studio and Asus Sonic Studio. We recommend disabling the Nahimic service in Windows or renaming the file NahimicOSD.dll.
• 1 - When using unattended robots on Virtual Machines, do not leave the Azure Virtual Desktop sessions in disconnected state (user is connected to a host pool in an AVD environment, but they are still connected to the session hosts). The robot is not able to use the disconnected session as it was created via AVD and does not have access to it. Because of this, it attempts to create a new session to run the unattended job, but fails because the AVD session is already created and in disconnected state. When this scenario happens, the job eventually fails due to a time out.

2 - This component is installed by default with the operating system and should be reinstalled if removed.