Documentation

Unity Hub

Command line interface overview

Compare the Unity command line interface and Hub command line interface and choose the interface that fits your workflow.
Read time 2 minutesLast updated 5 days ago

Install and manage Unity Editors and modules from a command line interface (CLI) in one of the following ways:
  • Unity CLI: The standalone
    unity
    binary. Install, update, and run it without the Unity Hub desktop application. Use it for new scripts, automation, and CI pipelines.
  • Hub CLI: The headless mode of Unity Hub 3. Unity Hub 4.0 and later don't run Hub CLI commands. Use the Unity CLI instead. For the equivalent commands, refer to Hub CLI.
Note
The Unity CLI is experimental. The CLI might not include every feature available in the Hub UI. The Hub CLI is deprecated from version 3.18.0 of the Unity Hub, and Unity Hub 4.0 removes it.

Unity CLI updates from the Hub

The Unity Hub includes a copy of the Unity CLI. When you start the Hub, it installs that copy if the Unity CLI isn't installed yet, and updates your Unity CLI when the Hub includes a newer version. To check or update the Unity CLI from the Hub, select Tools > Unity CLI in the Hub toolbar.
If you installed the Unity CLI with a package manager, such as Homebrew, apt, or rpm, the Hub doesn't install or update it. Use your package manager to update the Unity CLI instead.
Important
The Hub has no setting to turn off these Unity CLI updates. To use a specific version of the Unity CLI, refer to Install a specific Unity CLI version. For other ways to update the CLI, refer to Update the Unity CLI.

Command reference

For command syntax, flags, and module IDs, refer to Unity CLI reference. If you still use Unity Hub 3, refer to Hub CLI reference.