Unity produces log files for the Unity Editor, Package Manager, licensing, development Players, and Hub. You can use these log files to understand where any problems happened in your application.
Unity adds all messages, warnings, and errors from the Console windowA Unity Editor window that shows errors, warnings and other messages generated by Unity, or your own scripts. More info
See in Glossary to the log files. To add your own messages to the Console window, and the logs, use the Debug class.
You can use the Application.consoleLogPath property in your project code to obtain the log location for the currently running Editor or Player application.
Note: Not all platforms support this feature. For more information, refer to Platform development.
The location of the Editor’s own Editor.log file depends on whether Use Global Editor Log is enabled in the Preferences window:
-useGlobalLog is supplied, then the Editor writes to a single global log on your system. This global log is shared between all Unity projects and all Editor instances on the system. For the default global Editor log location on each platform, refer to the tables for Linux, macOS, and Windows.ProjectName/Logs/Editor.log.Tip: A global log file can get confusing and hard to debug if multiple projects or Editor instances write to the same file. Project-specific logs provide greater clarity and easier debugging, especially if you regularly switch between projects.
Each operating system has its own default locations for the global log and for the location of projects created with the Unity Hub. You can change the location in which the Unity Hub creates new projects in the Projects section of the Hub settings. You can also use the -logFile command-line argument to specify a location for logs. For more information, refer to Unity Editor command-line arguments.
To access the Editor log file directly from the Editor, open the Console Window (main menu: Window > General > Console) and select Open Editor Log from the More (⋮) menu.
| Log type | Log location |
|---|---|
| Editor |
Global Editor log: ~/.config/unity3d/Editor.log
|
| Package Manager | ~/.config/unity3d/upm.log |
| Licensing client | ~/.config/unity3d/Unity/Unity.Licensing.Client.log |
| Licensing audits | ~/.config/unity3d/Unity/Unity.Entitlements.Audit.log |
On macOS, you can also access Unity’s logs via the Console.app utility
| Log type | Log location |
|---|---|
| Editor |
Global Editor log: ~/Library/Logs/Unity/Editor.log
|
| Package manager | ~/Library/Logs/Unity/upm.log |
| Licensing client | ~/Library/Logs/Unity/Unity.Licensing.Client.log |
| Licensing audits | ~/Library/Logs/Unity/Unity.Entitlements.Audit.log |
On Windows, the Package Manager and global Editor logs are placed in folders which aren’t shown in the Windows Explorer by default. To view the AppData folder, you must enable the Hidden Items setting on Windows. For more information on how to do this, refer to View hidden files and folders in Windows in the Microsoft documentation.
On Windows, a standard out stream doesn’t exist by default, so you must launch the Editor with a valid configured stdout stream, as a child process from a CI system. If you specify - to send output` tostdout`, then you won’t see the output in the console window.
| Log type | Log location |
|---|---|
| Editor |
Global Editor log: %LOCALAPPDATA%\Unity\Editor\Editor.log
|
| Package manager | User account: %LOCALAPPDATA%\Unity\Editor\upm.log SYSTEM account: %ALLUSERSPROFILE%\Unity\Editor\upm.log
|
| Licensing client | %LOCALAPPDATA%\Unity\Unity.Licensing.Client.log |
| Licensing audits | %LOCALAPPDATA%\Unity\Unity.Entitlements.Audit.log |
| Crash files |
%TMP%\Unity\Editor\Crashes Note: You can overwrite the location of the folder location with the -crash-report-folder command line argument. |
To view the Player log, open a Console Window (main menu: Window > General > Console) and select Open Player Log from the Console window menu. You can also navigate to the following folder:
| Operating system | Player logThe .log file created by a Standalone Player that contains a record of events, such as script execution times, the compiler version, and AssetImport time. Log files can help diagnose problems. More info See in Glossary location |
|---|---|
| Android | To access the Player log for an Android application, use Android logcat. For more information, see View Android logs. |
| iOS | Use the GDB console, or the Organizer Console through XCode to access iOS device logs. For more information on device logs, see Apple’s documentation. |
| Linux | ~/.config/unity3d/CompanyName/ProductName/Player.log |
| macOS |
~/Library/Logs/Company Name/Product Name/Player.logNote: You can also use the Console.app utility to find the log file. |
| Universal Windows Platform | %USERPROFILE%\AppData\Local\Packages\<productname>\TempState\UnityPlayer.log |
| Web | Unity writes the log output to your browser’s JavaScript console. |
| Windows | %USERPROFILE%\AppData\LocalLow\CompanyName\ProductName\Player.log |
For the location of Player crash files on Windows, refer to CrashReporting.crashReportFolder.
You can access the Hub logs by using your operating system’s file manager application. You can also access these logs from within the Hub. For more information, see Hub documentation.
| Operating system | Player log location |
|---|---|
| Linux | ~/.config/UnityHub/logs/info-log.json |
| macOS | ~/Library/Application\ Support/UnityHub/logs/info-log.json |
| Windows | %UserProfile%\AppData\Roaming\UnityHub\logs\info-log.json |