WindowsmacOSLinux

Where Are Unity Editor Logs Stored?

Unity Editor.log location on Windows, macOS and Linux, the first file to check when the editor crashes or a build fails.

Last updated

When Unity misbehaves, Editor.log is the starting point. It records imports, compile errors, license checks and crash traces for the current session.

The path follows each OS convention rather than the project folder. Player logs are separate and live next to built games, so do not confuse the two.

Where Unity stores this, by platform

Windows
%LOCALAPPDATA%\Unity\Editor\Editor.log

Open with any text editor. The previous session is preserved as Editor-prev.log in the same folder.

macOS
~/Library/Logs/Unity/Editor.log

Access via Console.app or Go to Folder in Finder. Previous session kept as Editor-prev.log alongside.

Linux
~/.config/unity3d/Editor.log

Same naming, previous session in Editor-prev.log. Player logs for built games live with the game data instead.

Frequently asked questions

How do I use Editor.log to debug a crash?

Reproduce the problem, then open Editor.log immediately. The tail of the log holds the stack trace or failing asset import. Attach it when filing bug reports.

Where is the log from my last session?

The previous log is renamed to Editor-prev.log in the same folder on the next launch. Check there if the crash wiped the current log.

Notice an outdated path? Let us know.