How to Restore Joomla Files Manually
Use a backup that matches the database state
Choose the filesystem backup from the same recovery point as the database you intend to keep or restore. Joomla stores important application state in both places, so mixing old extension files with a newer database can cause missing classes, schema mismatches, or broken configuration. Preserve the current files separately before replacing anything.
Identify the correct Joomla document root
Confirm the directory containing configuration.php, index.php, administrator, components, plugins, templates, and the other Joomla application directories. Hosting accounts may call this public_html, httpdocs, www, or a domain-specific directory. Do not extract the backup one level too high or too low, which can leave the public site pointing at the wrong files.
Remove or isolate damaged files instead of blindly merging
When performing a full file restore, move the existing site files to a protected temporary location or replace the document root according to the hosting provider's safe procedure. Blindly extracting an old archive over a damaged installation can leave unwanted new files behind because files absent from the backup are not automatically deleted.
Extract the backup with its original directory structure
Upload and extract the archive using the hosting file manager, SFTP, SSH, or the backup tool's documented restore method. Include hidden files and media directories that belong to the backup. Do not overwrite the database merely because you are restoring files; database recovery is a separate operation and should use the matching SQL backup when required.
Restore normal ownership and permissions
Files must be readable by the web/PHP process and writable only where Joomla legitimately requires it. Preserve the hosting account's expected owner and group. Avoid world-writable 777 permissions as a shortcut. If extraction was performed by root or another system account, ask the host or use its supported tools to correct ownership.
Review configuration.php before loading the site
If the files were restored to a different server, account, directory, or database, update the environment-specific values in configuration.php. Check database credentials and table prefix as well as log and temporary paths. Keep the file protected and do not replace it with a generic configuration file from a clean Joomla package.
Test the restored files against Joomla's database state
Load frontend and Administrator pages and inspect PHP logs for missing classes or version mismatches. If the restore follows a failed core update, use Joomla's supported update/reinstall and database-maintenance tools to return files and schema to a consistent version. A page that renders is not enough; test extensions, forms, media, and Administrator workflows.
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.