If you want to automate the deployment of Unity in an organization, you can install the Unity Editor and other components from the command line. The components are normal installer executable programs and packages which you can use to automate the deployment of Unity.
To automate the Unity deployment through the command line:
install.bat on Windows or install.sh on Linux or macOS) to install all downloaded items.The following procedures use the individual installer files option for installing Unity on Windows and macOS. For information about using the Download Assistant option, refer to Install Unity on offline computers.
Use the following command line arguments to install the Editor and other components on Windows.
| Command line argument | Description |
|---|---|
| /S | Performs an installation which runs silently without any user interaction. |
| /D=PATH | Sets the default installation directory. Use with the silent installation option. The default folder is C:\Program Files (x86)\Unity (32-bit) or C:\Program Files\Unity(64-bit). |
Note: Installer command line arguments are case-sensitive.
To install the Editor to a specific folder location, follow this example. This example demonstrates installing a 64-bit Editor to the E:\Development\Unity folder:
UnitySetup64.exe /S /D=E:\Development\Unity
Running this command installs Unity silently to E:\Development\Unity folder, which becomes the root of the Unity installation. In this case, the command installs the Editor program file to E:\Development\Unity\Editor\Unity.exe.
Note: Specify the default installation directory path as the last argument on the command line. Don’t enclose the provided path in quotes, even if it contains spaces.
To perform a silent uninstall, run Uninstall.exe /S from the command line or a script.
Note: Although the process finishes right away, there’s a delay before the files are actually removed. This is because the process copies the uninstaller to a temporary location so it can remove itself. Make sure that the working directory isn’t located within the folder where you installed Unity. If it is, the uninstaller is unable to remove the folder.
To install other Unity components such as those that provide platform build support, use the following command as an example:
UnitySetup-Android-Support-for-Editor-6000.0.24f1.exe /S /D=C:\Program Files\Unity 6000.0.24f1
Note: You can optionally specify the folder path in the command when installing other components. In this case, make sure you specify the installation folder path to the Unity root folder that contains the Editor folder and not the folder that contains Unity.exe.
Unity provides the individual installers as .pkg files. You can install these by using the installer command.
To install the Editor to the /Applications/Unity folder on the specified target volume, use the following command as an example:
sudo installer [-dumplog] -package Unity.pkg -target /
To install other Unity components such as those that provide platform build support, use the following command as an example:
`
sudo installer [-dumplog] -package UnitySetup-Android-Support-for-Editor-6000.0.24f1.pkg -target /
You can install multiple versions of Unity on the same computer.
On macOS, the installer creates a folder called Unity, and overwrites any existing folder with this name. To install more than one version of Unity on macOS, rename the existing Unity folder before installing another version.
On Windows, the installation folder is always named Unity X.Y.Z[fp]W, where the f marks an official release, and p marks a patch release.
Note: If you rename a Unity folder, the recommended best practice is to name the new folder logically. For example, add the Unity version number at the end of the name. In this case, any existing shortcuts, aliases, and links to the offline documentation no longer work if they still point to the old Unity version. If your browser bookmarks to the offline documentation no longer work, check if the URL points to the correct folder name.