Build paid WordPress memberships with subscriptions, content protection, checkout, member accounts, courses, coupons, and recurring billing.
Plugin Health & Stats
Historical overview
364-day WordPress.org historyRestrict Content Pro is a WordPress membership plugin built around paid membership levels, recurring subscriptions, content restriction, member management, and an extension ecosystem. It is aimed at publishers, communities, course businesses, associations, and other sites where access rules and subscription billing need to remain inside WordPress.
What Restrict Content Pro does
The core workflow starts with membership levels. Site owners can create free or paid plans, set recurring or one-time billing, offer trials and discount codes, and restrict content according to membership status, level, role, or other rules. This makes it suitable for premium articles, private resources, paid communities, downloadable content, coaching libraries, and subscription-based information products.
Restrict Content Pro also includes member account management, renewal and expiration handling, registration workflows, payment records, reporting, and developer hooks. Its add-on library extends the platform with group accounts, drip content, REST API access, BuddyPress and bbPress integrations, Mailchimp and MailPoet connections, download protection, WooCommerce member discounts, and other membership-specific workflows.
Restrict Content Pro is becoming Kadence Memberships
The current free package is version 4.0.4 and the current Pro package is 4.0.7 in Nexcess’s September 2026 changelog. The underlying membership model, Restrict Content shortcodes, membership records, gateway integrations, and developer APIs remain recognizable, but branding and distribution are moving into the Kadence/Nexcess ecosystem.
Existing sites should treat the change as a product transition rather than a reason to rebuild memberships from scratch. Before updating, back up the database and test registration, Stripe or PayPal renewals, cancellations, expiration dates, drip rules, group accounts, and restricted-content queries. Version 4.0.3 specifically fixed several Stripe renewal, free-trial, and declined-card edge cases, while 4.0.4 reduced database load and fixed email/gateway-label issues.
For migrations away from the platform, export members, membership levels, payments, expiration dates, and gateway profile IDs separately. Existing recurring charges are tied to processor subscriptions, so changing a membership level price does not automatically rewrite what current members are charged. Preserve historical levels for active subscribers until their renewal lifecycle has been intentionally moved.
Pricing and licensing
Restrict Content Pro is now transitioning to Kadence Memberships. The free WordPress.org package is published under the Kadence Memberships name, while Nexcess documentation continues to reference Restrict Content Pro during the transition. Because the old standalone RCP pricing structure is no longer the right buying reference, verify the current Kadence/Nexcess package that includes Memberships Pro rather than relying on historical RCP license prices.
Where the product fits
Restrict Content Pro fits sites where membership billing and access control are the primary job. It is more focused on subscriptions and protected content than profile-first tools such as Ultimate Member, and it is less centered on course-building than platforms that bundle a full LMS. That narrower focus can be useful when a site already has its own theme, content structure, community layer, or learning tools.
The group accounts add-on is especially relevant for associations, teams, schools, and business memberships because one account owner can manage multiple members under a shared plan. Drip Content can release protected material over time, while the REST API and developer hooks support integrations with external systems or custom membership workflows.
Payment and subscription considerations
Before adopting any membership plugin, check the exact payment gateways required by the business, whether recurring billing is supported for those gateways, and how failed renewals, cancellations, upgrades, downgrades, refunds, and expiration dates are handled. These details matter more than the headline feature count once a site has paying members.
Existing membership sites should also review how member records and active subscriptions would move. User accounts can often be imported more easily than active payment agreements because recurring tokens and processor-side subscription objects may remain tied to the original system. A migration plan should therefore separate WordPress user data, access rules, historical payments, and live recurring billing.
Strengths
- Focused membership and content-restriction workflow.
- Recurring and one-time membership billing.
- Discount codes, trials, renewals, and expiration handling.
- Large membership-specific add-on library.
- Group accounts and drip-content options.
- Developer hooks and REST API options for custom workflows.
Limitations to plan for
Restrict Content Pro is not designed to replace every community, LMS, directory, or ecommerce plugin. A site that needs social feeds, advanced member directories, courses, forums, or complex commerce may still need integrations or companion plugins. The add-on model is flexible, but it also means the final stack can contain several moving parts.
Membership migrations also deserve caution. Changing access-control plugins on an established site can affect protected URLs, shortcodes, registration forms, payment callbacks, recurring subscriptions, email notifications, and user metadata. Testing on staging before changing a live membership system is a practical requirement rather than an optional cleanup step.
Operational planning for established membership sites
For an established membership business, test renewal emails, cancellation rules, access after failed payments, manual admin changes, and gateway webhooks on staging before moving production traffic. Membership systems sit directly between revenue and protected content, so a small configuration mismatch can either block paying members or expose material that should remain restricted. Documenting the existing lifecycle before migration makes the comparison between Restrict Content Pro and another membership platform much more reliable.
Frequently Asked Questions
Does Restrict Content Pro support recurring memberships?
Yes. It supports recurring membership billing as part of its paid membership workflow, subject to the capabilities of the payment gateway used on the site.
Can Restrict Content Pro drip protected content?
Yes. The Drip Content add-on can release protected content according to a schedule after a member joins.
Does Restrict Content Pro support group memberships?
Yes. Its Group Accounts add-on lets a group owner manage multiple members under a shared membership arrangement.
Does Restrict Content Pro work with BuddyPress or bbPress?
Restrict Content Pro offers integrations for BuddyPress and bbPress so membership rules can be combined with community or forum access workflows.
What should I check before moving an existing membership site?
Review member accounts, access rules, active recurring subscriptions, payment tokens, coupons, drip schedules, protected URLs, emails, and gateway callbacks. Active billing relationships are usually the most sensitive part of a migration.
Who is Restrict Content Pro designed for?
It is designed for WordPress sites where paid or free memberships, content restriction, recurring billing, and member lifecycle management are central requirements.
Compare before you install
Similar Plugins
Open-source WordPress membership platform with free self-hosting, recurring payments, content restriction, premium add-ons, and optional managed hosting.
Creates WordPress membership plans with recurring payments and content restriction, tying site access to each member subscription.