FREEFirst project with us? Your landing page design is on the house.See the offer

Webflow

Memberships on Webflow: what to use now

Webflow retired User Accounts, its own memberships feature. What changed, the tools Webflow points to, and a simple rule for picking the right setup.

By Abdul QuadirUpdated 2026-11-046 min read
TL;DR
  • Webflow sunset User Accounts, first released as Memberships, on 29 January 2026. Its own help page says so.
  • Webflow names Outseta and Memberstack as its recommended tools for gated content.
  • Pick by what you need: login and gating only, or login plus payments, CRM, email and support.
  • Simple cases need no members tool at all: a password page or a form gate may be enough.
  • If a site used User Accounts, check that formerly gated pages are not now open to everyone.

The short answer

Webflow no longer has its own memberships feature. It sunset User Accounts, which started out under the name Memberships, on 29 January 2026, and it recommends two third-party tools instead: Memberstack and Outseta. Both add sign-up, log-in and gated content to a Webflow site with a script and some setup in the Designer.

Choose Memberstack if you mainly want login, payments and gating that fit around your own design. Choose Outseta if you also want a CRM, email and help desk in the same tool. If you only need to hide a few pages, you may not need either.

What Webflow changed

Webflow's update on the change and its help page on the User Accounts sunset say:

  • User Accounts would no longer be available from 29 January 2026, on every site that used it.
  • From 31 January 2025, it could no longer be turned on for new sites.
  • The User Accounts APIs and webhooks went away on the same date as the feature.
  • For sites still using it on the day, member data was not moved to the CMS, member pages became normal static pages, content gates were removed, and members could no longer log in.
  • Ecommerce customers with paid subscriptions keep them in Stripe, and subscribers continue to be charged.

Webflow called this an ecosystem-first approach: its app partners now cover memberships, and its recommended partners are Outseta and Memberstack.

If your site used User Accounts, check this first

  1. Gated pages. With gates removed, content that was for members only may now be public. Open each former members page in a private window.
  2. Sign-up and log-in pages. Redirect them to a useful page.
  3. Subscriptions. If you sold subscriptions, check Stripe. People may still be paying for access they no longer get.
  4. Forms and automations. Anything that listened to User Accounts webhooks stopped receiving data.

Our redirect map template helps with the second step.

The options, from simplest to fullest

  • Password protection. Webflow can put a password on a page, a folder or the whole site. One shared password, no member accounts. Fine for a press kit or a client preview. Check which plan includes it on Webflow's pricing page.
  • A form gate. Ask for an email, then show the download or the page. No log-in, no account. This suits reports and guides where the goal is a lead, not access control.
  • Memberstack. Its site describes authentication, payments and gated content that drop into an existing site, and says it works on any site where you can add a script tag, not only Webflow.
  • Outseta. Its site lists payments through Stripe, authentication and gating, a CRM, email campaigns and automations, and a help desk in one product.
  • Your own auth. A service such as Clerk, Supabase or Auth0, wired up with custom code or an app on Webflow Cloud. Most control, most code to own.

Webflow's help page also points to its app marketplace for other options. Check each tool's own docs for what it supports today.

A simple rule for choosing

You needStart with
Hide a few pages from the publicPassword protection
Collect emails before a downloadA form gate
Member log-in and paid plans, your own tools for email and CRMMemberstack
Log-in, paid plans, CRM, email and support in one placeOutseta
Accounts inside a product, custom roles, your own databaseYour own auth, or a real app

If the last row is you, the "site" may really be a web app. Plan it as one, not as a marketing site with a log-in on top.

Questions to ask before you pick a tool

  • Where does member data live, and can you export it in full?
  • How does gating work: hidden in the browser, or content that never reaches a visitor without access? Ask the vendor directly.
  • Does it handle your payment case: one-off, monthly, trials, team seats, taxes?
  • Can members manage their own billing and password without emailing you?
  • How do sign-up and log-in screens fit your design and your Webflow components?
  • What happens to members if you leave the tool one day?

The User Accounts sunset is a good reminder of the last question. Keep a regular export of member data, whichever tool you use.

A worked example: a paid resource library

Say a company wants a library of templates and recorded workshops. Some are free with an email, some need a paid plan. Here is how the rule above sorts it:

  • Free templates: a form gate. The visitor leaves an email, the download appears, the lead goes to the CRM. No account needed.
  • Paid workshops: a members tool, because people need to log in again next week, and billing has to renew.
  • CRM and email already in place: Memberstack fits, since the existing tools keep doing their jobs.
  • No CRM yet, small team: Outseta is worth a look, since it bundles the CRM, email and support desk.

The public side stays simple: one page per template or workshop, with a summary anyone can read, and the full content behind the gate.

SEO and gated content

Search engines and AI tools only see what a logged-out visitor sees. Gated pages will not rank on their content. If you want people to find your members content, publish a public page for each piece with a clear summary, then gate the full version. Keep log-in, account and checkout pages out of your sitemap and set them to noindex.

What a typical setup looks like

  1. Write down the plans, what each one gives access to and the price.
  2. Pick the tool using the table above, and create the plans there.
  3. Add the tool's script to the site's custom code.
  4. Build sign-up, log-in and account pages in Webflow with your own components.
  5. Mark the gated pages or folders, following the tool's docs.
  6. Test as a visitor, a free member and a paid member, on desktop and phone.
  7. Set up exports and a backup routine for member data.

What to do next

If your site still has pages from User Accounts, run the checks above first. If you are planning a members area, decide what really needs a log-in; often it is less than you think. We build these on top of Webflow development projects and the integrations above. Tell us what you want to gate and we will suggest the lightest setup that works.

Abdul Quadir
Abdul QuadirFounder of Kookies. Builds Webflow and Astro sites for startups and growing teams.

Terms used: Webflow, Gated content

FAQs

Questions
people ask.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

No. Webflow sunset User Accounts, originally called Memberships, on 29 January 2026. It recommends Outseta and Memberstack for gated content.

Webflow says member data was not moved to the CMS, member pages became static pages, content gates were removed and members could no longer log in.

Memberstack if you want login, payments and gating that fit your own tools. Outseta if you also want a CRM, email and help desk in one product.

Yes, for simple cases. Use password protection for a few private pages, or a form gate when you want an email before a download.

Not directly. Search engines only see what logged-out visitors see. Publish a public summary page and gate the full version.

Webflow says paid subscriptions stay in your Stripe account and keep charging. Check that members still get what they pay for.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.