Project ZomboidHébergement de serveur

Your server is provisioned automatically and you'll get login details for the [LOW.MS Control Panel](https://control.low.ms) by email within a few minutes. From there, hit Start, wait for the first-boot log lines to settle, then open Web Console to run `/setaccesslevel "YourUsername" "admin"` once you're in-game. Everything else, settings, mods, backups, is in the sidebar.

Yes, and there are two ways. The easy one is **Steam Workshop** in the panel sidebar: a full Workshop browser where you search for a mod and click Install, and the panel updates the `WorkshopItems=` and `Mods=` lines in `servertest.ini` for you. Its companion pages, Steam Workshop (installed) and Steam Workshop (updates), show what's on the server and what has an update waiting. The manual route is editing those two lines yourself in Configuration Files, covered in our [server configuration guide](/knowledgebase/project-zomboid-server-configuration). Restart after either and the mods download on the next start. One thing to watch since Build 42 went stable: mods written for Build 41 will still download without any error, but they can fail at world load or kick players on join, so it's worth rebuilding your mod list rather than assuming it carried over.

Yes. Build 42 went to the stable public branch on 29 July 2026, so it's the default version a new server installs, and it brings the much larger map, basements, new crafting disciplines and animal husbandry. If you'd rather stay on Build 41 to finish an existing world, we can pin your server to the `legacy41` Steam branch, and every player will need to select that same branch under Properties, then Game Versions & Betas, in Steam. Build 41 saves won't load on Build 42, so take a backup before you switch either way. Open a ticket and we'll pin the branch for you.

Open Configuration Files in the panel sidebar and edit `servertest_SandboxVars.lua`. Zombie density is controlled by the `Zombies` variable (1 = Insane, 4 = Normal, 5 = Low). Loot works differently since Build 42: the old per-category keys like `FoodLoot` on a 1-4 scale were replaced by renamed keys such as `FoodLootNew` that take a decimal multiplier instead, so a Build 41 loot config won't carry across cleanly and is worth redoing from scratch. Restart the server for changes to take effect. Our [server configuration guide](/knowledgebase/project-zomboid-server-configuration) walks through the settings that actually matter for multiplayer.

Your player cap is whatever the slot count on your plan is. You can also raise or lower `MaxPlayers` in `servertest.ini` if you want a lower hard cap. For most groups 10-16 active players is comfortable, and we run servers well above that without drama. The one caution worth repeating comes from the server config itself: player counts above 32 can lead to poor map streaming and desync, so scale up deliberately rather than jumping straight to a big number. See our [Project Zomboid plans](/game-servers/project-zomboid-server-hosting) for slot tiers.

Yes, automatic Cloud Backups are included on every plan. You'll find **Cloud Backup** and **Cloud Restore** as two separate entries in the panel sidebar; Cloud Restore is the one you want when something goes wrong. Project Zomboid also keeps its own in-game backups in `Zomboid/Backups/` that you can grab via File Manager or SFTP (port 8822) if you prefer that route. Worth taking a manual backup before any major version change, since a world from an older build won't load on a newer one.

Once you've promoted yourself via `/setaccesslevel "YourUsername" "admin"`, you can type commands directly into the in-game chat. Common ones: `/additem` to spawn items, `/teleport` to move players, `/kick` and `/ban` for moderation, `/save` to force a world save. You can also run any command from **Web Console** in the panel sidebar, which is useful if you need to recover access or act on the server without being in-game. Our [getting started guide](/knowledgebase/project-zomboid-getting-started) has the full access-level breakdown.

More than most hosts pretend. A small 2-5 player vanilla server runs comfortably on around 4 GB. Once you're at 8-10 players with a handful of mods you want 8 GB minimum and ideally more, and a mod-heavy 15-player server can easily push 12 GB. Build 42 is noticeably heavier than Build 41, and its install alone is about a third larger, so plan for extra headroom on both memory and disk. All our plans ship with plenty of RAM for the slot count you pick, and you can upgrade in-place if you need more. See [Project Zomboid plans](/game-servers/project-zomboid-server-hosting).

Votre Project Zomboid est configuré instantanément après le paiement, vous permettant de commencer l'hébergement sans délai.

Oui! Notre panneau de configuration convivial vous donne un contrôle total sur les modes de jeu, les cartes et les configurations de serveur sur votre serveur Project Zomboid.

Nous fournissons une assistance 24h/24 et 7j/7 pour votre serveur Project Zomboid par chat en direct et par e-mail pour vous aider en cas de questions ou de problèmes techniques.

Absolument. Si vous n'êtes pas satisfait de votre serveur Project Zomboid. Nous effectuons un remboursement complet dans les 5 premiers jours.

Nos serveurs Project Zomboid utilisent du matériel Intel ou AMD de premier plan pour garantir un fonctionnement parfaitement fluide de votre serveur !