To use Unity, you need an activated license.
The primary license activation method for Unity Pro and Unity Personal is the Unity Hub. For information about activating a Unity Industry license, refer to the Unity Support article, How to activate or return a Unity Industry license.
The following information covers an alternate method to Unity Hub for activating and returning a license for Unity Pro, by using the command line. You might consider this method in situations such as:
Note: The following procedures don’t apply to Unity Personal. To activate and return a license for Unity Personal, log in and log out of Unity Hub, respectively. |
If you don’t know your Unity license information, speak to the Owner of your license. Owners can assign a seat to you via the Organization, or you can contact Unity Customer Service.
Before activating your Unity license by using the command line, make sure that the license file folder exists. Refer to Unity license file location in License troubleshooting. Also make sure that you have write permission to this folder.
Enter the following command into the Terminal to launch Unity and activate your license:
<unity-command-location> -quit -batchmode -serial SB-XXXX-XXXX-XXXX-XXXX-XXXX -username 'name@example.com' -password 'XXXXXXXXXXXXX'
Notes:
Replace <unity-command-location>
with the full path to your Unity Editor application, concatenated with /Contents/MacOS/Unity
. For example, if you installed a 2022.2.0b4
Editor to the default location, <unity-command-location>
is:
/Applications/Unity/Hub/Editor/2022.2.0b4/Unity.app/Contents/MacOS/Unity
If you want to activate a named user license without activating its serial key, use the same command, but omit your serial key after specifying the -serial
keyword:
... -serial -username 'name@example.com' -password 'XXXXXXXXXXXXX'
The following example activates a named user license without activating its serial key:
/Applications/Unity/Hub/Editor/2022.2.0b4/Unity.app/Contents/MacOS/Unity -quit -batchmode -serial -username 'name@example.com' -password 'XXXXXXXXXXXXX'
The following example activates a serial key. If your plan supports named user licensing, it activates that license and also activates its serial key.
/Applications/Unity/Hub/Editor/2022.2.0b4/Unity.app/Contents/MacOS/Unity -quit -batchmode -serial SB-XXXX-XXXX-XXXX-XXXX-XXXX -username 'name@example.com' -password 'XXXXXXXXXXXXX'
Enter the following command into the Command Prompt to launch Unity and activate your license:
"<editor-installation-location>" -quit -batchmode -serial E3-XXXX-XXXX-XXXX-XXXX-XXXX -username name@example.com -password XXXXXXXXXXXXX
Notes:
Replace <editor-installation-location>
with the full path to your Unity Editor application. For example, if you installed a 2022.2.0b4
Editor to the default location, <editor-installation-location>
is:
C:\Program Files\Unity\Hub\Editor\2022.2.0b4\Editor\Unity.exe
If you want to activate a named user license without activating its serial key, use the same command, but omit your serial key after specifying the -serial
keyword:
... -serial -username 'name@example.com' -password 'XXXXXXXXXXXXX'
The following example activates a named user license without activating its serial key:
"C:\Program Files\Unity\Hub\Editor\2022.2.0b4\Editor\Unity.exe" -quit -batchmode -serial -username name@example.com -password XXXXXXXXXXXXX
The following example activates a serial key. If your plan supports named user licensing, it activates that license and also activates its serial key.
"C:\Program Files\Unity\Hub\Editor\2022.2.0b4\Editor\Unity.exe" -quit -batchmode -serial E3-XXXX-XXXX-XXXX-XXXX-XXXX -username name@example.com -password XXXXXXXXXXXXX
Wait several seconds after running this command to give Unity enough time to communicate with the license server. If activation fails, you can open the Editor.log for information. For any activation errors, check Activation issues to find a solution for your issue.
Enter the following command into the Terminal to return the license:
<unity-command-location> -quit -batchmode -returnlicense -username 'name@example.com' -password 'XXXXXXXXXXXXX'
Replace <unity-command-location>
with the full path to your Unity Editor application, concatenated with /Contents/MacOS/Unity
. For example, if you installed a 2022.2.0b4
Editor to the default location, <unity-command-location>
is:
/Applications/Unity/Hub/Editor/2022.2.0b4/Unity.app/Contents/MacOS/Unity
/Applications/Unity/Hub/Editor/2022.2.0b4/Unity.app/Contents/MacOS/Unity -quit -batchmode -returnlicense -username 'name@example.com' -password 'XXXXXXXXXXXXX'
Enter the following into the Command Prompt to return the license
"<editor-installation-location>" -quit -batchmode -returnlicense -username name@example.com -password XXXXXXXXXXXXX
Replace <editor-installation-location>
with the full path to your Unity Editor application. For example, if you installed a 2022.2.0b4
Editor to the default location, <editor-installation-location>
is:
C:\Program Files\Unity\Hub\Editor\2022.2.0b4\Editor\Unity.exe
"C:\Program Files\Unity\Hub\Editor\2022.2.0b4\Editor\Unity.exe" -quit -batchmode -returnlicense -username name@example.com -password XXXXXXXXXXXXX
Wait a few seconds after running this command to give Unity enough time to communicate with the license server. You can use the Hub to confirm that you returned your license by opening the Preferences menu () and selecting Licenses. If you experience issues, refer Troubleshooting.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.
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.