What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
For most sites, the safest way to upgrade WordPress is to first verify a backup of both the database and site files, then use Dashboard > Updates > Update Now for the core update. Follow any database-upgrade prompt and check the site afterward. Manual file replacement is a fallback—not a better default—and changing PHP is a separate task handled through your host.
Before you upgrade: make sure you can recover
WordPress recommends backing up before an upgrade. A complete recovery point needs both the database and the site files: the database holds content and settings, while files include themes, plugins, uploads, and wp-config.php. A database export alone is not a complete site backup. See WordPress’s database backup guidance and its extended upgrade instructions.
- Confirm the backup completed and that you know how it can be restored; do not begin on the assumption that an automatic host backup is complete.
- If the site is business-critical or you cannot verify restoration, ask your host what its backup covers and how it restores the database and files.
- Review available updates at Dashboard > Updates. Check plugin update information and compatibility notes where available. Compatibility may be unknown, particularly when a plugin has not been updated since the latest core release. WordPress’s plugin management guidance covers plugin updates.
- If the site is already unstable, avoid combining the WordPress core update with several unrelated changes. That makes it easier to identify what caused a problem.
Upgrade WordPress core from the dashboard
The dashboard’s one-click core update is the ordinary route and works on most servers, according to WordPress.org’s Updating WordPress guide. That page, last updated September 15, 2024, says, “You should always update WordPress to the latest version.” Check your site’s Updates screen for the version currently offered to it.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →- Sign in to your WordPress administration area and open Dashboard > Updates.
- Review the available core update and any plugin, theme, or translation updates listed. Keep the core update distinct from other changes if you need to isolate problems.
- For the core update, select Update Now and allow the process to finish. Do not repeatedly retry a failed update without checking the cause.
- If WordPress displays a database-upgrade prompt after updating files, follow it promptly.
- Open the public site and the administration area. Check important pages and functions, then clear the site cache so visitors receive the updated files.
Core updates and automatic plugin or theme updates are separate. WordPress documents automatic background installation of minor and security releases for supported installations; major feature releases require the site owner to initiate an update. Plugin and theme automatic-update controls vary by installation, host, and configuration, and scheduled updates rely on WordPress Cron tasks. Do not assume every site has the same settings; check the Updates screen and the current plugin and theme auto-update documentation (last updated January 13, 2023).
#1 Best Overall
When to use the manual upgrade process
Use a manual upgrade if the dashboard update does not work or if you already manage WordPress files directly. It requires access to site files and careful handling; WordPress describes the process in its extended instructions.
- Back up and verify both the database and all site files before changing anything.
- Follow the current WordPress instructions for obtaining the package and replacing core files. Deactivate plugins as directed by the extended procedure, then reactivate them afterward.
- Preserve
wp-config.phpandwp-content. In particular, do not delete the existingwp-contentdirectory when copying the new package: it contains themes, plugins, and uploads. - Run the upgrade program or follow the database-upgrade prompt when required, then check the site and administration area.
- Refresh permalinks or
.htaccesswhere applicable in the extended procedure, and clear caches.
Do not improvise a file-deletion or replacement recipe if you are unsure which files belong to WordPress core. Ask your host or a WordPress professional to help.
What to check after the update
- Open the homepage and several important pages on the public site.
- Sign in to the administration area and confirm it loads correctly.
- Test the functions your site depends on, especially forms, checkout, search, and other plugin-powered features.
- Reactivate plugins if you used the manual procedure, and clear any site or hosting cache.
- If following the extended manual process, refresh permalinks or
.htaccesswhere applicable.
If an update fails or the site looks broken
The one-click update failed
Filesystem permissions are one documented reason a dashboard update may fail. Consult the official update instructions; if the issue involves server access or permissions, contact your host rather than changing permissions blindly. A failed update may leave a .maintenance file that keeps a maintenance notice visible. WordPress documents removing that file through FTP as a narrow fix for someone who can safely access site files.
A database-upgrade prompt appears
Follow the prompt after the core files have been installed. Do not treat the prompt as a reason to restore files or alter the database without a recovery plan.
Rank #3
A plugin fails or site behavior changes
Plugin compatibility may be unknown. Review the plugin’s update information, and contact its developer or your host if you cannot identify the problem. If recovery is needed, use a coherent backup of both files and database rather than restoring only one part of the site.
Custom code or theme changes disappear
Core upgrades can overwrite edits made directly to WordPress distributed files, including default theme files. WordPress explains this in its troubleshooting guidance. Keep custom work out of files that an upgrade replaces, and retain a backup before updating.
Rank #4
The site still shows old pages
Clear the site cache after the upgrade so updated files are served.
PHP upgrades are separate from WordPress core updates
Changing the server’s PHP version is not a required step in every WordPress core upgrade. PHP is set at server level, and the method depends on the hosting provider. Before requesting a PHP change, back up the site, update WordPress, themes, and plugins, and check compatibility. Compatibility checks can miss issues or report false positives. WordPress’s PHP update guidance explains the host-dependent process. If a PHP change causes trouble, ask the host whether it can restore the previous PHP version; coordinate that with restoring the site backup if necessary.
Best Value
Dashboard update or manual update?
| Route | What you need | Best fit | Main risk to manage |
|---|---|---|---|
| Dashboard: Dashboard > Updates > Update Now | WordPress administration access | Most sites and users who do not manage WordPress files directly | Server permissions or another server-side issue can block the update; consult the host if needed. |
| Manual file update | Site-file access and care following the official procedure | A dashboard update that fails, or administrators who intentionally manage files directly | Replacing or deleting the wrong files can damage the site; preserve wp-config.php and wp-content. |
Neither route removes the need for a verified backup. Manual updating is a fallback with more hands-on steps, not a guarantee of a safer result.
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.
