Where to Find Log Files?

Getting Log Files From Yuzu

When something goes wrong in Yuzu, such as a game crash, graphical glitch, or freezing during gameplay, developers rely heavily on log files to determine the cause. The emulator generates these files automatically and they contain detailed runtime information, which is extremely useful for debugging and troubleshooting.

Even though Yuzu is no longer actively developed, this guide provides a reference for how users used to collect logs to help identify and resolve issues.

Why Log Files Are Important?

Log files function as a black box flight recorder for Yuzu. They keep records:

By reviewing these logs, developers and support teams can determine what caused a crash or unexpected behavior and whether it is related to the emulator, game files, system configuration, or even mod compatibility.

Set logging to *:info before starting

Log files function as a black box flight recorder for Yuzu. They keep records:

Before creating any logs for reporting:

  1. Launch Yuzu.
  2. Navigate to Emulation > Configure > General Tab.
  3. Go to the Debug sub-tab.
  4. Under Logging, make sure the log filter level is set to *:info.

This step is necessary because it ensures that detailed logs are captured. Without this, only minimal data will be recorded, which may be insufficient for diagnosing more complex issues.

How To Create and Share Log Files?

Step 1: Launch the Problem Game

Open Yuzu and launch the game that is causing problems—whether it is crashing, freezing, or acting strangely. Allow it to run until the problem arises.

Step 2: (Android Users) Share Logs

If you use Yuzu on Android:

  • Navigate to Settings > Share Debug Logs.
  • This automatically packages your logs and allows you to share them via email, messaging apps, or cloud storage.

Step 3 (Windows/Linux): Close Yuzu After the Issue

If you are using Windows or Linux, you must close Yuzu immediately after the problem occurs.

 Do not relaunch Yuzu after the crash. This will overwrite the existing log, resulting in the loss of valuable information.

Step 4: Locate the log file

The method varies slightly depending on your operating system.

4a. For Windows 10/11 Users:

  1. To open the Run dialog, press Windows + R.
  2. Type %appdata%\yuzu\log\ and hit Enter.
  3. Look for the file “yuzu_log.txt”.

This is Yuzu’s main log file. It contains the entire output from the most recent session.

4b. For Linux users:

  • Open the terminal.
  • Type echo $XDG_DATA_HOME and press the Enter.
    • If it returns a path, follow that location. For example, 

/home/yourusername/.local/share/yuzu/log/)

  • If nothing is returned, the default log directory is probably 

/home/yourusername/.local/share/yuzu/log/

  • Look for the file “yuzu_log.txt”.

Step 5: Compress Log Files, If Needed

Platforms such as Discord have upload limits (for example, 8MB). If your log file exceeds the following:

  • Use WinRAR, 7-Zip, or built-in compression tools to zip the log file before uploading.
  • On Linux, you can compress using: 

yuzu_log.zip yuzu_log.txt.

  • This preserves the file and makes it easier to distribute.

Step 6: Upload or Share the Log

Now that your log is prepared:

  • Upload it to the location where support is requested (e.g., Discord server, GitHub issue, forum thread, etc.).
  • Mention the problem (e.g., “Game crashes after loading screen”) and include system specifications if possible.

Tips for Better Debugging Logs

  • Try to replicate the problem clearly and avoid combining multiple test cases into a single log file.
  • Unless you are troubleshooting a specific mod-related issue, leave mods disabled while logging.
  • Make a note of the game version and Yuzu build you were using.
  • Always report on clean, unmodified log files.

Yuzu was a large and community-driven project. Although it is no longer actively developed, the information in log files is still useful for those who continue to use it or maintain forks. Sharing accurate logs is one of the most effective ways to improve compatibility and stability—even in legacy builds.

For related help and deeper debugging, look at: