Remove only verified, unnecessary data and keep required records or backups outside the hosting account before deletion.
Applies to: SiteWorx accounts approaching storage or inode limits
Work from the largest safe opportunity
- Use the storage-usage article to identify whether files, email, databases or backups are responsible.
- Download or export data that must be retained.
- Remove obsolete archives, failed deployment copies and caches that the application can safely recreate.
- Review large mailbox folders and empty Trash/Junk only after checking retention needs.
- Optimise application/database data through supported application tools rather than deleting tables directly.
- Move independent backups outside the hosting account.
- Recheck storage and inodes after the system has updated its figures.
Important: Do not delete unknown system files, active application folders, database tables or mail storage directly through File Manager.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| Usage does not fall immediately. | Quota figures are recalculating, deleted mail remains in server folders or files are still open/generated. | Wait for recalculation, check Trash and confirm the correct account/path was cleaned. |
| Usage returns quickly. | An application, log, backup task or mailbox is continually generating data. | Identify the growth rate and source before deleting another copy; fix the generating process or upgrade. |
Related articles
- Check website, database and email storage usage
- Resolve a full mailbox or quota warning
- Troubleshoot large file uploads
- Export a database backup
- How hosting backups and self-restore work
Last reviewed: 2026-07-25.
