Can Webflow Do Memberships?

No - Webflow does not have a native memberships feature today. Webflow's own Help Center states it directly: "We've made the strategic decision to sunset Webflow User Accounts (originally under the name 'Memberships'), our native solution for gated content experiences, on January 29, 2026" (Webflow, "User Accounts sunset", checked September 2026). That date has already passed as of this check, and Webflow's own page confirms the result: "On January 29, 2026, the User Accounts functionality will no longer be available on all Webflow sites in which it's currently in use." Here's exactly what that means and what Webflow points customers toward instead.

What did Webflow User Accounts (Memberships) used to do?

Before the sunset, User Accounts was Webflow's built-in system for gated content: "you can add users, login functionality, and control access to pages with access groups to build gated-content experiences for your audience" (Webflow, "Webflow User Accounts overview", checked September 2026). The feature set included:

• Free and paid access groups that gated specific pages or folders to logged-in users, with paid groups tied to an Ecommerce membership product.
• Prebuilt User pages - Log in, Sign up, User account, and a password-reset flow - created automatically once enabled.
• A Subscriptions element, addable only to the User account page, so members could view and cancel their own recurring subscriptions.
• A Users API and webhooks, letting a site sync signups to a mailing list or CRM, or invite and manage users programmatically through Webflow's Logic automation tool.
• Element-level visibility gating, so any element - not just a whole page - could show or hide based on whether a visitor was logged in.

When exactly did it sunset, and what's the timeline?

Webflow announced the deprecation on December 11, 2024, framing it as a strategic shift: "In light of this renewed focus, we've made the strategic decision to deprecate our native Logic and User Accounts in favor of our ecosystem of vetted app partners that are well-positioned and purpose-built to meet the needs of our customers in these areas" (Webflow, "Deprecating Logic and User Accounts", checked September 2026). The rollout had two dates:

• Starting January 31, 2025 - no new sites could enable User Accounts, though existing sites that already had it kept working.
• January 29, 2026 - User Accounts functionality "will no longer be available on all Webflow sites in which it's currently in use," and Webflow also confirms "you will not be able to add User Accounts to any new or existing sites, or call Webflow's User Accounts APIs and webhooks" from that date on.

Both dates are behind us as of this check, so the second one is the state Webflow is in today, not a future warning.

What happened to a site that still had User Accounts enabled?

Webflow's sunset article lists the consequences directly for any site that was still using the feature on January 29, 2026:

• "You'll lose access to User Accounts and all User Accounts data, as it will not be migrated to the CMS."
• "User Accounts pages will be migrated to regular static pages."
• "Content gates within your site will be removed."
• "For published sites, 'members' will no longer be able to login to their accounts."

Paid subscriptions don't stop cleanly, either - Webflow addresses that separately: "If you're a Webflow Ecommerce customer using paid subscriptions, your subscriptions will still be available in your Stripe account, and subscribers will continue to be charged," but Webflow "still recommend[s] migrating to a third party memberships solution before January 29, 2026 to ensure a consistent experience for your customers." In other words, Stripe keeps billing on its own even after the Webflow-side login and gating disappear - which is a mismatch worth fixing quickly if it applies to you, since customers would keep paying for content they can no longer log in to see.

Does this also break Webflow's native Ecommerce Subscriptions?

Functionally, yes, for anyone setting one up fresh. Webflow's own Subscriptions guide - still live, and still carrying the same sunset warning - lists the setup requirements for a subscription product: enable Ecommerce and User Accounts, add an Ecommerce Site plan, connect Stripe as a payment provider, and enable checkout (Webflow, "Subscriptions", checked September 2026, verified by same-origin browser fetch since this host blocks plain fetches). Enabling User Accounts is the first item on that list, and User Accounts can no longer be enabled on any site, new or existing, per the sunset dates above. Webflow's documentation doesn't describe an alternate way to create a new subscription product without it, so if your site doesn't already have both Ecommerce and User Accounts enabled together, this native path is effectively closed today - not just the login-and-gating half of memberships, but the recurring-billing half too.

What does Webflow point customers toward instead?

Webflow named its own recommendations in the same deprecation announcement: "User Accounts will no longer be available on January 29, 2026. Our top recommended partners are Outseta and Memberstack" (Webflow). Both vendors have run migration offers for former User Accounts sites; check their own sites for what is current.

Those two aren't the only options. Webflow's own integrations directory lists several more membership and user-login tools built for this exact gap (Webflow, "Memberships and user login integrations", checked September 2026), including MemberSpace ("add membership plans, content gating, and recurring billing to any Webflow site"), Patreon ("membership widgets," synced patron data, "tier-based content access"), Memberful ("checkout, member account management, and gated content delivery through your own Stripe account"), and Supabase for teams that want to build their own authentication and database layer rather than use a packaged membership tool. Course-specific platforms like Thinkific, LearnDash, and Kajabi are also listed if what you actually need is course delivery rather than a general paywall.

How do I redirect the old login and signup URLs?

If members had bookmarked or been emailed links to /log-in, /sign-up, or similar User Accounts pages, those paths still resolve to whatever Webflow converted them to (a static page, or nothing useful) unless you redirect them. Webflow's own steps, from the sunset article:

1. Go to Site settings → Publishing → 301 redirects and click Add.
2. Enter the Old path, adding a % symbol before the hyphen - for example, /sign%-up rather than /sign-up.
3. Enter the Redirect to path, pointing at wherever the equivalent page now lives (often your new membership provider's hosted login).
4. Click Add redirect path, then publish your site.

Webflow flags this exact gotcha directly: "You must add a % symbol before the hyphen when entering the old path, otherwise you'll get an error and the redirect won't be added" (Webflow). Skipping that detail is the most common way this redirect setup fails silently.

Example (hypothetical): A course creator who had User Accounts live for a paid video library exports their User Accounts data via Webflow's CSV import/export tools before the deadline, signs up for Memberstack's discounted plan, and points their old /log-in path at Memberstack's hosted login with a 301 redirect. Existing Stripe subscribers keep being billed throughout, so the creator prioritizes getting login access restored before touching anything else. This is illustrative only, not a migration Figment ran.

What can I still export before I lose access?

Webflow's sunset article confirms the data path: "You can export your site's User Accounts data with Webflow's existing CSV import/export functionality" (Webflow). That gets you the list of users and their fields - it doesn't get you a working login system, gated content configuration, or subscription history in a format a new tool can import automatically. Treat the export as a starting point for re-registering members on whatever platform you choose, not a drop-in migration.

Where does Figment fit in?

Nowhere for the membership itself. Figment publishes a website from a Figma design through its Figma plugin; it has no login system, access groups, or subscription billing of its own to replace what User Accounts did. If you're rebuilding a marketing site's front end while your gated content moves to Outseta, Memberstack, or another provider, Figment can be the front door - the membership logic still needs to run on a dedicated tool. For what Webflow itself still charges for hosting and the CMS that isn't affected by this sunset, see our Webflow pricing guide; for what its Ecommerce plans do for a store rather than a membership, see our Webflow ecommerce guide.

Bottom line: Webflow's native memberships feature is gone, not paused - the sunset date passed on January 29, 2026, and Webflow's own documentation still points to Outseta and Memberstack as its named replacement partners. If a site still shows old User Accounts pages or login links, treat the CSV export and the 301-redirect setup above as immediate priorities, not optional cleanup.