Chunks & world size · Java · Intermediate

Why You Must Clean entities and poi Folders When Deleting Region Chunks

When resetting terrain in a Minecraft Java Edition world, simply deleting terrain files from the `region` folder is no longer safe in modern versions (1.17+). Minecraft now separates block data, entity data, and villager points of interest across three distinct folders that must be modified together. This guide explains why these files must stay synchronized and how to use our Chunk Trimmer to prune them safely without causing ghost villagers or orphaned mobs.

Open the Chunk TrimmerPaint chunks on the map and delete them, or remove every chunk nobody really visited.

What you need

  • A Minecraft Java Edition world save (version 1.14 or newer for POI, 1.17 or newer for separated entities)
  • A complete backup copy of your world folder or .zip archive
  • Access to the Chunk Trimmer tool in your browser

Step by step

  1. 1Back Up and Inspect Your World Folder Structure

    Before making any changes, always create a full duplicate backup of your world folder in case you accidentally delete a build. Open your world save directory and locate the three primary data folders for the Overworld: `region`, `entities`, and `poi` (for the Nether and End, look inside `DIM-1` and `DIM1` respectively). Inside each of these folders, you will see Anvil `.mca` files with identical coordinate names, such as `r.0.0.mca`. Because these files correspond to the exact same 32x32 chunk area, modifying one without modifying the others breaks world synchronization.

    Tip: Make sure Minecraft is completely closed before copying or editing your world files so all session data is properly saved to disk.

  2. 2Load Your World into the Chunk Trimmer

    Open the Chunk Trimmer tool in your web browser; because the tool runs entirely locally in your browser, your world files are never uploaded to a server. Click to open your world folder or `.zip` archive and select the dimension you wish to prune. The tool will parse your world data and render a top-down map of your explored terrain based on the existing `.mca` files. Wait a moment for the map grid to fully populate before making any selections.

  3. 3Select the Chunks or Regions to Delete

    Use the selection controls in the Chunk Trimmer to highlight the chunks you want to reset or remove to reduce file size. You can select individual 16x16 chunks or entire 32x32 chunk regions, or filter chunks based on their `InhabitedTime` value to automatically target areas players merely walked through without building. Verify carefully on the visual map that none of your bases, farms, or intentional mob storage areas are included in the deletion selection. Everything highlighted will be permanently wiped so the game can regenerate it fresh.

    Tip: If you are unsure of the exact coordinates of your base, load the world in Minecraft first and press F3 to write down your chunk and region coordinates.

  4. 4Execute a Synchronized Trim Across All Three Folders

    Configure the Chunk Trimmer to apply the deletion across terrain (`region`), entities (`entities`), and points of interest (`poi`) simultaneously, then run the trim operation. When you export or save the changes, the tool automatically removes the targeted chunk entries from the matching `.mca` files in all three directories at once. If you downloaded a trimmed `.zip` or updated folders, replace your active world save files with the newly trimmed versions. Launch Minecraft and visit the pruned borders to confirm clean terrain generation without floating mobs or broken villager schedules.

How it works

Prior to Minecraft Java 1.14 and 1.17, almost everything inside a chunk—blocks, chests, mobs, and village data—was stored inside a single `.mca` file inside the `region` folder under the root `Level` NBT tag. Starting in 1.14, village job sites, beds, nether portals, and beehives were split into the `poi` (Point of Interest) folder. Then, in 1.17, all mobs, boats, minecarts, and dropped items were removed from the terrain files and placed into a dedicated `entities` folder to improve game performance and prevent lag during chunk loading.

Because all three folders use identical Anvil `.mca` naming and chunk coordinate headers, the game engine expects them to match when generating or loading a chunk. If you manually delete `r.0.0.mca` from the `region` folder to get new update terrain, Minecraft sees the missing terrain chunk and runs the world generator to create new blocks, trees, and structures. However, if `r.0.0.mca` still exists inside the `entities` folder, Minecraft does not clear those old entities; instead, it loads your old mobs, armor stands, and newly generated mobs together into the newly shaped terrain.

This desynchronization causes severe gameplay bugs. Old entities may load deep underground inside newly generated stone and suffocate, or float high in the air where a mountain used to be. Even worse, if the `poi` folder is not cleaned alongside `region`, the game remembers ghost workstations, beds, and portals at coordinates where blocks no longer exist. Villagers will refuse to claim new beds or restock trades because they are trying to pathfind to invisible POI records stored in the outdated `poi` file.

