How to Install Datapacks on a Minecraft Server

Datapacks vs plugins vs mods

All three change your server, but they are not the same thing, and mixing them up is the usual reason an install fails:

• Datapacks are built into vanilla Minecraft. They change data — recipes, loot tables, functions, structures — and load from a folder inside your world. No extra software, and players need nothing on their side.
• Plugins are server-side add-ons that need Paper or Spigot to run (see installing plugins). Datapacks work on plain Vanilla; plugins do not.
• Mods need a loader like Forge or Fabric and every player to install the same mods (see modded servers).

Because datapacks are vanilla and server-side, they are the lightest way to customise a survival or SMP server — and they run happily on Paper too, so you can combine datapacks and plugins on the same server.

Step 1: Find a datapack for your version

Datapacks are distributed as .zip files. The main sources are Modrinth and Planet Minecraft, plus creators' own pages.

1. Match your Minecraft version. This is the one thing that trips people up. A datapack built for an older version may refuse to load on a newer server because its pack.mcmeta declares a pack_format number tied to the game version. Download the release that lists your server's version.
2. Download the zip — do not unzip it. Minecraft loads the datapack as a .zip. Unzipping it is a common mistake (an unzipped folder can work too, but only if the inner structure is exactly right — the zip is safer).

Step 2: Install it in the world datapacks folder

Datapacks live inside a specific world, in that world's datapacks folder. This is the whole install:

1. Open your world folder. Every datapack path is <world>/datapacks/. If your world is named world, that is world/datapacks/.
2. Drop the zip in. Place the datapack .zip straight into that datapacks folder — no subfolders.
3. Load it. If the server is running, type /reload in the console or in-game; otherwise it loads on the next start. A brand-new datapack that adds world generation should be added before the world is first created.
4. Verify it loaded. Run /datapack list — your pack should appear in the enabled list. If a pack is present but disabled, enable it with /datapack enable "file/name.zip".

Where the folder is: self-hosted vs hosted

The folder is the same; only how you reach it differs.

• Self-hosted. The world sits in your server directory (or under saves/ for a single-player world you are converting), so the path is <server>/world/datapacks/. Copy the zip in with your file explorer.
• Hosted. Open the panel's file manager (or connect over SFTP), browse to world/datapacks/, and upload the zip — then run /reload from the web console. On a HytHost Minecraft server that is a drag-and-drop and a click, with one-click backups right there if you want a snapshot first.

If your server runs multiple worlds (a Nether/End split, or a multiverse setup), remember datapacks are per-world — install into the world you actually want them in.

Why a datapack will not load

Nearly every failed datapack comes down to one of these:

• Version mismatch. The pack's pack_format does not match your Minecraft version — the console warns about an incompatible pack. Get the release for your exact version.
• Wrong folder. It must be in the world's datapacks folder, not the server root or a resource-pack folder.
• You forgot to reload. Nothing happens until /reload or a restart. After that, confirm with /datapack list.
• It is actually a resource pack. Resource packs change how the game looks and are a client/server-list setting, not a datapack — they do not go in this folder.

Still stuck? Read the console on start-up or after /reload — datapack errors are printed there with the file name and the reason.

Running several datapacks well

• Watch for conflicts. Two datapacks that edit the same recipe or loot table can clash. Add them one at a time and test, so you know which one caused a problem.
• Order can matter. When packs overlap, load order decides which wins; you can set it with /datapack enable and its first/last/before/after options.
• Keep them versioned with your server. When you update Minecraft, update your datapacks too, or the mismatched ones stop loading.
• Combine with Paper for the best of both. Datapacks for vanilla-friendly content, plugins for management and protection — they coexist fine on a Paper server.