Table of contents10
The first time I bought a premium WordPress plugin, I clicked “Single Site” without a second thought. It cost $49, I had one website, and the maths looked simple. Two weeks later a friend asked me to build a small site for her bakery, and I reached for the same plugin out of habit. That is when the red banner appeared: “License limit reached.” I sat there feeling like I had been caught stealing something — even though I had paid for it. By the end of that month I had bought the same plugin twice, and the sting stayed with me far longer than the plugin did.
I am Amélie Dubois, and over the past eight years I have managed license keys across more than sixty WordPress sites — my own, my clients’, and a few I inherited from developers who vanished. If you are staring at a pricing page right now wondering whether the single-site license is enough or the unlimited one is overkill, I know exactly what that feels like. The fear is real: pick too small and you pay twice, pick too big and you have thrown money at sites you will never build.
In this guide I will walk you through the exact four-step method I use before every purchase — count your real sites, map the coverage, do the three-year maths, and lock down ownership — so you buy once, buy right, and never think about it again. Whether you run one blog or twenty client sites, this is the decision process I wish someone had handed me in 2018.

Here is what this guide covers:
- The question you are actually asking (it is not what you think)
- Step 1: Count your production sites — properly
- Step 2: Put every site on a coverage map
- Step 3: Do the three-year maths before you click buy
- When an unlimited license is genuinely worth it
- When a single-site license is the smart buy
- Who should own the license (the rule that saves businesses)
- Renewal traps that cost real money
- Frequently Asked Questions
- Final Thoughts
Ready? Let us make this the last time you ever agonise over a license tier.
The Question You Are Actually Asking
Here is the thing nobody tells you on those pricing pages: a WordPress license key does not control whether the plugin runs. It controls two things — the update feed and the support desk. That is the whole business model, and understanding it changes the entire question.
WordPress itself is released under the GPL, and every plugin or theme that extends it inherits those freedoms: the freedom to run the software for any purpose, on as many sites as you like. The license key cannot take that away. What the key buys you is a year of one-click updates from the developer’s server and someone to email when things break. As one developer who sells licenses for a living puts it, the site limit is a *service limit* — the sixth site on a five-site key cannot activate or download updates, but the code already installed keeps running.
Why does this matter for your decision? Because you are not buying permission. You are buying a year of safe, supported updates, multiplied by the number of live sites you actually run. Once you see it that way, “single vs unlimited” stops being a guess about the future and becomes a simple counting exercise — which is exactly what Step 1 is.
Note: an unlicensed copy that never updates stops being worth running within a year. WordPress core ships multiple major releases annually, and a plugin frozen in time will eventually conflict, break, or open a security hole. You are not paying to be allowed — you are paying to stay current. The GPL license that WordPress uses guarantees your freedoms; the commercial license guarantees your updates.
Step 1: Count Your Production Sites — Properly
The biggest mistake I see is people counting wrong. They count their main site, forget the client’s brochure site they maintain, forget the membership site they launched last spring, and then act surprised when the license runs out. I keep a simple list — a spreadsheet, nothing fancy — and I update it every time a site goes live or gets retired. Here is how to count.
Count every live, public-facing WordPress install as one. Your blog, your shop, each client site you maintain — each one is a production site. If a plugin is active on it and you want updates and support for it, it needs a license slot.
Do not count staging, development, or local copies. Almost every reputable vendor excludes clearly-marked dev environments from the site count — localhost, staging subdomains like `staging.yoursite.com`, `.test` or `.local` domains. One vendor’s policy spells it out plainly: localhost, staging and development environments do not count toward the maximum as long as the domain clearly looks like a dev or staging site. So your live site plus its staging copy is one slot, not two.
Multisite networks are usually one slot. A WordPress multisite network shares a single plugins folder, so one license key normally covers the whole network — you add it on the main site. But separate WordPress installs on subdomains or subfolders of the same domain are *not* one network; each install is its own site. When in doubt, the rule of thumb from one well-known plugin maker is worth memorising: you need a license for each `/wp-content/plugins/` folder.
Be honest with yourself here. Write the list. I once discovered I was running eleven production sites when I would have sworn I had “about six.” That single piece of paper changed every license decision I made that year.

