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. 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.

This tool: v1.22 · updated 21 Aug 2026