Kiwistic Get a Free Quote

Home / WordPress Guides / Security & Maintenance / How to Manually Update WordPress Plugins Step by Step

How to Manually Update WordPress Plugins Step by Step

Ognjen Velickovic
}

Last updated Oct 27, 2026

TABLE OF CONTENTS

Free WordPress Site Review

Is your WordPress setup ready for what 2026 demands?
Get a Free Site Review

TL;DR

To manually update a WordPress plugin, go to Plugins → Installed Plugins and click Update Now next to the plugin. Back up your website first and test important features after the update. If the dashboard update fails or isn’t available, you can replace the plugin files through SFTP or your hosting File Manager using a verified plugin package. Always keep a recovery option in case the update causes problems.

WordPress plugin updates can fix security vulnerabilities, resolve bugs, and improve compatibility with newer versions of WordPress. But an update can also introduce conflicts that affect your site’s functionality.
Manually updating plugins gives you control over when changes are applied and lets you test important features afterward. That’s especially useful for business websites that rely on contact forms, WooCommerce, or other essential plugins.
This guide covers updating plugins through the WordPress dashboard and via SFTP when dashboard access isn’t available, including how to handle failed updates and restore a working version.

Why Regular WordPress Plugin Updates Matter

Outdated plugins can expose your website to known security vulnerabilities, compatibility issues, and bugs that have already been fixed in newer releases. Keeping plugins updated helps reduce these risks, but every update still needs to be handled carefully.
There are three main reasons to review plugin updates regularly:

1. Security fixes. Some updates address vulnerabilities that could otherwise be exploited. Check the plugin’s changelog or security notices to understand whether an update contains an important security fix.

2. Bug fixes and compatibility. Developers release updates to resolve errors and support newer WordPress or PHP versions. However, a new release can also introduce conflicts, particularly when your website relies on several interconnected plugins.

3. Performance and functionality. Updates may improve how a plugin runs or introduce useful features. These benefits depend on the specific release, so don’t assume every newer version will make your website faster.

For business websites, the safest approach is to review available updates, back up the site, and test critical functionality afterward.

Manual updates give you control over when changes happen. Automatic updates reduce the need for routine intervention. Neither approach eliminates the possibility of errors, so the right choice depends on the importance of each plugin and how your website is maintained.

Plugins you no longer use need attention too. Learn about the risks of inactive WordPress plugins before deciding which ones to keep installed.

Before You Update WordPress Plugins

Before updating a plugin, take a few minutes to check what’s changing and make sure you can recover if something goes wrong.

1. Review the update details. Go to Plugins → Installed Plugins and check the available version, changelog, and compatibility information. Pay particular attention to major releases or plugins that haven’t been updated in a long time.

2. Back up your website. Create a current backup of your database and website files. If the plugin stores orders, form submissions, or other important data, make sure your recovery plan accounts for changes made after the backup. Verify that the backup is accessible and can be restored.

3. Test important updates on staging. If a plugin controls checkout, payments, bookings, forms, or other business-critical features, test the update on a staging website when possible. Check the affected functionality before updating the live site.

4. Know what to check afterward. Identify the features that depend on the plugin. For example, after updating a contact form plugin, submit a test form and confirm the message is received. After updating a WooCommerce extension, test the relevant store functionality.

Don’t update several critical plugins at once unless you’ve already tested them together. Updating them individually makes it easier to identify which change caused a problem.

How to Manually Update WordPress Plugins from the Dashboard

The WordPress dashboard is the simplest way to update an installed plugin manually. You can update plugins individually or select several available updates at once.
If your backup is ready and you’ve reviewed the updates, follow the appropriate method below.

Method 1: Update a Single WordPress Plugin

Use this method when you want to update one plugin and check the result before making other changes.

1. Open your WordPress dashboard. Go to Plugins → Installed Plugins.

2. Find the available update. Look for a notification beneath the plugin showing that a newer version is available.

3. Review the release details. Click the version details link, if available, and check the changelog and compatibility information.

4. Click Update Now. WordPress will download and install the update.

Manually Update WordPress Plugins: Update Now

5. Wait for confirmation. Don’t navigate away while the update is running.

6. Test the plugin. Open the website feature that depends on the plugin and confirm that it still works.

For example, after updating a contact form plugin, submit a test form and verify that the submission reaches its intended destination. Seeing an update success message does not confirm that every plugin feature is working.

If you don’t see an update notification: The plugin may already be current, or its developer may distribute updates outside the WordPress plugin directory. Premium plugins may require an active license or their own update mechanism.

