Knowing how to restore WordPress from website files and a database can save you from losing an entire website after a server failure, security incident, broken update, migration problem, or accidental deletion. A WordPress website is made up of two critical parts: its files and its database. Both need to be restored correctly for the website to work as expected.
The good news is that you do not necessarily need a complicated restoration tool. If you have a working copy of your WordPress files and a database backup, you can restore the site manually using an FTP/SFTP client, hosting control panel, phpMyAdmin, or WP-CLI. This guide explains the process step by step so you can restore your WordPress website safely and understand what each stage does.
7 Steps to Restore WordPress from Website Files and a Database
1. Check Your WordPress Backup Files and Database
Before restoring anything, confirm that you have both parts of your WordPress backup: the website files and the database. The files normally contain WordPress core files, themes, plugins, media uploads, and configuration files. The database contains posts, pages, users, settings, comments, and other dynamic website information.
A common mistake is having only one part of the backup. Restoring the files without the database will not recreate your website’s content, while restoring only the database will not provide the themes, plugins, or uploaded media.
Ideally, check the backup date and make sure the files and database belong to the same version of the website.
Before continuing, verify:
- WordPress files are complete and accessible.
- A database backup is available.
- You know the database name, username, and password.
- The backup date is suitable for the restoration.
- You have access to your hosting account.
2. Create a New Database for the WordPress Restoration
If you are restoring WordPress on a new server or a clean hosting account, create a new MySQL or MariaDB database before importing your backup.
Most hosting control panels provide a database management section where you can create the database, database user, and password. Record these details because WordPress will need them to connect to the restored database.
If you are restoring over an existing installation, consider creating a fresh database rather than immediately overwriting the old one. This provides an additional safety layer if you need to troubleshoot the restoration.
The exact database creation process depends on your hosting provider, but the important requirement is that the database user has sufficient privileges to access the database.
3. Import the WordPress Database Backup
The next step is to restore the database containing your WordPress content and settings. One of the most common options is phpMyAdmin, which allows you to manage MySQL or MariaDB databases through a web interface.
Open phpMyAdmin, select the newly created database, and use the Import function to upload your SQL backup. After the import completes, check that the database contains WordPress tables such as those beginning with your site’s configured table prefix.
For larger databases, phpMyAdmin may have upload or execution limits. In that situation, your hosting provider may offer another database restoration method, or you can use a command-line tool such as WP-CLI or the MySQL client.
Do not delete your original backup after importing it. Keep it available until the restored website has been fully tested.
4. Upload and Restore Your WordPress Website Files
After restoring the database, upload your WordPress website files to the correct document root on the server. Depending on your hosting setup, this might be a directory such as public_html, htdocs, or another configured web root.
You can transfer files using SFTP, FTP, your hosting file manager, or another supported method. Make sure important directories such as wp-content, wp-admin, and wp-includes are restored correctly.
Pay particular attention to the wp-content directory because it contains your themes, plugins, and uploaded media. Your wp-config.php file is also important because it contains the database connection information WordPress uses.
If the backup came from another server, do not assume its database credentials will work on the new hosting account. Update the configuration with the new database details when necessary.
5. Update wp-config.php and Check the Database Connection
WordPress needs the correct database credentials to communicate with the restored database. These details are normally stored in the wp-config.php file.
Check the database name, database username, database password, and database host. If any of these values differ from your new hosting environment, update them accordingly.
For example, the configuration must point WordPress toward the database you just restored. If the credentials are incorrect, you may see database connection errors instead of your website.
Also check the $table_prefix value. It must match the table prefix used by the restored database. If the database uses a different prefix and the configuration points to the wrong one, WordPress may behave as though the site has no content.
Once these values match, load your website and check whether WordPress can connect to the restored database.
6. Correct the Site URL and Refresh WordPress Permalinks
If you restored the website to a different domain, subdomain, or temporary URL, you may need to update the site’s URL. WordPress stores its site address in the database, so simply uploading the files does not always change the URL automatically.
Be careful when performing search-and-replace operations because WordPress databases can contain serialized data. Use a WordPress-aware tool rather than performing a basic database-wide text replacement without understanding the consequences.
After the URL is correct, log in to WordPress and visit Settings → Permalinks. You can usually refresh the permalink structure by selecting the current setting and saving the changes.
This can resolve situations where the homepage loads but individual posts or pages return 404 errors.
Also check images, internal links, redirects, SSL configuration, and canonical URLs if the website has moved to a different domain.
7. Test the Restored WordPress Website Before Going Live
A WordPress restoration is not complete simply because the homepage loads. Perform a structured test before considering the website fully recovered.
Start by checking the homepage, important landing pages, blog posts, images, menus, contact forms, and login functionality. Test the WordPress dashboard and confirm that plugins and themes are functioning correctly.
You should also check whether the website is loading over HTTPS and whether there are mixed-content warnings. Review important SEO elements such as robots.txt, XML sitemaps, canonical tags, redirects, and indexability if the restoration involved a domain or server change.
Finally, test backups and security settings after recovery. If the site was restored because of malware or another security issue, investigate the original cause before assuming the website is safe.
Quick Comparison: Manual Restoration vs. Backup Tools
The best restoration method depends on your situation.
| Restoration method | Best for | Main advantage |
| Manual files + database | Developers and administrators | Maximum control |
| Hosting backup | Most website owners | Usually faster and simpler |
| WordPress backup plugin | Routine recovery | Easy scheduled backups |
| SFTP + phpMyAdmin | Manual migration or recovery | Widely supported |
| WP-CLI | Technical users | Efficient for larger sites |
For a small website, a hosting backup or reliable WordPress backup plugin may be the easiest option. Manual restoration is particularly useful when you have only a database dump and website files or need to recover a site on a different server.
Tips for a Safer WordPress Restoration
Before restoring a live website, keep a copy of the current files and database if they are still available. This gives you something to return to if the restoration does not work as expected.
It is also useful to restore the website in a staging environment first. You can then identify broken plugins, missing files, database errors, URL problems, or PHP compatibility issues without disrupting visitors.
For future protection, maintain automated backups and store copies separately from the production server. A backup is most useful when you can actually restore it, so periodically test your backup restoration process rather than assuming every backup is valid.
Conclusion
Learning how to restore WordPress from website files and a database gives you a reliable way to recover a website after server problems, failed updates, accidental deletion, migration issues, or other unexpected events. The essential process is straightforward: verify your backup, create a database, import the SQL file, restore the WordPress files, configure wp-config.php, correct the site URL when needed, and thoroughly test the website.
For businesses that want help with hosting, website recovery, technical fixes, SEO, or ongoing website management, TK WebHosts provides professional web and technical services designed to keep business websites running and growing. Taking backups regularly and knowing how to restore them can make the difference between a minor interruption and a major website recovery problem.
Frequently Asked Questions
Can I restore WordPress using only website files?
No. Website files alone normally cannot restore the complete WordPress website because posts, pages, users, settings, and other dynamic information are stored in the database. To fully restore WordPress, you generally need both a compatible copy of the website files and a database backup.
How do I restore a WordPress database using phpMyAdmin?
Create or select the destination database in phpMyAdmin, then use the Import option to upload your SQL backup. After the import, confirm that the WordPress tables are present. Your wp-config.php file must then contain the correct database name, username, password, host, and table prefix.
What happens if WordPress files and the database are from different backups?
The website may still work, but inconsistencies can occur. For example, the database could reference plugins, themes, media, or settings that are missing from the older file backup. Whenever possible, restore files and the database from the same backup date.
Can I restore WordPress to a new hosting provider?
Yes. You can restore WordPress to a new host by creating a database, importing the database backup, uploading the website files, configuring wp-config.php, and updating the site URL when necessary. You should then test the website, SSL, DNS, redirects, forms, and other important functions.
How can I avoid losing my WordPress website again?
Use automated, scheduled backups that include both the WordPress files and database. Keep backup copies outside the production server and periodically test restoration. A reliable hosting environment, security monitoring, updates, and tested backups can significantly reduce recovery time.