Chunks & world size · Java & Bedrock · Intermediate

How to Fix Harsh Chunk Borders and Wrong Biomes After Version Upgrades

Upgrading 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.

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

What you need

  • A complete backup of your Minecraft world folder or archive
  • Access to the Chunk Trimmer tool on our site
  • Minecraft Java Edition or Bedrock Edition (version 1.18 or newer is required for automatic terrain blending)

Step by step

  1. 1Back Up Your World Files

    Before altering any terrain data, locate your world save folder and create a duplicate copy in a safe location. For Java Edition, this folder contains your level.dat file and region folder; for Bedrock Edition, it contains level.dat and the db folder. If you accidentally delete a chunk containing part of your base, this backup is the only way to restore it.

    Tip: Compressing your backup folder into a .zip file prevents you from accidentally opening or modifying the backup while working.

  2. 2Load Your World into the Chunk Trimmer

    Open the Chunk Trimmer tool on our website. Click to open your world folder or drag and drop a .zip archive of your world directly into the browser window. Because the tool runs locally in your browser, your files are processed instantly on your device without being uploaded.

    Tip: Ensure Minecraft is completely closed before opening the world folder so your operating system does not lock the files.

  3. 3Identify the Harsh Borders and Unbuilt Chunks

    Use the 2D map view to locate your main builds and trace outward to find the jagged edges or explored trails where you walked during older updates. The logic here is that Minecraft cannot blend two chunks that already exist in your save file, even if they were generated in different updates. You must identify the buffer of explored, unbuilt chunks sitting along the edges of your actual builds.

    Tip: Switch between dimensions (Overworld, Nether, End) using the dimension selector if you also want to refresh outer Nether wastes or End islands.

  4. 4Select and Prune the Boundary Chunks

    Use the selection brush or box tool to highlight the unwanted outer chunks, or select your core builds and use the invert selection option to target everything outside your safe zone. You can also filter by the InhabitedTime tag in Java Edition to automatically highlight chunks players simply flew past without spending time building in. Once you have verified that no important structures are highlighted, click the trim button to delete those chunks and download the modified world.

    Tip: Leave a small buffer of two to three original chunks around your builds so the terrain blending slope does not warp the ground directly under your walls.

  5. 5Trigger Biome and Terrain Blending in Minecraft

    Replace your old world save with the newly trimmed world folder (extracting it first if it downloaded as a .zip). Launch Minecraft in the newest version, load the world, and travel to the edges you just pruned. As the game generates new chunks next to your trimmed borders, its internal blending algorithm will detect the version mismatch at the edge and smoothly interpolate the terrain height and biomes.

How it works

In Minecraft Java Edition, terrain is stored in the region folder as Anvil (.mca) files, where each file holds a 32x32 grid of chunks. In Bedrock Edition, chunk data is stored as key-value pairs inside the LevelDB database (the db folder). Each generated chunk stores its block data, biome palette, and a DataVersion tag (or equivalent version header in Bedrock) that records which version of the game created it.

When you walk into a brand-new area in modern Minecraft versions (1.18 and above), the world generator checks the existing chunks immediately bordering the empty space. If it sees an older chunk next to an empty slot, the game activates its blending algorithm. It samples the heightmap, terrain density, and biome data of the old chunk and gradually morphs the new chunk's generation noise to match, eliminating flat 90-degree chunk walls.

However, if you already explored an area after upgrading—or if you have a ragged border of half-generated chunks—both sides of the border already exist in the .mca or db files. Minecraft will never overwrite an existing chunk's blocks during normal gameplay. By using the Chunk Trimmer to completely erase the outer chunk records from the region files or database, you create a clean boundary between your old chunks and empty void, allowing the blending engine to do its job when you return to that area.

Common mistakes

  • Trimming chunks while the world is still open in Minecraft, which causes file conflicts and causes the game to overwrite your trimmed regions from memory when you save and quit.
  • Pruning right up against the wall of a build without leaving a buffer chunk, causing the blending slope to raise or lower blocks immediately adjacent to your structure.
  • Relying solely on low InhabitedTime filters without visually inspecting the map, which can delete long minecart railways, redstone lines, or nether ice highways that players pass through quickly.
  • Expecting smooth terrain blending in game versions prior to 1.18, as the modern chunk blending mechanic did not exist in earlier releases.

FAQ

Why did the biome color change inside my existing base after an update?

Sometimes a chunk's saved biome ID shifts if an update renames biomes or if a chunk was only partially generated (proto-chunk) before upgrading. Trimming unbuilt surrounding chunks helps smooth the transition at the edge, while changing biomes inside an already built chunk requires an NBT or biome editor.

Does pruning chunks reduce my world's file size?

Yes. Deleting thousands of explored but unused chunks removes their data from the .mca region files or LevelDB database, often shrinking world sizes by hundreds of megabytes.

Will deleting chunks break structures like bounding boxes for Witch Huts or Nether Fortresses?

If you delete a chunk containing a structure, it will regenerate using the new version's seed rules and structure layouts. If you depend on an old farm's specific bounding box, do not trim the chunks containing that structure.

To fix harsh chunk borders after an update, back up your world, use the Chunk Trimmer to delete unbuilt outer chunks around your base, and reload the world in the latest version so Minecraft's terrain blending smoothly connects the old edges to new generation.

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 sizeWhy You Must Clean entities and poi Folders When Deleting Region ChunksWhen 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.JavaIntermediate4 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 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