
World file format explained · Java · Intermediate
Why Minecraft Separated region, entities, and poi Into Three Folders
Before Minecraft Java Edition 1.17, nearly everything inside a chunk—terrain blocks, mobs, dropped items, and villager workstations—was crammed into a single region file. To improve game performance and allow asynchronous chunk loading, the developers split this data into three distinct folders: region, entities, and poi. This guide explains the logic behind this separation and shows you how to inspect and manage these folders safely using our browser-based tools.
What you need
- A Minecraft Java Edition world saved in version 1.17 or newer
- Access to our browser-based NBT Viewer and Region Coordinator tools (your files are processed locally and never upload)
- A complete backup copy of your world folder before making any edits
Step by step
1Back Up and Locate Your Dimension Folders
Always create a full backup copy of your world folder before inspecting or modifying game files. Open your world save directory on your computer. For the Overworld, you will see the region, entities, and poi folders right at the root level. For the Nether and the End, navigate inside the DIM-1 and DIM1 folders respectively to find their own sets of these three folders.
Tip: Even if a dimension has no villagers, the game still creates a poi folder to track Nether portals and lightning rods.
2Inspect Terrain Data in the region Folder
Open our browser tool, click Open world folder or .zip, and select your world to load it into the NBT Viewer. Navigate to the region folder and select an Anvil file, such as r.0.0.mca, to view its chunks. Notice that modern chunks (DataVersion 2724 and higher) store block palettes inside a sections tag and block entities like chests inside a block_entities tag, while the old Entities list tag is completely gone. Separating terrain allows the game engine to generate and render blocks on separate background threads without waiting for complex mob AI to initialize.
Tip: You can check the DataVersion tag at the root of any chunk to confirm which Minecraft version last saved it.
3Examine Mobs and Items in the entities Folder
In the NBT Viewer, return to the world root and open the entities folder, then click the matching r.0.0.mca file. Even though it uses the exact same .mca extension and region coordinate grid as the terrain folder, its internal NBT structure is purely dedicated to an Entities list tag. Here you will find passive mobs, hostile monsters, item frames, armor stands, and boats. Keeping entities in their own files allows Minecraft to load terrain visuals first and tick entities slightly later, preventing massive lag spikes when you travel quickly.
Tip: Players are not stored in these region files; they live in the level.dat file and the playerdata folder.
4Explore Villager Data in the poi Folder
Navigate to the poi (Points of Interest) folder in the NBT Viewer and open a file like r.0.0.mca. Inside each chunk column, you will see a Sections compound tag organized by vertical Y-subchunks, containing records with tags like pos, type, and free_tickets. This folder acts as a lightweight index for blocks that AI and game mechanics need to find quickly, such as villager beds (minecraft:home), job sites (like minecraft:armorer), bells, beehives, nether portals, and lightning rods. By reading this tiny file, a villager or bee can locate a valid block without forcing the game to scan millions of terrain blocks inside the heavy region folder.
Tip: If free_tickets is set to 0 on a workstation record, it means a villager has already claimed that block.
5Perform Selective Resets Carefully
Understanding this three-folder split gives you surgical control when troubleshooting or pruning your world. If you use our Chunk Pruner or delete an .mca file manually, you must decide whether to delete the matching file across all three folders. For example, deleting r.1.2.mca ONLY inside the entities folder will wipe out lag-inducing mob farms or thousands of dropped items in that area while leaving your built houses in the region folder completely intact. Conversely, if you want to completely regenerate a natural area for a new game update, you must delete the matching r.x.z.mca file from region, entities, and poi simultaneously.
Tip: Use our Region Coordinator tool to find the exact r.x.z.mca filename for any in-game block coordinates before deleting files.
How it works
All three folders—region, entities, and poi—use the Anvil file format (.mca). Each file covers a 32x32 chunk area (512x512 blocks) and begins with an 8-kilobyte header containing location offsets and timestamps, followed by compressed NBT chunk payloads. Because the naming convention (r.X.Z.mca) is identical across all three folders, the game engine can easily correlate terrain, mobs, and points of interest for any given coordinate.
The primary reason for this split—partially introduced in 1.14 for poi and finalized in 1.17 for entities—is asynchronous loading and thread safety. In older versions, loading a chunk meant parsing terrain palettes, tile entities, and mob AI simultaneously on the main server thread. If a chunk contained hundreds of chests and cows, the entire server tick would freeze while reading that single giant file.
With the modern separated architecture, the game can read terrain geometry from the region folder on background worker threads and send it to your graphics card immediately. Meanwhile, the server loads the entities file independently and only starts ticking mob AI once a player is close enough. The poi folder stays partially cached in memory so pathfinding algorithms and portal linking checks can execute instantly without even loading the surrounding terrain chunks from disk.
Common mistakes
- Deleting a file from the region folder to reset terrain while leaving the matching file in the entities folder, which causes old mobs, item frames, and armor stands to fall into the void or suffocate in newly generated hills.
- Looking for chests, furnaces, or signs inside the entities folder; these are Block Entities (formerly Tile Entities) and remain stored inside the region folder under the block_entities tag because they are tied to the block grid.
- Editing or deleting a block like a villager workstation or Nether portal in the region folder without updating the poi folder, leading to 'ghost' points of interest where villagers pathfind to empty air.
- Assuming a 0-kilobyte or missing .mca file in the entities or poi folder means the world is corrupted; the game often skips creating files in those folders if no mobs or points of interest have ever existed in that 512x512 area.
FAQ
Why didn't chests and hoppers move to the entities folder in 1.17?
Chests, hoppers, furnaces, and signs are Block Entities, not free-moving Entities. Because they are strictly locked to a specific X, Y, Z block grid coordinate and cannot move across chunk borders, they remain stored inside the region folder under the block_entities NBT tag.
What happens if I delete the entire poi folder?
Your buildings and villagers will remain intact, but villagers will temporarily forget where their beds and workstations are, bees will lose their hives, and existing Nether portals won't be detected as exit targets until players load the chunks and interact with or re-trigger those blocks.
How does Minecraft convert a 1.16 world to this three-folder system?
When you open an older world in 1.17 or newer, the game converts chunks on the fly as you explore them (or all at once if you click Optimize World in the singleplayer edit menu), stripping the Entities list out of the region file and writing it into a newly created entities folder.
Minecraft separated chunk data into region, entities, and poi folders to enable asynchronous loading, reduce server tick lag, and allow quick AI lookups without parsing heavy terrain files.