Yes. Webflow User Accounts, the feature originally launched as Memberships, stopped being available on 29 January 2026. This was not a rumour or a pricing change. Webflow announced the deprecation itself, gave more than a year of notice, and pointed customers at outside tools instead.
If you search for it today you will find the old marketing page returns a 404 and the User Accounts entries have gone from Webflow''s developer documentation. The feature is genuinely gone, not hidden behind a plan tier.
So the real question is no longer which membership tool Webflow offers. It is which third-party tool you should run on top of Webflow, and what this episode should teach you about platform risk.
Webflow published an update on 11 December 2024 announcing it would sunset two native features. Webflow Logic ended on 27 June 2025, and User Accounts ended on 29 January 2026. Customers could still enable both features on sites up to 31 January 2025, which Webflow described as a grace period.
The User Accounts shutdown covered more than the visible login screens. Webflow''s announcement was explicit that this was a full deprecation of the native capability, and its developer documentation for the User Accounts endpoints is no longer published, so anything built against those APIs stopped working too.
Webflow directed impacted customers to a Help Center article covering dates, migration guidance, partner discounts, and a list of certified Webflow agency partners who could help with the move. If you are only discovering this now, that article is the first place to look.
Webflow said it was choosing focus. In its announcement, Webflow framed the decision as part of its shift to being a Website Experience Platform, and said it made the strategic decision to deprecate native Logic and User Accounts in favour of its ecosystem of vetted app partners that are purpose-built for those needs.
The same post named where Webflow is putting effort instead: Localization, Analyze, and Optimize, plus continued investment in design systems and in becoming what it called the leading visual-first, composable CMS. Read together, that is a company deciding it is a website platform rather than an application platform.
We think that call was correct, even though it hurt the people who had built on the feature. Memberships done properly means authentication, billing, permissions, email, and compliance. That is a whole product. A team maintaining it as a side feature will always lose to a team for whom it is the entire business.
What we are less comfortable with is the position it left agencies and clients in. Anyone who launched a membership site on Webflow in 2024 built on something the platform withdrew within about two years.
It means the gated part of your site is no longer functioning and needs replacing rather than repairing. There is no setting to turn it back on. The work is a migration: a new tool, new user records, new login flows, and new links between your gated pages and whatever now controls access to them.
Treat the user data as the urgent part. Everything else on your site is still in Webflow and still yours. The list of who your members are, what they paid for, and what they can see is the piece that depends on a system being switched off, so that is where attention belongs first.
If you took payments, check what happened to the billing side separately from the login side. Those are two different systems even when one product presented them as one feature, and they can fail independently.
Webflow named both as its top recommended partners for User Accounts, so both are safe starting points. Our rough rule is that Memberstack suits you when you mainly need logins, gating, and payments bolted onto a Webflow site. Outseta suits you when you want membership plus CRM, email, and support in one system.
Memberstack is the more focused tool. It is built specifically around adding authentication and paid access to sites like Webflow, and it stays in its lane. That narrowness is the reason we reach for it most often, because a smaller tool has fewer opinions to fight when you already have a design you like.
Outseta is the broader bet. It bundles more of the business around a membership, which is genuinely useful if you are otherwise going to buy three products. The tradeoff is that you take on a bigger system than you may need, and switching later is harder because more of your operation lives inside it.
MemberSpace is worth a look as a third option, though note it was not one of the two Webflow named. If you want a recommendation, start with Memberstack unless you already know you need the CRM and email side, in which case look at Outseta first.
Memberstack''s published pricing runs from a Basic plan at 29 dollars a month with a 4 percent transaction fee and up to 1,000 members, through Professional at 49 dollars with a 2 percent fee and 5,000 members, to Business at 99 dollars with a 0.9 percent fee. An Established plan at 499 dollars a month carries no transaction fee.
The transaction fee is the part to model carefully, because it changes which plan is cheapest at your revenue. A site processing meaningful monthly payments can pay more in fees on the cheap plan than the price difference to the next one up. Work out your fee cost before picking on the headline price.
Memberstack lists the usual capabilities across its plans, including Stripe payments, social logins, custom single sign-on, and branded emails. It also advertises that you can start without a credit card and stay free until you launch, which makes it easy to build and test the migration before committing.
Sometimes, and it is worth checking before you buy anything. If all you need is one protected page for a client or a downloadable resource behind an email address, Webflow''s built-in password protection on paid site plans or a simple form gate will do the job. Not every restriction needs accounts.
The question we ask is whether you need identity or just a barrier. A barrier stops casual access and costs nothing. Identity means you know who each person is, what they bought, and what they can see, and that genuinely requires a membership system.
Plenty of the membership projects we get asked about turn out to be barrier problems. A resource library, a pricing sheet for existing clients, or a beta signup does not need per-user accounts. If you can solve it with a form and a link, you should, and our guide to building Webflow forms covers most of what that takes.
That Webflow will pick partners over parity, and that the pattern repeats. Logic was Webflow''s native automation feature and it ended on 27 June 2025, with Webflow naming Zapier and Make as its top recommended replacements. The User Accounts decision followed exactly the same shape, announced in the same post.
The useful signal is which direction Webflow keeps moving. Native features that duplicate a mature third-party category get handed to that category. Features that are core to designing, building, and managing a website get investment. That is a coherent strategy and it is fairly predictable once you see it.
In practice, the Logic transition was the easier of the two, because automation tools are interchangeable in a way that user databases are not. Moving a workflow to Zapier or Make is a rebuild you can do in an afternoon, as we cover in our walkthrough on automating web workflows with Zapier and Make. Moving a member list is a migration with real risk attached.
Assume anything that is not the core of a platform''s business can be withdrawn, and build so that withdrawal is survivable. That mostly means knowing where your data lives and whether you could export it tomorrow. If the answer is that it only exists inside a feature, you have a dependency rather than a tool.
We now ask one question before recommending any native feature on any platform: is this the thing the company sells, or a convenience they added? Webflow sells website design, hosting, and content management, so we build heavily on those. Anything adjacent, we prefer to run on a tool whose whole business it is.
This is not pessimism about Webflow specifically. It is the same reasoning we would apply to any platform, including the payment and commerce features we discuss in our piece on whether to use Webflow for ecommerce. The question is always what happens to your data if the feature goes away.
If you still have a site that used User Accounts, treat it as a live outage and start the migration this week. If you are planning a membership build, skip the question of native support entirely and choose between Memberstack and Outseta based on whether you need just access control or a whole business system around it.
The wider lesson is worth holding on to. A platform narrowing its focus is usually good for the platform and occasionally expensive for you, and the way to stay safe is to keep your critical data somewhere you could leave from.
If you are staring at a broken membership site or trying to work out which tool to migrate to, we are happy to talk it through. Reach out at phoenix.studio and we will help you scope it.
Tell us where you want to go. We'll tell you how we'd get you there.