How to Install a Minecraft Data Pack

A data pack changes how Minecraft behaves using nothing but the vanilla game — loot tables, recipes, mob drops, advancements, the world border, whole chains of commands. There is no loader to install, no mods folder, and in multiplayer nobody but the host needs the file. You drop a zip into one folder inside one world save, reload, and the rules of that world are different.

What a data pack is, and what it is not

Minecraft already reads a large part of its own behaviour from JSON files: what a block drops, what a recipe needs, when an advancement fires, what a damage type does, how the world generates. A data pack is a bundle of replacement files for exactly that layer. The game loads it natively — no third-party code runs at any point.

Two things it cannot do. It cannot add a genuinely new block or item to the game, and it cannot change a single pixel of a texture. When a pack looks like it adds a custom sword, it is reusing a vanilla item with a model swap that ships in a separate resource pack alongside it.

• Against a mod. Mods run actual code. They need Fabric, Forge or NeoForge, they live in the mods folder of your install, they affect every world you open, and in multiplayer every player usually needs the same jars. That is a different job entirely — installing mods walks through it, and the catalogue is at MineSpecs Mods.
• Against a resource pack. Resource packs are the client's half of the split: textures, sounds, models, fonts, language files. They go in the resourcepacks folder, get switched on in Options, and apply to every world. If that is what you actually want, see installing resource packs. Shaders are a third thing again — rendering, loaded through Iris or OptiFine, covered in the shader guide.
• The short version. A resource pack changes what you see. A data pack changes what happens. A mod changes what the game is capable of.

Check the zip before you move it

Most failed installs are a zip packaged one folder too deep. A valid data pack has pack.mcmeta at the very top level of the archive, sitting next to a folder called data. Nothing above them.

Open the zip and look. If the first thing inside is a single folder named after the pack, with pack.mcmeta buried in there, Minecraft will not read it. To fix it: open that folder, select pack.mcmeta and the data folder, and compress those two items directly. On Windows 11 that is right-click, then Compress to ZIP file; on Windows 10, or under Show more options in the Windows 11 menu, it is right-click, Send to, Compressed (zipped) folder.

Two more things worth a glance:

• File extensions. If Windows is hiding known extensions, a downloaded pack.mcmeta can quietly be pack.mcmeta.txt, which the game skips. Turn extensions on in File Explorer's View menu and check.
• Version. pack.mcmeta declares a pack_format number. If it does not match the version you are running, the game flags the pack as incompatible; well-maintained packs declare a supported range so one file covers the whole 1.21 line. There is a separate clue for old packs: 1.21 renamed the internal folders from plural to singular — loot_table, recipe, advancement, function. Every version before 1.21 used the plural names, 1.20.6 included, and a pack still built that way loads without a single error while doing absolutely nothing.

Find the world folder

The fast route skips the file system entirely. On the title screen go to Singleplayer, click your world once to select it, click Edit, then Open World Folder. The correct folder opens.

Navigating manually, the saves folder lives at:

• Windows — press Win+R, type %appdata%, press Enter, then open .minecraft and then saves.
• macOS — in Finder press Shift+Cmd+G and enter ~/Library/Application Support/minecraft, then open saves. Note there is no dot in the folder name on Mac.
• Linux — your home folder, then .minecraft (press Ctrl+H to show hidden folders), then saves.

If you launch through Prism, MultiMC, the Modrinth app or the CurseForge app, none of those paths apply. Each instance keeps its own .minecraft, and every one of those launchers has an open-folder option on the instance itself. Use that.

Drop the zip into datapacks

Inside the world folder you will see region, playerdata, level.dat and, usually, datapacks. Put the zip in there. If the folder does not exist, create one named exactly datapacks, all lowercase.

You have a choice of format: a data pack works zipped or as a plain extracted folder, as long as pack.mcmeta is at the top level of whichever you use. Leaving it zipped is tidier and easier to remove later.