Method 2: Update Multiple Plugins Using Bulk Actions

WordPress also lets you update several plugins from the same screen.

1. Go to Plugins → Installed Plugins.

2. Select Update Available to view plugins with pending updates, if that filter is displayed.

3. Check the boxes next to the plugins you want to update.

4. From the Bulk Actions dropdown, select Update.

5. Click Apply.

Manually Update WordPress Plugins: Bulk Action Update

6. Wait for the updates to complete and review any error messages.

Bulk updates save time, but they also make it harder to identify which change caused a problem if several plugins introduce issues simultaneously.

For business-critical plugins, update and test them individually when practical. This is especially important for checkout, payment gateways, booking systems, and other features that directly affect customers.

Check Your Website After Updating

Before considering the updates complete, verify the features affected by the changes:
  • Open the homepage and important pages.
  • Check contact forms and other interactive elements.
  • Test WooCommerce checkout-related functionality if an updated plugin affects your store.
  • Review the WordPress dashboard for update errors or new warnings.
If a feature stops working, record which plugin was updated and when the problem appeared. Avoid installing additional updates until you’ve identified the cause.

If an update fails or WordPress becomes inaccessible, you’ll need to investigate the error before proceeding. The next method explains how to replace plugin files using SFTP or your hosting File Manager when a dashboard update isn’t suitable.

How to Manually Update a WordPress Plugin via SFTP

Use SFTP when a plugin update fails through the WordPress dashboard, the automatic updater is unavailable, or you need to replace plugin files manually.

SFTP lets you access the files stored on your hosting server without relying on the WordPress administration interface.
Unlike regular FTP, SFTP encrypts the connection. If your hosting provider supports SFTP or FTPS, use one of those options instead of an unencrypted FTP connection.
For this example, we’ll use FileZilla. The same general process can also be completed through a hosting File Manager that supports uploading, extracting, and renaming folders.

Step 1: Download the Correct Plugin Version

Before connecting to your server, obtain the replacement plugin package.

1. Find the plugin in the official WordPress Plugin Directory or on its developer’s website.

2. Confirm that you’re downloading the correct plugin and intended version.

3. Review its WordPress and PHP compatibility requirements.

4. Download the installation ZIP file.

5. Extract the ZIP file on your computer.

For premium plugins, use the package provided through your licensed account or the plugin developer’s official distribution channel.

Don’t download plugin files from unverified third-party websites. Modified packages can contain malicious code or outdated dependencies.

Also, confirm that the extracted folder contains the actual plugin files, rather than another ZIP file or an additional packaging directory.

Step 2: Connect to Your Website Using SFTP

Open FileZilla or another SFTP client.
Update A WordPress Plugin or Theme Manually: FTP details
Enter the connection details supplied by your hosting provider, which may include:
  • SFTP hostname.
  • Username.
  • Authentication password or SSH key.
  • Port number.
Connect to the server and locate the correct WordPress installation.
Most WordPress installations contain these directories:
wp-admin/, wp-content/, and wp-includes/.
Next, open:
wp-content/plugins/
This directory contains the folders for your installed WordPress plugins.
Update A WordPress Plugin or Theme Manually

Before proceeding, confirm that you’re working on the correct website. Hosting accounts may contain several domains, staging installations, or development environments.

Step 3: Identify and Preserve the Existing Plugin

Find the folder belonging to the plugin you want to update.
For example:
wp-content/plugins/example-plugin/
Before replacing it:

1. Confirm that you’ve identified the correct plugin directory.

2. Record the currently installed version, if available.

3. Download a copy of the existing plugin folder.

4. Keep that copy outside the live website’s public directory.

5. Confirm that your website backup includes both files and database data.

Don’t delete the original plugin folder before you have a usable recovery copy.

Remember that some plugin updates change database structures or stored settings. Restoring old files alone may not completely reverse those changes.

Step 4: Upload the New Plugin Files

For a more controlled replacement, prepare the new plugin folder before switching away from the existing version.

1. On your computer, locate the extracted folder containing the updated plugin files.

2. In wp-content/plugins/, upload that folder using a temporary name, such as example-plugin-new.

3. Wait until all files have finished transferring.

4. Check that the transfer completed without failed files or interrupted uploads.

5. Prepare to make the final folder-name changes.

When you’re ready to switch versions:

1. Rename the original example-plugin folder to example-plugin-backup.

2. Rename example-plugin-new to example-plugin.

3. Confirm that the new plugin files are now in the original directory.

The final path should be:
wp-content/plugins/example-plugin/

