Chronos Backups
github.com
- Free plan
- Windows
- macOS
- Linux
What Chronos Backups is
Chronos Backups is a free, server-side utility for making backups of Minecraft Java worlds across multiple loaders and game versions. It filters world data to reduce backup size and lets server operators exclude chosen files and folders with a configurable blacklist. Backups can run on a schedule or be started and canceled through in-game `/chronos` commands; the required permission level defaults to 4. Supported loaders include Fabric, NeoForge, Forge, Bukkit, Spigot, Paper, Purpur, and Folia, with availability depending on Minecraft version. Backups can be kept locally or synced to Google Drive. Sync can upload completed backups, catch up on uploads after a failure or restart, and optionally remove local copies after a successful upload. Retention settings cap the number stored per world and remove the oldest first. Configuration lives in an automatically created TOML file, and there is no configuration GUI. One restore limitation is that sufficiently recent chunks may be omitted, leaving recent changes in them missing from a backup.
Who it suits
Chronos Backups is suited to Minecraft Java server operators who want scheduled world backups across supported loaders. It supports Linux, macOS, and Windows.
Good to know, and what to watch
- Schedules backups or runs them through in-game commands.
- Supports several loaders, depending on Minecraft version.
- Google Drive sync can catch up after interruptions.
- Blacklist can exclude selected files and folders.
- Recent chunk changes may be missing from backups.
- Google Drive is the only currently supported cloud provider.
- Configuration has no graphical interface.
- Nightly builds should not be assumed stable.
The verdict
Chronos Backups offers configurable local and Google Drive backups for Minecraft Java servers. Operators should account for the recent-chunk restore caveat and manage settings through its TOML file.
What the maker publishes
- Backup controls
- Users can schedule backups or run and cancel them with in-game `/chronos` commands; the required permission level defaults to 4. source
- Backup size
- The README says default backups typically shrink to about 1–15% of the original world size, and can often be under 7% of the world-plus-LOD footprint when Distant Horizons or Voxy data is filtered out. source
- Cloud integration
- Google Drive is the currently supported cloud sync provider; OneDrive and Dropbox are described as planned but unavailable. source
- Cloud sync behavior
- Cloud sync can upload finished backups, catch up on missing uploads after a failure or restart, and optionally delete local copies after successful upload. source
- Cloud token access
- The README says anyone with access to the stored Google Drive token can upload and delete backups in that Drive, but cannot access other Drive files. source
- Configuration
- Configuration is stored in an automatically created `config/chronos.toml` file, and the README says no configuration GUI is available for the foreseeable future. source
- Downloads
- Stable releases are available through Modrinth, CurseForge, and GitHub Releases; GitHub Actions also publishes nightly builds that the project says should not be assumed stable. source
- File exclusions
- A configurable copy blacklist can exclude files and folders from backups and comes prefilled with common server-related entries. source
- License
- The project is published under the MIT license. source
- Maker
- The GitHub profile identifies MagicJinn as the creator of Chronos Backups and lists the Netherlands as their location. source
- Minecraft compatibility
- The project lists support across Minecraft versions 1.7.x through 26.x, with loader availability varying by version. source
- Pruning and filtering
- Backups can prune and filter world data, and a configurable blacklist can exclude specified files and folders. source
- Purpose
- Chronos Backups is a multi-loader, multi-version Minecraft backup utility that keeps backups smaller by saving the most important parts of a world. source
- Release channels
- The README says nightly GitHub Actions builds are not the same as stable releases and should not be assumed stable. source
- Restore limitation
- The README warns that chunks not yet considered old enough may be omitted, so recent changes in those chunks can be missing from a backup and lost on restore. source
- Retention
- The `maxStoredBackups` setting caps retained backups per world locally and on each enabled cloud destination, removing the oldest first; the README recommends 5. source
- Server use
- The project describes Chronos as a server-side utility, and its Modrinth listing also lists server-side as a supported environment. source
- Supported loaders
- The README lists Fabric, NeoForge, Forge, Bukkit, Spigot, Paper, Purpur, and Folia support, with availability varying by Minecraft version. source
Checked against the maker's pages on 30 Sept 2026.