Skip to content
HyperDAF editorialBuying Guides

Single vs Unlimited License: Which WordPress License Fits?

Every premium WordPress product makes you choose: a single-site license or an unlimited license, with a few tiers in between. The price gap can be enormous — sometimes five or…

Buying GuidesEditor-curated guide
10 min11 sectionsIntermediate
Before you beginWhat this guide gives you
11Focused sections10Minutes to finishIntermediateExperience level9Article views
Start reading

Every premium WordPress product makes you choose: a single-site license or an unlimited license, with a few tiers in between. The price gap can be enormous — sometimes five or ten times — which makes the decision feel high-stakes. Choose too small and you will be buying upgrades within months. Choose too big and you have paid for capacity you will never use.


This guide gives you a decision framework instead of a guess. You will learn exactly how sellers define each tier, how to calculate the true per-site cost, which hidden differences to check between tiers, and a simple formula for picking the right license for your situation — whether you run one blog, manage client sites, or operate an agency.


What the Tiers Actually Mean


Before comparing, make sure you understand the vocabulary. Sellers use these terms with reasonable consistency:


Single-site license. Covers one production WordPress installation. Usually the cheapest tier. Staging, development, and local copies are typically excluded from the count by reputable sellers — but verify this, because some sellers count everything.


Multi-site license (5, 10, 25 sites). Covers a fixed number of production installations. The per-site cost drops as the site count rises. This is the sweet spot for freelancers and small agencies.


Unlimited license. Covers an unlimited number of sites under your ownership or management. Usually the most expensive tier, sometimes dramatically so. “Unlimited” almost always has practical boundaries — read the definition carefully.


Developer or agency license. Some sellers offer this as a separate tier above unlimited, adding white-label rights, client-transfer tools, or priority support. Do not assume unlimited includes agency features; check.


The names vary, but the structure is nearly universal. Your job is to map these tiers to your real site count and growth plans.


The Per-Site Cost Formula


The only honest way to compare tiers is per-site cost. Here is the formula:


Per-site cost = tier price ÷ number of sites you will actually use


Work through an example. Suppose a plugin costs $49 for single-site, $99 for 5 sites, and $199 for unlimited:



  • You run 1 site: single-site = $49/site. The 5-site tier = $99/site if you only use one — terrible value.

  • You run 3 sites: single-site × 3 = $147 total ($49/site). The 5-site tier = $99 total ($33/site). The 5-site tier wins.

  • You run 8 sites: single-site × 8 = $392. The 5-site tier plus extras gets complicated — this is where unlimited at $199 ($25/site) wins clearly.


The break-even point between tiers is simple arithmetic, but most buyers never do it. Do it once per product and the right tier usually becomes obvious.


Include renewals in the math. If the single-site tier renews at $39/year and unlimited renews at $149/year, the long-term comparison may differ from the first-year comparison. Calculate a three-year total cost for each tier you are considering:


Three-year cost = purchase price + (renewal price × 2)


Sellers with aggressive first-year discounts and steep renewals look cheap until year two. The three-year view exposes this.


When Single-Site Is the Right Choice


Single-site licenses are not a trap — they are the correct choice in clear situations:


You run one website. Bloggers, small business owners, and hobbyists with a single site should buy single-site. Paying for unlimited “just in case” is speculation, and you can almost always upgrade later by paying the difference.


You are evaluating the product. Buying single-site for a trial deployment is sensible. Test on one real site for a month or two; upgrade when you are convinced.


Each site has a separate budget. If every client pays for their own licenses, single-site per client keeps billing clean. The client owns the license, the client pays the renewal, and there is no ambiguity about who is responsible.


The product is site-specific. Some products — a theme for a flagship site, a specialized booking plugin for one business — will only ever run in one place. Match the license to reality.


When Multi-Site Tiers Win


The middle tiers are the best value for the largest number of buyers:


Freelancers with a handful of sites. If you manage three to ten sites — your own plus a few clients — a 5-site or 10-site tier typically cuts your per-site cost in half compared to stacking single-site licenses.


Growing portfolios. If you add two or three sites per year, buy the tier that covers next year’s count, not just today’s. Upgrading mid-year usually costs the price difference, but some sellers make you repurchase — check the upgrade policy.


Testing across projects. Developers who install a plugin on several experimental or client-prototype sites benefit from multi-site tiers even if only one or two sites go live.


The upgrade path matters. Before buying a middle tier, confirm you can upgrade to unlimited later by paying the difference — not by buying a whole new license. Sellers with fair upgrade policies make the middle tier a safe stepping stone.


When Unlimited Makes Sense (and When It Does Not)


Unlimited licenses are powerful but frequently oversold. Here is how to think about them clearly.


Unlimited makes sense when:



  • You manage more than roughly ten sites using the product. Above this threshold, the per-site cost of unlimited almost always beats every other option.

  • You run an agency where every new client site will need the product. The marginal cost of each new site drops to zero, which simplifies proposals and pricing.

  • The product is infrastructure — security, backups, performance, SEO — that belongs on every site you touch.


