A yellow notice has appeared at the top of the dashboard: your licence for a premium plugin has expired, please renew. Or perhaps there is no notice at all, and you only find out when a developer mentions that one of your plugins has not been updated in well over a year. The site still looks fine. So does it matter?
It does, though usually not in the way people fear. An expired WordPress plugin licence rarely switches anything off overnight. The real cost is quieter, and it builds up over time. The sections below cover what normally stops, how to find out who holds the licence, and the honest options for dealing with it, including a premium plugin renewal that does not catch you out next year. Like the rest of this section, it is part of our guide to managing your WordPress site.
What stops with an expired WordPress plugin licence
Each vendor sets its own terms, so read the ones for your plugin. In most cases, though, an expired licence affects four things:
- Updates in the dashboard. The plugin stops receiving new versions through WordPress’s normal update screen. This is the important one.
- Downloads. Your account on the vendor’s site may no longer let you download the latest zip file.
- Support. Ticket or email help from the vendor typically ends with the licence.
- Connected services, for some plugins. Features that depend on the vendor’s own servers, such as a template library, an online API or a cloud feature, may stop working.
For most premium plugins, the code already on your site keeps running. Your forms keep sending, your layouts still display, your shop keeps taking orders. A few products do disable some features without an active licence, which is why checking that plugin’s own terms matters.
Why an expired licence is a security issue
Plugins receive security fixes through updates. When updates stop, the version on your site stays frozen. If a flaw is later found in that version, the fix goes out to licensed sites and yours stays exposed. Once a flaw becomes public, automated scanners start looking for sites that still run the old version. Our explainer on plugin vulnerabilities walks through how that happens.
Often nothing on screen warns you, either. The plugin keeps working, and the update count in your dashboard may stay at zero, because many premium plugins only report new versions to sites with an active licence. That silence is what makes a lapsed licence easy to overlook for years.
A frozen plugin also falls behind WordPress and PHP. Sooner or later a WordPress release or a server upgrade by your host brings a change that an un-updated plugin cannot handle, and something breaks at a moment you did not choose.
Who holds the licence?
This is often the real problem, especially on a site built by an outside developer. Licences are attached to whoever bought them, and that may not be you. Work through these steps:
- Look in the plugin’s settings. Most premium plugins have a Licence or Account tab. It may show the key (often partly hidden), its status and sometimes the email address it belongs to.
- Search your business email and accounts for receipts from the vendor. If you find one, you own the licence and can log in to renew.
- Ask whoever built or maintains the site. They may have bought it on their own account, or used a multi-site licence that covers many of their clients.
- Contact the vendor if you are still unsure. Many can tell you which account a licence key belongs to, or at least advise on transferring it.
If your developer holds the licence, ask whether they will keep renewing it, transfer it to you, or help you buy your own. A licence covering many client sites usually cannot be split off, so buying your own is often the clean answer. Taking over a site from a previous developer brings up this question along with others, which our post on taking over a website from another developer covers.
Your options when the licence has expired
| Option | When it fits | Watch out for |
|---|---|---|
| Renew it | The plugin still does an important job well | Update straight after renewing; you may be several versions behind |
| Move to the free edition | A free version exists and covers what you actually use | Paid-only features stop; check pages that relied on them |
| Replace the plugin | You rarely used the paid features, or a better option exists | Content and settings may need moving by hand |
| Remove it altogether | The site no longer needs that job done | Shortcodes or layouts left behind in your pages |
| Leave it as it is | Only as a short pause while you decide | No security fixes; risk grows with every month |
If you go the replacement route, plan it the way you would any plugin swap: our guide to replacing a WordPress plugin safely covers exporting settings, updating pages and testing. Whether to pay for the plugin again at all is a judgement about value, and free and paid plugins compared may help you decide.
Updating after a renewal
Renewing does not automatically bring the plugin up to date. Once the licence is active again:
- Check the plugin’s licence tab shows the key as active for this site’s address. If not, enter or re-activate the key.
- Look at Dashboard → Updates, or the Plugins screen, for the new version. It can take a little while to appear; the Check again link on the Updates screen asks WordPress to look straight away.
- Read the changelog for every version you missed. After a long gap there may be a major release or a database change in there.
- Back up the site, update, and check the pages that use the plugin.
If you are many versions behind on something important, such as a page builder or a shop extension, test the update on a staging copy first.
The option to avoid
When renewal feels expensive, sites offering the same premium plugin “free” or at a steep discount can look tempting. They are not the vendor, the files may have been altered, and they are a common way malware gets onto business sites. Our post on why nulled plugins and themes carry malware explains the risk in full. A plugin that cannot be updated legitimately is better replaced than patched with a copy of unknown origin.
Making the next premium plugin renewal painless
Most licence trouble comes from nobody knowing a renewal was due. A little setup now saves the scramble later:
- Use a business account. Register the purchase to a shared company mailbox, so renewal reminders reach someone who is still around.
- Decide on auto-renewal deliberately. Most vendors let you switch it on or off in your account. On is safer for plugins you rely on; off suits ones you are reconsidering.
- Keep the card current. A renewal can fail for no better reason than an expired card on file.
- Put the date in a calendar a few weeks before renewal, with a note of who decides whether to renew.
- Review each renewal. It is a natural moment to ask whether the plugin is still needed.
Licences are one of the slower-moving parts of plugin care. For how they fit with choosing, updating and removing plugins, see our WordPress plugins guide.
Frequently asked questions
Will my website stop working the day the licence expires?
For most premium plugins, no. The installed version keeps running and your pages look the same. What stops is new versions and vendor support, plus any feature that depends on the vendor’s servers. A small number of products do switch features off without a licence, so check the vendor’s terms for the plugin in question.
I renewed, but the plugin still says the licence has expired. What now?
Open the plugin’s licence settings and check the key is entered and activated for this site. Some plugins need you to deactivate and re-activate the key, or to click a button that re-checks the licence. Also confirm the site’s address matches the one registered with the vendor. If it still shows as expired, contact the vendor’s support with your order details.
Can a licence bought by my old developer be moved to my own account?
Sometimes. Some vendors will transfer a single-site licence on request when both parties agree. Licences that cover many sites, such as agency or developer plans, usually cannot be split, so buying your own licence for your site is often simpler. Either way, ask the developer to deactivate their key on your site once yours is in place.
Is it fine to let a licence lapse on a plugin I barely use?
Only if you also deal with the plugin. A barely used plugin still runs code on your site and still needs security fixes. If you do not need it, export anything it stores, remove it properly and let the licence go. If you might need it later, the free edition or a replacement is safer than an un-updated copy.
A plugin that has quietly stopped updating is easy to miss when nobody is watching the whole list. Keeping an eye on updates is part of our WordPress maintenance plan, together with backups and security monitoring.
Next in this series: Remove Leftover Plugin Data From WordPress Safely
