Submit a license request from the command line to manually activate your license if you’re unable to use the other activation methods.
The default installation paths for the Unity Editor are:
/Applications/Unity/Hub/Editor/<version>/Unity.app
/Applications/Unity/Hub/Editor/<version>/Unity.app
To manually activate your Unity license, follow these steps:
.alf
) from the command line..alf
file to generate a Unity license file (.ulf
) from Unity..ulf
file to activate your license from the command line.You must run this command from the computer where you installed Unity, but the computer doesn’t need internet access for this step to work.
Make sure you know the installation location of your Unity Editor (ending with Unity.app
), described earlier. For this procedure, you’ll add /Contents/MacOS/Unity
to this path.
Note: Although you don’t need Finder for this step, this latter subdirectory structure isn’t visible in Finder, unless you right-click the Unity application (Unity.app
) and select Show Package Contents.
For example, for a 2022.2.0b4
Editor, the complete path to the Unity
command is:
/Applications/Unity/Hub/Editor/2022.2.0b4/Unity.app/Contents/MacOS/Unity
Open a Terminal session and make sure you’re aware which directory you’re in. The directory you run the command from is the same directory where the .alf
file is output. You can use the pwd
command to determine your directory.
Run the following command, replacing <editor-command-location>
with the complete path to the Unity
command from Step 1:
<editor-command-location> -batchmode -createManualActivationFile -logfile
Note: This command doesn’t return output to the Terminal window. When the command completes, it returns control to the command prompt.
When the command completes, check the directory where you ran the command to make sure it created an activation license file, such as Unity_v2022.2.0b4.alf
. If you experience issues, see Troubleshooting.
Now you are ready to generate a Unity license file.
Assuming you installed a 2022.2.0b4
Editor at /Applications/Unity/Hub/Editor/2022.2.0b4/Unity.app
, the command for this step is:
/Applications/Unity/Hub/Editor/2022.2.0b4/Unity.app/Contents/MacOS/Unity -batchmode -createManualActivationFile -logfile
The next step is to use the license activation file (.alf
) that you just created to request a Unity license file (.ulf
).
Important: You can generate a Unity license file from any computer; it doesn’t necessarily need to be the same computer where you installed Unity. However, the computer you use in this step must have an internet connection.
Go to id.unity.com and make sure you’re signed in to your Unity ID. You need a valid login to request a Unity license file.
Use the same browser session to go to license.unity3d.com/manual. The Manual activation page appears.
Note: If you experience issues accessing this page, try pasting https://license.unity3d.com/manual
into your browser’s address bar.
Select the Browse button and use your computer’s file browser to select the license activation (.alf
) file from the create a license request file step.
If the upload was successful and Unity detected that the file you chose was a license activation file, the filename appears in the text box with a green check mark. If you see a red X instead, try again.
Select the Next button. The Activate your license page appears.
Select which license type you are activating:
PS/SC/E3-XXXX-XXXX-XXXX-XXXX
.Select the Next button. The Download license file page appears.
Select the Download license file button. If prompted, allow downloads for the license.unity3d.com/manual page.
Open your browser’s downloads location and confirm the new Unity license file, which has a .ulf
extension. For example, Unity_v2017.x.ulf
.
Now you are ready to activate your Unity license from the command line.
You must run this command from the computer where you installed Unity, but the computer doesn’t need internet access for this step to work.
Make sure you know the following paths:
<editor-command-location>
is the same value as the path described in the create a license request file step.<yourUlfFile>
is the full path of the .ulf
file you generated in the generate a Unity license file step.Open a Terminal session and run the following command, replacing <editor-command-location>
and <yourUlfFile>
with the actual full paths:
<editor-command-location> -batchmode -manualLicenseFile <yourUlfFile> -logfile
Note: This command doesn’t return output to the Terminal window. When the command completes, it returns control to the command prompt.
When the command completes, you can view your active license in the Hub by opening the Preferences menu () and selecting Licenses. If you experience issues, see Troubleshooting.
This example assumes that you:
2022.2.0b4
Editor at /Applications/Unity/Hub/Editor/2022.2.0b4/Unity.app
.ulf
file and stored it at /Users/myAccount/Downloads/Unity_v2017.x.ulf
/Applications/Unity/Hub/Editor/2022.2.0b4/Unity.app/Contents/MacOS/Unity -batchmode -manualLicenseFile /Users/myAccount/Downloads/Unity_v2017.x.ulf -logfile
If the command line operations don’t yield the expected results, view the Editor.log
file. Check the location of this file in Log Files.
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising. Some 3rd party video providers do not allow video views without targeting cookies. If you are experiencing difficulty viewing a video, you will need to set your cookie preferences for targeting to yes if you wish to view videos from these providers. Unity does not control this.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.