Minecraft2026-10-20 · 6 min read

Minecraft World Corruption — How to Recover It

A corrupted region file sounds catastrophic but almost always only affects a 32x32 chunk area — knowing the right recovery order matters more than panicking.

Recovering a modpack world instead? Same approach applies — see the Prominence II pack page.

Recognizing corruption

  • Server crashes repeatedly with 'Exception ticking world' or similar, always around the same coordinates.
  • Visible holes, missing chunks, or floating terrain where generated land should be.
  • A world that loads fine in singleplayer or offline tools but crashes the dedicated server specifically on load.

What usually causes it

  • Killing the server process (kill -9, power loss, host crash) mid-write instead of a graceful /stop.
  • Running out of disk space while the world is actively saving — a half-written region file is a corrupted one.
  • A plugin or mod directly editing world files while the server is also writing to them.

Recovery, safest option first

Restore from a recent backup if you have one — this is always faster and safer than trying to hand-repair a region file.

If you must repair in place: identify the broken region file from the crash log's chunk coordinates (region files are named r.<x>.<z>.mca, each covering a 32x32 chunk area), then delete just that file — the server regenerates the missing chunks as fresh terrain on next load, trading a hole in the map for a server that boots again.

Never edit a world's region files while the server is running — stop it first, every time.

FAQ

Will deleting a corrupted region file delete my whole world?+

No — each .mca file covers only a 32x32 chunk area. Deleting one regenerates just that area as new terrain; the rest of the world is untouched.

Can I prevent corruption from happening again?+

Always stop the server with /stop, or a graceful shutdown signal, rather than killing the process, and make sure disk space never runs critically low on the host.

Are automated backups enough to recover from this?+

Yes, in almost every case — a backup from before the crash lets you roll back cleanly instead of losing the affected chunks permanently.

Automated backups before this becomes a problem

CoalHost takes scheduled backups and graceful-stop shutdowns by default, so a host crash doesn't become a corrupted world.

View Minecraft Hosting →