The essentials · 30-second read
Finsweet builds Webflow tools. Client-First and Attributes are free and open source. Components: free on webflow.io, from $19 a site for life. Finsweet+ costs $199 a year.
- Finsweet is a Webflow agency and product studio. Its best-known products are Client-First, a free style system for naming and structuring Webflow projects, and Attributes, a free open source library of 33 no-code solutions.
- Finsweet Components add JavaScript-powered components built visually in Webflow: free on a webflow.io domain, then from $19 per site for life, $59 for all components on one site, or agency plans from $29 a month billed yearly.
- Other products: Consent Pro for cookie consent (from $19), Wized for apps on Webflow, CMS Bridge, a free Chrome extension, and Finsweet+ membership at $199 a year or $59 a quarter.
- Our verdict: Client-First is a solid convention for any Webflow team, and our former Webflow site followed it; Attributes and Components are useful when you stay on Webflow, less so if you plan to leave it.
Summarize this page with AI
If you have opened a Webflow project built by a serious agency, you have probably met Finsweet without knowing it: class names like section_hero or padding-global come from its Client-First convention, and attributes starting with fs- come from its Attributes library. Finsweet is both a Webflow agency and the studio behind some of the most used tools in that ecosystem. This guide explains what each Finsweet product does, which ones are free, what the paid ones cost, which alternatives exist and how relevant all this is in 2026, when many teams are weighing Webflow against custom code.
01What is Finsweet?
Finsweet is a company built entirely around Webflow. It sells agency services (design, strategy, development and long-term support for Webflow sites) and publishes products that extend Webflow. The official site is finsweet.com, where the home page now presents the agency as a builder of websites and web apps for B2B and enterprise companies, next to the product menu. The Attributes code is public on GitHub.

