
level.dat & world settings · Java & Bedrock · Intermediate
How to Enable Experimental Features and Datapacks on an Existing World
Normally, Minecraft locks experimental features and built-in experimental datapacks behind the world creation screen, forcing you to start a new game to test upcoming mechanics. By directly editing your world's root configuration file, you can unlock these experiments on an existing survival save without losing your progress. Our browser-based level.dat Editor lets you modify these feature flags safely and locally on your device without uploading any files.
What you need
- An existing Minecraft world save (Java Edition or Bedrock Edition)
- A complete backup copy of your world folder or archive
- Access to our browser-based level.dat Editor
- The exact internal name of the experimental feature or datapack you want to enable
Step by step
1Back Up Your World Save
Before making any changes to core world files, close Minecraft completely and locate your world save folder on your device. Create a duplicate copy of the entire world folder or compress it into a backup zip archive. Because experimental features actively alter world generation and item registry data, having a clean backup is mandatory in case an experiment causes instability or corruption.
Tip: Always make sure Minecraft is not running your world in the background while you copy or edit its files.
2Find the Exact Feature Flag Names
If you do not know the exact internal ID for a specific update's experiment, launch Minecraft and create a temporary dummy world with that exact experimental toggle turned on. Load into the dummy world briefly, save and quit, and then locate its save folder. You can open this dummy world's level.dat file in our editor first to inspect the exact string names Minecraft generated for your current game version.
Tip: Feature flag IDs change across major updates as experimental mechanics graduate into the base game.
3Load Your World into the level.dat Editor
Open the level.dat Editor in your browser and select Open world folder or .zip (or choose the level.dat file directly from your save directory). The tool reads your file directly in your browser's memory without uploading anything over the internet. Once loaded, expand the root Data compound tag in the tree view to inspect your world's configuration.
4Add Java Edition Feature Flags and Datapacks
For Java Edition worlds, locate or create the enabled_features list tag inside the Data compound. Add a new string entry to this list using the exact resource location of the experiment, such as minecraft:bundle or minecraft:trade_rebalance. Next, expand the DataPacks compound tag, open the Enabled list tag, and add the exact same feature name as a string entry there, ensuring it is also removed from the Disabled list if present.
Tip: In Java Edition, an experimental feature will not function unless it is listed in both enabled_features and DataPacks -> Enabled.
5Enable Bedrock Edition Experimental Toggles
For Bedrock Edition worlds, locate the experiments compound tag inside the root tree of your level.dat file. Inside this compound, examine or create byte tags corresponding to the specific experiment you want, such as cameras, data_driven_biomes, or upcoming_creator_features, and set their value to 1. You must also create or locate the experiments_ever_used and saved_with_toggled_experiments byte tags inside the same compound and set both of their values to 1.
Tip: If you are unsure of the exact Bedrock byte tag name for a brand-new update, inspect a dummy world created with that toggle turned on.
6Save and Replace Your level.dat File
Once you have added the required tags and verified their spelling, click the Save or Download button in the level.dat Editor to export your modified file. Move the newly downloaded level.dat file into your world's save folder, overwriting the original file. Launch Minecraft and load your world; you may see an experimental features warning prompt, which confirms the game recognizes your newly activated flags.
Tip: Delete or rename level.dat_old in your world folder if Minecraft attempts to revert your changes using its automatic backup file.
How it works
Minecraft stores global world rules, seed data, and active expansion flags inside the level.dat file using the Named Binary Tag (NBT) format. When you toggle an experiment on the world creation screen, the game simply writes specific string or byte flags into this file before generating the first chunks. The game engine locks these UI buttons after creation to prevent players from accidentally breaking item registries, even though the underlying engine can enable them at any time.
In Java Edition, experimental mechanics are packaged as built-in datapacks that are gated behind feature flags. The game checks the enabled_features list during world load to unlock the internal code registries, and then loads the corresponding recipes, loot tables, and world generation rules from the DataPacks compound. Both entries must match because the datapack cannot load its assets if the underlying code flag is still locked.
In Bedrock Edition, the engine uses a slightly cleaner system but applies a different NBT structure. Bedrock level.dat files contain an uncompressed header followed by little-endian NBT data, where the experiments compound holds boolean byte tags (0 for false, 1 for true). Setting the master flag experiments_ever_used to 1 tells the Bedrock engine to bypass standard vanilla validation and evaluate the individual experimental toggles during world initialization.
Common mistakes
- Adding the feature string to enabled_features in Java Edition but forgetting to add the matching string to the DataPacks -> Enabled list.
- Omitting the minecraft: namespace prefix on Java Edition feature strings (for example, typing bundle instead of minecraft:bundle).
- Forgetting to set experiments_ever_used and saved_with_toggled_experiments to 1 in Bedrock Edition, which causes the game to ignore individual experiment byte flags.
- Expecting new experimental terrain or structures to appear in chunks you have already explored; new generation rules only apply to newly generated chunks.
- Trying to disable an experiment later by deleting the tags, which often causes the game to crash or delete unknown blocks and items from player inventories.
FAQ
Can I turn off experimental features after enabling them in level.dat?
It is strongly discouraged. Once a world is saved with experimental features active, new item IDs, block states, or biome data become baked into your region files. Removing the tags later can cause Minecraft to crash on load or refuse to open the world.
Will enabling experimental features disable achievements in Bedrock Edition?
Yes. In Bedrock Edition, setting the experimental byte flags to 1 flags the world as modified, which permanently disables achievement unlocks for that specific save file.
Why aren't new experimental structures or biomes spawning in my world?
World generation changes only affect chunks that have never been loaded before. You must travel to unexplored areas of your world to see new experimental terrain or structures.
Is my world uploaded to a server when I use the level.dat Editor?
No. All tools on our site run entirely inside your web browser using local processing. Your world files never leave your computer.
By adding the proper NBT feature flags and datapack entries in the level.dat Editor, you can safely unlock upcoming Minecraft experiments on any existing survival world.