MailWizz is a self-hosted email marketing application, and most of the disk pressure it creates has nothing to do with email bodies themselves. The storage you actually pay for on a shared plan gets consumed by uploaded template images, embedded assets referenced inside campaigns, exported CSV files, backup archives, and the caching MailWizz writes to disk during delivery. Because the application runs as an unprivileged hosting user, every file it writes counts against your account quota and, just as importantly, against your inode allocation. Unlike a general CMS that renders a public website, MailWizz serves images to inboxes that are opened at unpredictable times across many providers, so an unoptimized media setup produces both a storage problem on the server and a deliverability and load-time problem inside recipient mail clients.

The practical constraint on LiteSpeed, AlmaLinux, and CloudLinux shared hosting is that you tune MailWizz through its own admin interface, cPanel or DirectAdmin file tools, .htaccess, and .user.ini. There is no root access, no server-wide configuration, and no ability to install image libraries or object-storage daemons. What follows works entirely inside those boundaries and respects what MailWizz genuinely integrates with versus what marketing material implies.

Where MailWizz actually stores media and why it grows

Before trimming anything, map the directories so you delete the right things. In a standard installation under your document root (for example /home/youruser/public_html or a subfolder like /home/youruser/mailwizz), the storage that grows over time lives in predictable places. The frontend/assets/files and backend/assets/files trees hold uploaded template images and editor media. The frames directory and template thumbnails accumulate every time a user saves or previews a template. Import and export jobs write temporary and finished files into backend/runtime and the per-customer files area, and these frequently survive long after the job finished.

Open cPanel File Manager (or DirectAdmin File Manager) and sort each of these directories by size and by date. The real killer on shared hosting is usually inode count rather than raw gigabytes: thousands of tiny thumbnail and cache files can exhaust your inode limit while total disk usage still looks modest. Check your current inode usage from the cPanel right-hand statistics panel or DirectAdmin's