How to Sell WordPress Plugins: A Developer’s Guide for 2026

Selling a WordPress plugin used to mean uploading a ZIP to CodeCanyon. Since July 2026 that route costs you half of every sale — so here is how the plugin business actually works now, from GPL rules to pricing tiers to the licensing plumbing nobody warns you about.

1. The 2026 reality check: the marketplace era is over

For more than a decade, the default answer to “how do I sell my WordPress plugin?” was simple: upload it to CodeCanyon and let Envato’s traffic do the work. That answer stopped making sense this year.

On July 1, 2026, Envato retired its tiered exclusive author model and moved every seller on CodeCanyon and ThemeForest to a flat 50% revenue share. Under the old system, long-standing exclusive authors could keep up to 87.5% of each sale. Overnight, an elite author keeping 87.5 cents on the dollar was keeping 50.

That reframes the whole question. Selling a WordPress plugin in 2026 is not about picking a marketplace. It is about building a small software business: a free product that earns distribution, a paid tier that earns money, and the licensing, tax and support plumbing that keeps it running. This guide walks that path end to end.

2. Validate the idea before you write the code

There are over 61,000 free plugins in the WordPress.org repository and roughly 90,000 across the whole ecosystem. Building something that already exists in ten flavours is the single most common way developers waste six months.

The good news is that WordPress is unusually transparent. Every plugin’s public page shows active install counts, review history, support-thread volume and time since the last update. That is a free market-research dataset, and it is the first thing you should mine.

3. What GPL actually lets you sell

This is where new plugin developers get most confused, so let’s be precise. WordPress is licensed under the GPL, and any plugin that calls WordPress functions is treated as a derivative work. Every plugin in the official directory must be GPL-compatible, with GPLv2 or later recommended.

The practical consequence: you cannot legally stop a customer redistributing your plugin’s code. Someone can buy your $99 license, drop the ZIP on a “GPL club” site for $5, and be entirely within their rights as far as the code goes. So what are people paying you for?

And there is one thing GPL explicitly does not cover: trademarks. Your plugin name, brand and logo are yours. Neither does it cover your marketing graphics, screenshots and promotional artwork — those keep their own copyright. That is the lever you actually have against resellers: a cease-and-desist for trademark infringement, or a DMCA takedown over your artwork, never over the code itself. If your plugin becomes meaningful revenue, registering the name as a trademark (from around $275 per class with the USPTO) is a sensible early expense.

Where premium code is allowed to live

WordPress.org guideline 5 prohibits shipping a plugin whose functionality is “restricted or locked, only to be made available by payment.” You cannot upload a crippled plugin with a paywall inside it. The three accepted patterns are:

1. Separate Pro plugin. The free plugin is genuinely complete on its own; a distinct premium plugin, hosted and distributed by you, adds the paid features.
2. Add-on architecture. The free core exposes hooks; each paid extension is its own plugin.
3. Paid service. The plugin is a free client for a paid SaaS backend — explicitly permitted, provided you disclose the external service and get consent.

4. Pick a business model

Three models dominate, and the right one depends far more on how well-known you are than on how good your code is.

Layered on top of the model is the billing structure, and here the industry has converged: an annual license, priced per site. It aligns what customers pay with the ongoing cost of shipping updates, and it turns a plugin into a business with predictable revenue rather than a lottery ticket dependent on new sales every month.

5. Where to sell: marketplace vs your own store

You are really choosing three things at once: how much commission you pay, who owns the customer relationship, and how much infrastructure you run yourself.

The maths is stark. On $50,000 of annual revenue, CodeCanyon’s 50% cut leaves you $25,000. A hosted platform at ~10% leaves roughly $45,000. A self-hosted store paying only gateway fees leaves about $48,500 — minus extension licenses and the hours you spend maintaining the store yourself.

But commission is not the whole story. The reason experienced plugin sellers left the marketplaces is the customer list. On CodeCanyon, buyers are Envato’s buyers: you cannot email them about a new product, a renewal, or a security notice. Selling direct means every customer is an asset you can market to for years. Barn2 CEO Katie Keith put it flatly: “WordPress product sellers — if you’re still on Envato, I’d love to know why.”

If you run your own store, it’s production infrastructure now

Your store is also your license server and your update server. When it goes down, customers cannot activate, cannot update, and cannot buy. Put it on hosting you trust rather than the cheapest shared plan — our roundups of the best cheap web hosting services of 2026 and the best VPS hosting services for 2026 are useful starting points, and a VPS is the sensible floor once your update endpoint is serving real traffic. Set up automated off-site backups and know how to restore them; if you have never done it by hand, walk through how to back up a WordPress website manually once so you understand what your automated system is actually doing.

6. Price it properly

Underpricing is the most expensive mistake in this entire guide, and marketplace culture is where the habit comes from. An analysis of CodeCanyon’s WordPress plugin catalogue found an average price of $18.91, the most common price point at $15, and 98.2% of plugins priced under $40. Only five plugins in the whole catalogue were priced above $100.

