A prospect sent me their Webflow site in July and asked why members could not sign in any more. Nobody had told them the login was gone.
That is the honest state of Webflow Memberships. The feature people still search for by that name was switched off on 29 January 2026, and most of the tutorials ranking for it were written while it still worked. So the useful work sits downstream of that: what a premium content site on Webflow should run instead, and which parts of that stack actually enforce access rather than merely hide it.
Is Webflow Memberships Still Available in 2026?
No. Webflow sunset User Accounts, the feature it originally launched as Memberships, on 29 January 2026, and the APIs and webhooks stopped answering the same day.
The wind-down took a full year. New activations were blocked from 31 January 2025, and the runtime followed twelve months later, per Webflow's User Accounts sunset notice. Webflow named Memberstack and Outseta as its recommended migration partners, and both put discounts in front of affected customers.
Set that beside Logic, which Webflow switched off on 27 June 2025, and the pattern reads clearly enough. Two native features gone inside seven months, and both of them were the parts that made Webflow behave like an application instead of a site builder. Webflow keeps the design surface and the CMS. Your membership state belongs to somebody else now.
If you inherited a site built in the Memberships era, go check the behaviour rather than the Designer. Open a private window and try to reach a gated page. On the site that prospect sent me, every gated page was serving to everyone, and had been for months.
What Replaces Webflow Memberships for Paid Content?
Four paths absorbed the work: Memberstack, Outseta, MemberSpace, or your own auth and billing running on Webflow Cloud. They are not interchangeable, and the choice turns on how much of your business lives inside the member record.
Pick by what the member record has to do, not by which pricing page looks cheapest. A paywalled newsletter and a cohort-based course have almost nothing in common operationally, even though both are "premium content."
| Option | Entry price | Transaction fee | Fits |
|---|---|---|---|
| Memberstack | $29/mo (1,000 members) | 4%, down to 0.9% on Business | Gating and auth as a layer over an existing Webflow build |
| Outseta | $47/mo (1,000 contacts) | 2%, 1% above Founder | Membership plus CRM, email and help desk in one record |
| MemberSpace | $24/mo annual (1 site) | 5%, 2% on Growth | Small paywalled sites where setup speed beats control |
| Webflow Cloud + Auth0 + Stripe | Site plan only | Stripe's cut alone | Custom entitlement rules, or a member record you must own |
Those are first-party numbers, taken from the Memberstack pricing page, the Outseta pricing page and the MemberSpace pricing page in 2026. Read the fee column carefully, because it is the part that scales with your success rather than your member count. Memberstack does not charge a transaction fee on free members, which matters a lot if your funnel is free-tier-heavy.
Outseta is the odd one out here, and deliberately so. It bundles payments, authentication, gated content, CRM and email onto every tier with unlimited seats, which makes it a different product shape from a pure gating layer. If your team already lives in a separate CRM, you will pay for that bundle twice.
Your Gated Content Is Probably Still in the Page Source
Every mainstream Webflow membership tool gates in the browser. A script loads, checks whether the visitor has an active plan, and hides or reveals elements on the page. That is a legitimate pattern for a paywalled blog. It is not access control.
The distinction matters the moment the gated thing has real value. Disable JavaScript, or open the page source, or hit the Webflow CMS API directly, and content that was only hidden is content that was never protected. For a subscriber-only essay, shrug. For client deliverables, course videos with signed URLs, or anything with a compliance story attached, that gap is the whole risk.
You can feel the difference in how server-enforced gating gets built. On Callidus, the multi-tenant clinic platform I built this year, a tenant in its grace period can still view pages, but every mutation is blocked at the route layer and again in the Firestore security rules. Two layers, deliberately, so there is no single-layer bypass. Actually, "deliberately" undersells it. The rules layer exists precisely because I assume the route layer will eventually be wrong.
Webflow gating tools cannot offer you that, because your content lives in Webflow's CMS and your rules live in a script Webflow loads. If your premium content is genuinely worth stealing, the honest answer is that it should not sit behind a client-side check at all. Move the asset to storage you control and serve it through signed, expiring URLs, with the Webflow page acting as the shop window.
What Does a Webflow Paid Content Stack Actually Cost?
Budget for three bills at once: the Webflow site plan, the membership tool, and the percentage cuts that stack on top of every payment.
Webflow restructured its site pricing in May 2026. The CMS and Business plans were folded into a single Premium plan at $25 per month billed yearly, with 20,000 CMS items and up to 2.5 TB of bandwidth, while Basic sits at $15 per month, according to Memberstack's 2026 breakdown of the new Webflow plans. Existing plans reprice at the first renewal on or after 29 June 2026, and Freelancer or Agency workspaces move on 16 November 2026.
So a modest paid-content site on Premium plus Memberstack Basic starts at roughly $54 a month before a single member pays you. Then the fees compound. Stripe takes its processing cut, your membership tool takes 4%, and both apply to the same transaction. On $3,000 of monthly recurring revenue that is around $120 a month leaving in fees, or a little over a Premium plan every month, purely for the privilege of collecting.
That number is why the fee percentage deserves more attention than the sticker price. Moving from Memberstack Basic at 4% to Business at 0.9% costs $70 more per month and saves $93 on that same $3,000. The break-even arrives earlier than most people assume.
I have watched the same arithmetic play out outside Webflow. Pizzeria Bestek, a restaurant ordering platform I built and handed over in September 2025, exists mainly because aggregator commission was eating roughly 30% of every order. The owners now keep 100%. Percentage fees feel harmless at launch and become the reason for a rebuild at scale.
The Migration Step Nobody Budgets For
Passwords do not migrate. That single fact causes more member loss than any technical part of the cutover.
Webflow's CSV export carries the member records, but no platform hands over usable password hashes, and even where hashes exist the algorithms rarely match between providers. Every member therefore resets on first login. Notice what Memberstack's migration guide covers in detail and what it does not: the form converters get a four-step walkthrough, and passwords are not part of the flow at all.
Here is where it hurts. A subscriber returns weeks after your migration, types the password they have used since 2023, and gets rejected. They do not read your announcement email. They assume the site is broken and they leave, and your churn dashboard records it as a normal cancellation with no cause attached.
Budget for that. Email before the cutover and again on the day, put a plain-language explanation on the login page itself rather than in a modal, and watch reactivation for a full billing cycle instead of a week. If you have a high-value cohort, reach out to them individually. It is unglamorous work and it is the difference between a migration and an attrition event.
Where Webflow Still Wins
Design control, and it is not close. If your subscribers buy partly because of how the site reads and feels, Webflow plus a membership tool beats a generic course platform on every axis that matters commercially. The gating layer is a component you swap. The brand experience is the product.
Building It Yourself on Webflow Cloud
Webflow's own sanctioned path for a subscription membership site now runs on Webflow Cloud with Auth0 for login and Stripe for billing, documented on the Webflow blog. The shape is familiar to anyone who has shipped a SaaS:
- Keep the marketing site and CMS in Webflow, exactly as they are today.
- Deploy a small app to Webflow Cloud, which runs on a Cloudflare-backed edge runtime alongside your site.
- Hand authentication to Auth0 and read the session in that app.
- Take subscriptions through Stripe Checkout, then handle every webhook event that changes entitlement, starting with
checkout.session.completedand continuing through the subscription updates and payment failures behind it. - Store the membership flag yourself, and have the app serve gated content only after checking it server-side.
One trap is worth naming before you start: do not reach for NextAuth.js as your Auth0 wrapper here. It depends on Node-specific modules that the edge runtime does not provide, and the failure shows up at deploy rather than in local development.
The webhook half is where these builds actually get hard. On Callidus I handle twenty Stripe events end to end, including the trial-ending warnings and the 3D Secure escalation path when a payment needs customer action. Handling checkout.session.completed gets you a demo. Handling the failure states gets you a business.
Is that worth building for a paywalled blog? No. Is it worth building when your entitlement rules are unusual, or when a percentage fee on every transaction has compounded into real money? That is a genuinely different calculation, and more sites cross the line than admit it.
Do This Before You Pick a Tool
If you are gating content behind a login on Webflow today, three decisions cover it. Pick a tool by fee curve rather than sticker price, because the percentage is what grows. Decide honestly whether your content needs hiding or protecting, and move it off the page entirely if it is the latter. Plan the password reset as a retention campaign rather than a support ticket.
For the wider stack questions this sits inside, pairing Webflow with Zapier covers the automation layer that Logic used to hold, and my rundown of the best CMS platforms for marketing sites explains where Webflow's content model genuinely wins. If you are weighing a self-hosted editor against a bespoke front end, WordPress versus a custom website build is the fork that decides more than any plugin comparison. On the delivery side, how SaaS and web application design and development actually run and what a website build actually costs will tell you whether the custom path fits this year's budget.
Open your Webflow site in a private window right now and try to reach your most valuable gated page without logging in. Then view source on it. What you find in the next sixty seconds decides which half of this post applies to you.
