Log files reference
Locate Unity's log files which record messages, warnings, and errors that can help you understand the source of problems in your application.
Read time 4 minutesLast updated 6 days ago
Unity produces log files for the 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 window to the log files. To add your own messages to the Console window, and the logs, use the Debug class.
Each operating system stores the log files in different locations. The default locations are outlined on this page, but you can also use certain command line arguments to control when and where Unity generates log files. For more information, see the Command line arguments documentation.
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.
Editor-related log locations
You can access the Editor logs from the console window. To do this, open a Console Window (main menu: Window > General > Console) and select Open Editor Log from the Console window menu.
You can access the other logs by using your operating system’s file manager application.
Linux
Log type | Log location |
|---|---|
| Editor | |
| Package manager | |
| Licensing client | |
| Licensing audits | |
macOS
On macOS, you can also access Unity’s logs via the Console.app utility
Log type | Log location |
|---|---|
| Editor | |
| Package manager | |
| Licensing client | |
| Licensing audits | |
Windows
On Windows, the Package Manager and 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, see Microsoft’s documentation on View hidden files and folders in Windows.
On Windows, a standard out stream doesn’t exist by default, so you must launch the Editor with a valid configured stream, as a child process from a CI system. If you specify to send outputto , then you won’t see the output in the console window.
stdout- stdoutLog type | Log location |
|---|---|
| Editor | |
| Package manager | User account: SYSTEM account: |
| Licensing client | |
| Licensing audits | |
| Crash files | Note: You can overwrite the location of the folder location with the |
Player-related log locations
To view the Player log, open a Console Window (main menu: Window > General > Console) and select Open Player Log from the Console window More (⋮) menu. You can also navigate to the following folder:
Operating system | Player log 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 | |
| macOS | Note: You can also use the Console.app utility to find the log file. |
| Universal Windows Platform | |
| Web | Unity writes the log output to your browser’s JavaScript console. |
| Windows | |
Player crash files (Windows only)
For the location of Player crash files on Windows, refer to .
CrashReporting.crashReportFolderUnity Hub log locations
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 | |
| macOS | |
| Windows | |