Backups & maintenance · Guide
How to Update Polylang Pro (Step by Step)

Short answer
Activate your license key under Languages, Settings, then update Polylang Pro from Dashboard, Updates like any plugin. If the key will not activate, download the latest ZIP from your Polylang account and upload it with the Replace current with uploaded option.
Key takeaways
- Polylang Pro updates come from Polylang's servers and need an active license key.
- Activate the key under Languages > Settings in the License keys module.
- Manual updates use the Upload Plugin screen and Replace current with uploaded.
- Deactivate the free Polylang plugin when Pro is active.
- Back up first and test the language switcher after updating.
How do you update Polylang Pro?
Activate your license key under Languages > Settings, then update Polylang Pro from Dashboard > Updates like any plugin; without an active key, download the new ZIP from your Polylang account and replace the plugin manually.
Polylang Pro is a commercial plugin, so it does not get updates from WordPress.org. Updates come from the Polylang servers, and your license key is what lets your site fetch them.
Once the key is active, updating is a one-click job. The manual route takes a few minutes longer but works on any site.
Either way, take a backup and check the changelog before you start. A multilingual plugin touches every page, so a bad update is very visible.
The changelog lists bug fixes, new features and any minimum version changes. Read it for words like requires or breaking, which tell you to test on staging first.
What do you need before updating Polylang Pro?
You need an active Polylang Pro license, administrator access, a recent backup, and ideally a staging copy to test on first.
Checklist:
- A valid license. Updates only work while the license is active. Check its status in your account on the Polylang website.
- A backup. Back up files and the database. Our guide on using UpdraftPlus is one simple way.
- Compatible versions. Check that your WordPress and PHP versions meet the new release's requirements.
- Add-on versions. Polylang for WooCommerce and other add-ons should be updated in the same session.
- A quiet time. Update when traffic is low, in case you need to roll back.
If you are not sure whether you even run the Pro version, look at Plugins > Installed Plugins. The free plugin is named Polylang, while the paid one is Polylang Pro.
How do you activate your Polylang Pro license key?
Go to Languages > Settings, open the license keys section, paste your key into the Polylang Pro field, and click Activate.
Steps:
- Log in to your Polylang account and copy your license key.
- In WordPress, go to Languages > Settings.
- Find the License keys module and open its settings.
- Paste the key into the Polylang Pro field.
- Click Activate.
- Confirm that the status shows the license as valid.
If you also run Polylang for WooCommerce, it has its own key in the same section.
Polylang's guide to managing license keys explains activation, deactivation and moving a key between sites.
A key only works on the number of sites your plan allows. If activation says the limit is reached, open your Polylang account, find the old site in the list of activations, and remove it before trying again.
How do you update Polylang Pro automatically?
With the license active, go to Dashboard > Updates, click Check again, tick Polylang Pro, and click Update Plugins.
Steps:
- Go to Dashboard > Updates.
- Click Check again to refresh the update list.
- Tick Polylang Pro in the plugins section.
- Click Update Plugins.
- Wait for the success message.
You can also click update now under Polylang Pro on the Plugins screen. Both routes do the same thing.
If the update stalls, do not reload the page right away. WordPress puts the site into maintenance mode while it swaps files, and a reload mid-update can leave the plugin half installed.
If the site gets stuck showing a maintenance message, delete the .maintenance file in the site root with FTP or your host's file manager, then run the update again.
WordPress also lets you turn on automatic updates per plugin. Use the Enable auto-updates link on the Plugins screen if you want Polylang Pro to update itself.
Auto-updates are convenient but risky on large multilingual sites. Many site owners prefer to update by hand after reading the changelog. WordPress explains both options in its plugin and theme auto-updates guide.
How do you update Polylang Pro manually?
Download the latest ZIP from your Polylang account, go to Plugins > Add New Plugin > Upload Plugin, upload it, and choose Replace current with uploaded when WordPress asks.
Manual updates are useful when the license key will not activate, the update check is blocked by your host, or you manage many sites.
Steps:
- Log in to your account on the Polylang website.
- Download the latest Polylang Pro ZIP.
- In WordPress, go to Plugins > Add New Plugin > Upload Plugin.
- Choose the ZIP and click Install Now.
- WordPress detects the existing plugin and shows a comparison.
- Click Replace current with uploaded.
Your languages, translations and settings are stored in the database, so replacing the plugin files does not remove them.
Keep the old ZIP somewhere safe for a week or two. If the new version causes trouble, you can upload the old one the same way to roll back quickly.
The Manage Plugins documentation covers uploads and replacements in general.
Can you update Polylang Pro over FTP?
Yes. Unzip the new version, upload the polylang-pro folder to wp-content/plugins, and overwrite the old files.
Our guide on getting FTP access to WordPress explains how to connect. Rename the old folder first, such as polylang-pro-old, so you can switch back fast.
Should the free Polylang plugin stay installed?
No; Polylang Pro includes all the free plugin's features, so the free Polylang should be deactivated and can be deleted once Pro is running.
Running both at once can cause conflicts. Polylang Pro normally deactivates the free version when you activate it, but check the Plugins screen to be sure.
| Plugin | Needed with Pro? | Update source |
|---|---|---|
| Polylang (free) | No, deactivate it | WordPress.org |
| Polylang Pro | Yes | Polylang servers with license key |
| Polylang for WooCommerce | Only for WooCommerce stores | Polylang servers with its own key |
| Third-party Polylang add-ons | Only if you use them | Their own vendors |
If you are still on the free version and only need it updated, the normal route in our guide on updating plugins in WordPress applies.
What should you check after updating?
Visit each language's homepage, test the language switcher, open the translation screens, and clear every cache.
A post-update checklist:
- Language switcher. Click every language and confirm the links work.
- URLs. Check that language prefixes or subdomains still resolve.
- Translated content. Open a few posts in each language.
- Strings. Check Languages > Translations for menus and widget text.
- WooCommerce. Test a product page and the cart in each language if you sell online.
- Caches. Purge your cache plugin, server cache and CDN.
If the switcher misbehaves, our guide on Polylang language switcher not working lists the common fixes.
Why is the Polylang Pro update not showing?
The update usually doesn't show because the license key is inactive or expired, the site URL changed after activation, the update cache is stale, or your server can't reach the Polylang servers.
Work through these causes:
- Expired license. Renew it in your Polylang account, then click Check again.
- Key not active on this domain. After a migration, deactivate and reactivate the key on the new URL.
- Stale update data. Click Check again on Dashboard > Updates.
- Blocked outgoing requests. Ask your host whether PHP can make outgoing HTTPS requests. PHP's cURL extension handles most of these calls.
- Staging limits. Some licenses count staging sites. Check your account for active sites.
If none of these work, use the manual ZIP method above. It does not depend on the update check.
What if the update breaks the site?
Restore your backup or roll back to the previous Polylang Pro version, then report the problem to Polylang support with your error log.
Rollback options:
- Restore the backup you took before updating. Our guide on restoring a WordPress site from backup explains the steps.
- Upload the older ZIP with the Replace current with uploaded option, if you kept a copy.
- Rename the plugin folder over FTP to disable it if the dashboard will not load.
Turn on logging first so you have details for support. The WordPress debugging handbook explains the WP_DEBUG_LOG setting.
Test updates on a staging copy next time. Our guide on setting up a staging site shows how.
Frequently asked questions
Will updating Polylang Pro delete my translations?
No. Languages, translations and settings are stored in the database, not in the plugin files. Updating or replacing the plugin keeps them. A backup is still wise in case an update conflicts with another plugin.
Can I update Polylang Pro with an expired license?
Automatic updates stop when the license expires. You need to renew to get new versions from your account. The plugin keeps working on your site, but you will miss security and compatibility fixes.
Do I need to keep the free Polylang plugin?
No. Polylang Pro includes the free plugin's features. Keep the free version deactivated or delete it, because running both can cause conflicts.
Why does Polylang Pro not show in the update list?
The license key is probably inactive on this domain, or WordPress has not checked for updates recently. Reactivate the key under Languages > Settings and click Check again on the Updates screen.
Should I turn on auto-updates for Polylang Pro?
It depends on the site. Auto-updates keep you current with less effort, but on large multilingual or WooCommerce sites, many owners prefer to update by hand after a backup and a quick read of the changelog.
Sources
- Managing the license keys Polylang
- Manage Plugins WordPress.org
- Plugins and themes auto-updates WordPress.org
- Debugging in WordPress WordPress Developer Resources
- cURL PHP Manual
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