The product family in November 2026:
- Client-First: the Webflow build system, a free set of rules for naming classes and structuring projects.
- Attributes: free, open source solutions added to Webflow elements through custom attributes.
- Components: JavaScript-powered components (sliders, tabs, feeds, marquees) built visually in Webflow through an app.
- Consent Pro: a consent management platform for GDPR cookie banners, which replaced the old Cookie Consent component.
- Wized: a tool for building dynamic web apps on top of Webflow, covered in our Wized page.
- CMS Bridge: a product to connect external data to the Webflow CMS.
- Finsweet Extension: a free Chrome extension for Webflow builders.
- Finsweet+: a paid membership with support, discounts and community access.
02Client-First, Attributes and Components explained
Client-First is a set of guidelines and strategies for building Webflow websites, in Finsweet's words. It defines how to name classes (custom classes with an underscore that groups them into folders, such as team-list_headshot-wrapper, and utility classes made only of hyphens, such as text-size-large), how to structure a page (page-wrapper, main-wrapper, sections, padding-global, containers) and how to use rem units. Version 3 is rebuilt around Webflow Variables, split into Base, Theme, Typography, Layout and Sizes collections, uses the native Section element and keeps one class per spacing decision. Finsweet provides a cloneable starter project, a Figma kit and a launch checklist.
Attributes is the library many Webflow developers install first. You add one script tag, set named attributes on Webflow elements, and a feature appears: CMS filters, load more, sorting, nested collections beyond Webflow's limits, a table of contents built from a rich text block, accessible modals and accordions. Version 2 is current, and version 1 has been discontinued.
Components goes a step further: a Webflow app lets you build JavaScript components visually, without managing scripts or libraries. The catalogue includes Favorites, Auto Tabs, YouTube and Instagram feeds, Slider, Marquee, Table and Number Count.
03How we see Finsweet at BeBranded
We have been a Webflow Certified Partner since 2023, and our former Webflow site, online until our move to custom code on 9 November 2026, followed Finsweet's Client-First convention strictly: page structure, class names, utility classes. Our own site now runs on Next.js and Payload, and Webflow is no longer our main offer, but we still build and maintain Webflow sites for clients. Here is how we use that experience when advising them.
- We recommend Client-First to any team that builds in Webflow with more than one person. A shared naming convention makes a project readable by the next developer, and by the client.
- We recommend Attributes when a Webflow site needs filters, sorting or richer CMS lists and the team prefers a documented, free solution to custom JavaScript.
- We weigh Components and Consent Pro case by case, comparing the licence cost with a native Webflow feature or a few lines of maintained code.
- We advise against stacking many scripts on one site: each solution adds a dependency to maintain and test.
- We suggest leaving the toolkit behind when a project outgrows Webflow; our article Is Webflow still relevant in 2026? explains when that happens.
Our Webflow website creation and design system services build on Client-First when the client stays on Webflow.
04Key features
- Client-First style system: class naming, folders, utility classes, rem units and a page structure shared by many Webflow agencies.
- Client-First v3: Webflow Variables in five collections, native Section element, one class per spacing decision.
- Attributes v2: 33 open source solutions, including List Filter, List Load, List Sort, List Nest, List Combine and List Slider.
- UI and form solutions: Modal, Accordion, Combo Box, Range Slider, Star Rating, Input Counter, Custom Form Select and Form Submit.
- Content helpers: Table of Contents, Read Time, Code Highlight, Social Share, Copy to Clipboard and Inject Elements.
- Components: visual Webflow app for sliders, tabs, feeds, favourites and marquees, with free Table, Number Count and Accessibility components.
- Consent Pro: cookie consent management for GDPR, from $19.
- Chrome extension: free tools for Webflow builders.
- Education: documentation, tutorials, live streams and a Slack community for Finsweet+ members.
05Use cases
Starting a Webflow project on a shared convention
An agency or an in-house team starts a new Webflow site and wants any developer to understand it in a year. Starting from the Client-First cloneable gives a ready page structure, utility classes and variables. What to know: the convention only works if everyone applies it; agree on the rules before the first page, and document project-specific classes. Our guide to mastering Webflow development with Client-First goes deeper.
A filterable directory or resource library
A company wants a list of case studies, jobs or partners that visitors can filter by category and search. Attributes List Filter, List Load and List Sort deliver that on a Webflow CMS collection without writing the logic. What to know: Webflow limits how many items a collection list loads, and filtering happens in the browser, so very large catalogues need a different architecture.
Richer blog articles
Content teams want a table of contents, a reading time and code highlighting in articles written in Webflow's rich text. Attributes provides all three. What to know: test the result on mobile and check that the table of contents follows a clean heading structure.
Agencies shipping the same component on many sites
An agency reuses sliders, auto tabs or social feeds across client projects. Finsweet Components agency plans license a number of sites per year instead of paying per site. What to know: count the sites you really publish in a year before choosing a plan, and check what happens to each component if the client leaves your agency.
Cookie consent on a European Webflow site
A Webflow site that loads analytics or advertising tags needs a consent banner. Consent Pro is Finsweet's dedicated product for that, after the old Cookie Consent component was retired. What to know: a banner is only part of compliance; tags must really wait for consent, which you should test.
06Integrations
Finsweet's tools live inside Webflow: Attributes through a script and custom attributes, Components through a Webflow app, Client-First through classes and variables. Client-First is also the convention used by Relume for its Webflow export, and Finsweet provides a Figma kit so designers in Figma can follow the same structure. Wized connects Webflow front ends to back ends and APIs, and CMS Bridge brings external data into the Webflow CMS. For memberships, Finsweet's tools are often combined with Memberstack; for animations, with GSAP, the animation library now owned by Webflow.
07Finsweet pricing in 2026
Prices checked on finsweet.com on 18 November 2026: the Components pricing page (finsweet.com/components/pricing), the Finsweet+ page and the home page. Prices are shown with a "$" sign and no currency code; tax is not mentioned. Client-First, Attributes and the Chrome extension are free.
| Product | ||
|---|---|---|
| Client-First | Price Free | What you get Style system, cloneable starter, Figma kit, documentation |
| Attributes | Price Free, open source | What you get 33 no-code solutions for Webflow |
| Finsweet Extension | Price Free | What you get Chrome extension for Webflow builders |
| Components, single site | Price $19 to $39 per component, $59 for all, one-time per site for life | What you get Table and Number Count free; free testing on webflow.io |
| Components, agency plans | Price Basic $29, Lite $49, Pro $79, Unlimited $129 a month, billed yearly | What you get 12, 24, 48 or unlimited sites a year, all components |
| Consent Pro | Price From $19 | What you get Cookie consent management |
| Finsweet+ | Price $199 a year or $59 a quarter | What you get 10% off Finsweet products, human support for Attributes, Slack community, events |
Agency plans total $348, $588, $948 and $1,548 a year. The Components page also shows an older subscription for all components at $12 a month, $10 a month yearly or $199 for life per site; its FAQ says the $10 price applies to legacy subscribers. Finsweet agency services are quoted on request.
Is Finsweet free? The core is. Client-First, Attributes and the Chrome extension cost nothing, and you can test every Finsweet Component on a webflow.io staging domain. You pay when you publish paid components on a custom domain, use Consent Pro, or join Finsweet+ for human support and discounts.
08Pros and cons
Advantages
- Client-First gives Webflow teams a widely shared, documented naming convention.
- Attributes solves common Webflow limits (filters, nesting, load more) for free.
- No JavaScript to write for many features clients ask for.
- Tools built by heavy Webflow users, with documentation and tutorials.
- One-time per-site licences for Components, plus agency plans.
- A large community, so many Webflow developers already know these tools.
Drawbacks
- Everything depends on Webflow: none of it helps if you move to another platform.
- Each Attributes solution or component is a third-party script you do not control.
- Several scripts on one page add weight; performance needs checking.
- Client-First is verbose at first and needs discipline from the whole team.
- Version changes (Attributes v1 discontinued, Client-First v3) can require migration work.
- Product pricing is spread across several pages and models (one-time, yearly, membership).
09Our verdict
Who it's for
- Webflow agencies and freelancers who want projects any developer can take over.
- In-house marketing teams that maintain a Webflow site with a partner.
- Webflow builders who need filters, sliders or richer CMS lists without custom code.
- Teams that need a cookie consent solution designed for Webflow.
Who it's not for
- Teams that do not use Webflow, or plan to leave it soon.
- Projects with very large catalogues or complex search, where a dedicated search such as Algolia or custom code fits better.
- Web applications with accounts and business logic, better built as a web app.
- Teams that cannot maintain third-party scripts over time.
10Finsweet alternatives
| Tool or approach | ||
|---|---|---|
| Relume | Replaces Components, page sections | Notes AI sitemaps, wireframes and 1,000+ components, Webflow export in Client-First |
| Native Webflow features | Replaces Some Attributes | Notes Webflow has added native features over time; check before adding a script |
| Memberstack | Replaces Gated content and memberships | Notes Logins and payments on Webflow |
| Wized | Replaces Advanced app logic | Notes A Finsweet product for apps on Webflow |
| GSAP | Replaces Animated components | Notes Animation library, owned by Webflow |
| Algolia | Replaces Search and filtering at scale | Notes Hosted search engine |
| Custom code (Next.js and a headless CMS) | Replaces The whole Webflow toolkit | Notes Full control, needs developers |
Our rule: on Webflow, start with native features, then Attributes, then Components or custom code for what is left. Use Relume when the problem is structure and page sections rather than behaviour. If your list of workarounds keeps growing, look at our Webflow vs Payload comparison and our article on Webflow alternatives.
11Finsweet vs Relume
Finsweet and Relume are often compared because both make Webflow builds faster, but they solve different problems and work well together.
Finsweet is about how a site is built and what it can do. Client-First defines the naming and structure; Attributes and Components add behaviour such as filters, sliders and feeds. It does not design pages for you.
Relume is about what the site contains and how it looks at first. Its AI drafts a sitemap and wireframes from a brief, then assembles pages from a library of more than 1,000 components, which it exports to Webflow using Client-First classes, as well as to Figma and React. In 2026 it also hosts sites on custom domains.
A typical Webflow project can use Relume to agree on the structure and get a first build, Client-First to keep that build organised, and Attributes for the few features Webflow lacks. Our article Figma to Webflow: plugin or Client-First rebuild shows where each step fits.
12Getting started with Finsweet
- Read the Client-First documentation and clone the starter project before building your first page.
- Agree on project rules with the team: class names for each section, which utilities to use, how variables are named.
- Install the free Chrome extension to speed up everyday work in the Designer.
- Add Attributes one solution at a time, following the documentation exactly; a misconfigured attribute simply does nothing.
- Test Components on the webflow.io domain before buying a licence for the custom domain.
- Measure page speed after adding scripts, and remove what is not used.
- Document the choices for whoever maintains the site next. If you need help, our Webflow website creation team works in Client-First.
