A data pack goes inside the world folder, in a subfolder named datapacks, not in a top-level folder next to the server jar. That is the short answer to where to put data packs on a Minecraft server. The world folder takes its name from level-name in server.properties, so the path is world/datapacks/ by default, though a renamed level-name or a multi-world setup can put it somewhere else. Get that location right and everything after it, loading the pack, handling world generation, verifying it worked, gets much easier.
Find the datapacks folder for your world
Every world a vanilla server runs has its own datapacks folder, the same as a singleplayer save. Check server.properties for the level-name value, since that string is the folder name the server actually uses, and datapacks sits directly inside it. A fresh server on default settings uses world/datapacks/, but a renamed level-name, or a second world added later, moves the folder and gives each world its own separate datapacks subfolder.
- Open server.properties and read the level-name value, that is the exact folder name to look for.
- Go into that world folder, not the server's root directory next to the jar or the plugins folder.
- Create a folder named exactly datapacks inside it if one is not already there.
- Drop the pack's zip file or unzipped folder straight into datapacks, without nesting it inside another folder first.
Browse our data packs section for ready-to-install packs if you are starting from scratch. Everything there installs into this same folder.
Load the pack without taking the server down
Data packs behave differently from server plugins here. A plugin usually needs a restart to load; a data pack can be picked up with /reload, run from the console or by an operator in-game. Type /datapack list to confirm the server sees the new pack, then /datapack enable "<pack name>" if it is not already active. That is the fastest way to install a datapack on a server you are not willing to take offline, though a full restart is still the safer default whenever you are not sure a pack is worldgen-only.
World generation packs need to go in before the world exists
Some data packs only add loot tables, recipes, or advancements, and those apply the moment you reload. Worldgen packs are different. Terralith, Incendium, and Structory all change how terrain, biomes, or structures generate, and that only affects chunks the server generates after the pack is active. Chunks that already exist keep their original terrain permanently; no reload or restart rewrites ground that has already generated.
- Installing before the server's first start applies the pack across the whole map as players explore it.
- Installing on a server with explored terrain only changes new chunks past the existing border.
- Mixing several worldgen packs works the same way, add them all before launch if you want one unified world.
Verify the pack actually loaded
Run /datapack list enabled from the console or as an operator to see exactly which packs are active right now, not just which ones the server found. A pack that fails to load usually prints its failure in the server console at startup or right after /reload, naming the pack and the reason it was skipped.
If that console error points at a missing pack.mcmeta, a pack_format that does not match your server version, or a pack nested inside an extra folder, those are packaging problems with the pack itself, not a server configuration issue. We cover them in detail in fixing data packs that will not show up.
Common questions
What does /datapack list show?
/datapack list shows every data pack the server has found, both enabled and available but disabled. Add enabled or available to narrow it, for example /datapack list enabled shows only what is active right now. It will not show a pack that was placed in the wrong folder, since the server never detected it in the first place.
Does a data pack apply to one world or the whole server?
A data pack applies to the single world whose datapacks folder holds it, not to the whole server. A standard vanilla server runs one overworld, nether, and end together as one world, so one datapacks folder covers all three. If you run multiple separate worlds, through a plugin like Multiverse or several server instances, each world needs its own copy of the pack in its own datapacks folder.
Do data packs need Forge, Fabric, or another mod loader?
No. Data packs are a vanilla Minecraft feature and load on a plain vanilla server jar, no mod loader required. That is what separates them from Java mods, which do need Forge, Fabric, NeoForge, or Quilt installed on the server to run. A data pack only needs the datapacks folder and a Minecraft version whose pack_format matches what the pack declares.
