---
title: "Project Zomboid \"File doesn't match the one on the server\": Causes and Fix"
description: "What Project Zomboid's \"File doesn't match the one on the server\" error means, how to read the file path it shows, and how to fix it on your server."
url: "https://www.gameserverkings.com/knowledge-base/project-zomboid/file-doesnt-match-the-one-on-the-server/"
category: "Project Zomboid"
category_url: "https://www.gameserverkings.com/knowledge-base/project-zomboid/"
published: "2026-09-28T04:25:11.247Z"
updated: "2026-09-28T04:25:11.247Z"
source_format: "markdown"
site: "GameServerKings"
---

# Project Zomboid "File doesn't match the one on the server": Causes and Fix

"File doesn't match the one on the server" is a Project Zomboid connection error. It means one of your game files is different from the server's copy of the same file. When you join, the server compares checksums of the Lua, script and animation files both sides have loaded, from the base game and from every mod. If one file differs, the game stops the connection and shows the error with the path of the file that failed. With mods, that file is almost always in a Workshop mod that has updated on one side and not the other.

This guide explains how to read the message, the causes in the order to check them, and the fix on a GameServerKings server. The error text and the logic behind it come from Project Zomboid's own code (Build 42, public branch, checked 27 September 2026).

## Reading the Error Message

The message has up to three lines. The first line is the reason and the second is the file:

```text
File doesn't match the one on the server:
<path of the file inside the game or mod>
<full path of that file on your computer>
```

The third line appears when the file's full location on your PC differs from the short path. It's the most useful line, because it shows **where** your copy came from:

- A path under `steamapps\workshop\content\108600\<number>\` is a Steam Workshop mod. `108600` is Project Zomboid's Steam app ID, and the long number after it is the **Workshop ID** of the mod that doesn't match.
- A path inside the Project Zomboid install folder is a base game file.
- A path under your own `Zomboid\mods` folder is a mod someone copied there by hand, not the Workshop version.

The same check has three siblings, with the same format and different first lines:

| First line | What it means |
|---|---|
| `File doesn't match the one on the server` | Both sides have the file, but the contents differ |
| `File doesn't exist on the server` | Your game loaded a file the server doesn't have |
| `File doesn't exist on the client` | The server loaded a file your game doesn't have |
| `File status unknown` | The check failed without a specific reason |

If your error reads `Client version (42.x) does not match server version (42.y)` instead, the problem is the game build rather than a file. That one is covered in [Project Zomboid Multiplayer](/knowledge-base/project-zomboid/project-zomboid-multiplayer/), under branch matching.

## Causes, in the Order to Check Them

### 1. A mod updated on Steam, but the server is still running the old version

This is the most common cause on a modded server. A mod author publishes an update and players' Steam clients download it straight away. The server only fetches Workshop items **when it starts**, so it keeps the old version until its next restart. From then on, every player who has the new version gets the error on the mod's changed files.

The game's own text for the related Workshop error says the same: *"Possibly the server's version is outdated, requiring the server to be restarted."*

The fix is a server restart. See the GSK steps below.

### 2. The player's copy is out of date or damaged

The reverse case: the server restarted and picked up the update, but a player's Steam hasn't downloaded it yet, or a download was interrupted. The game's advice here is *"If your version is outdated, try restarting Steam to get the latest version."* If that doesn't clear it:

1. Quit Project Zomboid and Steam completely, then start Steam and wait for **Downloads** to finish before launching the game.
2. If the path shows a Workshop ID, unsubscribe from that item on its Workshop page, wait for Steam to remove it, then subscribe again.
3. If the path points at a base game file, right-click Project Zomboid in your Steam library, then choose **Properties → Installed Files → Verify integrity of game files**.

### 3. A modified or hand-copied file on the player's PC

Changes to the game's own Lua files, a manually installed mod in `Zomboid\mods`, or a mod edited for single player will all fail the check. That's intended: the check exists to keep modified clients off the server. Remove the local copy, then verify game files or resubscribe as above.

### 4. The server's mod files were edited

