
Chunks & world size · Java · Intermediate
How to Reduce World File Size by Trimming Low-InhabitedTime Chunks
Over 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.
What you need
- A Minecraft Java Edition world folder or .zip archive
- Enough free hard drive space to create a full backup of your world
- Access to the Chunk Trimmer tool on our site
Step by step
1Back Up Your World Folder
Before altering any region data, locate your world folder inside your Minecraft saves directory. Make a complete copy of the entire folder or compress it into a backup .zip file and store it somewhere safe. Deleting chunks is a permanent destructive action, and a backup ensures you can instantly restore your world if you set your trimming threshold too high.
Tip: Make sure the world is completely closed in your game client or that your server is stopped before copying the files.
2Load Your World into the Chunk Trimmer
Open the Chunk Trimmer on our site and click to open your world folder or .zip file. Because the tool runs locally in your browser, it will read your files directly from your disk without uploading them over the internet. Once loaded, the tool will scan the Anvil region files located in the region folder (Overworld), DIM-1/region (Nether), and DIM1/region (The End).
Tip: If you only want to shrink one specific dimension, such as The End after an Elytra raid, select that specific dimension inside the tool's dimension switcher.
3Configure the InhabitedTime Threshold
Locate the InhabitedTime filter setting within the Chunk Trimmer interface. Minecraft tracks how long players have spent near each chunk using an NBT tag called InhabitedTime, measured in game ticks (where 20 ticks equal 1 second of real time). Set your minimum threshold to a value between 1,200 ticks (1 minute) and 6,000 ticks (5 minutes) depending on how aggressively you want to prune explored terrain. This logic targets chunks generated during rapid travel while sparing any chunk where a player lingered long enough to place blocks.
Tip: If you are unsure which tick value to choose, test a lower value like 600 ticks (30 seconds) first and check the visual preview map in the tool to see which chunks get highlighted for deletion.
4Execute the Trim and Save Your Files
Review the preview map in the Chunk Trimmer to confirm that your main bases, farms, and railway lines are not marked for removal. Click the trim button to purge the low-time chunks from the loaded data, and then export or save the modified region files back to your computer. Replace the old region, poi, and entities folders in your active world save with the newly trimmed versions generated by the tool.
Tip: Keeping the poi (Point of Interest) and entities folders synced with your region folder prevents leftover entity data or phantom villager job sites from lingering in deleted chunks.
5Verify the World in Minecraft
Launch Minecraft Java Edition and load your world to inspect the results. Visit your main bases and long-distance builds to confirm they are completely intact, and fly out to previously explored borders to verify they generate fresh terrain. If everything looks good, you can keep the newly reduced world and delete your temporary backup whenever you are ready.
How it works
Minecraft Java Edition stores world terrain using the Anvil file format, grouping 32x32 chunks into individual .mca files inside the region, entities, and poi directories. Even if a player only flies across the corner of a region for a few seconds, the game must generate the terrain data and write that .mca file to your hard drive. Over months of gameplay, thousands of these untouched chunks accumulate and bloat your world size.
Inside every individual chunk's NBT data structure lies a long integer tag named InhabitedTime. Every game tick (1/20th of a second) that at least one player is within the simulation distance of a chunk, the game increments that chunk's InhabitedTime value by one. This serves as a built-in heatmap of player activity, originally designed by the game developers to scale local regional difficulty.
The Chunk Trimmer reads the header and NBT data of every chunk inside your .mca files and checks the InhabitedTime value against the threshold you specify. When a chunk falls below your threshold, the tool zeroes out its location pointer in the 4-kilobyte region file header and repacks the remaining valid chunks to reclaim the empty disk space. If all 1,024 chunks inside a single .mca file fall below the threshold, the entire file is removed, resulting in massive storage savings and virgin terrain ready for future game updates.
Common mistakes
- Trimming the world while it is currently open in Minecraft or running on an active server, which causes region file corruption as the game overwrites changes from memory.
- Setting the InhabitedTime threshold too high (such as several hours), which can accidentally delete quick outposts, nether portals, or long railway tunnels that players pass through quickly.
- Only replacing the region folder while forgetting to update the corresponding entities and poi folders, which can cause duplicate mobs or broken villager mechanics when those chunks are regenerated.
- Confusing seconds with game ticks when typing the threshold number, resulting in trimming 20 times less or 20 times more time than intended (always multiply seconds by 20 to get ticks).
FAQ
What happens when a player walks into a deleted chunk in-game?
Minecraft will seamlessly regenerate the chunk from scratch using your world seed and the terrain generator of whichever game version you are currently playing.
Will trimming chunks delete my inventory or player data?
No, player inventories, Ender chests, and statistics are stored separately in the playerdata and stats folders, which the Chunk Trimmer does not touch.
How do I protect a redstone line or railway that players only traveled through briefly?
Use the visual map inside the Chunk Trimmer to manually deselect or whitelist the specific chunks containing your railway before applying the InhabitedTime filter.
By filtering your world's Anvil region files using the InhabitedTime NBT tag in the Chunk Trimmer, you can effortlessly purge gigabytes of empty explored terrain while keeping every player build untouched.