Web Analytics Made Easy - Statcounter

Tools / Project Zomboid

Project Zomboid: Server Log Analyzer

Pick your console.txt or paste the last few hundred lines of any Zomboid server log. We flag missing mods, Workshop download failures, version mismatches, map load errors, port conflicts, and out-of-memory crashes in plain language.

When the log points to a mod that failed to load or wasn't found, the Project Zomboid Mod Config Checker reconciles your servertest.ini against what each Workshop item actually provides and hands back the corrected, startable config.

Your log never leaves your browser. By default the analysis runs entirely in this tab - the matching rules are downloaded to the page and applied locally. Verify with the network tab open. Only anonymous findings metadata (which rule categories matched) is sent back to improve the analyzer - never log content. If nothing matches, you can choose to send us the error lines we could not read: you see them first, and we keep them for 30 days. A server-side analysis remains available below if you prefer it.

Analyze on the server instead

This path sends the log to our server. We strip passwords, tokens, private IPs, and Discord webhooks before storage - the log isn't kept, only a hash of the redacted text we analyze. Redact secrets yourself first to be safe.

The uploaded file is analyzed in memory only; raw log text is not stored.

Analyzing...

How to grab your log

  • Linux dedicated: ~/Zomboid/Logs/console.txt
  • Windows: %USERPROFILE%\Zomboid\Logs\console.txt
  • Pick the whole file - it's read locally, and for huge logs we analyze the last 25 MB where the crash or startup failure lands.

In-browser analysis never sends the log anywhere; feedback sends findings metadata only. The optional server-side path strips passwords, tokens, IPs, and Discord webhooks before storage, and keeps a hash of the redacted text - not the text itself.

Frequently asked questions

Where do I find my Project Zomboid server log?

On Linux: ~/Zomboid/Logs/console.txt and ~/Zomboid/Logs/*.txt. On Windows: %USERPROFILE%\Zomboid\Logs. Most server crashes leave a relevant message in the last few hundred lines of console.txt.

What kinds of errors can this detect?

Missing mods, Workshop download failures, game-version mismatches, map load failures, port conflicts, and out-of-memory crashes. The detection set grows as we add patterns. When no match is found, we point you at related tools and common-cause documentation.

What happens if it can't diagnose my issue?

You get three recovery paths: a checklist of common causes for PZ server failures, a link to our Workshop Collection importer to regenerate your config, and the option to use Supercraft's full AI Server Doctor as a paying customer (which can see your live deployment signals).

Is my log uploaded or stored?

By default, no. The analysis runs entirely in your browser: the matching rules are downloaded to the page and your log never leaves it. Only anonymous findings metadata (which rule categories matched, and how far the server got through startup) is sent back to improve the analyzer - never log content. One exception, and only if you choose it: when nothing matches, the page offers to send us the ERROR/WARN lines it could not match. You see the exact lines first, with passwords, IPs, tokens and emails removed, and if you press Send we keep them for 30 days to review, then delete them. If you explicitly choose the optional server-side analysis instead, we strip known secret patterns (passwords, Discord webhooks, IPs, tokens) before storing anything; the log itself isn't kept, only a hash of the redacted text, and that hash is deleted when the report expires after 30 days.

This tool: v1.33 · updated 2 Oct 2026