On a vanilla Java server, the normal autosave interval is 6,000 game ticks—about five minutes. Use save-off to pause level-file writes during a backup, save-all (or save-all flush) to force a save, and save-on to resume them. Paper servers normally keep that behavior but control the rate of chunk writes with max-auto-save-chunks-per-tick, which defaults to 24 in config/paper-world-defaults.yml.
Playing with friends? Godlike.Host runs hosted Minecraft Java servers from 10 data-center locations, with free DDoS protection.
This guide covers Java Edition dedicated servers running vanilla or Paper. Bedrock Dedicated Server behavior is not covered because its autosave implementation was not verified here.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Minecraft | Java & Bedrock Deluxe Collection | Windows Digital Code | $39.99 | Buy on Amazon |
| 2 |
|
Minecraft | Java & Bedrock Ultimate Collection | Windows Digital Code | $49.99 | Buy on Amazon |
| 3 |
|
Minecraft | Standard Edition | XBOX Digital Code | $19.99 | Buy on Amazon |
| 4 |
|
Minecraft | $6.99 | Buy on Amazon |
| 5 |
|
Minecraft - Bedrock Edition PS4 | $42.98 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What Minecraft server autosave does
Autosave writes the in-memory world state to disk so the server can recover it after a clean shutdown or an unexpected failure. The relevant data includes terrain and other level files; player, advancement, and statistics files are handled separately when level saving is disabled.
Java Edition measures server activity in ticks. The vanilla default is 6,000 ticks, which is approximately five minutes at the normal 20 ticks per second. That interval is a periodic safety net, not a substitute for a separate backup. A crash between saves can still lose recent block changes, inventories, or other world activity.
#1 Best Overall
- DELUXE COLLECTION — Includes Minecraft: Java & Bedrock Edition, three Bedrock add-ons, three exclusive Character Creator items, and 700 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
Autosave is a runtime server function. The standard controls are console or in-game commands rather than a documented server.properties autosave key. The commands below apply to dedicated Java servers and require permission level 4.
Check which server software you run
Your configuration path depends on the server implementation.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Vanilla Java: use the save commands described below. The normal interval is 6,000 ticks.
- Paper: use the same commands, and optionally adjust the rate at which Paper writes chunks during autosave.
- Bedrock: do not apply these instructions without checking Bedrock Dedicated Server documentation; its command and file behavior was not verified for this guide.
If you are unsure, look at the startup log or the server jar name. A Paper startup identifies itself as Paper, while a plain Mojang server jar identifies as vanilla. Do not edit Paper files on a vanilla server: those files will not exist or will have no effect.
Vanilla Java autosave commands
| Command | Function | Important behavior |
|---|---|---|
save-all |
Writes the server’s current data to disk. | Works even while automatic level saving is disabled. |
save-all flush |
Forces an immediate save and flushes the write. | The server can freeze briefly while the flush completes. |
save-off |
Disables automatic writes to level files. | Level changes are queued until saving is enabled again. Player, advancement, and statistics files are exceptions. |
save-on |
Re-enables automatic level-file writes. | Use it immediately after a backup or maintenance window. |
Run the commands in the server console without a leading slash. In chat, an operator uses the slash form, such as /save-all. Permission level 4 is required, and these controls are for dedicated servers rather than a single-player world opened to LAN.
Rank #2
- ULTIMATE COLLECTION — Includes Minecraft: Java & Bedrock Edition, five Bedrock add-ons, five exclusive Character Creator items, and 1000 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
How to make a safe backup with autosave paused
The dependable Java backup sequence is to pause level writes, copy the world, then turn saving back on. Pausing prevents the level files from changing while the copy is made; changes that occur during the pause remain queued in memory.
- Warn players. Tell players that saving is being paused and that a short maintenance window is starting. Avoid making the announcement after you have already stopped writes.
- Pause level saving. Run
save-offin the console. Confirm that the command is accepted before beginning the copy. - Optionally force a final write. If you want the latest state committed before the pause, run
save-allaftersave-off. The command still writes the server data while automatic saving is disabled. For a strict immediate flush, usesave-all flush, but expect a brief freeze. - Copy the world data. Copy the server’s world directory (and any additional dimensions or world directories your installation uses) to backup storage. Keep the original directory untouched while the copy runs.
- Verify the copy. Check that the destination contains the expected region files and has a plausible size. A backup job that silently copies only part of a directory is not a usable recovery point.
- Resume saving. Run
save-onas soon as the copy is complete. This releases queued level changes and returns the server to normal autosaving. - Record the backup. Note the date, server version, and world name so you can identify the correct restore point later.
Do not leave a live server in the save-off state. Every block placement, container change, and other level update made during that period increases the amount of queued data and the potential loss if the process crashes before save-on is issued.
Why the order matters
Copying first and running save-off afterward creates a race: files may change while they are being copied, producing an inconsistent snapshot. Running save-off first establishes a stable level-file set. The subsequent save-on is not optional; it is the step that resumes normal persistence.
What happens after a restart
The save-off state resets when the server restarts. A server that was paused before a crash or planned restart will not remain intentionally paused after it comes back up. Nevertheless, check the console and perform a manual save-all after maintenance if you need to confirm that the restored process has written its current state.
Rank #3
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that is unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world full of surprises.
- SURVIVAL ADVENTURES — Face mysterious foes, travel across varied landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play solo or join friends in local split-screen and cross-platform play across console, mobile, and PC. Online multiplayer supports up to 8 players.
- COMMUNITY PLAY — Connect with players on community servers, or subscribe to Realms Plus (sold separately) to play with up to 10 friends on a private server.
Forcing a save during normal operation
Use save-all before planned shutdowns, configuration changes, or other maintenance that could interrupt the process. It is also useful as an operational checkpoint before starting a backup workflow.
Use save-all flush when the priority is to push the write through immediately rather than merely request a save. The flush can pause the server briefly, so run it during a quiet period and warn players if a short stall would be disruptive.
Free tools Windows power users keep installed
One-click scans. No signup required.
A forced save does not change the automatic interval. It creates an additional write at that moment; periodic autosave continues according to the server software’s normal behavior unless you have explicitly used save-off.
Paper: control chunk-write pacing
Paper exposes a separate setting for how many chunks autosave can write in one tick. The setting is max-auto-save-chunks-per-tick. Its documented default is 24, and it is located under the chunks section of config/paper-world-defaults.yml.
Rank #4
- Skins! We have biome settlers, city folk, town folk, and more!
- The Nether and all its inhabitants. Fight Ghasts and make friends with Pigmen
- Cross platform play for up to five players between Pocket Edition and Windows 10
- Revamped touch controls, controller support, and a controller mapping screen
- Enhanced Weather effects! Accumulating snow and more
| Paper setting | Default | File and scope | What it changes |
|---|---|---|---|
max-auto-save-chunks-per-tick |
24 | config/paper-world-defaults.yml, under chunks |
Caps the number of chunk saves processed per tick during autosave, spreading disk work over time. |
| Per-world override | Not stated | The individual world’s paper-world.yml |
Lets one world use a different chunk-write cap from the global world default. |
This is pacing, not an autosave interval. Lowering the cap does not make the server wait longer between autosaves; it limits how much chunk-writing work Paper performs in each tick. A lower value can reduce a concentrated write spike on slow storage, while also taking longer to finish a complete autosave cycle.
Editing the Paper setting
- Stop the server cleanly. Use your normal shutdown procedure and wait until the process has exited. Editing YAML while Paper is running risks losing your change when the file is rewritten.
- Open the current configuration file. Use
config/paper-world-defaults.ymlon current Paper versions. Older guides that tell you to editpaper.ymldescribe an older layout; the configuration was split intopaper-global.ymlandpaper-world-defaults.ymlin the 1.19-era layout. - Find the
chunkssection. Locatemax-auto-save-chunks-per-tickand change only its numeric value. Preserve YAML indentation and spelling. - Save a copy of the original. Keep the previous file so you can revert quickly if startup reports a configuration error or performance gets worse.
- Start Paper and watch the console. Confirm that the server loads the file without a YAML error, then observe tick performance and disk activity during a normal autosave cycle.
- Use a per-world override only when needed. Put a world-specific value in that world’s
paper-world.ymlwhen one world has a distinct workload. Leave the global default in place for worlds that do not need special treatment.
Paper’s documentation indicates that most servers can keep the default of 24. Treat changes as performance tuning, not a mandatory optimization.
Choosing a Paper value without guessing
Community recommendations conflict: one style of guide suggests values around 6–12 for slow storage, while another advises retaining 24 and profiling first. Neither range is a universal rule. Storage speed, world size, entity activity, player count, and other plugins can change the result.
Use this decision process:
- Establish a baseline. Leave the value at 24 long enough to observe several ordinary autosave cycles. Record when lag spikes occur and whether they coincide with saving.
- Check the symptom. If the server experiences brief, repeatable tick stalls during chunk writes, pacing may be relevant. If lag occurs continuously or during chunk generation, changing autosave pacing may not address the cause.
- Change one value. Make a modest adjustment, document it, and restart Paper so the configuration is loaded cleanly. Do not change multiple performance settings at once.
- Compare like with like. Observe similar player counts and workloads before deciding whether the change helped. A quiet test period can hide a problem that appears during peak activity.
- Revert when there is no measurable benefit. A lower cap can spread writes but prolong the period over which autosave work is processed. If it does not reduce the observed spike, return to 24.
Do not use a lower number simply because it appears in a community post. Profile first, and keep a written record of the original value.
Best Value
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
Autosave interval versus write pacing
These settings solve different problems:
| Question | Vanilla Java commands | Paper chunk cap |
|---|---|---|
| Can it pause automatic level writes? | Yes: save-off and save-on. |
Not by itself. |
| Can it force an immediate save? | Yes: save-all or save-all flush. |
No; it only limits work per tick. |
| Does it change the normal five-minute default? | The commands do not edit the interval. | No; it changes chunk-write pacing. |
| Primary trade-off | Pausing reduces file changes during a backup but increases unsaved-change exposure until saving resumes. | Lower per-tick work may smooth spikes but can extend the time needed to process all autosave writes. |
This distinction prevents a common mistake: lowering Paper’s chunk cap when the real requirement is a longer or shorter scheduling interval. The cap is a per-tick workload limit, not a timer.
Diagnosing autosave-related lag
Lag appears as a short, repeatable spike
First confirm that the spike lines up with autosave activity rather than world generation, a backup copy, garbage collection, or a plugin task. On Paper, keep 24 as the baseline and profile. If evidence points to chunk-write bursts on slow storage, test a modestly lower cap and compare the same workload.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsLag continues after changing the cap
Restore the previous value if the change made no difference. The bottleneck may be storage saturation, a different server task, or a backup process reading the same files. Autosave pacing cannot fix a CPU-bound plugin or a full disk.
The server starts with a configuration error
Stop the process, restore the saved original configuration, and start again. YAML indentation, a misspelled key, or editing an obsolete file can prevent the intended setting from loading. Confirm that you are editing the current Paper path rather than an old paper.yml file.
Players report lost recent changes after a crash
Review when the last successful autosave or save-all occurred. A crash can lose changes made after the most recent write, and any period spent under save-off increases that exposure. Resume saving promptly and use a separate backup schedule rather than relying solely on the five-minute autosave cycle.
Quick Recap
Common mistakes to avoid
- Using a slash in the console: Console syntax is
save-all, not necessarily/save-all. The slash form is for chat or command interfaces that expect it. - Forgetting permission level 4: A lower permission cannot run these administrative save commands.
- Leaving saving disabled: Always pair a backup’s
save-offwithsave-on, even if the copy fails. - Assuming a restart preserves the pause: The disabled state resets on restart.
- Copying before pausing: This can produce a changing, inconsistent snapshot.
- Confusing autosave with backup: Autosave writes the live world; it does not create a second, independently restorable copy.
- Editing the wrong Paper file: Current Paper uses
paper-global.yml,paper-world-defaults.yml, and per-worldpaper-world.ymlfiles rather than the older singlepaper.ymllayout. - Changing several performance settings together: You lose the ability to identify which change helped or hurt.
- Assuming Bedrock behaves identically: These Java commands and Paper settings are not verified for Bedrock Dedicated Server.
A practical operating checklist
- Confirm that the server is Java dedicated, vanilla, or Paper.
- For ordinary vanilla operation, accept the 6,000-tick default unless you have a separately verified reason to change scheduling.
- Before a file backup, run
save-off, optionally runsave-allorsave-all flush, copy the world, verify the copy, and runsave-on. - On Paper, start with
max-auto-save-chunks-per-tick: 24inconfig/paper-world-defaults.yml. - Profile before changing Paper’s cap; test one change at a time and keep a rollback copy.
- After every maintenance window, confirm that automatic saving is enabled and that the console accepts a test
save-all. - Keep independent backups because autosave alone cannot recover changes made after the last successful write or protect against corruption of the live world directory.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →
