Expandable Paywall
A paywall solution that can be easily expanded with integration with several third party providers.
Solid choice
Expandable Paywall is a solid plugin choice in 2026, with a few things worth checking first. It runs on 10+ sites, is rated 5/5 and was last updated 2 weeks ago, and scores 68/100 on our health check.
- Actively developed — last update 2 weeks ago
- Small user base (10+ active installs)
- Very few reviews so far
- Needs PHP 8.3 or newer
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Expandable Paywall stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| cambey | #1 |
| external authentication | #66 |
| metered paywall | #3 |
| paywall | #7 |
| remote authentication | #38 |
Version adoption
Share of active sites per release.
Rating breakdown
★★★★★★★★★★ 5 from 2 reviews
About Expandable Paywall
From the official readme · v2.3.0Description
The Expandable Paywall plugin offers a robust solution for implementing paywalls on WordPress sites. Its core functionality includes a simple hard paywall using native WordPress authentication. The plugin is uniquely designed to integrate with various circulation fulfillment providers, making it ideal for magazine publishers. Premium add-ons expand its capabilities, supporting multiple paywall types, authentication methods, and advanced reporting features.
Installation
- Activate the plugin through the
Pluginsmenu in WordPress - Browse to Admin->Expandable Paywall
- You can find out more on how to install by visiting https://pramadillo.com/documentation/expandable-paywall/
Frequently asked questions
Do you offer installation and customization services?
Yes, if you need help with installation and/or would like additional customization work done for your website, you can fill out a request form at https://emoxie.com/contact
I wish this plugin had XZY feature
While I try to do my best to incorporate new features all the time, I implemented a new Feature Request board located at https://emoxie.com/contact
Changelog
Recommended for everyone: includes security hardening. If you use a page cache, clear it once after updating so any stored copy of your login page is rebuilt.
=2.3.0=
* SECURITY – Security hardening.
* FEATURE – New “Logins only” choice for debug logging, under Advanced. It records each sign-in attempt, how it ended, and what your authentication add-on reported while handling it, without the paywall decision for every page view. Sites that had debugging on keep logging everything.
* FEATURE – Authentication add-ons can troubleshoot one person’s logins, including with debug logging off. Cambey & West Authentication uses this to troubleshoot a single subscriber.
* BUGFIX – Logging in from the paywall on an article the theme loaded underneath the current one, such as TagDiv Newspaper’s automatic next-article loading, no longer lands readers on a stripped-down page that cannot be scrolled on phones.
* BUGFIX – Pages showing the login form are no longer stored by page caches, which sent everyone who logged in there back to the article the first visitor came from. Clear your cache once after updating.
=2.2.3=
* BUGFIX – The article a visitor has opened no longer gets a lock icon on its own heading when the theme renders it through a page builder template. This affected sites using TagDiv Newspaper Cloud Library templates on single posts.
* FEATURE – New “Also show the lock icon on the article being read” setting, under Show locks. Off by default, which is how sites behave today.
* FEATURE – New “Also show the lock icon in RSS feed titles” setting, under Show locks. Off by default, so feeds are unchanged unless you turn it on.
=2.2.2=
* BUGFIX – Lock icons appear again on protected posts listed on a page or alongside an article. “Show locks” stopped working on page builder front pages and on any layout built with TagDiv Newspaper flex blocks or Cloud Library templates, and in related post, previous/next and recent post listings. The article being read still has no lock on its own heading.
=2.2.1=
* BUGFIX – Fixed the paywall settings screen showing nothing selected under Categories, Tags and any other taxonomy after updating from 2.1. Saving the screen in that state cleared the selection for real. If you saved paywall settings on 2.2.0, see the upgrade notice.
* BUGFIX – Saving a settings form that does not contain the taxonomy fields, which is any paywall type other than Basic, no longer clears the protected categories and terms.
* UPDATE – The category, tag and taxonomy fields on the settings screen now search as you type instead of listing every term in the page, so the screen stays usable on sites with tens of thousands of terms.
=2.2.0=
* SECURITY – The “Enable Structured Data for Search Engines” option no longer puts the full article in the page. If you had it switched on, your paywalled articles were readable by anyone. See the upgrade notice.
* FEATURE – Protect posts by tag or by any custom taxonomy as well as by category. A post is protected if it matches any one of them.
* FEATURE – Create subscriber roles from the settings screen. A new role is a clone of the built-in Subscriber role under a name you choose.
* FEATURE – Optionally let verified Google and Bing crawlers read the whole article so it can be indexed on its full text. Off by default. Verification is by published crawler address, not by user agent.
* UPDATE – Installing the plugin no longer creates a “Paid Subscriber” role on its own. Roles already created are left exactly as they are.
* UPDATE – Paywall structured data is now JSON-LD in the page head, and is only added to articles that are actually protected.
* UPDATE – Plugin data is removed on uninstall. User roles are deliberately left alone.
* BUGFIX – Fixed sixteen strings that could never be translated, including every label on the login and registration forms, and rebuilt the translation template.
* BUGFIX – The upgrade notice on the Plugins screen no longer shows its own markup as text.
* BUGFIX – Replaced deprecated jQuery shorthands and stopped inserting server error messages as markup.
=2.1.11=
* SECURITY – Registration through the paywall form is now off by default, behind a new setting. Sites using the registration form must enable it after updating. See the upgrade notice.
* SECURITY – Roles that can edit or manage the site are no longer offered or accepted as subscriber roles.
* SECURITY – Registration now validates the email address and requires a password.
* SECURITY – New bypass links use a cryptographically random code. Existing links keep working.
* SECURITY – Reading and clearing the debug log now requires the same permission as the Log screen.
* SECURITY – Category, post type and role names are escaped on the settings screen.
* SECURITY – The forgot password link escapes its URL, and is omitted when none is configured.
* SECURITY – The Log screen no longer opens its own database connection or prints database errors to the browser.
* UPDATE – DataTables is bundled with the plugin instead of loaded from a CDN, and is about 117KB smaller.
* UPDATE – Tested up to WordPress 7.0.2.
* BUGFIX – Fixed a fatal error that took out the front end when the paywall was enabled but its settings had never been saved.
* BUGFIX – Fixed login failing for passwords containing < or >, and for usernames or email addresses containing an apostrophe.
* BUGFIX – Filters registered on init, which is where add-ons register them, are no longer ignored for protected categories and bypass roles.
* BUGFIX – Bypass links are now generated for posts saved in the block editor.
* BUGFIX – A second login or register shortcode on the same page now renders.
* BUGFIX – Logged user agents no longer store escaped slashes, and a missing User-Agent no longer raises a notice.
=2.1.10=
* UPDATE – Login Form redirects with cache busting parameter.
=2.1.9=
* UPDATE – Login Form shortcode now redirects back to page you were on when logging in
=2.1.8=
* BUGFIX – Removed Debugging Code
2.1.7
- BUGFIX – Fixed load_plugin_textdomain PHP Notice
2.1.6
- UPDATE – Updated all third-party vendor packages
- UPDATE – Added new filter for controlling when to show show_authentication_role_paid
2.1.5
- UPDATE – Updated all third-party vendor packages
2.1.4
- UPDATE – Excluded the search screen from paywall trigger
2.1.3
- UPDATE – Add stub function back into public class for extendability
2.1.2
- BUGFIX – Fixed issue with 500 error when trying to create a new user on specific installs
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
FAQ
Expandable Paywall: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 14, 2026
Is Expandable Paywall free?
Yes. Expandable Paywall is free to download and use from the official WordPress.org plugin directory.
Is Expandable Paywall safe to use in 2026?
Expandable Paywall is a solid plugin choice in 2026, with a few things worth checking first. It runs on 10+ sites, is rated 5/5 and was last updated 2 weeks ago, and scores 68/100 on our health check.
How many websites use Expandable Paywall?
Expandable Paywall is active on 10+ WordPress websites and has been downloaded 4,934 times since it launched in March 2020. It was downloaded 189 times in the last 30 days.
Does Expandable Paywall work with WordPress 7.1?
Expandable Paywall is officially tested up to WordPress 7.0.7, while the latest release is 7.1.3. It may still work, but try it on a staging site first.
What PHP version does Expandable Paywall need?
Expandable Paywall requires PHP 8.3 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Expandable Paywall last updated?
The latest version, 2.3.0, was released on October 2, 2026 (2 weeks ago).
Who makes Expandable Paywall?
Expandable Paywall is developed and maintained by Matt Pramschufer.
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card

