Finding that WordPress database tables missing is the cause of your site’s problems is more alarming than it sounds once you understand what it actually means — and less catastrophic than it sounds once you understand the available recovery paths. The WordPress database contains a set of standard tables: wp_posts, wp_options, wp_users, wp_usermeta, wp_terms, wp_postmeta, and several others. The WordPress database tables missing error appears when one or more of these tables cannot be found in the database, which can happen for several distinct reasons. A database that was created but never had WordPress’s tables populated. A migration that transferred files but not the database. A partial database deletion. A failed update that dropped tables it intended to recreate. Or a database that was corrupted severely enough that the affected tables are no longer accessible. Each of these WordPress database tables missing scenarios has a different recovery path, and identifying which one applies to your situation determines where to start. If you want the full context, see our WordPress Errors Complete Guide.
Understanding Why WordPress Database Tables Go Missing
The distinction between WordPress database tables missing and the WordPress database connection error matters for diagnosis. A database connection error means WordPress cannot connect to the database at all — credentials, server, or network problem. WordPress database tables missing means WordPress can connect to the database, finds the database itself, but the expected tables are absent or inaccessible. The difference is significant because it narrows the possible causes considerably.
| Scenario | Cause | Recovery Path |
|---|---|---|
| All tables missing | Wrong database selected in wp-config.php; migration without database transfer | Verify DB_NAME in wp-config.php; import database backup |
| Specific tables missing | Partial deletion; plugin/theme that dropped tables; failed update | Run WordPress database repair; restore from backup |
| Tables exist but inaccessible | Table corruption; user permissions; InnoDB crash | phpMyAdmin repair; MySQL table recovery |
| Tables missing after plugin deactivation | Plugin that created custom tables and removed them on uninstall | Plugin reinstallation; custom table recreation from plugin documentation |
The WordPress dashboard error message for WordPress database tables missing often includes a list of the specific tables that cannot be found — “One or more database tables are unavailable. The database may need to be repaired.” This list is the most useful diagnostic information available. Core WordPress tables being absent (any table in the standard wp_ prefix set) is more urgent and more structurally significant than custom plugin tables being absent. The core tables contain all posts, users, settings, and content; without them, the site cannot function. Plugin custom tables being absent breaks the plugin’s functionality but leaves the rest of the site intact.
Run the WordPress Database Repair Tool for Missing Tables
The WordPress built-in database repair tool is the first fix to attempt when WordPress database tables missing is suspected as the cause. This tool does more than repair corrupted tables — it also detects and attempts to recreate missing tables based on the expected WordPress schema. It is not guaranteed to restore data that has been deleted, but for tables that are missing due to corruption rather than outright deletion, the repair tool can often recover them.
- Open
wp-config.phpvia FTP and add this line before “That’s all, stop editing!:”:define( 'WP_ALLOW_REPAIR', true ); - Save the file and visit
https://yoursite.com/wp-admin/maint/repair.phpin your browser - Click Repair and Optimize Database — this is more thorough than the Repair-only option for WordPress database tables missing situations
- Wait for the tool to complete — it reports on each table, showing OK, Repaired, or errors for each one
- Note any tables still shown as errored after the repair — these are the ones that cannot be automatically recovered
- Remove the
WP_ALLOW_REPAIRline fromwp-config.phpimmediately after the repair completes - Reload the site and test whether the WordPress database tables missing error has cleared
If the repair tool cannot recover specific tables — either because they are truly gone rather than corrupted, or because the corruption is too severe — the next step depends on whether a database backup exists. A recent backup is the definitive solution for WordPress database tables missing caused by deletion or unrecoverable corruption. In the absence of a backup, phpMyAdmin can attempt lower-level table recovery using MySQL’s repair table functionality, which sometimes succeeds where WordPress’s own repair tool cannot.
Restoring Missing Tables From a Database Backup
A database backup is the most reliable path to full recovery when tables are genuinely missing rather than corrupted. WordPress database tables missing that result from accidental deletion, a plugin that dropped tables without warning, or a database migration that went wrong are all recovery scenarios where the WordPress repair tool alone cannot restore the missing data — the data needs to come from somewhere, and a backup is that source.
If you have a recent database backup as a .sql file, the import process through phpMyAdmin is straightforward. Log in to phpMyAdmin through cPanel, select your WordPress database from the left sidebar, click the Import tab, choose your backup .sql file, and import. For large databases, phpMyAdmin’s upload limit may be a constraint — if your backup file is larger than the allowed upload size, use MySQL’s command-line import instead: mysql -u username -p database_name < backup.sql. After the import, reload WordPress and verify the WordPress database tables missing error has cleared and all content is present.
For sites running managed WordPress hosting — Kinsta, WP Engine, SiteGround, Cloudways, and similar — daily automatic backups are a standard feature and restoration is typically one click from the hosting dashboard. If you discovered the WordPress database tables missing problem within the backup retention window (usually 14–30 days on managed hosts), restoring to a point before the tables went missing is available without any manual database work. This is the fastest recovery path and should be explored before attempting manual repair or partial imports.
When wp-config.php Points to the Wrong Database
A surprisingly common cause of the WordPress database tables missing error — particularly after hosting migrations — is that wp-config.php has the correct database server credentials but the wrong database name in the DB_NAME constant. WordPress connects successfully to the database server, but opens a different database than the one containing the WordPress tables. The selected database is empty or contains tables from a different application, and the WordPress database tables missing error results.
Open wp-config.php via FTP and verify the DB_NAME value. Then log in to cPanel and check MySQL Databases — the database names listed there need to match what is in wp-config.php exactly. On many hosting environments, the database name includes an account prefix: if your hosting account username is user1234, the database might be named user1234_wordpress rather than simply wordpress. A DB_NAME value of just wordpress without the prefix produces the WordPress database tables missing error because WordPress opens an empty or non-existent database while the actual WordPress database with the correct name goes untouched. Correcting the DB_NAME to the full prefixed name resolves this form of the WordPress database tables missing error immediately without any database repair or restoration.
Similarly, some migrations transfer the WordPress files to a new server and create a new database there, but the new database has a different name than what wp-config.php still references from the old server. The WordPress database tables missing error in this context is not a database problem at all — it is a configuration mismatch. Updating DB_NAME (and potentially DB_USER and DB_PASSWORD if those also changed) to reflect the new server’s database configuration is the complete fix, assuming the database was successfully transferred as part of the migration.
Plugin Uninstall Processes That Remove Database Tables
Some WordPress plugins create their own custom database tables when installed and remove them when uninstalled. This is the correct behaviour for well-designed plugins that do not want to leave orphaned database tables after removal. However, some plugins remove their tables on deactivation rather than uninstallation — which means simply deactivating a plugin to test it or troubleshoot it deletes its tables, and reactivating the plugin does not automatically restore the deleted data. The WordPress database tables missing error that results from this is specific to the plugin’s functionality: everything WordPress core does works fine, but the plugin that lost its tables shows errors or missing data when its features are accessed.
If the WordPress database tables missing error is isolated to a specific plugin’s functionality — an e-commerce store showing no products, a booking plugin showing no appointments, a custom post type plugin showing no content — a deactivation/reactivation cycle that deleted the plugin’s tables is a likely cause. Reinstalling the plugin from scratch (not just reactivating it) sometimes triggers the table creation routine again, restoring the table structure. But this restores the structure only — the data that was in the tables is gone unless a database backup is available. Check whether the plugin has an import feature that accepts the data format from a backup, and whether the plugin documentation describes what to do when its tables have been inadvertently deleted.
Our guide on fixing the WordPress database connection error covers the related database access problem where WordPress cannot connect to the database at all — the distinction between connection errors and WordPress database tables missing errors is important because they have entirely different causes and fixes. Our guide on how to backup a WordPress site properly covers automated backup configuration that prevents the WordPress database tables missing scenario from becoming a permanent data loss event — a daily automated backup means the worst case for missing tables is one day of data loss rather than complete data loss. The MySQL REPAIR TABLE documentation covers the low-level table repair options available directly through MySQL for WordPress database tables missing situations where the tables are not truly absent but are damaged beyond what the WordPress repair tool can address. If this sounds familiar, WordPress Theme Missing Stylesheet is worth a look.
