How to update WordPress safely: core, plugins, themes
Published on July 4, 2026 8 min read
Updating WordPress without breaking your site? Learn how to update the core, plugins and themes safely, set up auto-updates and restore your site.
Updating WordPress is one of the most important routines for anyone who runs a website. Every update to the core, your plugins and your theme closes security holes, keeps everything compatible and often makes your site faster. This guide explains why updates matter, how to update WordPress safely step by step, how to set up auto-updates and what to do if an update breaks your site.
Why updating WordPress matters
A WordPress site is made up of three layers that you update separately: the core (WordPress itself), your plugins and your theme. All three receive regular updates, and keeping them current matters for three reasons.
Security
Outdated components are the biggest security risk in WordPress. According to security firm Patchstack's report State of WordPress Security in 2026, 11,334 new vulnerabilities were found in the WordPress ecosystem in 2025. Of those, 91 percent were in plugins and 9 percent in themes. Only six were reported in the WordPress core itself, all of them low priority. Updating closes exactly those gaps. For 46 percent of the vulnerabilities, the developer did not have a fix ready when the flaw was made public. If a plugin has not received updates for a long time, replace it with one that is actively maintained. If a browser or antivirus warns that your site is unsafe, see how to check whether your site is infected and get the warning removed.
Together with a valid SSL certificate, updates are the foundation of a secure site.
Compatibility
Plugins, themes and the core all have to work with each other and with your server's PHP version. WordPress recommends PHP 8.3 or higher. When one component falls behind, features can stop working or clash with a newer plugin. Regular updates keep everything in step. To see which PHP version your site uses and how to change it safely, read change the PHP version in Plesk.
Speed
New versions often include performance improvements and take advantage of faster PHP versions, so an up-to-date site usually loads more quickly. If you want to go further afterwards, read how to speed up your website.
Before you start: make a backup first
The vast majority of updates go smoothly, but a small chance of a conflict always remains. That is why you start with a fresh backup every time. As long as you can fall back on a copy, a failed update is never more than a brief setback.
Make a full backup of your files and your database before you change anything. You can find out how in our guide on how to make a website backup. If you update through WP Toolkit in Plesk, you also create a restore point right before the update. If you run an important or busy site, consider testing large updates in a staging environment first. You can read more about both below.
How to update WordPress in 5 steps
Update your components one at a time and check your site after each step. That way you know straight away which update caused any problem. You will find all updates in your WordPress dashboard under Dashboard > Updates.
- Make a backup. Create a current copy of your files and database and store it away from your site, for example on your computer or in external storage.
- Update the WordPress core. Go to Dashboard > Updates and bring WordPress itself up to the latest version. By default, WordPress has installed minor updates automatically since version 3.7; major updates you apply here yourself.
- Update your plugins one by one. Update each plugin separately and check your site after every one. That way you spot a conflict immediately, rather than after running ten updates at once.
- Update your theme. If you use a customised theme, work with a child theme or note your changes, so a theme update does not overwrite your custom work.
- Check your site. Look at the front end and the dashboard, log out and test your site as a visitor too. Pay attention to your most important pages, your forms and your web shop if you have one.
Updating WordPress with WP Toolkit in Plesk
LJPc hosting includes WP Toolkit (formerly WordPress Toolkit) in Plesk. All WordPress sites in your hosting plan are listed there in one place, together with the updates that are ready for each site. The big advantage: WP Toolkit creates a restore point right before the update, so you can roll back a failed update without restoring your entire backup. If you installed WordPress with WP Toolkit, as described in install WordPress in Plesk, your site is already listed.
- Open Plesk from the customer portal: on the dashboard, click Plesk next to your site. Read open Plesk from the customer portal to see how that works.
- Click WordPress in the menu on the left. If your site is not listed, click Scan so WP Toolkit looks up your installation.
- Click Updates on your site. You will see the available updates, grouped under WordPress Core, Plugins and Themes.
- Select what you want to update and click Update.
- WP Toolkit recommends creating a restore point first. Choose Create a restore point and confirm the update.
- Check your site as in step 5 above.
If something goes wrong, open the Restore Point section on your site and click Restore. WP Toolkit then takes your site back to the version from before the update. A restore point only contains the data the update changes, so it does not replace a full backup.
Setting up auto-updates
If you would rather not update by hand every week, you can have updates applied automatically. You can do this in WordPress itself and through WP Toolkit in Plesk.
Auto-updates in WordPress itself
Since WordPress 5.5 you can switch on auto-updates per plugin and per theme from the dashboard. Go to Plugins and click Enable auto-updates next to a plugin. For a theme, open it under Appearance > Themes and click Enable auto-updates. Security updates for the core have run automatically by default since version 3.7. Auto-updates are convenient, but keep an eye on your site now and then, because an automatic update can cause a conflict too.
Auto-updates through WP Toolkit in Plesk
In WP Toolkit you set per site what gets updated automatically. In Plesk, click WordPress and then Update Settings on your site. You choose three things there:
- Update WordPress automatically: No, Yes, but only minor (security) updates, or Yes, all (minor and major) updates. The middle option installs security updates automatically and leaves major versions to you.
- Update plugins automatically and Update themes automatically: Defined individually (each plugin or theme follows its own setting), Defined individually, but security updates are autoinstalled (components with a known vulnerability are still updated automatically), or Forced (everything is updated automatically).
If you want to decide yourself when to update while still closing known vulnerabilities quickly, choose Defined individually, but security updates are autoinstalled for plugins and themes. If you do not see WordPress in the Plesk menu, or an option is missing, contact support.
Testing large updates in a staging environment
A staging environment is a separate, shielded copy of your site that visitors never see. There you can test large updates, a new plugin or a theme change without any risk to your live site. Once everything works as expected, you apply the change to your real site.
For a small blog this is usually not necessary, but for a web shop or a business site with many plugins it is a sensible habit. With WP Toolkit in Plesk you create such a copy yourself. See how to create a WordPress staging site. There are also standalone plugins that offer staging.
If the test succeeds, run the update again on your live site. If you use Copy Data to copy the database from the copy to your live site as well, you overwrite the orders and form entries that came in on a web shop or a site with forms since you made the clone. Once you no longer need the copy, remove it so only your current site stays online.
What to do if an update breaks your site
If something does go wrong despite your care, stay calm. It is usually fixed quickly. Below are the most common situations and how to handle them.
| Symptom | Cause | Solution |
|---|---|---|
| Blank page or critical error | A plugin or theme clashes with the new version | Since version 5.2, WordPress emails a recovery mode link to your admin address. Log in through that link and disable the component. The error log in Plesk shows which component causes the error. |
| Site works, but something looks off | A theme or plugin update changed the layout | Clear your cache, check the component's settings and, if needed, update the matching theme or plugin as well. |
| A plugin shows an error | The plugin is not ready for the new core yet | Disable the plugin for now, wait for an update from its maker or look for an alternative. |
| Nothing works any more | Several problems at once | Restore your backup. If you updated with WP Toolkit and created a restore point, roll back the update with Restore under Restore Point. |
Locked out of your dashboard? Log in through the recovery mode link in the email from WordPress, or restore your most recent backup. Then try the update again, this time one component at a time. What the technical issue email and the other emails from your site mean is explained in unexpected email from your WordPress site.
With a fresh backup, updates applied one at a time and a quick check afterwards, you keep your WordPress site secure, compatible and fast. Stuck? Create a support ticket and we will help you out.
Frequently asked questions
How often should I update WordPress?
Check your site for updates weekly if you can, and install security updates as soon as possible. WordPress applies minor core updates automatically. For plugins and themes, the sooner you update, the smaller the chance that a known flaw gets exploited.
Should I update the core or the plugins first?
Always make a backup first. Then update in this order: the WordPress core first, then your plugins one by one and finally your theme. Check your site after each step so you can see straight away which component caused a problem.
Are automatic updates safe?
Automatic security updates for the core have run since WordPress 3.7 and are very reliable. Auto-updates for plugins and themes are convenient but carry a small chance of a conflict. A good middle ground is the WP Toolkit setting that updates plugins and themes with a known vulnerability automatically and leaves the rest to you. Test large updates in a staging environment and check your site from time to time.
Can I roll back a WordPress update?
Yes, if you run the update with WP Toolkit in Plesk and create a restore point. Click Restore under Restore Point on your site to return to the version from before the update. If you updated from the WordPress dashboard, restore your backup instead.
My site is blank after an update. What now?
Since WordPress 5.2, a critical error automatically triggers an email with a recovery mode link to your admin address. Use that link to log in and disable the component causing the error. If that does not work, restore your backup.
Which PHP version do I need for WordPress?
WordPress recommends PHP 8.3 or higher. At LJPc hosting you choose the PHP version per site in Plesk, and PHP 8.3 and 8.4 are available on all our servers. Choose the newest version your plugins and theme support. Read the article on changing the PHP version in Plesk to see how to check and change it.