Missing Minecraft chunks can be a display issue, the wrong world state or corrupted data. First compare the same location with a second matching client and secure your findings. Regenerating replaces terrain, but it does not restore lost buildings and inventories.
What exactly is missing?
Note the dimension, coordinates, affected structures and the time when the area last looked correct. If possible, compare the same spot with a second matching client. If the problem only affects one player's display, changing server files is not justified at first.
If real data loss is possible, stop the server and back up the complete state along with the startup and error logs. Investigate only a copy. Do not keep exploring through the affected region while you are trying to secure a reliable initial state.
Separate observation from cause
| Observation | Possible way to investigate |
|---|---|
| Second client sees everything correctly | Check client rendering and graphics mods |
| Known landscape is there, newer builds are missing | Compare backup time or an older save state |
| Only one dimension looks untouched | Check the active dimension and the version-dependent layout |
| Sharp terrain edge after an update | Investigate a generation change or a mixed data state |
| Log reports an error when reading a chunk | Check the file, data version and storage state |
A straight edge alone is not proof of corruption. Older and newly generated areas can also look different. If the entire world appears wrong, the investigation starts with the active world folder and level-name.
Keep the original, evidence and working copy separate
Keep the faulty world unchanged. Make a complete copy outside the running server and create another working copy for your experiments. Note the Minecraft and server versions last used, as well as any changes to mods, datapacks or software.
Also check whether the storage medium or the server storage has enough free space. If write errors keep occurring, this cause must be resolved first. A restore into the same still-faulty environment can fail again. The Paper troubleshooting guide helps you tell messages about chunk data that is too new apart from other startup problems.
A good backup is the first recovery attempt
Choose a backup from before the incident and restore it to a separate target. Use matching software and the same required mod set. First compare the affected coordinates, then players, containers and other dimensions.
Make a small test change, stop cleanly and start again. If this state works, you can decide with your group whether losing the progress made since then is acceptable. The backup guide describes the whole process.
Do not copy individual region files into a newer world state without a plan. Player data, entities, block data and additional systems can then come from different points in time. Such a partial recovery needs separate acceptance testing.
Use tools only once the format is clear
MCA Selector offers tools for selecting, exporting and editing Java chunks. Minecraft Region Fixer examines certain region errors. Before using them, check whether the specific tool version supports your Minecraft data format.
Start with an analysis on the working copy. Keep its report and do not immediately apply suggested deletions. A region file can contain many chunks; the file name does not mean that only a single structure is affected.
These Java tools are not a general Bedrock repair guide. New data formats can overwhelm older tools. If a program does not recognize the world, do not convert your only backup to an older format just to work around the error.
When you should abort a repair
Stop if the tool wants to change more regions than expected, the wrong dimension was opened or its output is unclear. Start any further attempt again with a fresh copy of the original. A working world that has already been partly modified is not a neutral basis.
Without a healthy backup, a complete recovery may be impossible. The result of a repair must therefore be described precisely: restored original data, imported partial areas and newly generated terrain are different outcomes.
Acceptance and documentation
Check the borders of the affected areas, structures, containers, inventories and important mechanics. Let a normal account join and repeat the comparison after a restart. Keep the original, the backup used, the tool version and the report until the new state is confirmed.
FAQ
Does deleting a chunk repair the houses in it?
No. New generation recreates the landscape according to the rules used, not your building history.
Do I need to do a server restore for a graphics glitch?
If the same data appears correct for other clients, investigate the local rendering first. A restore can remove progress unnecessarily.
Can I fix the damage with a version downgrade?
For an older server, use a suitable earlier backup state. Downgrading data that has already been saved by a newer version is not a reliable repair method.
Related guides
This guide in other languages
English · Español · Français · Nederlands · Português · Русский
Narrowing down damage by location and time
Note the dimension, block coordinates and the last known date with a correct structure. First compare the region in a world copy with the most recent matching backup. If only newer changes are missing, check the backup time and write errors instead of immediately using a repair tool. An error when reading a specific region should be documented with the file path and data version. Use a tool only for the format it explicitly supports. Never delete entire region files just because a single chunk looks suspicious: they contain multiple chunks, and intact builds in them could otherwise disappear too.