Important: This is a controlled file-replacement technique, not an atomic update. There may still be a brief period when the original plugin directory is unavailable, and some plugins may be deactivated or fail to load during the change.

For a business-critical website, perform the operation on staging first and schedule the live replacement appropriately.
Don’t leave old plugin copies inside the active plugins directory after the update has been verified. Move backups outside the publicly accessible installation or remove temporary copies when they are no longer needed.

Step 5: Verify the Plugin Updates

After replacing the files:

1. Open your WordPress dashboard, if accessible.

2. Go to Plugins → Installed Plugins.

3. Confirm that WordPress recognizes the updated plugin and its expected version.

4. Check whether the plugin is still active. Reactivate it if necessary and safe.

5. Test the website feature that depends on the plugin.

6. Review PHP error logs if the website shows unexpected errors.

If the update affects WooCommerce, payment processing, bookings, or another business-critical feature, test that functionality using an appropriate staging or test environment.
A successful file transfer does not necessarily mean the plugin is working correctly.

Don’t change file or folder permissions automatically. Only adjust permissions if you’ve confirmed that they are incorrect for your hosting environment.

What If the Plugin Stops Working?

If the website develops an error after the replacement:
  • Record the error message and when it appeared.
  • Check the PHP logs for the affected plugin.
  • Avoid updating additional plugins while investigating.
  • Use your existing backup and recovery plan if restoring the previous version is necessary.
Be aware that a plugin update may introduce database changes that aren’t reversed by replacing files.
We’ll cover common update failures and rollback considerations later in this guide.

Should You Enable Automatic WordPress Plugin Updates?

Automatic plugin updates can help keep your WordPress website current without requiring you to install every new release manually. However, not every plugin needs the same update strategy.

The best approach depends on how much your website relies on each plugin, whether you can test updates beforehand, and how quickly you can recover if something breaks.

When Automatic Updates Make Sense

Automatic updates can be useful for plugins with a reliable maintenance history, straightforward functionality, and limited impact on critical website operations.

Before enabling them, make sure you have:
  • Reliable backups and a tested recovery process.
  • A way to monitor website errors or downtime.
  • Someone responsible for reviewing failed updates and compatibility issues.
Automatic updates reduce routine maintenance work, but they don’t replace monitoring or testing.

When Manual Updates Are a Better Choice

Consider a controlled manual update process for plugins that directly affect revenue, customer data, or essential business functionality.
Examples include payment gateways, WooCommerce extensions, booking systems, and plugins involved in custom integrations.
For these plugins, reviewing the release notes and testing changes on staging can help identify problems before they affect the live website.

Important: If a release fixes a serious security vulnerability, delaying the update indefinitely can create a greater risk than applying it. Evaluate the urgency of the security fix alongside the compatibility risk.

How to Enable or Disable Automatic Updates

You can manage the setting directly from WordPress:

1. Go to Plugins → Installed Plugins.

2. Find the plugin you want to configure.

3. Locate the Automatic Updates column.

4. Click Enable auto-updates or Disable auto-updates, depending on your preference.

Enable auto-updates

5. Review the setting periodically, especially after adding new plugins or changing critical website functionality.

Some managed hosting environments or custom update systems may control these settings differently.
For business websites, the goal isn’t to automate every update or manually install everything. It’s to maintain a reliable update process that balances security, compatibility, and recovery.

If you’d prefer ongoing monitoring, tested updates, and technical support, Kiwistic’s WordPress maintenance services can help you manage those responsibilities.

Troubleshooting Failed WordPress Plugin Updates

A failed plugin update doesn’t always mean the plugin itself is broken. The problem may come from file permissions, an interrupted download, a compatibility issue, or a server error.

Start with the exact error message and the time the update failed. Don’t repeatedly attempt the same update or change unrelated settings without identifying what went wrong.

1. WordPress Is Stuck in Maintenance Mode

During an update, WordPress may temporarily display:

“Briefly unavailable for scheduled maintenance. Check back in a minute.”

If this message remains after the update has stopped, WordPress may have left a .maintenance file behind.
To check:

1. Confirm that no update is still running.

2. Connect using SFTP or your hosting File Manager.

3. Open the WordPress installation directory containing wp-admin.

4. Enable hidden files if .maintenance isn’t visible.

5. If the update has definitely stopped, remove the leftover .maintenance file.

6. Reload the website and check the plugin’s version and status.

Removing this file only exits maintenance mode. It doesn’t complete an interrupted update or repair damaged plugin files. Verify the installation before trying again.

2. The Update Fails With a File Permission Error

