DayZ · Mods

How to install mods on a DayZ server

Install Steam Workshop mods on a DayZ server: download them, copy the .bikey keys, set -mod and -servermod, add loot entries and fix common errors.

Last updated 2026-10-09

Installing Steam Workshop mods on a DayZ server comes down to three things: the mod folders, their .bikey keys, and the -mod launch parameter that loads them. Skipping any one step is how most “my mod doesn’t work” problems start, so follow them in order.

1. Get the mod files from the Steam Workshop

Every mod lives on the Steam Workshop and has a numeric ID in its URL. You can download mods by subscribing in the game launcher, or straight to the server with SteamCMD:

steamcmd +login <your steam account> +workshop_download_item 221100 <workshop id> +quit

221100 is the app ID of the DayZ game (the client), and Workshop downloads use that ID. The dedicated server tool has a different ID, 223350, which is not the one to use here. The Steam account you log in with must own DayZ, and SteamCMD may ask for a Steam Guard code the first time it logs in.

SteamCMD saves the files to steamapps/workshop/content/221100/<id>/, a folder named only with the numeric Workshop ID. You will rename it in the next step.

Workshop mods are not updated automatically on a server: when an author releases an update, download it again.

2. Put the mod folders on the server

Copy each mod folder into the server’s root folder, next to the server executable, and rename it to @ModName, for example @CF. Keep the @, and make the name in -mod= match the folder name exactly, because names are case-sensitive on Linux hosts.

3. Copy the .bikey keys

Inside every mod folder is a keys folder containing one or more .bikey files. Copy each one into the server’s own keys folder, keeping the file names exactly as they are. If a key is missing, the server rejects every player who has that mod.

Keys are only enforced when signature checking is on. In serverDZ.cfg, verifySignatures = 2 is the setting that makes the server check them, so leave it at 2.

4. Set the -mod and -servermod launch parameters

Mods are loaded through the server’s launch parameters, separated by semicolons:

-mod=@CF;@YourMod

Your host’s control panel or startup command line will have a field for this. Order matters: put dependencies first, so Community Framework (@CF) goes before any mod that needs it. Mods that should only run on the server go in -servermod= instead, so players do not have to download them. If you set these in a shell launch line, put the whole value in quotes, for example "-mod=@CF;@YourMod", because the semicolon would otherwise end the command.

5. Add loot entries (types.xml and cfgeconomycore.xml)

Mods that add items need those items to be known to the loot economy. Merge the mod’s types.xml entries into your mission’s types.xml, or load them as a separate file through cfgeconomycore.xml. Check the XML is valid before restarting, because broken XML can stop the server starting. For how the files fit together, see our guides to cfgeconomycore.xml, types.xml and DayZ events.

6. Restart the server and check the logs

Restart the server however your host or panel allows, then read its console output and log files (the RPT and script logs). Missing dependencies and addon errors show up there. A missing key mostly shows up as players being kicked rather than as a server message.

Common questions

Do DayZ servers download Workshop mods automatically?

No. A DayZ server only loads the mod folders that are already on its disk, so you install each mod yourself and download it again whenever the author publishes an update, unless your host provides a tool that does it for you.

What are .bikey files and where do they go?

A .bikey is a mod’s public key: the server uses it to check the signatures (.bisign files) on that mod’s files. Copy it from the mod’s keys folder into the server’s keys folder so players running that mod are allowed in.

Do players need the same mods as the server?

Yes. Players need every mod in -mod= at the same version as the server; the DayZ launcher offers to download them when they join. Mods in -servermod= stay on the server only.

Why is my modded DayZ server kicking players or not showing up?

The usual causes are a missing .bikey key, a dependency loaded after the mod that needs it, or a mod version that no longer matches what players have. The server logs normally name the mod at fault.

How do I find which mod is crashing my DayZ server?

Remove all mods, then add them back one at a time, restarting between each. The mod that brings the crash back is the one to look at, and the logs from that restart usually say why.

Troubleshooting

  • Every player is kicked after adding a mod: a .bikey is missing from the keys folder.
  • Server will not start: check the load order, and check any merged XML is valid.
  • Players cannot join: they must run the same mod list and versions as the server.
  • Memory use jumps: large mods such as DayZ Expansion can noticeably increase memory use.

Need a hand?

We provide managed DayZ and other game servers, build custom DayZ mods and admin tools, and you can read how we run The Hoard, a heavily modded DayZ server.

Want this handled for you? Log in to the panel or contact us.