Skip to content
Game panel

Project Zomboid disk full: No space left on device

Project ZomboidIntermediatepanel.oxy.games

No space left on device means a write failed because storage could not accept it. The message alone does not identify the files responsible: diagnose the usage before changing backups or deleting saves.

What you'll do
  1. Capture the error and disk usage
  2. Identify the files using space
  3. Protect a usable recovery point
  4. Clean up confirmed backups and check saving

Record the complete error, its time and any file path in the console. Note whether it happened during startup, gameplay or a backup, and record the panel’s disk usage and limit. Avoid repeated restarts while the cause is unclear.

Use Files or SFTP to inspect the affected path without deleting anything. Identify large directories and files, including saves, downloaded mods, logs and archives. Treat these as things to check, not confirmed causes. If your file view cannot show enough information, ask support to measure directory usage.

If the panel shows free space but writes still fail, send support the error and usage figures so they can check the storage limit and underlying filesystem. Do not assume that deleting a world will fix it.

Stop the server before copying its files. Follow the backup guide and confirm that the backup completes. Download the copy, check its date and contents, and keep the matching build and mod details. Include world, character/account and configuration files. A completed download alone does not prove that recovery works; ask support to check usability if you are unsure.

If a full disk prevents backup creation, keep existing recovery points and contact support. Use SFTP to download the stopped server’s files if possible. Do not create another archive on the full server, delete your only backup or assume a failed backup is usable.

Panel backups and backups written by the game are different systems. The panel backup guide describes separate object storage. That does not prove that a folder in your game files is an old backup, or that deleting a panel backup frees the space causing this error.

If the error points to ZipBackup or backups/startup and that directory uses the missing space, open .cache/backups/startup/ in Files. Project Zomboid writes startup backup ZIPs there on setups using .cache as their data root. Check the timestamps and sizes. If the path differs, follow the path in the error or ask support to identify it. Never treat .cache/Saves/Multiplayer/ as a backup directory.

When ZipBackup or measured startup backups are the cause and you have a usable replacement backup, you can stop future startup backups. Stop the server, open the matching .cache/Server/<ServerName>.ini in Files and change the line to:

.cache/Server/<ServerName>.ini
BackupsOnStart=false

Save the file, then start the server. This stops future game backups at startup; it does not free space already used by old ZIPs or replace your panel backup routine. Do not make this change if you have not identified startup backups as the problem.

After the agreed cleanup, recheck disk usage, start the server and inspect the console. Join, check the expected world and character, then verify a normal save and subsequent start retain new progress. If the error returns, stop and send the logs and before/after usage to support.

  • Keep useful logs: download the error log before any agreed log cleanup.
  • Lost world or character: follow the world recovery guide first. Use the reset guide only if you want to start over.
  • Support details: include the build, profile, error time, affected path and disk usage; leave passwords out.

Host your own Project Zomboid server

Play together on your own server

View Project Zomboid hosting