
Server world admin · Java & Bedrock · Intermediate
How to Prepare and Shrink a SMP Server World Download at the End of a Season
At the end of an SMP season, sharing the world download lets everyone preserve their builds, but raw server folders are often bloated to dozens of gigabytes and full of sensitive admin files. By trimming unvisited chunks and cleaning out server logs and metadata, you can easily reduce your file size by up to 80% while protecting player privacy. All tools on this site process your world locally in your browser so your massive files never need to upload.
What you need
- A complete backup copy of your SMP world folder (Java Edition or Bedrock Edition)
- A modern desktop web browser with sufficient RAM
- Enough free disk space to save the final compressed archive
Step by step
1Back Up and Strip Sensitive Server Files
Always make a duplicate copy of your raw server world before deleting or editing any files. Open your working copy and delete server-only files that expose player IP addresses and permissions, including the logs folder, ops.json, whitelist.json, banned-ips.json, and usercache.json. If you ran a plugin-based Java server where dimensions are split into separate folders (like world_nether and world_the_end), move the DIM-1 and DIM1 folders back inside the main world folder so singleplayer clients can read them.
Tip: If you want players to explore in Creative mode without their old survival inventories, you can also empty the playerdata and advancements folders, though most communities prefer keeping their final loadouts.
2Trim Unvisited Wilderness with the Chunk Trimmer
Open our Chunk Trimmer tool and load your world folder or .zip file directly into the browser. Filter the chunks by InhabitedTime and select a threshold between 100 and 200 ticks (5 to 10 seconds) to highlight chunks that players merely flew over with an Elytra without actually building anything. Apply the trim to the Overworld, Nether, and End to strip away gigabytes of untouched terrain, then save the cleaned region files.
Tip: Always check the 2D chunk map preview before confirming the deletion to ensure long connecting paths, Nether ice highways, or perimeter farms are not accidentally caught in the filter.
3Clean Up Level Metadata and World Borders
Open the level.dat editor tool on our site to inspect the root world settings. On Java Edition, inspect the BorderSize tag (default is 60000000) and reset it if you had a custom shrinking border active during an end-of-season finale event, otherwise singleplayer explorers will suffocate outside the boundary. Look through the Data and GameRules tags to set allowCommands (or cheatsEnabled on Bedrock) to 1 so people downloading the archive can freely switch to Spectator mode.
Tip: In Java Edition, make sure to delete the Player compound tag inside level.dat if one exists, otherwise anyone who opens the world in singleplayer will spawn with the host's personal inventory and location.
4Remove Admin Chests, Op Books, and Temporary Entities
Before finalizing the archive, scan your spawn area or admin district for command blocks, debug sticks, or written books containing private staff coordinates. In Java Edition, check the data folder and delete scoreboard.dat or command_storage_*.dat if your server stored sensitive verification tokens or private admin data in scoreboards. For Bedrock worlds, double-check that experimental or admin behavior packs are unlinked from the world_behavior_packs.json file so singleplayer users do not get missing dependency errors.
5Test in Singleplayer and Package the Archive
Move your cleaned world folder into your local Minecraft saves directory (or import the folder into Bedrock) and load it in singleplayer. Verify that your gamemode switching works, check that dimension portals link properly, and confirm that trimmed chunk borders generate smoothly into new terrain. Once confirmed, compress the world folder into a standard .zip file (or rename the zip to .mcworld for Bedrock players) so it is ready to distribute.
Tip: When zipping the folder, compress the contents directly or clearly label the root folder so players do not accidentally extract a nested folder-inside-a-folder into their saves directory.
How it works
Minecraft stores terrain data efficiently, but exploratory gameplay causes exponential file growth. In Java Edition, the region folder holds .mca Anvil files, each storing a 32x32 grid of chunks alongside an entity and poi folder. Every chunk tracks a tag called InhabitedTime, which increments by 1 every game tick (20 times per second) while a player is within that chunk's activation distance. By deleting chunks with very low tick counts, the Chunk Trimmer removes massive swaths of generated wilderness while leaving every base and farm completely intact.
Bedrock Edition uses a different architecture inside the db folder based on a LevelDB key-value store. Rather than splitting the world into fixed region files, Bedrock writes individual chunk sub-sections, block entities, and actor data as distinct keys compressed in sequence. When our browser tool trims a Bedrock world, it strips out the terrain keys for unvisited coordinates and compacts the database blocks, allowing the game engine to seamlessly generate fresh terrain if a player visits those coordinates later.
Server software also leaves behind structural footprints that confuse singleplayer clients. Dedicated Java servers often split dimensions into separate root folders and ignore the singleplayer Player tag inside level.dat, relying solely on UUID files inside the playerdata folder. Recombining the DIM-1 and DIM1 folders and clearing the root Player tag ensures the world behaves like a native singleplayer save for anyone who downloads it.
Common mistakes
- Trimming chunks with an overly aggressive InhabitedTime threshold (such as over 1200 ticks / 1 minute), which frequently deletes segments of long Nether ice boat highways or rail networks where players move too fast to accumulate ticks.
- Forgetting to merge split world_nether and world_the_end folders back into the main world folder's DIM-1 and DIM1 directories, resulting in completely wiped dimensions when opened in singleplayer.
- Leaving usercache.json, logs, and server configuration files inside the zip archive, which leaks player IP addresses and connection timestamps to the public.
- Not resetting a shrunken world border or custom spawn-protection radius, leaving singleplayer users trapped or unable to interact with blocks at the center of the map.
FAQ
What happens when a player walks into an area that was deleted by the Chunk Trimmer?
Minecraft will simply regenerate those chunks from scratch using the world seed stored in level.dat. If the player opens the world in a newer game version than the server ran on, those freshly trimmed areas will generate with the newest biomes and structures.
Will deleting playerdata delete players' builds or chests?
No. All placed blocks, normal chests, signs, and item frames are saved inside the region terrain files (or the db folder on Bedrock). The playerdata folder only holds personal inventory items, Ender Chest contents, XP levels, and logout coordinates.
How do I know what InhabitedTime number is safe for my specific server?
If you are unsure, start by filtering for 0 ticks (chunks generated at the edge of someone's render distance but never stepped in), check the visual map in the Chunk Trimmer, and slowly increase the threshold to 100 or 200 ticks while watching to make sure known roads and outposts stay unselected.
By stripping server logs, merging dimension folders, resetting level.dat boundaries, and using our browser-based Chunk Trimmer to purge unvisited wilderness, you can turn a massive SMP server folder into a compact, privacy-safe singleplayer world download.