How to enable data packs in Minecraft: new worlds, old worlds, servers
Where a data pack goes, how it gets switched on in each case, the /datapack commands and the quoting they need, and the Experiments packs you can never add later.
A data pack is a folder or .zip with a pack.mcmeta file and a data folder at its root. It belongs to one world: it lives in that world's datapacks folder and is enabled per world. How you switch it on depends on whether the world exists yet.
A new world: the Data Packs button
- Create New World, then open the More tab.
- Click Data Packs. The screen says "Drag and drop files into this window to add packs" — drop the
.zipor folder on it, confirm, and it appears under Available. - Move it to Selected and click Done. Packs higher in the Selected list override the ones below them.
If a pack is broken, world creation stops at "Data pack validation failed!" with Go Back and Reset to Default — the second one drops every non-vanilla pack, so go back and remove the bad one instead.
Experiments: decide before you create
The Experiments button on the same tab lists Mojang's own feature packs. In 26.3 there are three, all shipped inside the game jar: Minecart Improvements, Redstone Experiments and Villager Trade Rebalance. The game's own warning is literal: "Experiments can't be turned off after world creation." They can't be turned on afterwards either — trying gives "cannot be enabled, since required flags are not enabled in this world".
An existing world: the datapacks folder
- On the singleplayer list, select the world, click Edit, then Open World Folder.
- Put the
.zipor folder intodatapacksinside it. - Load the world. A pack that is new to the world is enabled automatically when it loads, unless it needs an experiment the world was not created with.
If the world is already open with commands allowed, /reload does the same without leaving: it enables every pack in the folder that was not deliberately disabled before.
The /datapack commands
/datapack needs permission level 2 — cheats on in singleplayer, operator on a server.
/datapack list every pack, enabled and available
/datapack list available packs found but switched off
/datapack enable "file/my_pack.zip" switch one on
/datapack enable "file/my_pack.zip" first …at the lowest priority
/datapack disable "file/my_pack.zip" switch it off againTwo details catch everyone. A pack from the folder is named file/ plus its folder or zip name. And because that name contains a slash, it has to be in double quotes; typed bare, the command cannot read past the slash and fails. enable also takes last, before <pack> and after <pack> to set where it lands in the load order.
/datapack create <id> <description> makes a new, empty pack in the world's folder. It needs permission level 4, the level of a server's owner.
On a server
Put packs in the datapacks folder of the world directory — world/datapacks unless level-name says otherwise — then /reload from the console or restart. The initial-enabled-packs and initial-disabled-packs settings in server.properties only apply when the server creates a brand-new world, which is where experiment packs have to be named. If a pack stops a server from starting, the --safeMode start-up option loads the world with the vanilla pack only.
When a pack does not show up, or does nothing
A pack that never appears in /datapack list usually has its pack.mcmeta one folder too deep — zipping the folder instead of its contents does that. One that appears but changes nothing usually has its files in the wrong folders or namespace. 26.3 expects data pack format 121 in pack.mcmeta. Our guide to the folder structure and the three names that must match has the exact tree.
Building the pack in the first place is easier in the browser: the Datapack Studio assembles recipes, loot tables and functions into a zip with a correct pack.mcmeta, ready to drop onto the Data Packs screen.