Direct answer

Modrinth announced a Backup settings page for Hosting on October 21, 2026. Its changelog says the server panel settings modal can enable or disable automatic backups, adjust their cadence, and divide backup slots between automatic and manual copies. The Backups tab also shows slot allocation more clearly. Do not assume a scheduled backup exists until your own server panel shows a successful backup.

Documentation discrepancy: Modrinth's March 2026 backup help article still says automatic backups are unavailable, while the newer October 21 changelog announces the settings. Treat the newer announcement as the feature description, and verify availability and behavior in the panel before relying on it.

Configure automatic backup settings

  1. Open the Modrinth Hosting server panel for the intended server. Confirm you are configuring the correct server, not a client Modrinth App instance.
  2. Open the panel's Settings modal and look for Backup settings. If the controls are missing, check Modrinth's current announcements or ask Hosting support rather than assuming backups are enabled.
  3. If available, enable automatic backups and choose a cadence based on the amount of player progress you can afford to lose.
  4. Allocate backup slots between automatic and manual backups. Keep enough manual capacity for a pre-update snapshot before changing Minecraft versions, mods, or modpacks.
  5. Save the settings, open Backups, and confirm your allocation and the appearance of an actual successfully completed backup.

The October announcement does not publish universal default backup intervals, retention counts, or guarantees about when a scheduled backup first runs. Use the values shown in your own panel, not assumed defaults.

Make a manual backup before major changes

Modrinth's existing support instructions for manual backups say to stop the server completely, open the Backups tab and choose Create backup. Wait until creation finishes before starting the server again. Do not assume these manual-backup shutdown instructions also describe how the new automatic scheduler operates.

Save the name, time, and relevant game/modpack revision of each important restore point. Download a separate copy before risky updates when the panel permits it.

Restore and verify a backup safely

  1. Confirm which backup will be restored and whether it contains the world, plugin/mod files, and configuration needed for your situation.
  2. Save a separate copy of any newer files you might need. Modrinth warns that Restore replaces server files with those from the selected backup.
  3. Stop the server and follow Modrinth's Restore workflow. Wait for the restore to finish; do not restart during replacement.
  4. Verify the resulting software/modpack version, server logs, player inventories and world state. The help article warns that server software may not always be rolled back correctly; follow its current recovery instructions if a mismatch occurs.

Retention, privacy and off-site copies

  • Slots are finite: determine how automated/manual allocation affects your usable restore points; never rely only on the most recent copy.
  • Protect private data: server archives can contain player information, plugin databases, IP addresses, and secrets. Store and share downloads only with authorized administrators.
  • Keep an independent copy: test a download or restore so you know backups are accessible outside a failed or unavailable panel.
  • Watch for silent failures: a schedule toggle is not proof of completed backups. Review timestamps after changes to the plan or server.

Common questions

Does Modrinth Hosting now create backups automatically?

Its October 21, 2026 changelog announces automatic-backup controls. The older help article still says no. Verify the actual control and completed backups on your account; do not infer successful scheduling from either page alone.

Can I restore after changing modpacks?

Backups are useful before changing modpacks, but restoring replaces server files and may not perfectly revert the software selection. Keep the original server files and exact version details, and test recovery before a production rollback.

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