Which file should you open?
| Situation | File to check first |
| --- | --- |
| Single-player game or multiplayer client | console.txt |
| Player-hosted co-op server | coop-console.txt |
| Dedicated server | server-console.txt |
| A support request that needs broader context | logs.zip |
The files are stored in the Project Zomboid user folder, not the Steam installation folder. On Windows that folder is normally %UserProfile%\Zomboid.
Capture a useful error sample
- Close Project Zomboid so you start with a clear test.
- Launch the game and reproduce the problem once.
- Open the matching console file and search for
ERRORorSTACK TRACEnear the time of the failure. - Copy the first relevant trace plus several lines before and after it. Include what you clicked or did when it appeared.
- If you ask for help, share the small relevant section or the requested
logs.zip, not unrelated personal files.
What to look for
Start with the first trace associated with the failure. Look for a named Workshop item, mod ID, Lua file, Java class, missing resource, database file, port, or memory message. A line containing the word “error” can be harmless context, while the first repeatable stack trace is usually more useful.
Protect private information
Read the excerpt before posting it. Usernames, local folder names, server addresses, and account-related values can appear in diagnostic files. Redact private values without removing the error signature, file name, or surrounding trace.
Sources
The Indie Stone support: error log file location — Official confirmation of the user-folder console log.
Steam support: using logs to investigate mod problems — Support discussion about log limits and mod isolation.