Freemium WordPress Plugin Approval: Compliant Free Core?
Yes, a freemium WordPress plugin can have a compliant free core, provided the free version is fully functional and self-contained, and the premium version offers genuine enhancements rather than gating essential security or functionality. WordPress.org’s guidelines require that plugins listed in the repository are not “try before you buy” demos; the free version must work as a complete plugin on its own. This article explains how to build a freemium plugin that passes WordPress.org review, the common pitfalls, and how to structure your free core for compliance.
Background: WordPress.org Plugin Guidelines
WordPress.org is the official directory where most users download plugins. To be listed, a plugin must comply with the Detailed Plugin Guidelines. The key rule for freemium plugins is Guideline #11: “The plugin must not be a ‘try before you buy’ demo.” This means the free version must be a fully operational plugin that provides real functionality without requiring a purchase. You cannot disable core features that are essential to the plugin’s purpose and then charge to unlock them. For example, a contact form plugin that requires a paid upgrade to actually send emails would be rejected, because the free version is just a shell. The free core must be genuinely useful on its own.
How the Approval Process Works
When you submit a plugin to WordPress.org, it goes through a manual review by a team of human reviewers. They check the code for security issues, adherence to coding standards, and compliance with the guidelines. The review process is not automated, so there is room for interpretation, but the “try before you buy” rule is strictly enforced. The reviewer will install the plugin, test its features, and look for any code that restricts or disables functionality without a license key. If they find that the free version is just a teaser, they will reject the submission with a note explaining the issue. You can resubmit after fixing the problem, but repeated violations can lead to a ban.
What Makes a Free Core Compliant?
To pass review, your free core must meet these criteria:
- Fully functional: The free version must accomplish its primary purpose. A caching plugin must cache, a SEO plugin must add meta tags, a gallery plugin must display galleries.
- No essential feature gating: You cannot lock up features that are integral to the plugin’s core function. For example, an e-commerce plugin that requires the premium version to process payments is a demo, not a free plugin.
- Reasonable premium features: The premium version can offer advanced features, but they must be enhancements, not necessities. For example, a gallery plugin could offer more gallery layouts, or a form plugin could offer more form fields, but the free version must still allow basic form creation and submission.
- No time limits or trial periods: The free version must work indefinitely without a license. You cannot have a 30-day trial that then disables features.
- No hidden restrictions: The code must not contain artificial limits like “only 10 forms” if the free version is supposed to be unlimited. If you want to limit features, those limits must be clearly communicated and not just arbitrary code blocks.
Common Problems and Misconceptions
A common misconception is that you can use the free version as a marketing funnel by making it barely functional. That is exactly what the guidelines prohibit. Another mistake is to include upgrade prompts that are too aggressive. While you can show a small “Upgrade to Pro” notice, you cannot interrupt the user’s workflow with popups that block usage. Also, some developers think that by making the plugin “open source” they can bypass the rules, but the guidelines apply regardless of the license. The free core must be genuinely free and functional.
How to Structure Your Freemium Plugin
A compliant approach is to build a solid free plugin that solves a specific problem, and then offer premium features that extend its capabilities. For example, a free SEO plugin might provide basic meta tag editing, while the premium version adds schema markup, social previews, and redirection management. The free version is still a complete SEO tool, but the premium adds advanced features. When coding, use a class-based structure with a filter or action hook that conditionally loads premium features only if a license key is present. The free code should not contain any references to premium features that would break if the premium plugin is not installed. Instead, use the plugins_loaded hook to check for the premium version and load its class.
How to Choose What Goes in the Free Core
When deciding what to put in the free core, ask yourself: “Would a user be satisfied with this plugin if they never paid?” If the answer is no, then you are likely gating essential features. A good rule of thumb is to include the most basic, useful functionality that solves the plugin’s main problem. For a backup plugin, the free version could offer manual backups, while the premium offers scheduled backups and offsite storage. The free version is still useful because it can back up the site. For a page builder, the free version should allow creating and editing pages, while the premium adds more widgets and templates. The free version is still a page builder. The key is that the free core is not a crippled version, but a simpler version.
Costs and Alternatives
There is no cost to submit a plugin to WordPress.org, but you must release it under a GPL-compatible license, which means anyone can use and modify the code. This is a fundamental aspect of WordPress. If you are not comfortable with that, you can sell your plugin directly on your own website, but then you lose the exposure and trust that comes from being in the official directory. Another alternative is to offer a “freemium” model where the free version is hosted on WordPress.org, and the premium version is sold separately. This is the most common approach. You can also use a service like EDD (Easy Digital Downloads) to manage licenses, but that is a separate cost.
Frequently Asked Questions
Can I disable features after a trial period?
No. The free version must work indefinitely. You cannot have a time-based trial that disables features. If you want to offer a trial of the premium version, you can do that separately, but the free version must remain fully functional.
What if my free version has a limit, like only 5 forms?
You can have a limit, but it must be clearly communicated and the free version must still be useful. For example, a form plugin that allows 5 forms is still a functional form plugin. However, if the limit is so low that it’s unusable (e.g., only 1 form), it may be considered a demo. The key is that the limit is a reasonable restriction, not a way to force an upgrade.
Can I show upgrade prompts in the free version?
Yes, you can show a small, unobtrusive notice or a link to the premium version. But you cannot use popups that block the admin area or interrupt the user’s workflow. The prompts should be informational, not coercive.
Do I need to release the premium version under GPL?
Yes, because the premium version is a derivative work of the free version, which is GPL. You must release the premium version under a GPL-compatible license as well. This is a requirement of the WordPress ecosystem. You can still sell it, but the code must be open source.
What if my plugin is rejected for being a demo?
If your plugin is rejected, the review team will provide a reason. You can then modify the free version to make it more functional and resubmit. It’s important to read the feedback carefully and address the specific issue. Do not just resubmit the same code; that will likely be rejected again.
Can I have a free core that requires a license to work at all?
No. That would be a demo, not a free plugin. The free version must work without any license key. The license key should only be needed to activate premium features.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.