How to Restore Joomla Files Manually

A manual Joomla file restore replaces the application filesystem with files from a known-good recovery point. Use a backup that matches the database state you intend to run, preserve the current damaged files before replacing them, and avoid blindly merging an old archive over a newer installation.

Preserve the current filesystem before restoring

Even a broken site may contain newer uploads, configuration changes, logs, or custom files that are not in the backup. Copy or rename the current Joomla document root before replacing it. If disk space is limited, at minimum preserve configuration.php, user-uploaded media, custom code, and relevant logs.

Choose the correct backup and document root

Use the filesystem backup from the same recovery point as the database you plan to keep or restore. Identify the Joomla root by locating configuration.php, index.php, administrator/, components/, plugins/, and templates/.

Hosting providers may call this directory public_html, httpdocs, www, or a domain-specific folder. Extracting one level too high or too low will not restore the live site correctly.

Replace the damaged files instead of creating a mixed installation

  1. Put the site in maintenance/offline mode when possible.
  2. Move the current Joomla files to a protected temporary directory or otherwise isolate them.
  3. Upload or extract the backup into the actual Joomla document root.
  4. Include hidden files such as .htaccess when they belong to the backup.

Simply extracting an old archive over existing files can leave newer unwanted files behind because files absent from the archive are not automatically removed.

Restore normal ownership and permissions

Make sure the hosting account and web/PHP process can read the restored files and write only where Joomla legitimately requires it. Avoid using world-writable 777 permissions as a shortcut. If an archive was extracted by a different system account, correct ownership with the hosting provider or its supported tools.

Review configuration.php for the restored environment

If the restore is on a different server, account, directory, or database, verify the database host, database name, username, password, table prefix, log path, and temporary path in configuration.php. Do not replace this file with a generic file from a clean Joomla package.

Verify files and database are compatible

  1. Load the frontend and Administrator.
  2. Check several components and extensions.
  3. Review PHP logs for missing classes or version mismatches.
  4. Open Joomla's database maintenance screen and check for core schema issues.
  5. Test forms, media, login, and other critical workflows.

If the file restore follows a failed update, make sure the Joomla core files and database schema represent a consistent Joomla version before returning the site to production.


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.

Open a Support Ticket