Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsTo change a WordPress database prefix on an existing site, you must do three things together: rename every table that uses the old prefix, update prefix-bearing keys in the usermeta table, and change $table_prefix in wp-config.php. Changing the configuration line by itself leaves WordPress looking for tables that no longer match, which can trigger the installation screen or make users appear to lose their roles.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Take a restorable database backup first, perform the work during a controlled maintenance window, and verify the front end, dashboard, logins, permissions, content, and plugins before returning the site to normal traffic.
As an Amazon Associate I earn from qualifying purchases.
What the WordPress table prefix is
The table prefix is the text WordPress places at the beginning of its database table names. The default is wp_, so a standard installation has names such as wp_posts, wp_options, wp_users, and wp_usermeta. WordPress documents the setting as the value placed in front of your database tables.
The setting lives in wp-config.php:
$table_prefix = 'wp_';A different value is valid. For example, site7_ would produce site7_posts and site7_options. The prefix is a naming convention, not a separate database or a replacement for access controls.
#1 Best Overall
Why changing one line causes the installation screen
WordPress uses $table_prefix to construct the table names it queries. If you change wp_ to site7_ while the database still contains wp_options, wp_posts, and the other old names, WordPress cannot find the expected tables. The official sample configuration warns that changing the value after installation can make the site think it has not been installed.
The same mismatch can produce missing settings, failed logins, absent roles, or an apparent empty site. These symptoms do not mean the content was necessarily deleted; they usually indicate that the configuration and database names do not agree. Stop and restore the backup or correct the mismatch before proceeding with more edits.
Recommended Free Tools
Plan the change before editing anything
Inventory the current prefix and tables
Open wp-config.php and record the exact value assigned to $table_prefix. Then inspect the selected database in phpMyAdmin, Adminer, or a MySQL-compatible client and record every table beginning with that value.
Your inventory must include core tables and tables created by plugins or themes that adopted the old prefix. A typical installation has tables for posts, comments, terms, options, users, user metadata, and related metadata, but the exact list varies. Do not assume that a list copied from another site is complete.
Create and test a restorable backup
Export the complete database, not only the tables that look like WordPress core tables. Keep a copy away from the server. WordPress migration guidance treats SQL changes as permanent and instructs administrators to back up first.
- Confirm that the export completes without errors.
- Check that the file is readable and has a plausible size.
- Keep the original export unchanged.
- If your hosting platform offers a restore or staging environment, test that the backup can actually be imported.
A backup that has never been restored is an assumption, not a recovery plan. Table renames and metadata updates can affect the whole site, so do not begin until you know how to put the original database back.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Choose a valid new prefix
Use only letters, numbers, and underscores. A trailing underscore, such as site7_, makes the boundary between the prefix and table name clear. Choose a value that is not already used by another installation in the same database.
Write the old and new values at the top of your change notes. You will use them repeatedly, and a one-character discrepancy is enough to break the site.
Schedule a maintenance window
Prevent writes while the rename and metadata update are in progress. Put the site in maintenance mode or otherwise stop visitors and background jobs from changing posts, comments, users, or options during the operation. A controlled window prevents new data from being written to tables while you are renaming them and makes verification easier.
Rename the tables with a GUI
phpMyAdmin and Adminer provide a visual inventory and make it easy to inspect table names and row counts. They depend on access to the correct database, so verify the database name before selecting anything.
- Open the database selected by WordPress in
wp-config.php. - Filter or scan the table list for the complete old prefix, for example
wp_. - For each matching table, choose the rename operation and replace only the prefix.
wp_postsbecomessite7_posts; the remainder of the name stays unchanged. - Repeat for every matching core and plugin table. Do not stop after renaming the familiar core tables.
- Refresh the table list and confirm that no table beginning with the old prefix remains unless it is deliberately unrelated to this installation.
Use the interface to inspect the list before executing changes. If you select the wrong database or omit a plugin table, WordPress may load partially while a plugin fails later, which is harder to diagnose than an immediate, complete mismatch.
Rename the tables with SQL
An SQL client is useful when you need a repeatable script or have many tables. It requires stronger database knowledge and an independently verified backup. Generate or write one RENAME TABLE operation for every table in your inventory.
For an installation changing from wp_ to site7_, a shortened example looks like this:
RENAME TABLE
`wp_commentmeta` TO `site7_commentmeta`,
`wp_comments` TO `site7_comments`,
`wp_options` TO `site7_options`,
`wp_postmeta` TO `site7_postmeta`,
`wp_posts` TO `site7_posts`,
`wp_term_relationships` TO `site7_term_relationships`,
`wp_term_taxonomy` TO `site7_term_taxonomy`,
`wp_termmeta` TO `site7_termmeta`,
`wp_terms` TO `site7_terms`,
`wp_usermeta` TO `site7_usermeta`,
`wp_users` TO `site7_users`;This is an example, not a universal table list. Add every table in your inventory that uses the old prefix, including plugin-created tables. If a plugin deliberately uses a separate naming scheme, do not rename it merely because it is in the same database; establish whether WordPress or that plugin expects the old name.
Review the SQL carefully before execution. A typo in a table name, a missing comma, or a statement run against the wrong database can stop the migration or modify an unrelated installation. After execution, refresh the database and verify that the old names are gone and the new names exist.
Update prefix-bearing user metadata
Renaming wp_usermeta to site7_usermeta changes the table name, but some rows inside it also contain the old prefix in their meta_key. Role and capability keys are the important examples. If those keys retain the old value, users can authenticate but lose expected permissions.
After the table rename, adapt the following documented migration pattern to your actual values:
UPDATE `site7_usermeta`
SET `meta_key` = REPLACE(`meta_key`, 'wp_', 'site7_');Do not run this blindly. First inspect the rows that will change, confirm that site7_usermeta is the table for this installation, and record the affected-row count. Replace wp_ and site7_ with the exact old and new prefixes. The statement is intended for metadata keys; do not perform a broad search-and-replace across every column in the database.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →If your SQL tool supports a transaction for the specific operation, use its preview and confirmation features, but remember that table-definition changes can be committed immediately by the database engine. Your tested backup remains the reliable rollback method.
Change wp-config.php to the same value
Edit the configuration file only after the database names are ready, or do both actions inside the same maintenance window. Change the assignment to the exact new prefix:
$table_prefix = 'site7_';Preserve the PHP syntax, quotation marks, semicolon, and file encoding. Do not add spaces or characters inside the prefix unless they are part of the intended value. The value in the file must match the beginning of the renamed tables character for character.
Keep a copy of the original file until verification is complete. If the site fails before you can access the dashboard, reverting the configuration can help you diagnose whether the problem is a table mismatch, a PHP syntax error, or another issue.
Verify the site in a deliberate order
Remove maintenance mode only after these checks pass:
- Database names: Confirm that the new prefix appears on every intended table and that the old prefix is not still used by a required table.
- Front end: Load several pages, including a post, a page, an archive, and a page that uses a plugin feature.
- Dashboard: Sign in and open the main administration screens. Confirm that settings and content are present.
- Roles and capabilities: Test an administrator account and, where appropriate, a lower-privilege account. Check that expected menus and permissions remain available.
- Content operations: Create or edit a draft, upload or edit media if your normal workflow requires it, and save a setting. Verify that each operation completes.
- Plugins and themes: Open plugin settings and test features that read or write custom tables. Review the PHP error log for missing-table messages.
- Background work: Check scheduled tasks, comment handling, forms, and other automated processes used by the site.
If WordPress displays the installation screen, do not complete a new installation. A new installation could write fresh options into the wrong tables and make recovery more confusing. Compare the configured prefix with the actual table names, confirm that the correct database is selected, and restore the backup if you cannot identify the mismatch quickly.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common failure modes and recovery
| Symptom | Likely cause | Action |
|---|---|---|
| Installation wizard appears | wp-config.php points to a prefix for which tables do not exist, or the wrong database is selected. |
Stop. Check the exact prefix and database, then restore or complete the rename consistently. |
| Users can log in but have no expected role | Role or capability keys in usermeta still use the old prefix. |
Inspect the renamed usermeta table and update the old prefix in metadata keys using the documented pattern. |
| Dashboard loads but a plugin fails | A plugin table was omitted, or the plugin expects a custom table name. | Compare the plugin’s tables with your inventory and restore or rename the missing table as appropriate. |
| Some pages show database errors | One or more tables were mistyped, partially renamed, or left with the old prefix. | Compare the complete old and new inventories, review the database error log, and restore the backup if the list cannot be reconciled. |
| PHP syntax error after editing | The $table_prefix assignment lost a quote or semicolon. |
Restore the saved configuration file, then reapply only the intended value with valid PHP syntax. |
| Data appears missing immediately after the change | WordPress is reading an empty or unrelated set of tables. | Do not create content or run the installer. Correct the database selection and prefix or restore the original database. |
Does changing the prefix improve security?
WordPress hardening guidance notes that many published WordPress-specific SQL-injection attacks assume the default wp_ prefix and that changing it can block at least some of those attacks. A non-default prefix therefore provides a small amount of defense in depth by making that particular assumption less reliable.
It is not a security boundary. It does not repair vulnerable plugins, enforce least privilege, protect weak credentials, replace software updates, or substitute for secure backups and an application firewall. The same hardening guidance warns that security changes performed carelessly can introduce vulnerabilities. Treat the prefix as one layer in a broader maintenance plan, not as a reason to delay updates or access-control work.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
New installations and shared databases
Choosing a prefix during a new installation
For a new site, choose the desired prefix before WordPress creates its tables. This avoids the migration work required by an existing installation. WordPress allows each installation to use its own prefix, so separate sites sharing one database can be distinguished by values such as site7_ and store2_.
Record the chosen prefix with the site’s deployment documentation. Future administrators need the value when inspecting backups, troubleshooting database errors, or moving the site.
Changing an existing installation
An established site is materially more involved because table names, user metadata keys, plugin tables, configuration, and active traffic all have to remain consistent. Plan the change as a migration, not as a one-line hardening tweak.
Choosing a method: GUI, SQL client, or migration tool
| Method | Strengths | Risks and requirements |
|---|---|---|
| phpMyAdmin or Adminer | Visual table inventory, easy row inspection, and a familiar rename interface. | Requires host access and careful selection of the correct database. Manual selection can omit plugin tables. |
| MySQL-compatible SQL client | Repeatable, scriptable, and efficient when many tables must be renamed. | Requires stronger SQL knowledge, precise identifiers, and an independently verified backup. A script can affect the wrong database if the connection is misidentified. |
| Migration plugin | May automate search-and-replace and reduce manual operations. | Compatibility, maintenance status, and behavior for your WordPress and plugin set must be checked separately. No specific plugin is universally safe for this task. |
Choose based on your ability to inventory, review, and recover, not on the assumption that one interface is automatically safer. A careful operator with a tested backup can use either a GUI or SQL; an unfamiliar operator should avoid irreversible automation until the process is understood.
Free tools Windows power users keep installed
One-click scans. No signup required.
Complete change checklist
- Record the current
$table_prefixand database name. - List every table beginning with the old prefix, including plugin-created tables.
- Choose a new value containing only letters, numbers, and underscores; a trailing underscore is recommended for readability.
- Export the complete database and retain an off-site copy.
- Confirm that the backup can be restored or imported.
- Schedule maintenance and stop writes during the operation.
- Rename every intended table from the old prefix to the new prefix.
- Rename the usermeta table before updating its keys.
- Inspect and update prefix-bearing keys in the renamed usermeta table.
- Change
$table_prefixinwp-config.phpto the exact new value. - Refresh the database inventory and check for omissions.
- Test the front end, dashboard, authentication, roles, content changes, plugins, themes, and background jobs.
- Keep the original backup and configuration copy until the site has operated normally.
The safe outcome is not merely a dashboard that opens. It is a complete, verified match among the configuration value, every required table name, prefix-bearing user metadata, and the site’s normal read and write operations.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
