Direct answer

Close the game or stop the server, copy the complete save plus the settings and mod records needed to reproduce it, label the copy with its exact game version and date, and test only a duplicate after an update.

Do this first

  1. Exit the client or stop the server cleanly.
  2. Open the active user-data or server-data directory.
  3. Copy the save and relevant configuration elsewhere.
  4. Name it with version, date, play mode, and mod status.
  5. Launch a duplicate only after the original is safe.

Back up context, not only one folder

A useful backup lets you reproduce the world. Keep the save, server configuration when applicable, exact version, and a list of Workshop items and mod IDs. Custom hosts can use different paths, so trust the active configuration and logs over an old copied path.

  • World/save data
  • Server INI and sandbox settings
  • Mod and Workshop lists
  • Exact client/server build
  • Backup date and reason

A safe update test

Keep the original offline. Duplicate the save, update the client or server, launch the expected branch, and verify the character, map, containers, vehicles, and server access before treating the update as complete.

Rollback is not migration

Returning to legacy41 or 42.19 preserves a world on its old line; it does not convert it to Stable. Keep written notes so a future launch does not open a save on the wrong branch.

FAQ

Quick answers

Can I back up while the server is running?

For a dependable manual copy, stop the server cleanly first so files are not changing during the copy.

Is a backup a way to convert Build 41 to Build 42?

No. A backup protects the old world; it does not remove the compatibility boundary.

Evidence log

Sources checked

Official sources establish universal facts; forum and specialist sources are used for symptoms, vocabulary, and cross-checking.

OfficialProject Zomboid Build 42.20 Released

Official Stable status, legacy41 instructions, and the explicit Build 41/42.19 save boundaries.

OfficialB42 Checklist

Official pre-launch checklist confirming that Build 41 saves do not carry into Build 42.