Server world admin · Java · Intermediate

How Paper/Bukkit Splits world_nether and world_the_end vs Vanilla Saves

Moving a Minecraft Java Edition world between a Vanilla or Fabric setup and a Paper, Spigot, or Bukkit server often results in players losing their Nether and End progress. This happens because Bukkit-based servers store dimensions in separate root directories rather than nesting them inside the main world folder. This guide explains the exact directory logic so you can merge or split your dimension folders safely without losing a single chunk.

What you need

  • Access to your server files or local singleplayer saves folder
  • A complete backup copy of your world files before making any edits
  • Our browser-based Region Map Viewer and NBT Editor tools (which run locally without uploading your files)

Step by step

  1. 1Back Up and Inspect Your Current Folders

    Before moving or deleting any files, duplicate your entire server world directories or local save folder to a safe location. Open your file manager and look at your directory structure: Vanilla and Fabric store everything inside a single folder (usually named world), whereas Paper and Spigot create three sibling folders named world, world_nether, and world_the_end. You can verify which dimension folder contains your actual builds by opening the folder or a .zip archive in our site's Region Map Viewer -> selecting the specific dimension to visually confirm your generated chunks.

    Tip: Make sure your server is completely stopped before copying or moving any region files, or you risk severe chunk corruption.

  2. 2Merging Paper/Bukkit Worlds into Vanilla or Fabric

    To move from Paper to Vanilla or Fabric, you must consolidate the three separate folders into the main overworld folder. Navigate inside your world_nether folder and locate the DIM-1 directory, then copy or move that entire DIM-1 folder directly into your main world folder. Next, open your world_the_end folder, locate the DIM1 directory, and move it directly into the main world folder as well. If the target world folder already has empty or newly generated DIM-1 and DIM1 folders, delete them first before moving your Paper folders in.

    Tip: Do not copy the level.dat or uid.dat files from world_nether or world_the_end into your main world folder; you only need the DIM-1 and DIM1 subdirectories.

  3. 3Splitting a Vanilla or Fabric World for Paper/Bukkit

    If you are moving a singleplayer, Vanilla, or Fabric world onto a Paper or Spigot server, you can either let Paper automatically split the folders on its first boot or do it manually to prevent directory conflicts. To do it manually, create two new folders alongside your main world folder and name them world_nether and world_the_end (if your main world is named differently in server.properties, replace 'world' with that exact name). Move the DIM-1 folder out of your main world folder and place it directly inside world_nether. Finally, move the DIM1 folder out of your main world folder and place it inside world_the_end.

    Tip: Paper will automatically generate the required level.dat files for the Nether and End folders when you start the server.

  4. 4Verify Dimension Data and Clean Up

    Before starting your server, double-check that your region (.mca), entities, and poi subfolders are intact inside DIM-1 and DIM1. If players were logged out in the Nether or End during a Paper-to-Vanilla migration, open your world folder in our site's NBT Editor -> navigate to playerdata -> open the player's .dat file -> verify that the Dimension tag reads minecraft:the_nether or minecraft:the_end rather than an old custom Bukkit world name. Once confirmed, launch your server and test a Nether and End portal to ensure your structures are exactly where you left them.

How it works

In standard Vanilla Minecraft (and mod loaders like Fabric that maintain Vanilla directory structures), all dimensions belong to a single parent save folder. The Overworld's region, poi, and entities folders sit right at the root of the main world folder. The Nether is stored in a subfolder named DIM-1, and the End is stored in a subfolder named DIM1. Those dimension numbers (-1 and 1) are legacy internal IDs from early Minecraft versions that the game still uses for folder naming.

When Bukkit was originally created, its developers designed a multi-world management system that treated every dimension as an entirely independent world instance with its own level.dat, gamerules, and world border. Spigot and Paper inherited this architecture for plugin backwards compatibility. Therefore, when a Paper server runs, it looks for three distinct root folders: the base world name, the base name plus _nether, and the base name plus _the_end.

Interestingly, Paper still maintains the DIM-1 and DIM1 folder names inside those separated directories. This means the actual region files (.mca) and folder names are 100% compatible between Vanilla and Paper; only their parent directory location changes. Moving DIM-1 and DIM1 up or down one directory level is all it takes to translate between the two server formats.

Common mistakes

  • Putting the region folder directly inside world_nether instead of keeping it inside world_nether/DIM-1/region.
  • Overwriting the main Overworld level.dat with the level.dat from world_nether, which breaks seed data, global dragon fight states, and world spawn points.
  • Forgetting to match custom level-name settings in server.properties (for example, if your level-name is survival, Paper looks for survival_nether, not world_nether).
  • Leaving old DIM-1 and DIM1 folders inside the main world folder when moving to Paper, which wastes disk space and confuses future backups.

FAQ

Why did my Nether reset when I switched from Paper to Fabric?

Fabric uses the Vanilla folder structure and looks for the Nether inside world/DIM-1. Because your Nether was still sitting in world_nether/DIM-1, Fabric couldn't find it and generated a brand new DIM-1 folder.

What do I do with the data,poi, and entities folders inside DIM-1 and DIM1?

Keep them inside DIM-1 and DIM1! When you move the DIM-1 or DIM1 folder as a whole, those subfolders move with it, preserving your villager workstations, entities, and raid data for that dimension.

Do I need to convert the .mca region files when switching between Paper and Vanilla?

No, the region file format is identical for the same Minecraft version. You only need to rearrange the folder hierarchy.

To switch between Vanilla/Fabric and Paper/Bukkit, simply move the DIM-1 and DIM1 folders between the main world directory and the separate world_nether and world_the_end directories.

More server world admin guides

Server world adminHow to Set a Server World Border and Delete All Chunks Outside ItUnrestricted exploration on a Minecraft Java Edition server can quickly bloat your world size to tens of gigabytes. By establishing a hard world border and purging all generated terrain beyond it, you can drastically reduce disk usage and speed up server backups. This guide shows you how to configure your border settings in level.dat and delete out-of-bounds chunks using our browser-based tools, where your files are processed locally and never uploaded.JavaIntermediate5 steps
Server world adminHow to Move Your Server Spawn Point and Adjust Spawn Chunk RadiusRelocating your server's default arrival point and trimming the permanently loaded area around it is one of the fastest ways to boost server performance and organize your player hub. By modifying the master configuration file of your Minecraft Java Edition world, you can set exact arrival coordinates and fine-tune how many chunks stay active in memory at all times. This guide walks you through safely editing these tags right in your browser without uploading any files.JavaIntermediate5 steps
Server world adminHow to Pre-Generate a Server World and Verify Coverage in the Map ViewerGenerating new terrain on the fly is the single biggest cause of server lag in Minecraft Java Edition. By pre-generating chunks within a set world border before players join, you shift that heavy CPU workload to an idle setup period. After running the generation task, you can use our browser-based World Map Viewer to visually audit your region files and ensure there are no missing gaps in the terrain.JavaIntermediate5 steps
Server world adminHow to Prepare and Shrink a SMP Server World Download at the End of a SeasonAt 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.Java & BedrockIntermediate5 steps
Server world adminHow to Reset the Nether or the End Dimension Without Losing Your OverworldResetting the Nether or the End is the best way to generate new update features, refresh looted structures, or shrink an overgrown save file without losing your Overworld builds. Whether you play on Java or Bedrock Edition, you can either wipe a dimension completely or use our browser-based Chunk Trimmer to selectively delete unused areas while preserving your Nether hubs and End farms. Because our tools run entirely in your browser, your world files are processed locally and never uploaded to any server.Java & BedrockBeginner5 steps