If you searched for Webflow Memberships because you want to sell a paid newsletter, course or member area, start with one check: open a private window and try to load a page you believed was gated. The feature behind that name no longer exists, and any tutorial that still shows its settings panel was written while it worked.
That changes the job. You are no longer configuring a Webflow feature, you are choosing a membership layer to sit next to Webflow, and deciding whether hiding content is enough or whether it has to be protected.
Is Webflow Memberships still available in 2026?
No. Webflow ended User Accounts, the feature originally launched as Memberships, on 29 January 2026, and its User Accounts APIs and webhooks stopped working the same day.
Webflow's User Accounts sunset notice (last updated 25 February 2026) says new sites could not enable the feature from 31 January 2025, and existing sites could keep using it until the shutdown date. It names Outseta and Memberstack as recommended replacements, with launch discounts for affected customers at the time of the notice. Logic went the same way earlier: Webflow's Logic sunset article puts its shutdown at 27 June 2025. My reading is that Webflow now wants to be the design and CMS layer, and expects accounts and automation to come from partners.
What should you check on a site built in the Memberships era?
Load your most valuable gated URL in a private window. If it opens, nothing is gating it any more. Then look for the old utility pages such as /sign-up and /log-in. The sunset notice says those pages go to draft on publish and shows how to 301-redirect them, with a percent sign entered before the hyphen in the old path. Do that before you add a new tool, or members will land on dead pages.
What replaces Webflow user accounts for paid content?
Memberstack and Outseta are the two tools Webflow itself recommended, and a self-built app on Webflow Cloud with Stripe is the third route when your access rules are unusual.
Pick by what the member record has to do. A paywalled newsletter and a cohort course are both "premium content", but they need very different things from the record behind the login.
| Option | Entry price (vendor page, 30 Sep 2026) | Transaction fee | Fits |
|---|---|---|---|
| Memberstack Basic | $25/mo billed yearly, up to 1,000 members | 4% | Login and gating layered over an existing Webflow build |
| Memberstack Professional / Business | $39/mo (5,000 members) / $79/mo | 2% / 0.9% | The same layer once volume makes the fee matter |
| Outseta Founder | $47/mo monthly or $37/mo annual, up to 1,000 contacts | 2% (1% on higher tiers) | Membership plus CRM, email marketing and help desk in one record |
| Webflow Cloud plus Stripe | Site plan plus usage | Stripe's fees only | Custom entitlement rules, or a member database you must own |
Those numbers come from the Memberstack pricing page and the Outseta pricing page, fetched on 30 September 2026. Both pages say transaction fees apply when members pay, and Memberstack states that free members incur none, which matters if your funnel starts with a free tier. Outseta bundles unlimited seats, CRM, email and help desk on every plan, so if you already run a separate CRM you would pay for that overlap. Memberstack lists passwordless login among its features, which is worth knowing before a migration (more on that below).
How do you choose between Memberstack and Outseta?
Answer three questions in order. Where does your list of members and leads live today? If it already sits in a CRM and email tool you like, a gating layer such as Memberstack adds the least. If you have nothing yet, Outseta's single record for billing, contacts, email and support saves you wiring four tools together. How much will members pay you per month? Below roughly the point where the fee difference exceeds the plan difference, the cheaper plan wins; above it, move up a tier, as the arithmetic below shows. And who will maintain it? Migration help, which Webflow's notice says Outseta offered as a free VIP migration and Memberstack through Slack, is worth more to a small team than a marginally lower fee.
What does a paid Webflow content site cost each month?
Budget for three bills: the Webflow site plan, the membership tool and the percentage cut on every payment. Webflow's May 2026 pricing update merged the CMS and Business plans into Premium, and the pricing page lists Basic at $15 a month billed yearly with no CMS, and Premium at $25 a month billed yearly with the CMS. A content site therefore needs Premium.
Here is the arithmetic on vendor prices, before Stripe's own processing fees. Take a hypothetical site earning $3,000 a month from members. On Memberstack Basic you pay $25 plus 4%, which is $145. On Professional it is $39 plus 2%, which is $99. On Business it is $79 plus 0.9%, which is $106. The cheapest sticker price is the most expensive plan at that revenue, so compare the fee curve with your expected volume rather than the entry price.
Percentage fees are also the reason some projects leave platforms altogether. The Pizzeria Bestek case study describes a restaurant that moved off a third-party ordering platform, which had been taking about 30% of each order, onto a system it owns. A subscription business will not face that rate, but the pattern of a fee that grows with success is the same.
Is your gated content protected or only hidden?
It is protected only if the paid content never reaches the browser of someone who has not paid; a script that hides elements after the page loads hides content without protecting it.
You can test this yourself in a minute. Open the gated page while logged out, view the page source and search for a sentence from the paid section. If you find it, anyone can read it. For a subscriber-only essay that may be an acceptable trade. For client deliverables, course video or anything with a compliance story, it is not, and the fix is to serve the asset from storage you control through short-lived signed URLs, with the Webflow page acting as the shop window. Check how your chosen tool works, because I can't tell you from outside whether it strips content server-side or hides it in the browser.
Server-side enforcement is what I built into Callidus, the multi-tenant clinic platform described in its case study. During a tenant's grace period the pages stay viewable, but mutations are blocked at the route layer and again in the Firestore rules, so neither layer is the only defence. The stack there is React, Firebase and Stripe Connect. It is a different product from a Webflow site, but the design question carries over: which layer actually refuses the request?
How do you build it yourself on Webflow Cloud?
Webflow's guide to a Stripe subscription site builds the subscription layer on Webflow Cloud and rests on one rule: Stripe owns the truth about billing, and your database keeps a copy. As that guide describes it, you need working authentication, a Next.js 15 or later project, and a place to store subscription state such as the Webflow Cloud SQLite binding. The build then runs in this order:
- Create the Stripe customer when the account is created and store its ID on your user record.
- Record subscription state from a verified webhook, using the async signature check that the Workers runtime requires.
- Derive access from status plus period end, so a member who cancels mid-period keeps what they paid for.
- Offer the Stripe customer portal for self-service.
- Add a reconciliation path for events that never arrive.
The hard part is the failure states. Callidus handles twenty Stripe webhook events end to end, including trial-ending warnings and 3D Secure escalation, and handling only a successful checkout gets you a demo rather than a working membership business. Is it worth building for a paywalled blog? Usually not. It starts to pay when your entitlement rules are unusual or a percentage fee has grown into real money.
What happens to your members' passwords?
Plan for every member to log in again on the new tool. The sunset notice says User Accounts data can be exported through Webflow's CSV export, and it does not mention password hashes. That suggests you should assume passwords will not carry over and treat the switch as a re-login campaign: email members before the cutover and on the day, put a plain explanation on the login page, and watch reactivation over a full billing cycle. Passwordless login, where your tool offers it, removes the "which password did I use?" step entirely.
Webflow still wins on design control, and that is often why people stay. The membership layer is a component you can swap, while the site itself is the product your subscribers see. The pricing page also lists password protection on the Basic plan. That is a page-level option rather than a member system with billing, so it can cover a small private area, but it will not replace a membership tool once people pay you individually and need to be added or removed as they subscribe and cancel.
Open Webflow's User Accounts sunset notice today, compare its redirect steps with your live /log-in and /sign-up URLs, and check which of the two recommended tools matches how your members currently pay. For the surrounding decisions, see Webflow with Zapier for the automation Logic used to handle, the best CMS for marketing sites and WordPress versus a custom website. If you are pricing the build, what a website costs and SaaS web design and development are the two longer reads, both in Bosnian.