How to Compare Joomla Core Files with a Clean Package
Comparing Joomla core files with a clean package is a reliable way to find missing, changed, or unexpected core files after a failed update, suspected corruption, or security incident. The comparison is useful only when the reference package matches the installed Joomla release and site-specific files are excluded from the core baseline.
Identify the exact Joomla version
Record the installed Joomla version before downloading anything. Use a clean official package for that exact release when performing an integrity comparison. Comparing different releases creates legitimate differences and can make healthy files appear damaged.
Prepare a clean reference safely
- Download the matching release from Joomla's official download source.
- Verify the published checksum when one is available.
- Extract the package into a separate directory outside the live web root.
- Do not copy it over the production site yet; begin with a read-only comparison.
Keep the original archive so you can reproduce the comparison later.
Separate Joomla core from site-specific content
A stock package does not represent every file that legitimately belongs on a working site. Exclude or separately review configuration.php, uploaded media, caches, logs, temporary files, backups, third-party extensions, custom templates, and other known site content. The purpose is to compare core with core, not to make the production tree identical to a fresh installation.
Compare recursively
With shell access, use a recursive file comparison or cryptographic hashes to classify paths as identical, changed, missing from production, or extra in production. Hosting file managers and deployment tools may provide checksum or directory-comparison features as well. Run the first pass without automatic synchronization so nothing is overwritten.
Pay particular attention to PHP entry points, administrator code, libraries, plugins supplied by core, JavaScript, and manifest files. A difference is a finding to investigate, not automatically proof of compromise.
Investigate every difference before repairing
A changed file can result from an interrupted update, disk corruption, unsupported manual core modification, or malicious activity. An extra file may be host-generated or suspicious. A missing file may have been deleted manually or omitted during deployment. Preserve unexplained files and logs when a security incident is possible.
Repair with one consistent release
If the comparison confirms damaged core files, prefer Joomla's supported core update or reinstall mechanism. When manual recovery is unavoidable, use only the exact official package for the intended release and protect site-specific files. Never repair a Joomla installation by mixing individual core files from different versions.
After repair, test the frontend and Administrator, run Joomla's update checks, review logs, and repeat the comparison. If unexplained modifications return, investigate the cause rather than repeatedly overwriting the symptom.
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.