Install Minecraft datapacksChange game content without plugins and without mods

Published on October 20, 2026

What a datapack can do - and what it cannot

Datapacks are part of vanilla Minecraft. They access data that the game loads anyway and change it:

• Change, add or remove recipes.
• Adjust loot tables - what mobs and chests drop.
• Define your own advancements.
• Influence world generation and biomes.
• Build functions from command chains - the basis of many minigame packs.

What they cannot do: introduce new blocks, new items or new mobs in the real sense. For that, you need mods - see Install plugins & mods. The big advantage remains: players do not have to install anything; a normal client is enough.

Datapack or resource pack? A look inside the ZIP

Both are called "pack", come as a .zip and contain a pack.mcmeta - so they are often confused. The difference lies in the top-level folder inside the file:

• A data folder means datapack. It belongs on the server, more precisely in the world folder.
• An assets folder means resource pack. It belongs to the client and is delivered via a URL - the process is described in Set up a resource pack.

Some projects ship both halves together, because the datapack brings its own recipes and the resource pack the matching look. Then you need each half in its place: a datapack alone delivers working recipes, but items in the default look - and to players, that looks like a bug even though the server is doing everything right.

A datapack that ends up in the wrong folder is not reported, by the way, but simply ignored. If nothing at all happens after installation and there is no error message in the log either, that is the first suspect.

Installation step by step

Datapacks live inside the world folder - that is the most important difference from plugins and mods:

1. Stop the server.
2. Go to the world folder via WebFTP or SFTP - its name is set as level-name in server.properties, world by default.
3. Open the datapacks subfolder there. If it does not exist, create it.
4. Put the datapack's .zip file in as it is - do not unpack it.
5. Start the server.

An unpacked folder works too, as long as the pack.mcmeta sits directly inside it. The most common mistake is one folder too many: if the pack.mcmeta is two levels deep, Minecraft does not recognize the pack.

Check and manage

After the start, check in the console whether the pack was loaded:

/datapack list

The output separates enabled and available packs. Further useful commands:

• /datapack enable "file/name.zip" - enable a pack.
• /datapack disable "file/name.zip" - disable it without deleting the file.
• /reload - reload datapacks without restarting the server.

You need operator rights for this - how to get them is explained in Become OP & admin rights.

One restriction on /reload: on a Paper or Spigot server, the command reloads not only the datapacks but also the plugins - and that is considered risky there, because some plugins do not survive a reload cleanly. On a server with plugins, a scheduled restart is the calmer route. Changes to world generation only take effect after a restart anyway.

Datapacks apply per world

Because they live in the world folder, datapacks are tied to the respective world - not to the server. This has consequences:

• If you generate a new world, the datapacks of the old one are no longer active.
• If you upload your own world, it brings its datapacks with it.
• With several worlds, you have to put the pack in every world folder where it should take effect - see Multiple worlds.

Packs that change world generation must be installed before the world is first generated. Added later, they only affect newly generated areas - and the result looks ugly at the seam.

When a datapack does not load

• Wrong folder depth - the pack.mcmeta must be directly in the pack directory, not in a subfolder.
• Wrong directory - datapacks belongs in the world folder, not in the server directory.
• Version mismatch - the pack_format number in pack.mcmeta must match the Minecraft version. If it does not, the server reports this at startup.
• Pack disabled - if it shows up under "available" instead of "enabled", enable it with /datapack enable.

The exact message is in the log - where to find it is explained in Server does not start.

Remove a datapack cleanly

Uninstalling is more than deleting a file. This order leaves the fewest remnants:

1. Switch the pack off during operation with /datapack disable and briefly check in the game whether everything important still works.
2. Stop the server.
3. Remove the file from the world's datapacks folder.
4. Start the server and check with /datapack list that the pack appears neither under "enabled" nor under "available".

What remains even then is everything the pack has already done in the world: granted advancements, terrain from a world generation pack and items that players crafted via changed recipes. The latter do not disappear; they just behave like perfectly ordinary items afterwards.

If a pack has intervened deeply in the world, the clean way back is therefore not removing it, but restoring a backup from before - see Create backups. This is also why a backup before installing a larger pack for the first time makes more sense than any later repair. If the world is supposed to start fresh anyway, Reset the world gets you there faster.

Frequently asked questions