Now load it. Either quit to the title screen and reopen the world, or stay in-game and run /reload, which re-reads the datapacks folder and picks up anything newly added. Freshly discovered packs come in enabled.

Verify with /datapack list

Guessing is not necessary. Run /datapack list and the game prints two separate groups:

• Enabled is what is currently affecting the world. Your pack should be in here, listed as file/YourPack.zip.
• Available is not a master list of everything in the folder. It is everything the game found there that is not currently switched on, so the two groups never overlap — which is why the game answers that there are no more data packs available once every pack is on. A pack sitting under available is installed correctly and simply turned off.
• If it is in neither, the game never saw it as a pack at all. That is the zip structure, the wrong world folder, or a broken pack.mcmeta — in that order of likelihood.

Both /datapack and /reload need cheats. In a singleplayer world created without them, press Esc, choose Open to LAN, set Allow Cheats to ON and start the LAN world. Commands work for the rest of that session, and a pack you enable that way stays enabled afterwards.

Enabling, disabling and load order

The pack name in commands is the one the list command printed, quotes included:

• /datapack disable "file/YourPack.zip" switches it off immediately. The file stays where it is.
• /datapack enable "file/YourPack.zip" switches it back on.
• /datapack enable "file/YourPack.zip" last puts it at the end of the load order, which is the winning end. There are also first, before and after variants for exact placement.

Order matters the moment two packs touch the same file. If both replace the diamond ore loot table you do not get a merge — the one loaded later wins outright and the earlier one silently does nothing for that block. Tags are the one exception: two packs adding to the same tag have their entries combined, unless one of them sets replace to true and throws the earlier list away. So if a pack is definitely enabled and still seems to do nothing, load order is the first thing to check.

You can also load packs before a world exists. On the world creation screen open the More tab and click Data Packs: drag zips straight onto that screen to copy them into the new save, then move them from available to selected. Anything incompatible with your version is flagged there, before you generate the world rather than after.

Packs apply per world, not per install

This is the part that trips up anyone arriving from mods or resource packs, and it is worth being blunt about: a data pack belongs to a world, not to your game. The file lives inside that save folder and the enabled list is stored in the world's data. Install one and your other worlds are untouched. Start a new world and you start again from plain vanilla.

The upside is that packs travel with the save. Zip the world folder, send it to a friend, and the packs go with it already enabled. Put the same world on a server and it behaves identically — on a server the datapacks folder sits inside the level directory, which is the folder named by level-name in server.properties, normally just world. Drop the zip in, then restart or run /reload from the console. Players joining install nothing, because none of it is client-side.

Removing one cleanly

Disable it, delete the zip, reload. Loot tables, recipes and advancements go back to vanilla at once.

What does not clean itself up is what the pack did while it ran. State stays: scoreboard objectives, teams and any game rules it changed are exactly as it left them. So does anything it physically put into the world — items it handed you, mobs it summoned and blocks it placed are ordinary world data now and survive the removal. Strip leftover objectives with /scoreboard objectives remove and put game rules back by hand if the pack's page does not list them.

One real caution. Packs that alter world generation or add dimensions should not be pulled out of a world you care about. Terrain already generated stays as it is, new chunks generate as vanilla, and the seam between the two is permanent. If a player is standing in a custom dimension when its pack disappears, expect trouble. Copy the whole save folder somewhere safe before adding or removing anything of that kind — thirty seconds of work against losing a world.

Where to get packs

MineSpecs hosts 20 original "Minecraft, but" data packs at /data-packs/ — ores that drop tenfold, hostile mobs that pay out real loot, a border that shrinks while you play, kills that hand you extra hearts. Each one is written here for Java 1.21 or later, with the few that need 1.21.2 or 1.21.4 labelled on their own pages, released under CC0, and served straight from the site rather than through a chain of ad redirects. They are all zipped correctly with pack.mcmeta at the root, so the entire install is: download, drag into datapacks, run /reload, confirm with /datapack list. Pick one, try it on a fresh world rather than your main save, and if you do not like what it does, disable it and the world goes straight back to vanilla.