Where is the crash log for each game engine?
It depends on the engine, not on the store. Unity, Godot 4 and Ren'Py write a log file on the player's machine by default. Unreal Engine writes logs and crash reports to its Saved folder. GameMaker, Defold, LÖVE and Bevy write no file unless you or the player ask for one. Web builds write to the browser console.
Replace the words in the paths with your own values. CompanyName and ProductName are the Unity Player settings. [project_name] is the Godot project name. [Project Name] is the Unreal project name. A cell that says "not documented" means the engine's documentation gives no path, so we give none.
| Engine | Windows | macOS | Linux | Steam Deck and Proton |
|---|---|---|---|---|
| Unity (Player.log) | %USERPROFILE%\AppData\LocalLow\CompanyName\ProductName\Player.log | ~/Library/Logs/Company Name/Product Name/Player.log | ~/.config/unity3d/CompanyName/ProductName/Player.log | Linux build: the Linux path. Windows build: the Windows path inside the Proton prefix. |
| Unreal Engine | Logs: the project's Saved/Logs folder. Crash reports on a player's machine: C:\Users\[Your Windows Username]\AppData\Local\[Project Name]\Saved\Crashes | Saved/Logs and Saved/Crashes in the project folder. A path on a player's Mac is not documented. | Saved/Logs and Saved/Crashes in the project folder. A path on a player's machine is not documented. | Windows build: the Windows path inside the Proton prefix. |
| Godot 4 (godot.log) | %APPDATA%\Godot\app_userdata\[project_name]\logs\godot.log | ~/Library/Application Support/Godot/app_userdata/[project_name]/logs/godot.log | ~/.local/share/godot/app_userdata/[project_name]/logs/godot.log | Linux build: the Linux path. Windows build: the Windows path inside the Proton prefix. |
| GameMaker | No file by default. Start the game with -output or -debugoutput and a file name. Minidumps with -minidump go to %localappdata%\<Game Name>. | Not documented. The command line parameters are for Windows only. | Not documented. The command line parameters are for Windows only. | Windows build: add the parameters as Steam launch options. |
| Defold | No path in the manual. Run the game from a terminal, or set Write Log File to get log.txt. | Run ./mygame.app/Contents/MacOS/mygame in a terminal. | Run the game from a terminal. | Same as Linux or Windows. |
| Ren'Py | log.txt and traceback.txt in the game's base directory, next to the launcher. | log.txt and traceback.txt in the game's base directory. | log.txt and traceback.txt in the game's base directory. | The same folder in the Steam library. |
| LÖVE (Love2D) | No log file. The error screen shows the traceback, and Ctrl+C copies it. | No log file. The error screen shows the traceback. | No log file. The traceback also prints to the terminal. | Same as Linux or Windows. |
| Bevy | No log file by default. Logs go to stdout. | No log file by default. Logs go to stdout. | No log file by default. Logs go to stdout. | Same as Linux or Windows. |
| Construct 3 | Browser console: F12. A WebView2 export also uses F12. | Safari: Command + Option + I. A WKWebView export uses the Develop menu in Safari. | Browser console: F12. A CEF export uses chrome://inspect. | Same as Linux or Windows. |
| Phaser and other web builds | Browser console: F12 in Chrome, Firefox and Edge. | Browser console: Command + Option + I in Safari. | Browser console: F12 in Chrome and Firefox. | Not applicable to a build in the browser. |
Sources: Unity manual, Log files reference; Unreal Engine documentation, Logging and Crash Reporting; Godot documentation, Logging and File paths; GameMaker manual, Command Line Parameters; Defold manual, game and system logs; Ren'Py documentation, config.basedir; LÖVE wiki, love.errorhandler; Bevy API documentation, LogPlugin; Construct tutorial, Checking for errors in browsers; Proton FAQ.
Where are the Unity Player.log, Editor.log and crash dumps?
A built Unity game writes Player.log in a folder named after your company and product. The Unity Editor writes Editor.log in the project's Logs folder by default, and has a global log as well. On Windows, a built game stores crash reports in %TMP%\CompanyName\ProductName\Crashes.
The crash folder is documented for Windows only. Unity assigns the folder at startup, and Windows.CrashReporting.crashReportFolder returns it, so your game can read the path before a crash occurs. The -logFile command line argument sends the log to a location that you choose.
Other platforms have no Player.log file path. On Android, read the log with Android logcat. On iOS, use the GDB console or the Organizer Console in Xcode. A WebGL build writes its log to the JavaScript console of the browser. A Universal Windows Platform build writes UnityPlayer.log to %USERPROFILE%\AppData\Local\Packages\<productname>\TempState.
| File | Windows | macOS | Linux |
|---|---|---|---|
| Player.log (built game) | %USERPROFILE%\AppData\LocalLow\CompanyName\ProductName\Player.log | ~/Library/Logs/Company Name/Product Name/Player.log | ~/.config/unity3d/CompanyName/ProductName/Player.log |
| Editor.log (project) | ProjectName\Logs\Editor.log | ProjectName/Logs/Editor.log | ProjectName/Logs/Editor.log |
| Editor.log (global) | %LOCALAPPDATA%\Unity\Editor\Editor.log | ~/Library/Logs/Unity/Editor.log | ~/.config/unity3d/Editor.log |
| Player crash reports | %TMP%\CompanyName\ProductName\Crashes | Not documented | Not documented |
| Editor crash files | %TMP%\Unity\Editor\Crashes | Not documented | Not documented |
Sources: Unity 6.6 manual, Log files reference; Unity 6.6 scripting reference, Windows.CrashReporting.crashReportFolder.
Where are Unreal Engine logs and crash reports?
Unreal Engine saves logs as .txt files in the project's Saved/Logs folder. Crash reports from the editor are in the project's Saved/Crashes folder. On a player's Windows machine, Epic gives this path for crash reports: C:\Users\[Your Windows Username]\AppData\Local\[Project Name]\Saved\Crashes.
Ask for the whole crash report folder, not only the log. Epic says a crash report contains a crash GUID, the error type and callstacks, system and build information, the log output, custom game data and user comments. Epic's pages give no crash report path for macOS or Linux, and no log path for a packaged game on a player's machine, so we give none.
The Crash Reporter Client is a separate program, and it is not included with packaged games by default. Turn on Include Crash Reporter under Project, Packaging, Advanced. Epic also says that, as of UE 5.4, it does not receive reports from packaged builds. You set DataRouterUrl in the [CrashReportClient] section of Config/DefaultEngine.ini, and point it at your own server or at a service. Epic names Backtrace, BugSplat and Sentry.
Sources: Unreal Engine 5.9 documentation, Logging in Unreal Engine and Crash Reporting in Unreal Engine.
Where does Godot 4 write its log, and how do I enable file logging?
On desktop platforms, Godot writes user://logs/godot.log by default, so there is nothing to enable. The setting is debug/file_logging/enable_file_logging in the Project Settings. Change the location with debug/file_logging/log_path. The user:// folder is in the table below.
Each session creates a new log file, and Godot renames the old file with the date. It keeps up to 5 log files by default; change that with debug/file_logging/max_log_files. Ask the player for the whole logs folder, because the crash can be in an older file.
When the project crashes, Godot writes the crash log to the same file and prints a crash backtrace to the standard error stream. The backtrace is only useful if the build contains debugging symbols.
For more detail, ask the player to start the game with the --verbose flag. Messages from print_verbose() are only visible in verbose mode. From Godot 4.5, you can also register your own Logger class with OS.add_logger() and send errors where you want.
| Operating system | Default | With use_custom_user_dir |
|---|---|---|
| Windows | %APPDATA%\Godot\app_userdata\[project_name]\logs\godot.log | %APPDATA%\[project_name]\logs\godot.log |
| macOS | ~/Library/Application Support/Godot/app_userdata/[project_name]/logs/godot.log | ~/Library/Application Support/[project_name]/logs/godot.log |
| Linux | ~/.local/share/godot/app_userdata/[project_name]/logs/godot.log | ~/.local/share/[project_name]/logs/godot.log |
Sources: Godot Engine 4.7 documentation, Logging and File paths in Godot projects.
Where does GameMaker write crash information?
Nowhere by default: the GameMaker manual documents no log file for a built game. You get a file with command line parameters, and the manual says these are available on the standard Windows target only.
For a text log, start the game with -output and a file name. It sends the console output to that file, with the debug messages from your code. -debugoutput does the same without your custom debug messages, and adds extra information from the runner for bug reports.
For a native crash, use -minidump. When a fatal exception occurs, the runner creates a basic minidump file with the call stack. -fullminidump writes a larger file. Without -minidumpdir, the files go to the game save area, which is %localappdata%\<Game Name> on Windows.
Sources: GameMaker manual, Command Line Parameters and The File System.
Where do Defold, Ren'Py, LÖVE and Bevy write errors?
Only Ren'Py writes a file by default. Defold, LÖVE and Bevy print to the terminal, so the player must start the game from a terminal, or you must add file logging before you ship.
For Ren'Py, the documentation says the base directory contains logs like log.txt, and is usually the folder above game/. The traceback.txt path comes from Ren'Py's source code: it tries the log directory first, then the current directory, then the system temporary directory with the name renpy-traceback.txt. On Android, the files are inside the package, so the documentation gives no guarantee that a file is there.
- How to add analytics to a Defold game →
- How to add analytics to a Ren'Py game →
- How to add analytics to a LÖVE (Love2D) game →
- How to add analytics to a Bevy game →
| Engine | Where errors go by default | How to get a file |
|---|---|---|
| Defold | The terminal that started the game. In Release builds the console log is empty. | Set Write Log File in game.project to Always. The game then writes log.txt. The manual gives the iOS location (AppData/Documents/) but no desktop path. |
| Ren'Py | log.txt in the base directory. traceback.txt when an exception occurs. | Nothing to set up. Ask for both files. |
| LÖVE (Love2D) | The default love.errorhandler prints the traceback and shows it on an error screen. | The player presses Ctrl+C on the error screen to copy the error. To write a file, replace love.errorhandler with your own function. |
| Bevy | stdout on desktop, the Android logs on Android, and the browser console in Wasm. | Redirect stdout to a file, or add your own layer with the custom_layer option of LogPlugin. Set the level with RUST_LOG. |
Sources: Defold manual, Debugging: game and system logs; Ren'Py documentation, config.basedir; Ren'Py source code, renpy/error.py; LÖVE wiki, love.errorhandler; Bevy API documentation, LogPlugin.
Where are the errors in Construct 3, Phaser and other web builds?
In the browser console. A web build has no log file on disk. The Construct team says browsers show no error messages by default, so a game that fails can show only a blank or frozen screen. Press F12 in Chrome, Firefox or Edge, or Command + Option + I in Safari, then open the Console tab.
The same applies to a Unity WebGL build, which writes its log to the JavaScript console, to a Bevy game in Wasm, and to a Defold HTML5 build.
Construct desktop exports differ. A Windows WebView2 export opens developer tools with F12. For a macOS WKWebView export, use the Develop menu in Safari. For a Linux CEF export, open chrome://inspect in Chrome or Chromium. The macOS and Linux exports must be made with Enable DevTools checked.
Sources: Construct tutorial, Checking for errors in browsers; Unity manual, Log files reference; Bevy API documentation, LogPlugin; Defold manual, game and system logs.
Where are the logs on Steam Deck and Proton?
It depends on the build that runs. A native Linux build writes to the Linux path in the table. A Windows build runs through Proton and writes to the Windows path, inside a Wine prefix that Proton creates for each game.
Valve's Proton FAQ says the prefix is in the same Steam library as the game, in steamapps/compatdata/[appid]/pfx/. Proton's launch script uses drive_c/users/steamuser as the Windows user folder. So a Unity Player.log on a Steam Deck is at this path:
[Steam library]/steamapps/compatdata/[appid]/pfx/drive_c/users/steamuser/AppData/LocalLow/CompanyName/ProductName/Player.log
For a Godot Windows build, replace the end with AppData/Roaming/Godot/app_userdata/[project_name]/logs/godot.log, because %APPDATA% is the Roaming folder.
Proton can also write its own log. Add PROTON_LOG=1 %command% to the Steam launch options of the game. Proton then saves steam-[appid].log in the home directory, and each new log replaces the old one. PROTON_LOG_DIR changes the folder.
Sources: Proton FAQ (Valve); Proton README, runtime config options; Proton launch script; Unity manual, Log files reference; Godot documentation, File paths in Godot projects.
How do I ask a player for a crash log?
Send one short message with the exact path, and ask for three facts: what happened just before the crash, the game version, and the operating system. Most players have never opened AppData, so give them a path they can paste.
On Windows, the Run box (Windows key + R) accepts paths with %USERPROFILE% or %APPDATA%. The message below is for a Unity game on Windows. Replace the path with the one for your engine from the table at the top.
Ask for the file before the player starts the game again. Unity gives one Player.log path per game, and Godot starts a new godot.log each session, so a new session can hide the crash.
Message to a player (Unity on Windows)
Sorry about the crash, and thanks for the report. Can you send me the log file?
1. Do not start the game again yet. A new session can replace the log.
2. Press the Windows key + R.
3. Paste this line and press Enter:
%USERPROFILE%\AppData\LocalLow\CompanyName\ProductName
4. Attach the file Player.log to your reply.
Please also tell me:
- What you did just before the crash.
- The game version (bottom corner of the main menu).
- Windows, macOS, Linux or Steam Deck.Sources: Unity manual, Log files reference; Godot documentation, Logging.
How do I read a crash log?
Read it in a fixed order: the top, the first error, then the end. A log is long, and the last line is often a result of an earlier problem, not the cause.
In Unreal Engine, search for the verbosity levels. Epic says Fatal always prints to the console and the log file and then crashes, and Error prints an error to both. In Godot, the crash backtrace is in the same file as the log.
- Read the top of the log. Note the engine version and your build, so you know which code the player runs.
- Find the GPU and driver lines near the top. Unity, Unreal Engine and Godot print the graphics API and the graphics card at startup. An old driver or an integrated GPU explains many crashes at startup.
- Search for the first error, not the last. Search for "Error", "Exception", "Fatal" or "Assertion". Later errors often follow from the first one.
- Read the stack trace below that error from the top down. The first line in your own code is where to start.
- Read the last 20 lines. They show what the game did just before it stopped.
- Compare with a log from a session that did not crash. Lines that appear in both are noise.
Sources: Unreal Engine 5.9 documentation, Logging in Unreal Engine; Godot Engine 4.7 documentation, Logging. The steps are our own practice.
What crash data does Steam give you?
Very little for a modern game. Steam does not collect your engine's log files. Its own feature, Steam Error Reporting, uploads minidumps after 10 similar exceptions and shows them on the Error Reports page of the Steamworks partner site. But Valve says it is available only for 32-bit Windows applications, that it is nearing its end of life, and that only limited support is available.
What Steam does give you is the result of crashes. Steamworks shows the refund rate and the notes that players write when they ask for a refund. The Steam reviews API marks each review with the playtime, a refunded flag and, when the author shows it, the hardware. These tell you that a build is broken. They do not tell you where the code failed.
Sources: Steamworks documentation, Steam Error Reporting, Developer Refund Reporting and IUserReviewsService.
What are symbols, and why does a stack trace need them?
Symbols are the data that turn memory addresses in a native crash into function names, files and line numbers. Without them, a crash dump from a release build is a list of numbers.
Keep the symbol files for every build that you ship, with the build number. You cannot rebuild them later with certainty. Godot says crash backtraces are only useful if they were recorded in a build that contains debugging symbols. Epic says a server that receives Unreal crash reports must symbolicate them. A GameMaker minidump needs the same care: it captures the call stack, and a debugger needs symbols to read it.
Script errors are easier. A C# exception in Unity, a GDScript error in Godot or a Lua traceback in LÖVE already names the function, so the log alone is often enough.
Sources: Godot Engine 4.7 documentation, Logging; Unreal Engine 5.9 documentation, Crash Reporting in Unreal Engine; GameMaker manual, Command Line Parameters.
When should I move from manual logs to automatic crash reporting?
Move when you cannot ask each player. Manual logs work in a playtest with 20 testers. They do not work after a launch, because most players who crash do not write to you: they refund or quit. From then on you need two things: a count of crashes for each build, and the stack trace for the worst ones.
The count is the crash-free rate: the share of sessions, or of players, with no crash. Read it for each build, so that a bad patch shows on the first day.
The stack trace needs a crash reporter. Sentry captures native crashes with minidumps on Windows and Linux and has a symbol server. Backtrace covers PC, mobile and consoles. Bugnet lists crashes, exceptions and player reports, with SDKs for six engines and the web. For a native crash, each of these fits better than Manalens.
Manalens does a different job. Its Godot and Unity SDKs send errors as events and send app_unclean_exit at the next launch after a crash. The Game health board shows crash-free sessions, crash-free players and the top errors for each build, next to retention and the campaign that brought the player. It stores no crash dumps and no symbols, and it has no SDK for Unreal Engine or GameMaker. Many games use it next to a crash reporter.
- What is crash-free rate? →
- Crash-free rate calculator →
- Error rate →
- Best crash reporting tools for indie games in 2026 →
- Manalens vs Sentry for game crashes →
- Manalens vs Backtrace for game crashes →
- Manalens vs Bugnet for game bug reports →
| Tool | Native crash dumps and symbols | What it shows | Engines |
|---|---|---|---|
| Manalens | No. A crash is counted at the next launch. | Crash-free sessions and players, and top errors for each build, next to retention and campaigns | Unity, Godot 4 and web. Unreal Engine and GameMaker: not yet. |
| Sentry | Yes: minidumps on Windows and Linux, and a symbol server | Stack traces for errors and native crashes | Unity, Unreal Engine, Godot, native C and C++, consoles |
| Backtrace | Crash and error reporting on PC, mobile and consoles | Crash reports on each platform | Unity, Unreal Engine and custom engines. Godot is not listed. |
| Bugnet | Its home page lists crashes and exceptions. We did not check dump support. | Crashes, exceptions and player bug reports, grouped into issues | Unity, Unreal Engine, Godot, GameMaker, Pygame, Construct 3 and web |
Sources: Manalens error tracking documentation; Sentry for gaming; Backtrace pricing page; Bugnet home page.
How do I see crashes for each build without asking players?
Manalens is the analytics and growth engine built for games. Add the Unity or Godot SDK. Errors and app_unclean_exit arrive on their own, and the Game health board shows crash-free sessions and the top errors for each build. Keep a crash reporter next to it for native stack traces.
Sources: Manalens error tracking documentation.
Frequently asked questions
Where is the Unity Player.log file?
On Windows, it is at %USERPROFILE%\AppData\LocalLow\CompanyName\ProductName\Player.log. On macOS, it is at ~/Library/Logs/Company Name/Product Name/Player.log. On Linux, it is at ~/.config/unity3d/CompanyName/ProductName/Player.log. CompanyName and ProductName come from your Player settings. On Windows, a built game also stores its crash reports in the folder %TMP%\CompanyName\ProductName\Crashes.
Where is the Godot crash log?
In user://logs/godot.log on desktop platforms. On Windows, the default folder is %APPDATA%\Godot\app_userdata\[project_name]\logs. On Linux, it is ~/.local/share/godot/app_userdata/[project_name]/logs. When the project crashes, Godot writes the crash log to the same file. It keeps up to 5 log files by default, so ask the player for the whole folder.
Where does Unreal Engine save crash logs?
Logs are .txt files in the Saved/Logs folder of the project. Editor crash reports are in Saved/Crashes. On a player's Windows machine, Epic gives C:\Users\[Your Windows Username]\AppData\Local\[Project Name]\Saved\Crashes. A crash report contains the callstacks, the system information and the log output, so ask for the whole folder.
Does Steam send me crash reports?
Not for most games. Steam Error Reporting uploads minidumps after 10 similar exceptions, but Valve says it supports only 32-bit Windows applications and is nearing its end of life. Steam does not collect your engine's log files. Use a crash reporter, or ask players for the log, and read refund notes for the effects.
Where are game logs on a Steam Deck?
A native Linux build uses the Linux path of its engine. A Windows build runs through Proton, which creates a prefix in steamapps/compatdata/[appid]/pfx/ in the same Steam library as the game. The Windows path starts below drive_c/users/steamuser in that folder. Add PROTON_LOG=1 %command% to the launch options to get a Proton log.
Does Manalens collect crash logs?
No. Manalens does not store log files, crash dumps or symbols. Its Godot and Unity SDKs send errors as events, and send app_unclean_exit at the next launch after a crash. You see crash-free sessions and the top errors for each build. For native stack traces, use Sentry, Backtrace or Bugnet next to it.
Sources and implementation
- Unity 6.6 manual: Log files reference (read 19 November 2026) ↗
- Unity 6.6 scripting reference: Windows.CrashReporting.crashReportFolder (read 19 November 2026) ↗
- Unreal Engine 5.9 documentation: Logging in Unreal Engine (Epic Games, read 19 November 2026) ↗
- Unreal Engine 5.9 documentation: Crash Reporting in Unreal Engine (Epic Games, read 19 November 2026) ↗
- Godot Engine 4.7 documentation: Logging (read 19 November 2026) ↗
- Godot Engine 4.7 documentation: File paths in Godot projects (read 19 November 2026) ↗
- GameMaker manual: Command Line Parameters (read 19 November 2026) ↗
- GameMaker manual: The File System (read 19 November 2026) ↗
- Defold manual: Debugging, game and system logs (read 19 November 2026) ↗
- Ren'Py documentation: Configuration Variables, config.basedir (read 19 November 2026) ↗
- Ren'Py source code: renpy/error.py, open_error_file (read 19 November 2026) ↗
- LÖVE wiki: love.errorhandler (read 19 November 2026) ↗
- Bevy 0.20 API documentation: LogPlugin (read 19 November 2026) ↗
- Construct tutorial: Checking for errors in browsers (Construct Team, last updated 25 June 2025, read 19 November 2026) ↗
- Proton FAQ (Valve, Proton wiki on GitHub, read 19 November 2026) ↗
- Proton README: runtime config options (Valve, GitHub, read 19 November 2026) ↗
- Proton launch script: prefix user folder (Valve, GitHub, read 19 November 2026) ↗
- Steamworks documentation: Steam Error Reporting (Valve, read 19 November 2026) ↗
- Steamworks documentation: Developer Refund Reporting (Valve, read 19 November 2026) ↗
- Steamworks documentation: IUserReviewsService (Valve, read 19 November 2026) ↗
- Sentry for gaming (read 19 November 2026) ↗
- Backtrace pricing (read 19 November 2026) ↗
- Bugnet home page (read 19 November 2026) ↗