Unlimited does not make sense when:



  • You run fewer than five sites and have no growth plan. The math simply does not work.

  • “Unlimited” excludes key features. Some sellers reserve priority support, onboarding, or advanced features for lower tiers’ buyers who pay per site, or cap the number of support tickets on unlimited plans. An unlimited license with kneecapped support is a false economy for professionals.

  • The renewal price is punishing. An unlimited tier at $499/year needs a lot of sites to justify itself. Run the three-year numbers.


Read the actual definition of unlimited. Honest sellers define it precisely: “unlimited sites that you own or manage for clients, excluding resale or redistribution of the license itself.” Vague definitions like “unlimited everything” with no terms page deserve skepticism. Also check whether client sites count when the client — not you — is the site owner. Agencies get tripped up here.


Hidden Differences Between Tiers


Price and site count are the advertised differences. These are the ones sellers mention less prominently:


Support levels. The most common hidden difference. Single-site buyers sometimes get community forum support while unlimited buyers get private tickets with response-time guarantees — or vice versa. Compare the support terms tier by tier, not just the site counts.


Feature gating. Occasionally, advanced features — multisite support, white-label options, API access, premium templates — are restricted to higher tiers. If you need a specific feature, confirm which tier includes it before comparing prices.


Update channels. All tiers should receive the same updates at the same time. If a seller staggers releases by tier, that is a red flag about their priorities.


License management tools. Higher tiers sometimes include better tooling: centralized dashboards, remote activation and deactivation, usage analytics. For agencies managing dozens of sites, these tools have real value beyond the site count.


Transfer rights. Can you transfer a license to a client when you hand off a site? Single-site licenses usually transfer cleanly. Unlimited and agency licenses usually cannot be split — which means you need a handoff plan for client sites covered under your unlimited license.


The Agency and Freelancer Special Cases


If you build sites for others, licensing gets more nuanced.


Who should own the license? Two models work: you own an unlimited or multi-site license and bundle its cost into your service pricing, or each client owns their own single-site license. The first is simpler for you; the second is cleaner for handoffs. Many professionals use a hybrid: their own multi-site license during development, transferred to a client-owned license at launch.


Client handoff planning. Before buying, decide what happens when a client leaves. If your unlimited license covers their site, can you cleanly remove it? Will the site keep working? Having this answer before the first client asks saves awkward conversations later.


White-label needs. If you present the plugin as part of your own service offering, check whether the license permits white-labeling — removing the seller’s branding from admin interfaces and client-facing elements. This is sometimes restricted to agency tiers.


Renewals Compared Across Tiers


Renewal behavior can differ by tier in ways that change the math:



  • Some sellers discount renewals more aggressively on higher tiers to reward commitment.

  • Others keep renewal pricing proportional — the ratio between tiers stays constant.

  • A few sellers offer “lifetime” only on the unlimited tier, which can make it the best long-term value despite the upfront cost.


Always compare renewal prices, not just purchase prices, and confirm whether renewal discounts apply equally across tiers. A tier that looks expensive in year one can be the cheapest over three years if its renewals are heavily discounted — and the reverse is equally true.


Decision Framework: Pick Your Tier in Five Minutes


Answer these questions in order:



  1. How many production sites will use this product twelve months from now? Be honest. Include your own sites and client sites.

  2. What is the three-year total cost per tier? Purchase plus two renewals, divided by your site count.

  3. Do all tiers include the features and support level you need? If not, eliminate the tiers that do not.

  4. Can you upgrade later by paying the difference? If yes, you can safely start smaller.

  5. Who owns the licenses — you or your clients? This determines whether multi-site or per-client single-site makes sense.


In most cases, question one and two alone point to the answer. The rest protect you from edge cases.


The HyperDAF Standard for Licensing


We believe licensing should be a five-minute decision, not a research project. That is why HyperDAF products use plain-language licenses with clear site counts, self-service license management, fair upgrade paths that only ever charge the difference, and renewal terms published upfront — no surprises in year two. Our unlimited tiers include the same features and the same expert support as every other tier, because a license that covers more sites should never mean worse service. When you run any seller’s tiers through the framework above, you are holding them to the standard that professional, expert-developed products are built to — and it is the standard we meet on every product we ship.


Conclusion


Single versus unlimited is not a philosophical question — it is arithmetic plus a few policy checks. Count your sites, project twelve months ahead, calculate three-year per-site costs, verify that features and support are consistent across tiers, and confirm the upgrade path. That process takes five minutes and prevents the two classic mistakes: outgrowing a single-site license in month three, or paying for unlimited capacity you never use.


Buy the smallest tier that honestly covers your needs with room to grow, from a seller whose terms you have actually read. Do that, and licensing becomes what it should be: a quiet, fair part of running your WordPress sites, not a recurring source of regret.

Written by

Amélie Dubois

Amélie crafts interfaces for WordPress products with a focus on clarity and accessibility. Her 7 years of design practice inform her articles on usability, typography, and conversion-focused layouts.

4 published articles
View all articles

Related articles

View all articles

Join the discussion

Your email address will not be published. Required fields are marked *

Keep comments relevant and respectful.

Stay ahead with weekly insights

Join creators and developers receiving our best articles and product updates every week.

No spam. Unsubscribe anytime.