MinecraftMinecraft Log Analyzer – Analyze crash reports and latest.log
The Minecraft Log Analyzer reads your latest.log, debug.log, or crash report and shows detected causes of errors with their severity, affected line, explanation, and suggested fix—for example, OutOfMemoryError, the wrong Java version, or Mod and plugin errors from Forge, Fabric, and Bukkit. Share the results via a short link in Discord or a support ticket. Free and no sign-up required.
Built by Luca Stanek
Crash solved? Get a server that catches problems before your players do.
Example result
What the report looks like in the Log Analyzer
You paste your latest.log or a crash report, and the analyzer lists the detected causes of errors with severity, line number, explanation, and suggested fix. The example below is an excerpt from a sample Paper server log; your findings depend on your log file.
Example · Shortened sample latest.log (Paper 1.21.1)
1 Error · 1 WarningInput
[18:42:01] [ServerMain/INFO]: Environment: Environment[sessionHost=https://sessionserver.mojang.com, servicesHost=https://api.minecraftservices.com, name=PROD][18:42:03] [Server thread/INFO]: Starting minecraft server version 1.21.1[18:42:03] [Server thread/INFO]: Loading properties[18:42:04] [Server thread/INFO]: This server is running Paper version 1.21.1-133 (MC: 1.21.1)[18:42:04] [Server thread/INFO]: Starting Minecraft server on *:25565[18:42:07] [Server thread/INFO]: [ExampleShop] Enabling ExampleShop v2.4.0[18:42:07] [Server thread/ERROR]: Error occurred while enabling ExampleShop v2.4.0 (Is it up to date?)[18:42:09] [Server thread/INFO]: Done (5.912s)! For help, type "help"[19:17:45] [Server thread/ERROR]: Encountered an unexpected exceptionjava.lang.OutOfMemoryError: Java heap space at java.base/java.util.Arrays.copyOf(Arrays.java:3541)[19:17:46] [Server thread/INFO]: Stopping serverOutput: findings
- 1 error
- 1 warning
Error · Row 10Java heap space exhausted (OutOfMemoryError)
The server needed more memory than its allocated Java heap and crashed. Common causes include too many Mods/plugins, a memory leak in a plugin, or simply too little RAM for the installed Mods or Player count. Suggested solution: Increase the allocated RAM (-Xmx) or purchase more memory for the server. If that does not provide a lasting fix, use a profiler (such as Spark) to identify which plugin or Mod is consuming the memory.
Warning · Row 7Error enabling a plugin
A plugin loaded but crashed during activation (onEnable). Suggested solution: Check the stack trace immediately below. It usually identifies a missing configuration file, a missing dependency, or a version conflict.
How it works
How to analyze a Minecraft log
From crash to cause in five steps.
Step 1
Find log file
In your game's Minecraft folder or server directory, open the logs folder (latest.log, debug.log). After a crash, open the crash-reports folder and find the latest crash-report-*.txt.
Step 2
Paste or upload log
Paste the contents into the text field, drag and drop the file, or select it using “Browse files” (.log or .txt, up to 3 MB).
Step 3
Confirm data notice
Tick the box to acknowledge that the log may contain your IP address, player name or folder paths, and that a publicly accessible link will be created.
Step 4
Analyze log
Click “Analyze log”. The log is first checked against the curated rule list. If it finds no error or warning, an AI assessment tries to identify the cause.
Step 5
Read and share the result
The results page shows each detected cause with its severity, affected line, explanation, and suggested fix. Copy the short link for Discord or a support ticket; it remains accessible for 45 days.
Detected errors
Errors the Log Analyzer detects in crash reports
Detection starts with a curated list of rules for known error patterns in Minecraft, Forge, Fabric, and Bukkit. If no rule matches, AI analysis attempts to identify the cause. These errors include:
Memory and performance
OutOfMemoryError caused by exhausted Java heap space or Metaspace, an overloaded garbage collector, and watchdog crashes caused by a server tick taking too long.
Java, network and system
The wrong Java version (UnsupportedClassVersionError), a port in use or that cannot be bound, unreachable Mojang authentication servers, a full disk, and too many open files.
World and configuration
Corrupted region files, chunks that fail to load, an outdated world format, an unaccepted EULA, and a server in offline mode (online-mode=false) as an informational finding.
Mods with Forge and Fabric
Missing or incompatible Mod dependencies, duplicate Mods, Mixin errors, Forge and Fabric Loader loading errors, and corrupted .jar files.
Plugins, datapacks and resource packs
Plugins that fail to load or enable, or are incompatible with the Bukkit, Spigot or Paper version, as well as datapacks and server resource packs that could not be loaded.
Why this analyzer
More than just a text field
The cause, not stack trace guesswork.
Curated error database
A curated list of rules detects common Minecraft, Forge, Fabric, and Bukkit errors.
AI fallback for unknown queries
If no rule detects an error or warning, AI analysis attempts to identify the cause.
Shareable short link
Share the result via a short link, e.g. in Discord or support tickets.
Crash report & log files
Submit latest.log, debug.log, and crash-report-*.txt as text, via drag and drop, or as a file up to 3 MB.
Directly from the server Dashboard
For Minecraft servers rented from ZAP-Hosting, you can load logs/latest.log with one click in the Tools tab.
Free, no account required
No registration, no hidden costs. Up to 8 analyses per hour and 10 per day per IP address.
Discover more
More Minecraft tools after analysis
Estimate RAM requirements, create a startup command with RAM and Aikar's Flags, regenerate server.properties, or check whether the server is back online: these tools help with the next step after diagnosis.
Server Configuration Generator
Describe your server.properties in your own words using the ZapX AI Agent or set each option manually — with a live preview to copy or download.
Built by Florian Galz
Server Status Checker
Check live whether a Minecraft server is online — player count, MOTD, version, server icon, and Mods.
Built by Luca Stanek
RAM calculator
How much RAM your Minecraft server or Modpack needs—a clearly labeled estimate based on server variant and player count, using ZAP server usage data when enough is available.
Built by Luca Stanek
Startup script and command generator
Create a Java startup command or startup script for your Minecraft server—with RAM and Aikar's Flags.
Built by Luca Stanek
FAQ
Frequently asked questions
Quick answers about crash reports, Exit Code 1, files and privacy.
A list of detected causes, each with its severity, affected line, explanation, and suggested fix, plus a link to share. For example, if your log contains “java.lang.OutOfMemoryError: Java heap space”, the finding is “Java heap space full” with “critical” severity, and the suggested fix is to increase the allocated RAM or purchase more memory for the server.
Exit Code 1 only means Minecraft or the server stopped with an error, not why. The Log Analyzer does not analyze the code itself: the actual cause is in latest.log or the crash report from the same session. Paste that file above. The rule list detects typical causes such as the wrong Java version, missing Mod dependencies, Mixin errors, or Forge and Fabric loading errors.
For the game, both are in the Minecraft folder: .minecraft/logs/latest.log (and possibly debug.log alongside it) and .minecraft/crash-reports/ containing crash-report-*.txt files. Launchers with separate instances, such as CurseForge or Modrinth, place these folders in the respective instance directory. On a server, you'll find logs/ and crash-reports/ in the server directory. If there's no crash report, analyze latest.log.
latest.log, debug.log and crash-report-*.txt. You can paste the contents into the text field, drag and drop the file into it, or select it using “Browse files” (.log or .txt). Files up to 3 MB are allowed; for larger logs, upload only the relevant section. Content that does not look like a Minecraft log or crash report will be rejected.
A curated list of common errors from Minecraft, Forge, Fabric, and Bukkit/Spigot/Paper, including OutOfMemoryError (Java heap space and Metaspace), watchdog crashes, the wrong Java version, a port in use, an unaccepted EULA, corrupted region files, missing or duplicate Mods, Mixin errors, plugin errors, and faulty datapacks and resource packs. If no rule detects an error or warning, AI analysis attempts to identify the cause. A finding is not guaranteed.
The server or game needed more memory than it was allocated. Increasing RAM via -Xmx or reducing memory-hungry Mods and plugins usually helps. Use the RAM calculator to estimate how much RAM your server needs. Go to the Minecraft RAM calculator
Yes, the analysis is free and requires no registration. To keep the service available to everyone, each IP address is limited to 8 analyses per hour and 10 per day.
Each analysis gets a short, hard-to-guess link. Anyone with the link can open the log and results. Both are automatically deleted after 45 days. Your log may contain your player name, folder paths or, in rare cases, IP addresses. Check it before sharing; you must acknowledge this notice by ticking a box before analysis.
Any more questions?
Contact Support
Host your own Minecraft server in 60 seconds
DDoS protection included, Modpacks installed in one click, cancel anytime — starting at just a few euros per month.
No setup. No risk. Online in seconds.
Looking for more tools? View all Minecraft tools
Preferred source on Google