Messages such as “Could not create directory” or “Could not copy file” can indicate a filesystem access problem.

Before changing permissions:

1. Check the exact directory or file named in the error.

2. Confirm that your hosting account has sufficient disk space and hasn’t reached its storage quota.

3. Check file ownership and write access using your hosting panel or ask your hosting provider.

4. Review whether WordPress requires filesystem credentials to perform updates.

Don’t apply 777 permissions or change every directory to 755 and every file to 644 blindly. Correct permissions and ownership depend on the server configuration.

Once the hosting issue is resolved, retry the update and verify the affected plugin.

3. A Plugin Update Causes a Critical Error

If your site displays “There has been a critical error on this website” after updating a plugin, first identify which component is failing.

1. Check the administrator email for a WordPress Recovery Mode link.

2. Review PHP error logs for messages recorded immediately after the update.

3. Check whether the error references the updated plugin.

4. Verify the plugin’s PHP, WordPress, and dependency requirements.

5. If the updated plugin is responsible, disable it or restore a compatible version using your recovery plan.

If dashboard access is unavailable, an authorized administrator may need to use SFTP to temporarily rename the affected plugin directory.

Be careful: disabling payment, security, membership, or other business-critical plugins can interrupt essential functionality.

A fatal error appearing after an update is a useful clue, not proof that the updated plugin alone is responsible. The failure may involve an interaction with another plugin, the active theme, or the PHP environment.

4. The Update Completes, but a Website Feature Stops Working

WordPress may report a successful update even when a plugin’s functionality has changed or a compatibility problem appears afterward.
For example, a contact form may stop sending notifications, a search filter may no longer return the expected results, or a WooCommerce extension may behave differently.
To investigate:

1. Reproduce the problem and record the affected page or feature.

2. Check the plugin’s changelog for changed settings, requirements, or deprecated functionality.

3. Review relevant PHP logs and browser console errors.

4. Compare the behavior with a staging environment or the previous working version, if available.

5. Check the plugin developer’s documentation for known compatibility issues.

Avoid installing additional updates while investigating. Changing several components at once makes it harder to isolate the cause.

If the issue cannot be resolved through configuration or a compatible update, restoring the previous plugin version may be appropriate.

How to Roll Back a WordPress Plugin Update

If a plugin update breaks your website, reverting to the previous working version may help restore functionality. However, a rollback should be a temporary recovery measure, not a substitute for investigating the problem.

Steps to Restore a Previous Plugin Version

1. Identify the problematic update. Check the plugin version, error logs, and when the issue started.

2. Find a trusted previous version. Use your existing backup or an older release from the official plugin developer. Confirm its compatibility before proceeding.

3. Restore the plugin files. Replace the affected plugin using your backup or the SFTP procedure explained earlier.

4. Check for database changes. Some updates modify stored data or database structures. Restoring old files alone may not reverse these changes.

5. Test the website. Verify that the plugin and its dependent features work correctly.

Important: Older plugin versions may contain known security vulnerabilities. If the update included a security fix, investigate a compatible solution promptly rather than leaving the website on an outdated release.

For WooCommerce stores or websites collecting live submissions, restoring an entire database backup may overwrite newer orders or customer data. Verify the impact before restoring it.

Conclusion

Manually updating WordPress plugins gives you control over when updates happen and how you verify the results. Whether you use the WordPress dashboard or SFTP, the essentials remain the same: review the update, keep a reliable backup, and test affected functionality afterward.
If an update causes problems, investigate the error before making further changes. A consistent update and recovery process is more valuable than simply keeping every plugin on its latest version.

FAQ

Can I update a WordPress plugin without updating WordPress itself?

Yes. WordPress core and plugins can generally be updated independently, provided the plugin is compatible with your installed WordPress and PHP versions. Check the plugin’s requirements and release notes before updating.

Will manually updating a WordPress plugin delete its settings?

Usually not. Most plugins store their settings in the WordPress database, separately from their installation files. However, updates may change database structures or stored settings, so a verified backup remains important.

How often should I check for WordPress plugin updates?

Check for available updates regularly, with a schedule appropriate to your website’s risk and maintenance needs. Review security fixes promptly rather than waiting for a fixed monthly update date. For major updates or business-critical plugins, test compatibility before applying changes to the live website.

Ognjen Velickovic

WordPress Developer & Product Manager at Kiwistic. I build and maintain WordPress sites for small businesses and troubleshoot everything from login lockouts to security issues. These guides come from real experience, so you don't have to figure it out alone.

You May Also Like…