Step 2: Put Every Site on a Coverage Map
Now take your site list and turn it into a coverage map. It takes ten minutes and it is the most valuable part of this whole process. For each site, note three things: which premium plugins are active on it, whose license key is entered, and when that license renews.
What you are looking for is overlap. Very often you will find the same plugin running on four or five sites under four or five separate single-site licenses — bought at different times, renewing at different times, some of them expired without anyone noticing. That is money leaking out of a dozen small holes. One unlimited or multi-site license frequently costs less than the pile of singles it replaces, and it gives you a single renewal date to watch instead of five.
The coverage map also exposes the dangerous pattern: licenses you do not own. If your developer bought the key under their email and entered it on your site, you have a problem waiting to happen. We will deal with that properly in the ownership section below, but flag every such case on your map now. Here is the deal: a license key tied to someone else’s account is a support ticket you cannot file and an update you cannot control.
Step 3: Do the Three-Year Maths Before You Click Buy
Pricing pages are designed to make the middle tier look sensible and the top tier look luxurious. Ignore the design. Do the maths over three years, because licenses renew annually and the first-year discount is where the traps hide.
Write down three numbers for each tier you are considering: the year-one price, the renewal price (check the fine print — renewal is often higher than the intro price), and the number of site slots. Then multiply by three. A $49 single-site license that renews at $49 costs $147 over three years for one site. A $199 unlimited license costs $597 over three years — but if it covers six sites, that is under $100 per site over three years, or about $33 per site per year.
The break-even question is simple: how many production sites will run this plugin within the next twelve months? If the answer is one and will stay one, the single-site license wins and it is not close. If the answer is three or more, the unlimited tier usually wins on price alone — before you count the convenience of one key and one renewal date.
Remember the upgrade path. Most serious vendors let you upgrade tiers later and only pay the difference — one license guide states it explicitly: you can always upgrade to a bigger package later and only pay the price difference. This kills the biggest fear in this whole decision. You do not need to predict your next three years perfectly. Start with the tier that fits today, and upgrade when your site count actually grows. The only real mistake is buying unlimited “just in case” for sites that never materialise.
Watch for the lifetime trap. Some vendors sell a “lifetime” tier at a high one-time price. Read what lifetime means: lifetime of the product, not your lifetime, and sometimes not even that — check whether major version upgrades are included. I have seen “lifetime” licenses that quietly required a new purchase at version 3.0. If the terms are vague, treat lifetime as a three-to-five-year bet and do the maths accordingly.
Bonus Tip: put renewal dates in your calendar with a reminder two weeks before, not on the day. Vendors love auto-renewal at the higher renewal price, and a two-week heads-up gives you time to downgrade, upgrade, or cancel with a clear head.
When an Unlimited License Is Genuinely Worth It
Unlimited licenses have a reputation as the “agency tax” — the expensive option for people with more money than sense. Sometimes that is true. But there are four situations where unlimited is the rational, money-saving choice, and I have lived through all of them.
You run an agency or freelance with client sites. If the same workhorse plugins go on every client build, one unlimited key beats a drawer full of singles. One renewal date, one invoice, no per-client key juggling. This is the classic case, and it is classic because the maths works.
You are a serial site-builder. Some of us just build a lot of sites — experiments, side projects, a new idea every quarter. If you know you will spin up four or five sites a year, stop buying singles. You will outgrow the tier by March.
The plugin is infrastructure. Some plugins are not a nice-to-have; they are load-bearing — your forms plugin, your SEO plugin, your security plugin. Infrastructure deserves the tier that can never run out of slots at 11pm before a launch. The cost of discovering you are one slot short during a client launch dwarfs the price difference.
You value simplicity over squeezing every dollar. This one is underrated. One key, one renewal, one support account. For some people that administrative calm is worth the premium even at three sites. There is no shame in paying for simplicity — just make sure it is a conscious choice, not a panicked one.
When a Single-Site License Is the Smart Buy
And now the other side, because the unlimited tier is oversold and I want to be honest about it. A single-site license is the right answer more often than pricing pages want you to believe.
You have one site and no plans for a second. Bloggers, small business owners, portfolio sites — if your site count is one and your roadmap says one, buy the single. The money you save is real, and the upgrade path exists if life changes.
You are testing a plugin. Never buy unlimited for a plugin you have not lived with yet. Buy the single, run it for two or three months, and see if it earns its place. I have a graveyard of unlimited licenses for plugins I stopped using by February. The single-site license is a cheap experiment; the unlimited tier is a commitment.
The plugin is niche. A plugin you will use on exactly one specialised site — a booking system for one client, a membership tool for one community — does not need unlimited coverage. Match the tier to the reality, not the fantasy.
Your budget is real. This matters and nobody says it: if the unlimited tier is 4x the price and you have one site, that extra money is not “investing in growth.” It is a donation to the vendor’s revenue line. Buy what you need today.

