Unity uses an installer, but not the Windows MSI format you might expect

Unity does not use MSI (Microsoft Installer) files on Windows. Instead, Unity uses its own custom installer executable that handles the installation process. When you download Unity from the official website, you get a .exe file on Windows that runs Unity's proprietary setup, not a standard MSI package. This matters because it means you cannot deploy Unity through Group Policy or other Windows enterprise tools that rely on MSI files.

On Mac, Unity uses a .dmg (disk image) file that you mount and drag into your Applications folder — a completely different installation method. The installer approach varies by operating system, but in neither case does Unity rely on MSI technology.

Key Takeaways

  • Unity's Windows installer is a custom .exe file, not an MSI, so enterprise deployment tools that require MSI files will not work with it.
  • You can install multiple versions of Unity on the same machine, and each version installs to its own folder without conflicts.
  • The Unity Hub is a separate application that manages your Unity installations and projects, and you install it independently from the engine itself.
  • If you need to install Unity on many machines in a workplace, you will need to run the installer on each one or use third-party deployment software that can execute the .exe file.

What the Unity installer actually does on Windows

When you run the Unity .exe installer on Windows, it unpacks files to a location you choose — typically C:\Program Files\Unity\Hub\Editor\[version number] if you are using Unity Hub, or a custom path if you run the installer directly. The installer creates shortcuts, registers file associations so .unity files open in the editor, and sets up the necessary system paths.

Unlike an MSI file, the Unity installer does not register itself in the Windows Add/Remove Programs list in a way that allows remote uninstallation or Group Policy management. You can uninstall Unity by running the installer again and selecting the uninstall option, or by deleting the folder manually and removing shortcuts. This is one reason why studios with many machines often use the Unity Hub instead — it centralizes version management across a team.

Why Unity does not use MSI format

MSI files are designed for enterprise software deployment, and they follow strict Windows standards that limit how software can be packaged and installed. Unity's custom installer gives the company more control over the installation process, including the ability to download and install components on demand, verify file integrity, and handle the complexity of multiple editor versions on one machine.

If your workplace requires MSI-based deployment, you have a few options. Some teams use third-party tools like Advanced Installer or InstallShield to wrap the Unity .exe into an MSI package, though this adds complexity and may break with future Unity updates. Others simply run the installer manually on each machine or use a script that executes the .exe file with specific parameters. The simplest approach for most small teams is to use Unity Hub, which handles version management without requiring enterprise deployment infrastructure.

Installing Unity through Unity Hub instead

Unity Hub is a separate application that sits between you and the actual Unity editor. You install Hub once, then use it to download and manage multiple versions of the editor. Hub itself installs as a standard .exe, but once it is running, you can add editor versions through the Hub interface without touching installers again.

This approach is cleaner if you work with multiple Unity versions or collaborate with others. Hub keeps track of which projects use which editor version, and it can warn you if you open a project in the wrong version. For a team, you can install Hub on each machine and have everyone download the same editor version through the interface, which ensures consistency without needing to manage installer files.

Installing specific Unity versions and components

The Unity installer lets you choose which components to install during setup. The core editor is always installed, but you can add or skip platform support (Android, iOS, WebGL), development tools, and documentation. If you are building for a specific platform, you need the corresponding module — for example, the Android module if you plan to build for Android devices.

You can also install multiple versions of Unity on the same machine without them interfering with each other. Each version installs to its own folder, and the Hub keeps track of all of them. This is useful when you have older projects that need an older editor version and newer projects that use the latest release. Just run the installer again, choose a different installation path or let Hub manage it, and both versions coexist peacefully.

Uninstalling Unity and cleaning up

To remove Unity from Windows, open the installer .exe again and select the uninstall option. This removes the editor files and shortcuts. If you installed through Hub, you can also remove versions directly from the Hub interface by clicking the three-dot menu next to the version and selecting remove.

Uninstalling does not remove your projects or any files you created in the editor — those stay in their original locations. If you want to clean up completely, you may also want to remove the AppData\Local\Unity folder, which contains cache files and editor preferences. On Mac, drag the Unity application to the Trash and empty it, then remove ~/Library/Unity if you want to clear preferences and cache.

Troubleshooting installation problems

If the installer hangs or fails, the most common cause is insufficient disk space or a corrupted download. Delete the installer file, download it again from the official Unity website, and make sure you have at least 10 GB free on the drive where you are installing. Run the installer as Administrator on Windows — right-click it and select "Run as administrator" — because some system paths require elevated permissions.

If you see an error about missing dependencies or .NET Framework, Windows may need updates. Run Windows Update and restart your machine, then try the installer again. On Mac, make sure you have enough space and that your system meets the minimum macOS version for the Unity version you are installing — older Macs cannot run recent Unity releases. Check the official system requirements page for your specific editor version.

Frequently Asked Questions

Can I install Unity on a network drive or shared folder?

You can, but it is not recommended. Network drives are slower, and the editor may behave unpredictably if the connection drops. Install Unity locally on each machine instead. You can store your projects on a network drive and open them from there, but the editor itself should be local.

Do I need to uninstall an old version before installing a new one?

No. You can install multiple versions side by side without uninstalling the old one. Each version installs to its own folder. If you use Hub, it manages all versions for you and you never need to uninstall manually.

What happens if I move the Unity folder after installation?

The editor may not work correctly because shortcuts and file associations point to the original location. Reinstall instead of moving the folder. If you use Hub, it handles all paths automatically and you do not need to worry about this.

Can I install Unity on a Mac without using the .dmg file?

The .dmg is the standard installation method for Mac. You can also use Hub on Mac, which downloads and manages editor versions the same way it does on Windows. Both approaches work; Hub is simpler if you manage multiple versions.

Does Unity installation require internet after the download is complete?

The installer itself does not require internet once you have the .exe or .dmg file. However, the first time you launch the editor, it may download additional components or verify your license online. Make sure you have internet available for that initial launch.