How to reset and restore a WordPress site

A reset usually means removing content, settings, plugins or themes so you can start again. A restore means returning the site to a saved state. They are different operations, so do not reset first if your real goal is to recover the current site.

For a clean rebuild, a fresh directory and empty database are safer than deleting selected tables and files from a live installation. Selective deletion can leave old plugin data, uploads or database tables behind.

Back up the database and the WordPress files separately. The database contains posts, pages, users, settings and plugin data, while the files include themes, plugins, media, wp-config.php and other server files. You need both for a full restore.

Download the SQL export and file archive, store them somewhere away from the server, and record the database name, host, user, password and table prefix from wp-config.php. A backup that contains only the files cannot restore your content.

For a genuine clean start, use your host to create a new database and install a fresh WordPress copy, or use WP-CLI if your server provides it. The command wp db reset --yes removes all tables from the current database, so confirm the site path and backup before running it.

Do not use a database reset on a live site just to troubleshoot one plugin. It can remove users, content and settings, and support reports regularly mention locked-out administrators after selecting every table. Keep the old database and files until the replacement site works.

Upload the backed-up WordPress files through SFTP, FTP or your hosting file manager. Restore the core files, wp-content, uploads, themes, plugins and any required server files. If you are restoring to a different database, edit wp-config.php so its database credentials and table prefix match the destination.

For a clean replacement, remove old files that are not in the backup rather than only overwriting existing files. Leftover plugins or modified files can keep causing the original problem. WordPress documentation recommends restoring the files before importing the database.

Use phpMyAdmin, Adminer or WP-CLI to import the SQL file into the destination database. With WP-CLI, the documented command is wp db import backup.sql. Import into the database named in wp-config.php, and check that the table prefix in the imported tables matches the prefix in the configuration file.

If the site is moving to a new domain, update the stored site address and replace old URLs carefully. Do not run a simple find-and-replace across serialized data; use a tool that understands serialized values or follow your host's migration procedure. The siteurl and home values are common causes of redirect loops and a missing dashboard after migration.

Open the homepage and /wp-admin, test user login, check media, forms, search, permalinks and any shop or membership features. In the dashboard, visit Settings > Permalinks and save the settings once to refresh rewrite rules if links return 404 errors.

Clear page, object and CDN caches, then check the PHP error log if you see a blank page or critical error. If the restore shows the WordPress installation screen, check the database credentials and table prefix before importing again. Keep the original backup untouched until every important function passes.

For developers who reset sites repeatedly, WP Reset PRO can shorten the process with one-click reset options, database snapshots and recovery tools. It is useful for testing changes or troubleshooting without rebuilding the site each time.

Before using any automated reset, read which tables, files, users and uploads the selected operation affects. Take a fresh snapshot first, and treat a reset as destructive unless the tool clearly offers a recovery point.