Find what is using space
Check the file manager and server resource information for:- Large or repeated log and crash-report files
- Old archives, installers, and uploaded migration copies
- Web-map tiles generated by mapping plugins
- Pregenerated or heavily explored worlds and dimensions
- Plugin databases, player analytics, or retained history
- Duplicate modpacks, plugin versions, or unused world folders
- Backups stored as ordinary files inside the server directory
Free space safely
1
Stop the server
Use a normal stop so the world finishes saving.
2
Create an external copy
Download old logs, crash reports, archives, or worlds that you may need before removing them.
3
Remove obvious duplicates
Remove completed upload archives, obsolete installer files, and duplicate plugin or mod
.jar files after confirming the active version.4
Review generated data
Check map tiles, analytics, logs, and plugin caches. Use the software’s documented cleanup or retention settings when available.
5
Start and verify saving
Start the server, read the console, join, make a small safe change, and perform a normal stop. Confirm the next start loads that saved state.
Prevent the problem from returning
- Configure log, map, analytics, and plugin retention where supported.
- Remove migration archives after verifying the migrated server and keeping an external copy.
- Pregenerate only the world area you intend to use and apply a practical world border.
- Review disk usage after adding a web map, large modpack, or world-generation plugin.
- Keep backups according to a deliberate retention plan instead of retaining every copy indefinitely.