Common mistakes

  • Deleting `.mca` files manually from the `region` folder in your operating system's file explorer while completely ignoring the `entities` and `poi` folders.
  • Trimming the Overworld root folders (`region`, `entities`, `poi`) when you actually meant to reset chunks in the Nether (`DIM-1`) or The End (`DIM1`), which have their own separate subfolders.
  • Cleaning the `entities` folder around a base without realizing that item frames, paintings, armor stands, and chests in boats are technically entities and will be permanently erased.
  • Editing or trimming world files while the world is currently open and paused in Minecraft, which causes the game to overwrite your changes from memory when you save and quit.

FAQ

Why do I have double mobs or animals suffocating in walls after resetting chunks?

You deleted the terrain data in the `region` folder without removing the matching chunks in the `entities` folder. Minecraft generated brand new terrain and freshly spawned mobs, then loaded your old saved mobs from the untouched `entities` file into the exact same space.

Why won't my villagers link to workstations or beds in newly regenerated chunks?

Your `poi` folder still contains old Point of Interest data for those chunk coordinates. Even though the physical blocks were deleted with the `region` file, the game still sees the old claimed beds or job sites in the `poi` data, preventing villagers from linking properly.

What happens if I only delete the `entities` folder and keep the `region` folder?

Your builds, terrain, and chests will remain completely intact, but every mob, villager, pet, boat, minecart, armor stand, and item frame in those chunks will be permanently deleted.

Always trim the `region`, `entities`, and `poi` folders together using the Chunk Trimmer so newly regenerated terrain does not collide with orphaned mobs or ghost villager workstations.

More chunks & world size guides

Chunks & world sizeHow to Convert Block Coordinates to Chunk and Region (.mca) File NamesWhen managing or repairing a Minecraft Java Edition world, you often need to pinpoint which exact region file on your disk contains a specific build or corrupted area. This guide explains the exact bit-shift math used by the game to convert in-game block coordinates into chunk coordinates and r.X.Z.mca region file names. You will also learn how to visually locate and manage these 512x512 block regions directly in your browser using our Chunk Trimmer without ever uploading your world files.JavaIntermediate5 steps
Chunks & world sizeHow to Delete Specific Chunks so New Game Updates Generate Fresh TerrainWhen a major Minecraft update releases, new biomes, ores, and structures will only appear in areas of your world that you have never visited before. Instead of traveling thousands of blocks away from your home, you can delete the surrounding explored chunks that you haven't built in. When you walk back into those deleted areas in the latest version, the game will seamlessly generate brand-new update terrain right outside your base.Java & BedrockBeginner5 steps
Chunks & world sizeHow to Fix Harsh Chunk Borders and Wrong Biomes After Version UpgradesUpgrading a Minecraft world to a major new version often leaves ugly, sheer cliffs or sudden biome shifts where old terrain meets newly generated chunks. While modern versions of the game include automatic terrain blending, it only works where old chunks directly meet completely ungenerated space. By using our browser-based Chunk Trimmer to prune unbuilt outer chunks, you can force the game to regenerate those borders smoothly without ever uploading your private world files to a server.Java & BedrockIntermediate5 steps
Chunks & world sizeHow to Regenerate a Single Ruined or Griefed Chunk Back to Natural TerrainDealing with a huge crater, lag machine, or griefed landscape right next to your base can feel frustrating, especially if you don't want to restore an old backup and lose recent build progress. Fortunately, Minecraft builds and saves worlds in individual 16x16 vertical columns called chunks. By deleting the data for just the ruined chunk using our browser-based tool, you can force the game to cleanly rebuild that specific square of natural terrain from your world seed.Java & BedrockBeginner4 steps
Chunks & world sizeHow to Reduce World File Size by Trimming Low-InhabitedTime ChunksOver time, Minecraft Java Edition worlds can balloon into gigabytes of data just from players flying across the terrain in search of structures or biomes. By using the browser-based Chunk Trimmer tool, you can safely delete chunks players merely passed through while preserving every single block where someone stopped to build. Because this tool processes everything locally in your browser, your large world files never have to be uploaded to a server.JavaIntermediate5 steps