There might be times during development when you need to get information from the logs of the standalone player you’ve built, the target device, the Package Manager or the Editor. The log files are useful when you have experienced a problem, to find out exactly where the problem occurred.
All messages, warnings, and errors written to 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 in the Editor are also written to these log files. You can write your own messages to the Console and log files using the Debug class.
On macOS, you can access the Player, Package Manager, and Editor logs through the Console.app utility.
On Windows, the Package Manager and Editor logs are placed in folders which are not shown in the Windows Explorer by default. See below for more information on where to find the logs.
To view the Package Manager log, navigate to the Unity log folder:
Operating system | Log files |
---|---|
Linux | ~/.config/unity3d/upm.log |
macOS |
~/Library/Logs/Unity/upm.log You can also use the Console.app utility from your /Applications/Utilities folder to find the log file. |
Windows (user account) | %LOCALAPPDATA%\Unity\Editor\upm.log |
Windows (system user account) | %ALLUSERSPROFILE%\Unity\Editor\upm.log |
To view the Editor log, open a Console Window (menu: Window > General > Console) and select Open Editor Log from the Console window menu. You can also navigate to the following folder:
Operating system | Log files |
---|---|
Linux | ~/.config/unity3d/Editor.log |
macOS |
~/Library/Logs/Unity/Editor.log You can also use the Console.app utility from your /Applications/Utilities folder to find the log file. |
Windows | %LOCALAPPDATA%\Unity\Editor\Editor.log |
To view the Player log, open a Console Window (menu: Window > General > Console) and select Open Player Log from the Console window menu. You can also navigate to the following folder:
Operating system | Log files |
---|---|
Linux | ~/.config/unity3d/CompanyName/ProductName/Player.log |
macOS |
~/Library/Logs/Company Name/Product Name/Player.log You can also use the Console.app utility from your /Applications/Utilities folder to find the log file. |
Windows | %USERPROFILE%\AppData\LocalLow\CompanyName\ProductName\Player.log |
On Windows and Linux standalones, you can change the location of the log file, or stop Unity from logging to it. For more information, see the Command line arguments documentation.
Access the device log in XCode via the GDB console or the Organizer Console. The latter is useful for getting crashlogs when your application is not running through the XCode debugger.
See the documentation on Troubleshooting and Reporting crash bugs for information about debugging crashes and issues.
Use the logcat console to access your device log. To use it, launch the adb
application in the Android SDK/platform-tools directory with the logcat
parameter:
$ adb logcat
You can also get Android Logcat package via Package Manager, which provides UI(User Interface) Allows a user to interact with your application. Unity currently supports three UI systems. More info
See in Glossary
interface for getting logs from Android.
Device | Log files |
---|---|
Desktop | %USERPROFILE%\AppData\Local\Packages<productname>\TempState\UnityPlayer.log |
Windows Phone | You can retrieve your Windows Phone log with Windows Phone Power Tools. The Windows Phone IsoStoreSpy also provides a number of helpful debugging tools. |
For WebGLA JavaScript API that renders 2D and 3D graphics in a web browser. The Unity WebGL build option allows Unity to publish content as JavaScript programs which use HTML5 technologies and the WebGL rendering API to run Unity content in a web browser. More info
See in Glossary
, Unity writes the log output to your browser’s JavaScript console.
On Windows Vista and Windows 7, to make the AppData folder visible in Windows Explorer go to Tools > Folder Options > View (tab). The Tools menu is hidden by default. Press the Alt key once to display it.
On Windows 10, to make the AppData folder visible in Windows Explorer go to View > Show/hide and enable the Hidden items option.
On Windows, no standard out stream exists by default, so you must launch the Editor with a valid configured stdout
stream, like as a child process from a CI system. If you specify -
to send output to stdout
you won’t see the output in the console window.
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.