If an admin changed a mod's files on the server, for example to tweak a value in its Lua, then every player's unmodified Workshop copy no longer matches. Either undo the edit or distribute the same edited version to every player. On a public server, undoing it is the realistic choice.

## Fixing It on a GameServerKings Server

### Restart the server so it re-downloads its mods

1. Tell players to disconnect, then **Restart** the server from the panel.
2. Watch the **Console** during startup. The server shows its Workshop download progress, logs a line ending `installed to <folder>` for each item, and reinstalls items that need it.
3. Once the console shows the server is up, have players restart Steam and then rejoin.

> [!NOTE] Steam Auto Update doesn't cover mods
> The **Steam Auto Update** variable on the **Startup** tab (off by default) only controls updates to the Project Zomboid **game** at boot. Workshop mods are fetched by the game server itself on every start, whether auto-update is on or off. When a mod update breaks joining, a restart is enough. You don't need to reinstall.

### Check that the mod list is what you expect

The server's settings file is in `.cache/Server/` and named after your **Server Name** variable: `Pterodactyl.ini` if you never changed it. Open it in the **File Manager** and look at the two mod lines:

```ini title=".cache/Server/<Server Name>.ini"
WorkshopItems=2392709985;2196102849
Mods=Authentic Z - Current;RavenCreek
```

`WorkshopItems` is what the server downloads and `Mods` is what it loads. Check that the Workshop ID from the error is in `WorkshopItems`, so you know which of your mods changed. [How to install mods for Project Zomboid](/knowledge-base/project-zomboid/how-to-install-mods/) covers both lines, and [Project Zomboid Server Settings and Config Files](/knowledge-base/project-zomboid/configuration-overview/) covers the rest of the file.

### Schedule mod updates instead of chasing them

Most "file doesn't match" reports on a busy server come in the hours after a popular mod updates. Two habits prevent most of them:

- **Restart on a schedule.** A daily restart picks up overnight mod updates before most players are online.
- **Add or update mods only at a restart**, and post the Workshop collection link in the server description so everyone subscribes to the same set.

### The last resort: DoLuaChecksum

The check is controlled by one server setting, `DoLuaChecksum`, which is on by default. The game describes it as: *"Kick clients whose game files don't match the server's."* Setting `DoLuaChecksum=false` in the `.ini` and restarting stops the error. It also lets anyone join with modified Lua, including cheat scripts, and players on mismatched mod versions can hit errors or desync in play instead of at the door.

> [!WARNING] Only turn DoLuaChecksum off on a private, trusted server
> On a public server, keep it on and fix the version mismatch. Turning it off doesn't fix the mismatch. It stops the game from telling you about it.

## Quick Reference

| Situation | Fix |
|---|---|
| Error started right after a mod update, for everyone | Restart the server |
| Only one player gets it | That player restarts Steam, then resubscribes to the Workshop ID in the error |
| Path is a base game file | Verify integrity of game files in Steam |
| Path is under `Zomboid\mods` on the player's PC | Remove the hand-installed copy |
| Error says `Client version ... does not match server version` | Branch mismatch. See [Project Zomboid Multiplayer](/knowledge-base/project-zomboid/project-zomboid-multiplayer/) |
| Error says `Workshop item version is different than the server's` | Same root cause as this page. Restart the server, then restart Steam |

## What to Read Next

- [How to install mods for Project Zomboid](/knowledge-base/project-zomboid/how-to-install-mods/): the `WorkshopItems` and `Mods` lines, and map mods
- [Project Zomboid Server Settings and Config Files](/knowledge-base/project-zomboid/configuration-overview/): where the `.ini` lives and what else is in it
- [Project Zomboid Multiplayer: How to Play With Friends](/knowledge-base/project-zomboid/project-zomboid-multiplayer/): branch mismatches and other join failures
- [Getting started with your Project Zomboid server](/knowledge-base/project-zomboid/getting-started-with-your-server/): first boot, wipes and backups
- [Project Zomboid Admin Commands](/knowledge-base/project-zomboid/how-to-add-admins-and-common-commands/): kicking, banning and access levels

---

Made with 💜 by GameServerKings