Direct sellers operate in a completely different band, because they are selling an annual relationship rather than a download. A typical ladder looks like this:

Three pricing decisions that matter more than the headline number:

• Set the renewal discount deliberately. A 20–30% renewal discount is common and materially improves retention. Automatic renewals with clear advance notice are standard practice; surprise charges generate refunds and one-star reviews.
• Charge in USD and let your merchant of record localise. Do not hand-manage currencies.
• Be careful with lifetime deals. They convert brilliantly at launch and then quietly become an unfunded support liability. If you offer one, price it at the high end and cap availability.

7. Build the licensing and update plumbing

This is what separates a plugin you can sell from a ZIP file you can email. A commercial plugin needs a small amount of real infrastructure.

You do not have to build any of this from scratch. Freemius ships it as an SDK, EDD sells it as the Software Licensing extension, and self-hosted alternatives exist as one-time purchases. What matters is choosing before launch, because migrating a licensing system with live customers is genuinely painful.

Build details worth getting right

Store your settings sensibly. Most plugins keep configuration in the wp_options table as key-value pairs — if you are unsure of the conventions and why they matter for uninstall cleanup and performance, our explainer on where WordPress plugin settings are stored covers the ground. Keep admin assets properly enqueued rather than dumped into the header; the same discipline described in how to load CSS stylesheets in a WordPress theme applies to plugin screens. And test against multiple PHP and WordPress versions before shipping — installing WordPress on a local host gives you a disposable environment for exactly that.

8. Sort out tax and compliance

Digital products are taxed where the buyer is, not where you are. Selling a $79 license to a customer in Germany creates a German VAT obligation. The EU, UK, Australia, Canada, Norway, Japan and 180+ other jurisdictions have equivalent rules, and many US states now tax software-as-a-service too. In most of the EU there is no revenue threshold that makes this go away.

Alongside tax, get the basics in place before launch: clear terms of service, a refund policy you can honour (a 14- or 30-day money-back guarantee is standard and measurably lifts conversions), and a privacy policy covering any data your plugin sends home. On that last point, WordPress.org guideline 7 requires explicit user consent before your plugin contacts an external server — opt-in telemetry only, always.

9. Get your first 100 customers

WordPress powers over 40% of the web, which sounds like a marketing plan but isn’t. Here is what actually moves plugin sales, roughly in order of return on effort:

1. Rank in the WordPress.org plugin directory. Your readme’s title and short description are the search fields. Active installs and recent five-star reviews drive ranking. Treat the readme like a landing page, because that is what it is.
2. Answer every support thread on the free plugin. Repo support is public marketing. A wall of resolved threads converts browsers into installers, and free-tier support is where your Pro upgrades come from.
3. Write the content your buyers already search for. Documentation, honest comparisons against the incumbent, and genuinely useful tutorials on the problem your plugin solves. This compounds; ads don’t.
4. Build an email list from day one. Capture emails at activation (with consent) and on your site. It is the only channel you own outright — and the single biggest reason to sell direct rather than through a marketplace.
5. Show up where your niche lives. WooCommerce, LMS and membership communities, relevant subreddits, Facebook groups, WordCamps. Be useful in public for months before you mention your product.
6. Run an affiliate programme. A 20–30% commission on first-year revenue turns WordPress bloggers into a commission-only sales team. Most licensing platforms include this for free.

10. What realistic revenue looks like

Plugin developers deserve honest numbers, not survivorship bias. The most detailed public dataset comes from an analysis of CodeCanyon’s WordPress plugin catalogue, and it is sobering.

Two lessons hide in those figures. First, the tail is brutally long: most plugins never become businesses. Second, the ones that do almost always share two characteristics — they sell renewable licenses at real prices rather than $19 downloads, and they own their customer relationship.

11. Mistakes that kill plugin businesses

• Pricing like a marketplace. $19 one-time cannot fund support, security patches and core-compatibility work. Price for the decade, not the download.
• Neglecting free-tier support. Bad reviews on WordPress.org directly reduce your ranking, which cuts off the funnel feeding your paid sales.
• Underpricing the middle tier. It is the tier most customers choose. Set it too close to the entry price and you give away most of your revenue.
• Hard-blocking on license-server failure. If your server goes down and customer sites break, you have manufactured an outage for the people who paid you.
• Ignoring tax until it’s a problem. Back-VAT assessments across multiple jurisdictions can exceed a small plugin’s annual profit.
• Shipping no documentation. Every undocumented feature converts directly into support tickets, and support time is your real cost of goods.
• Fighting GPL instead of building a brand. Code obfuscation is banned on WordPress.org, breaks trust with developers, and doesn’t work. Trademarks and better support do.

12. Pre-launch checklist

Frequently asked questions