Minecraft crash report and log analyzer

Paste a crash report or drop your whole latest.log in. It is read in this tab, it is never uploaded, there is no size limit and there is no account or monthly quota. 29 failure patterns, and where it can, it tells you whether the heap you gave the server is actually big enough for the pack you are running.

Or paste the report:

Analyze

Why this one is different

There are other Minecraft log analyzers and some of them are good. They each give something up, though, and it is usually the thing you need at 2am when a modded server will not boot:

• Upload vs local. Most run the analysis on their servers, so your log, with its IPs, player names and file paths, leaves your machine. This one never sends it.
• Quotas. Free tiers in this space are commonly a handful of analyses per month, often behind a sign-in. There is no counter here.
• File size. The uploading tools cap the file at a few megabytes, and the local one asks you to paste "only the section with errors". A modded latest.log is regularly larger than those caps, and finding the error section by hand is the job you came here to avoid. This reads the entire file in slices.
• Sizing. Every analyzer can tell you a mod threw. Only somebody who runs servers will tell you that -Xmx4G was never going to hold a 400-mod pack.

Where the log lives

On a server: logs/latest.log, and older runs in logs/ as dated .log.gz files. Crash reports go to crash-reports/. On a client the same folders sit inside your instance or .minecraft directory. If you are on a host panel, the file manager will have both folders at the root of your server.

A .log.gz from the logs folder can be dropped in directly; it is decompressed in the tab. Only .zip archives need extracting first.

Want this on a real server? Supercraft hosts Minecraft →