How to Find Large Files in a Joomla Website
Start with a filesystem-level size report
Use your hosting control panel's disk-usage tool or a read-only shell command supplied by your host to identify large files and directories under the Joomla account. Joomla itself does not maintain a complete index of every file size on disk, so filesystem or hosting tools are usually the most reliable starting point.
Check common data-heavy locations
Review images and media, backup archives, log directories, temporary files, caches, extension-generated exports, and downloadable documents. Large files are not automatically a problem: media and backups may be legitimate. The goal is to identify what owns the space before deciding whether it can be removed.
Separate Joomla core from site content
Use the Joomla root as a reference point and identify whether a large file belongs to core, a third-party extension, a template, media, or an operational tool. Joomla's path constants distinguish locations such as the site root, Administrator, cache, libraries, plugins, and templates, which can help developers classify files.
Pay special attention to backups and logs
Backup extensions can create multi-gigabyte archives, while verbose or malfunctioning logging can grow continuously. Check whether old backups already exist in a verified off-site destination before deleting local copies. For logs, determine why they are growing and adjust the responsible logging policy only after preserving needed diagnostic evidence.
Look for unexpectedly large PHP or script files
Normal size varies, but an unusually large or recently modified executable file deserves inspection, especially after a security incident. Do not delete it solely because of size. Compare it with a trusted package or vendor copy and preserve evidence if compromise is possible.
Check quotas as well as free disk space
Hosting accounts can hit a quota even when the underlying server has free space. Inode limits can also cause write failures when there are huge numbers of small files rather than a few large ones. Use the hosting platform's quota and inode reports when Joomla reports write, upload, cache, or update failures.
Remove files only after identifying their owner
Once a file is understood, follow the owning extension's or hosting platform's cleanup procedure. Avoid deleting Joomla core, extension libraries, manifests, or unknown data files to recover space. Take a backup when removal could affect site operation, then verify the frontend, Administrator, updates, uploads, and scheduled jobs.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.