How to update WordPress plugins manually without losing your setup

Before you start: confirm the package and requirements

Record the installed plugin name and version, then check the new release’s requirements and change notes. Pay attention to WordPress and PHP compatibility, dependencies, and any migration steps. For an add-on such as Astra Pro, check the base theme as well as the add-on. A plugin ZIP belongs under Plugins; a theme ZIP belongs under Appearance.

Obtain the update from the plugin developer or the authorized source covered by your purchase. Do not replace it with a similarly named archive from an unknown download site. If you cannot confirm the package, stop and ask your supplier. The ability to upload a file is not evidence that it is the correct update.

Schedule a quiet period and keep a way to contact your host. On a shop, account for new orders and customer changes while maintenance is underway. A full database restore after an update can erase transactions created since the backup.

Back up both your files and database

WordPress stores site data in a database and software, media, and configuration in files. Downloading the plugin folder alone is not a complete site backup. Create a recent backup set containing both parts, and store a copy somewhere other than the same hosting account.

Confirm how restoration works before you update. Ask your host where the restore control is, what it replaces, and whether you can restore to a staging site. A successful backup notification is useful, but a tested restore is stronger evidence that you can recover. Keep the previous authorized plugin package if your supplier provides it.

• Capture the database and WordPress files as one recent backup set.
• Check that the backup completed and is accessible.
• Know whether recovery will overwrite new orders, form submissions, or edits.

Try the update on staging first

Use a staging copy that reflects the live site’s theme, plugins, and server configuration. Protect it from public indexing. Disable real payment processing, customer emails, and other live integrations so your checks do not affect visitors.

Update one relevant component at a time unless the developer explicitly requires a coordinated sequence. Check the pages and actions that depend on the plugin, not only the homepage. A page-builder add-on may affect templates; a commerce extension may affect cart totals or checkout. Take notes on what you exercised so the live check is repeatable.

Install the update through the appropriate route

If WordPress offers an authorized update under Dashboard → Updates or Plugins → Installed Plugins, use that route after your checks. It is still a manual update when you choose when to click Update. You do not need to upload a ZIP simply because automatic updates are disabled.

When your update is supplied as a ZIP, go to Plugins → Add New Plugin → Upload Plugin, select the correct plugin archive, and choose Install Now. On WordPress installations that support replacing an installed plugin, compare the displayed existing and uploaded plugin details before choosing the replacement action. Stop if the names or versions do not match your plan.

Do not uninstall or delete the plugin as a routine update step: some plugins remove stored settings or data during uninstallation. If the upload is blocked by hosting limits or the replacement option is unavailable, use the developer’s documented procedure or ask your host rather than improvising a file transfer on the live site.

Verify the result and keep a recovery plan

Confirm the expected version appears in Installed Plugins and that the plugin is active. Clear relevant caches, then check the site in a logged-out browser and on a phone-sized screen. Exercise forms, navigation, key templates, and any purchase flow affected by the update. Check errors and scheduled tasks when those are part of the plugin’s job.

If you find a fault, capture the error and affected URL before making further changes. Use your tested recovery procedure. Replacing only the plugin code may not undo a database migration; restoring the whole site may lose newer data. Ask the developer or host which recovery path fits the failure.

Finally, record the installed version and date. WPPlugin’s Astra Pro lifetime-access offer uses manual updates, so someone must own this process for every covered site. An offer with automatic updates changes how versions arrive; it does not replace backups, compatibility checks, or verification.