{"id":2724,"date":"2023-03-04T21:05:29","date_gmt":"2023-03-04T21:05:29","guid":{"rendered":"https:\/\/xgamingserver.com\/blog\/?p=2724"},"modified":"2026-06-15T19:20:45","modified_gmt":"2026-06-15T19:20:45","slug":"how-to-change-the-level-type-of-your-minecraft-server","status":"publish","type":"post","link":"https:\/\/xgamingserver.com\/blog\/how-to-change-the-level-type-of-your-minecraft-server\/","title":{"rendered":"How to change the Level Type of Your Minecraft Server"},"content":{"rendered":"\n

The level-type<\/code> setting in your Minecraft server’s server.properties<\/code> file decides how the entire world is shaped: rolling vanilla terrain, a pancake-flat creative canvas, towering amplified mountains, or a single endless biome. Changing it is a one-line edit, but there is a catch that trips up almost everyone the first time: editing the value alone does nothing to an already-generated world. You have to regenerate the level for the new type to take hold. This guide walks through every valid level type, the modern minecraft:<\/code>-prefixed syntax versus the old bare names, custom superflat configuration with generator-settings<\/code>, how the world seed interacts with all of this, and the exact regeneration steps so you do not lose work by accident.<\/p>\n\n\n\n

What level-type actually controls<\/h2>\n\n\n\n

level-type<\/code> is a single key in server.properties<\/code>, the plain-text configuration file that Minecraft Java Edition reads once at startup. The format is key=value<\/code>, one entry per line, no quotes. The default value is minecraft:normal<\/code>, which produces the standard overworld generation most players expect.<\/p>\n\n\n\n

The level type is a world-generation preset<\/em>. It tells the server which algorithm to use the moment a chunk is created for the first time. Because of that, it only affects brand-new chunks. The terrain you have already explored is frozen in the region files on disk, so flipping the value does not retroactively reshape an existing map. We come back to that critical point below, but keep it in mind as you read.<\/p>\n\n\n\n

The five built-in level types<\/h2>\n\n\n\n

Modern Minecraft Java Edition ships with five world-generation presets. Since version 1.19, the server expects the namespaced minecraft:<\/code> prefix on each one. Here is what each does:<\/p>\n\n\n\n

Value (1.19+)<\/th>Legacy name (pre-1.19)<\/th>What you get<\/th><\/tr><\/thead>
minecraft:normal<\/code><\/td>default<\/code><\/td>Standard overworld: biomes, caves, oceans, mountains. The default.<\/td><\/tr>
minecraft:flat<\/code><\/td>flat<\/code><\/td>Superflat \u2014 layered slabs of blocks, no terrain features. Great for creative builds and minigames.<\/td><\/tr>
minecraft:large_biomes<\/code><\/td>largeBiomes<\/code><\/td>Same generation as normal but biomes are scaled up roughly 4x, so each is much larger.<\/td><\/tr>
minecraft:amplified<\/code><\/td>amplified<\/code><\/td>Exaggerated, extreme terrain with massive peaks and overhangs. Demanding on CPU.<\/td><\/tr>
minecraft:single_biome_surface<\/code><\/td>(buffet, older snapshots)<\/td>One biome stretched across the whole world. Configured via generator-settings<\/code>.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

You can also point level-type<\/code> at a custom world-generation preset supplied by a datapack, using that datapack’s namespaced ID. That is an advanced route most servers will never need, but it is the same mechanism \u2014 the bundled presets are simply the ones Mojang ships in the game.<\/p>\n\n\n\n

normal vs large_biomes vs amplified at a glance<\/h3>\n\n\n\n

If you want a recognizable survival world, stay on minecraft:normal<\/code>. Choose minecraft:large_biomes<\/code> when you want sprawling deserts and forests that take a long walk to cross \u2014 it is identical generation logic, just zoomed out. Reach for minecraft:amplified<\/code> only if your hardware can handle it: the dramatic terrain means far more blocks per chunk to generate and render, which raises CPU and memory pressure noticeably. On a small box, amplified worlds can cause lag spikes during exploration.<\/p>\n\n\n\n

Modern minecraft: prefix vs legacy bare names<\/h2>\n\n\n\n

This is the single most common reason a level-type change “does not work.” Before version 1.19, the value was a bare keyword: default<\/code>, flat<\/code>, largeBiomes<\/code>, amplified<\/code>. From 1.19 onward, Minecraft uses the namespaced form with the minecraft:<\/code> prefix and a slightly different naming scheme (note normal<\/code> instead of default<\/code>, and the snake_case large_biomes<\/code>).<\/p>\n\n\n\n

On a current server, write the prefixed value:<\/p>\n\n\n\n

level-type=minecraft:flat<\/code><\/pre>\n\n\n\n
On an older server (pre-1.19), the bare name is what works:<\/p>\n\n\n\n
level-type=flat<\/code><\/pre>\n\n\n\n
If you put a bare name into a 1.19+ server, or a prefixed name into a very old one, the server typically falls back to normal generation and you end up scratching your head over a flat-looking-not-flat world. Always match the syntax to your server version. When in doubt, use the prefixed form \u2014 that is the correct value for every modern build and for the calendar-versioned releases that followed the 1.21 line.<\/p>\n\n\n\n
Step-by-step: changing the level type<\/h2>\n\n\n\n
  1. Stop the server completely. server.properties<\/code> is only read at startup, so editing it while the server runs accomplishes nothing until a restart \u2014 and a clean stop avoids the file being overwritten on shutdown.<\/li>
  2. Open server.properties<\/code> in your control panel’s file editor or via SFTP.<\/li>
  3. Find the level-type<\/code> line and set your chosen value, for example level-type=minecraft:amplified<\/code>.<\/li>
  4. If you are switching to or from a generated world, plan to regenerate (see the next section) \u2014 otherwise the change will only apply to chunks you have never visited.<\/li>
  5. Save the file and start the server.<\/li><\/ol>\n\n\n\n
    Most managed hosts surface server.properties<\/code> directly in the panel so you do not need to touch SFTP at all. If you are setting up from scratch, our Minecraft server documentation<\/a> walks through where each file lives and how to edit it safely.<\/p>\n\n\n\n
    The catch: you must regenerate the world<\/h2>\n\n\n\n
    Here is the part the brief flags as the number-one gotcha, and it deserves its own section. level-type<\/code> is applied only when a world is generated<\/strong>. If you already have a world<\/code> folder full of explored terrain, changing the value and restarting will leave your existing area exactly as it was. New chunks at the far edges of the map will use the new type, producing an ugly seam where flat meets normal, or amplified meets flat. To get a fully new world in the new type, you must delete (or move aside) the existing world data so the server generates fresh.<\/p>\n\n\n\n
    By default the world folders are named world<\/code> (overworld), world_nether<\/code>, and world_the_end<\/code> \u2014 the names follow the level-name<\/code> value in server.properties<\/code>. To regenerate:<\/p>\n\n\n\n
    1. Stop the server.<\/li>
    2. Back up<\/strong> the existing world folders first if there is any chance you want them later. Download them or rename them rather than deleting outright.<\/li>
    3. Delete the world<\/code>, world_nether<\/code>, and world_the_end<\/code> folders (or just rename them to something like world_old<\/code>).<\/li>
    4. Confirm your level-type<\/code> (and any level-seed<\/code> or generator-settings<\/code>) values are correct.<\/li>
    5. Start the server. It will generate a brand-new world using the new level type.<\/li><\/ol>\n\n\n\n
      A neat trick if you do not want to delete anything: change level-name<\/code> to a new value, for example level-name=world_flat<\/code>. The server cannot find a world by that name, so it creates one from scratch using your current level-type<\/code> \u2014 and your old world stays untouched on disk under its original name. You can switch back later by pointing level-name<\/code> at the old folder.<\/p>\n\n\n\n
      Custom superflat worlds with generator-settings<\/h2>\n\n\n\n
      Setting level-type=minecraft:flat<\/code> gives you the default superflat layout: a layer of bedrock, two layers of dirt, and a layer of grass, on a plains biome. But you do not have to accept that. The generator-settings<\/code> key lets you define your own layer stack, biome, and structures. It is paired with the flat level type and is ignored by the other types.<\/p>\n\n\n\n
      The cleanest way to author the value is to build the preset in the single-player Customize screen (when creating a superflat world), copy the preset code, and paste it into generator-settings<\/code> on the server. Modern versions use a JSON object for this key. For example, a thicker superflat with extra stone layers and a desert biome looks conceptually like this:<\/p>\n\n\n\n
      level-type=minecraft:flat\ngenerator-settings={\"layers\":[{\"block\":\"minecraft:bedrock\",\"height\":1},{\"block\":\"minecraft:stone\",\"height\":10},{\"block\":\"minecraft:sand\",\"height\":2}],\"biome\":\"minecraft:desert\"}<\/code><\/pre>\n\n\n\n
      The exact JSON keys and accepted block IDs depend on your game version, so the safe workflow is always: generate the preset in the client’s flat-world customizer for your version, then copy that string into the server file rather than hand-writing it. Remember that, like the level type itself, generator-settings<\/code> only takes effect on world generation \u2014 change it, then regenerate the world.<\/p>\n\n\n\n
      The single_biome_surface<\/code> type works similarly: it reads a biome from generator-settings<\/code> and stretches that one biome across the entire normal-style terrain, giving you, say, an endless jungle or an all-mushroom-fields world.<\/p>\n\n\n\n
      How level-seed interacts with level-type<\/h2>\n\n\n\n
      The level-seed<\/code> key sets the seed for world generation. The level type and the seed work together but answer different questions: the type chooses the generation algorithm<\/em>, and the seed chooses the specific random layout<\/em> that algorithm produces. A given seed will produce a different-looking world under minecraft:normal<\/code> than under minecraft:large_biomes<\/code>, because the underlying algorithm differs even though the random input is the same.<\/p>\n\n\n\n
      If you want a reproducible world \u2014 for example to share a specific spawn area or to recreate a known map \u2014 set both keys before generating:<\/p>\n\n\n\n
      level-type=minecraft:large_biomes\nlevel-seed=192837465<\/code><\/pre>\n\n\n\n
      Both keys are read at generation time. Changing level-seed<\/code> on an existing world does nothing to already-generated chunks for the same reason level-type<\/code> does not \u2014 the layout is already committed to disk. Leave level-seed<\/code> blank to let the server pick a random seed. For superflat worlds, the seed has little visible effect since the terrain is uniform, but it still influences things like slime-chunk locations.<\/p>\n\n\n\n
      Frequently asked questions<\/h2>\n\n\n\n
      Why did changing level-type not change my world?<\/h3>\n\n\n\n
      Because level-type<\/code> is applied only when a world is first generated. Your existing world<\/code> folder already contains generated chunks, so the server keeps using them and ignores the new type for that area. Only never-before-visited chunks at the map’s edge will use the new value. To get a fully new-type world, back up and delete (or rename) the world<\/code>, world_nether<\/code>, and world_the_end<\/code> folders, or change level-name<\/code> to a new name so the server generates fresh.<\/p>\n\n\n\n
      What is the difference between minecraft:flat and the legacy “flat” value?<\/h3>\n\n\n\n
      They mean the same world type but apply to different versions. From Minecraft Java 1.19 onward, the server expects the namespaced form level-type=minecraft:flat<\/code>. On pre-1.19 servers, the bare keyword level-type=flat<\/code> is correct. Using the wrong form for your version usually causes the server to fall back to normal generation. If you are on any current release, always use the minecraft:<\/code> prefix.<\/p>\n\n\n\n
      How do I make a custom superflat world on my server?<\/h3>\n\n\n\n
      Set level-type=minecraft:flat<\/code> and then define your layers in the generator-settings<\/code> key. The most reliable method is to build the preset in single-player using the flat-world Customize screen for your exact game version, copy the generated preset string, and paste it into generator-settings<\/code> in server.properties<\/code>. Then regenerate the world so the new generation settings take effect. Hand-writing the JSON works too, but copying from the client avoids version-specific syntax mistakes.<\/p>\n\n\n\n
      Can I keep my world and just change the level type?<\/h3>\n\n\n\n
      Not for the area you have already explored \u2014 generated terrain is permanent. What you can do is keep your old world while generating a new one in a different type by changing level-name<\/code> to a fresh name (for example world_amplified<\/code>). The server creates a new world under that name and leaves the original folder intact, so you can switch back later. For running several world types simultaneously, use the Multiverse plugin instead of swapping names.<\/p>\n\n\n\n
      Does the level seed work with every level type?<\/h3>\n\n\n\n
      Yes. level-seed<\/code> sets the random input for generation regardless of the level type, but the same seed produces different results under different types because each type uses a different algorithm. Set both level-type<\/code> and level-seed<\/code> before the world is generated for a reproducible map. On superflat worlds the seed has little visible effect on terrain, since the layout is uniform, though it still affects features like slime chunks.<\/p>\n\n\n\n
      Which level type is best for performance?<\/h3>\n\n\n\n
      Superflat (minecraft:flat<\/code>) is the lightest because there is minimal terrain to generate and render. minecraft:normal<\/code> and minecraft:large_biomes<\/code> are comparable mid-weight options. minecraft:amplified<\/code> is by far the heaviest \u2014 its extreme terrain demands much more CPU, memory, and bandwidth, so reserve it for capable hardware and consider trimming view-distance<\/code> and simulation-distance<\/code> to compensate. While you are tuning generation, it is worth tightening the rest of your config too, from enabling Paper’s anti-Xray<\/a> to controlling mob and animal spawns<\/a> on flat or minigame maps.<\/p>\n\n\n\n\n
      \n
      Free Minecraft Tools<\/h3>\n
      Speed up your server with our free Minecraft tools:<\/p>\n
      Performance and gameplay considerations<\/h2>\n\n\n\n
      Level type has a real impact on server load. minecraft:amplified<\/code> is the heaviest because each chunk contains dramatically more terrain to generate, store, and stream to players. If you run amplified on constrained hardware, pair it with a sensible view-distance<\/code> (the default is 10<\/code> chunks, valid range 3\u201332) and simulation-distance<\/code> to keep CPU and bandwidth in check. Superflat worlds are the lightest, which is part of why they are popular for minigame and build servers.<\/p>\n\n\n\n
      For survival servers that want big, immersive landscapes without the cost of amplified, minecraft:large_biomes<\/code> is a strong middle ground. If you are choosing a world type for a fresh community server and want headroom for whatever you pick, a well-provisioned host matters \u2014 our low-latency Minecraft hosting plans<\/a> are sized to handle amplified and heavily-modded generation without the lag a budget box introduces.<\/p>\n\n\n\n
      If juggling several worlds with different level types on one server sounds appealing, that is exactly what the Multiverse plugin is for. Instead of swapping level-name<\/code> by hand, you can keep a flat creative world, a normal survival world, and a custom map live at once and teleport between them. See our walkthrough on running multiple worlds with the Multiverse plugin<\/a> for the full setup.<\/p>\n\n\n\n