Direct answer

On Java Edition servers, save-all requests saving loaded world and player data. Supported builds may accept save-all flush to flush pending chunk writes; it does not make copying a live world universally safe.

Recommended procedure

  1. Run save-all at the console, or /save-all in-game with suitable permissions. Check console output for completion or errors.
  2. If your Minecraft/server version supports it, use save-all flush before the planned stop.
  3. For an ordinary backup without an integrated snapshot tool, stop the entire server and wait for exit, then copy world folders and related configs.
  4. Do not confuse save-off with a backup tool: leaving saving disabled can lose later player or world changes.
save-all
save-all flush
stop

Why this matters

A backup must be recoverable, not merely a command that returned without error. Test restoration on a different instance.

How to verify the result

After restart, rejoin and confirm representative inventories and chunk changes. Test the copied world on staging when the goal is backup validation.

Version and compatibility notes

Command syntax and whether flush is available can differ across versions. The official Paper command permissions reference lists save-all.

Official references

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000