Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

If a WordPress plugin will not update from the dashboard, replace its folder through SFTP, FTPS, or FTP: back up the site’s files and database, preserve the existing plugin folder, upload the extracted replacement to wp-content/plugins, then activate and test it. Prefer SFTP or FTPS; ordinary FTP sends data in clear text.

Before you replace a plugin

Make a current backup of both the site files and database before uploading, replacing, or deleting WordPress files. Confirm you are working in the correct site directory, particularly if the hosting account contains multiple sites or staging environments. WordPress’s developer handbook gives this backup guidance at WordPress backups.

  • Download the plugin package from its author or the WordPress Plugin Directory.
  • Check the plugin vendor’s release notes for required migration steps, compatibility notes, or license activation requirements.
  • Arrange a rollback copy of the current plugin folder before changing it.

Choose a file-transfer method

Use your host’s connection details and credentials to connect to the site. FTP, FTPS, and SFTP clients can transfer folders; a hosting control-panel file manager can also work for a small, one-off replacement. FTP is not encrypted, so use SFTP or FTPS when your host offers it. The WordPress handbook explains the security distinction and cautions against changing permissions without knowing they are incorrect: WordPress file permissions.

Method Access path Transport security Typical scope
WordPress dashboard Plugins screen Not a file-transfer protocol; uses your site connection One plugin’s normal update
SFTP or FTPS client Connect with the host’s supplied credentials, then browse site files Encrypted transfer One plugin folder or other files you deliberately transfer
FTP client Connect with the host’s supplied credentials, then browse site files Clear-text transfer; avoid when a secure option is available One plugin folder or other files you deliberately transfer
Host file manager Hosting control panel Depends on the host’s control-panel connection Convenient for a small, one-off change

For ordinary updates, the dashboard is simpler when it works. A manual file replacement gives you direct control over the plugin directory, but it requires careful folder selection and a recoverable backup. WordPress introduced automatic plugin updates in version 5.5; manual replacement remains an option when dashboard updates are unavailable. See Manage Plugins.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Update one plugin through FTP or SFTP

  1. Deactivate the plugin if you can. In WordPress, open Plugins and deactivate the plugin you are replacing. If wp-admin is unavailable, skip this step and use the recovery section below if necessary.
  2. Unzip the downloaded package on your computer. The extracted folder should contain the plugin files. Do not upload just the ZIP unless your host’s file manager can extract it into the correct location.
  3. Connect to the correct site directory. In the remote file list, locate the WordPress installation’s wp-content/plugins directory. Check the site path before making changes.
  4. Preserve the existing plugin folder. Rename it to something such as plugin-name-old, or move it to a safe location off the server. Keep the expected original folder name available for the replacement. If the plugin is customized or its author specifies a migration procedure, follow those instructions rather than replacing it blindly.
  5. Upload the extracted replacement folder. Place it in wp-content/plugins and retain the directory name expected by the plugin. Confirm that the plugin’s main PHP file is inside that folder, not buried in an extra nested directory.
  6. Activate and check the site. In WordPress, open Plugins and activate the replacement. Check the front end, login, administration screens, forms, and features that depend on the plugin. Complete any required migration or license steps from the vendor’s release notes.
  7. Keep the old copy until checks pass. Once the replacement is confirmed to work, remove the old copy only when you no longer need it for rollback.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

If the replacement breaks the site

If you can still reach wp-admin, deactivate the replacement and use your preserved old folder to restore the prior version. If the dashboard is inaccessible, connect to the site’s files and restore the original plugin directory name, replacing or moving aside the new folder as needed. A WordPress.org troubleshooting guide describes renaming the old plugin folder, uploading the new version, and renaming the old folder back to back out: WordPress troubleshooting.

When wp-admin will not load

If you cannot identify the plugin causing the problem, rename wp-content/plugins to a temporary name such as plugins.hold using FTP, SFTP, or the host’s file manager. This disables all plugins while preserving their settings. Log in to WordPress, rename the directory back to plugins, then activate plugins one at a time to identify the failure. This affects every plugin, not just the one you updated. Follow the WordPress.org troubleshooting steps.

Rank #4

Avoid common recovery problems

  • Wrong destination: Uploading into the wrong WordPress installation or into a nested plugin directory leaves the site using the old files or unable to find the plugin. Verify the site path and folder structure.
  • No working rollback: Replacing the old folder without a backup removes the easiest route back. Keep the old folder or a complete file-and-database backup until verification is finished.
  • Permissions changed unnecessarily: Do not apply broad permission changes as a guess. WordPress warns that incorrect permissions can prevent WordPress, plugins, themes, or the web server from reading or writing files.
  • Persistent error after rollback: Restore the matching old plugin folder and, if needed, the site backup. If the plugin performs a database migration, replacing files alone may not reverse it; follow the vendor’s recovery guidance.

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.