Who Should Own the License (The Rule That Saves Businesses)
This is the section I wish someone had written for me years ago, because it is where the real damage happens — not in overpaying, but in losing control.
The rule is simple: the business that depends on the site should own the license. Not the freelancer. Not the agency. The business. I learned this watching a client lose access to every premium plugin on their site the week their developer stopped answering emails. The keys were bought under the developer’s account, the renewals were on the developer’s card, and when the relationship ended, the updates ended with it. The site did not break that week. It broke slowly, over the next year, as WordPress moved on and the frozen plugins did not.
As one security consultant puts it bluntly: you should not rely on your web company to renew a developer license each year, and in case your developer gets hit by a bus tomorrow, it is a reduction in risk if your company takes responsibility for paying for annual plugin licenses. That “hit by a bus” line sounds dramatic until it happens to you — or rather, to your client.
Here is the ownership routine I now run on every project:
1. Before launch, list every premium plugin and theme on the site. 2. For each one, confirm the license is purchased under the *client’s* email and payment method — or transferred to it. 3. Enter the client’s key on the client’s site. Test that updates actually flow. 4. Hand over a simple document: what each license is, what it costs per year, when it renews, and where to log in.
If you are the freelancer or agency, this protects you too. The moment the client owns the licenses, renewals are their responsibility, not your midnight emergency. Put the expected annual license cost in your proposal — clear contract clauses about who pays for what prevent the awkward conversation later. And when you hand the site over, license ownership goes on the handoff checklist right next to the admin accounts.
One exception: agencies running a genuine care plan sometimes hold unlimited developer licenses and cover client sites under them — that is a legitimate model, and it is exactly what unlimited tiers are for. But it must be in writing, in the maintenance agreement, with a clear answer to “what happens to my updates if I cancel the plan?” If there is no written answer, the client should own the keys.
Renewal Traps That Cost Real Money
You have chosen the right tier. Now do not lose the savings to the fine print. These are the four traps I check for on every purchase, and I have been caught by two of them.
The intro-price trap. Year one is $49; renewal is $79. The pricing page shows the big $49 and the renewal price hides in the FAQ or the checkout fine print. Always find the renewal price before you buy — it is the number you will actually pay for years two, three, and beyond.
The auto-renewal ambush. Most vendors auto-renew at the renewal price on your card. That is fine when you want to continue — and expensive when you forgot you owned the license. Calendar reminders, two weeks out, every license. I also keep a one-line note per license: keep, downgrade, or cancel, decided calmly in advance.
The expired-license limbo. When a license expires, the plugin keeps working — remember, the key never controlled permission. But updates stop, and that is where the slow damage starts. An expired security plugin is a contradiction in terms. If you decide not to renew, decide it deliberately: either replace the plugin or accept the risk with open eyes. What you must never do is let licenses expire silently across five sites and discover it during a security audit.
The “lifetime” asterisk. Lifetime deals are wonderful when they are honest and brutal when they are not. “Lifetime” should mean the lifetime of the product with all updates included — get that in writing (a screenshot of the terms page counts). If the vendor gets acquired or pivots, lifetime promises are the first casualty. I treat every lifetime deal as a bet, size the bet accordingly, and never put load-bearing infrastructure on a lifetime license from a vendor I have not watched for at least two years.
Keep your update routine disciplined regardless of tier — a valid license only helps if you actually install the updates it unlocks. And when an update goes sideways, knowing how to roll a plugin back matters more than which tier you bought.

Frequently Asked Questions
If I buy a single-site license, can I move it to a different site later? Yes, with almost every reputable vendor. You deactivate the key on the old site (usually one click in the plugin’s settings) and activate it on the new one. The slot follows the key, not the domain. This is why counting production sites matters more than predicting the future — sites come and go, and the license moves with you.
Do my staging and development sites use up license slots? No — not with any vendor worth paying. Localhost, staging subdomains, and `.test`/`.local` domains are excluded from the site count as long as they are clearly dev environments. Your live site plus its staging copy counts as one slot. If a vendor counts staging against you, that tells you everything about the vendor.
What actually happens when my license expires — does the plugin stop working? No. The plugin keeps running exactly as before. What stops is the update feed and the support desk. The real risk is slow: over the next year, WordPress core moves forward and your frozen plugin does not, until an update breaks it or a known vulnerability goes unpatched. Treat expiry as a decision point, not a cliff — renew, replace, or consciously accept the risk.
Can I upgrade from single-site to unlimited later without paying full price twice? With most established vendors, yes — you pay only the price difference, and your renewal date usually stays put. This is the single most reassuring fact in this whole article: you do not need to predict your future site count. Buy the tier that fits today and upgrade when growth actually happens.
Should my developer buy the licenses for my site? Convenient in the short term, risky in the long term. If your developer buys under their account and disappears, your updates disappear with them. The safer pattern: you buy under your own email and payment method, and the developer simply enters the key. If an agency covers your sites under their unlimited developer license as part of a care plan, get it in writing — including what happens to your updates if you ever cancel.
Final Thoughts
Here is what I want you to take away from all of this: stop asking “which tier is better” and start asking “how many live sites am I actually running, and who owns the keys?” That one shift — from guessing about the future to counting the present — makes the single-vs-unlimited decision almost boring. And boring is good. Boring means you bought once, mapped it, calendared the renewal, and never thought about it again. If you are also choosing a theme, see how to buy a WordPress theme without getting burned. For the licence basics behind this, read WordPress plugin licenses explained before you buy. When a vendor’s support desk is slow, find out where to get real WordPress help. The same buy-versus-build thinking applies when you weigh block themes vs classic themes. If you are still deciding how to host, read our guide to self-hosted WordPress.
You have done the hard part already by reading this far. Now open that spreadsheet, list your production sites, and run the four steps. Future you — the one who is not rebuying the same plugin at midnight before a launch — says thank you.
One honest line before you go: I still get this wrong sometimes. Last year I bought an unlimited tier for a plugin I now use on exactly one site. The maths did not justify it; the optimism did. Licenses are a small corner of running WordPress sites, but getting them right is one of those quiet professional habits that compounds.
Did this save you from a bad purchase — or did you learn it the hard way like I did? Tell me your license horror story in the comments. I read every one, and the best ones might just save the next reader some money.


2 comments