Webflow Class Naming: Client-First vs BEM vs Lumos

Webflow class naming comes down to three conventions, and the choice is mostly about who will touch the Designer after you. Each one makes the same four choices differently: how an element class is separated from its component, how utility classes are marked, how a variant is written, and how deep a class stack may go.
-
Client-First (by Finsweet): custom classes carry an underscore, utility classes use dashes only, variants start with
is-. Written so anyone can read a class name. -
BEM (Block, Element, Modifier):
block__elementwith a double underscore, modifiers after a single underscore or two dashes. Written for developers and portable to any codebase. -
Lumos (by Timothy Ricks): every element gets an underscore custom class first, utilities start with
u-, variants start withis-. Written for builders who already know Webflow, HTML, CSS and JavaScript well.
My short answer: pick Client-First when a client or marketer will open the Designer after launch, Lumos when a senior team owns the site long term, and BEM when the same class names must also live in hand-written code. The rest of this post shows the literal rules, the same component named three ways, and what breaks when a site mixes them.
What are the rules of Client-First, BEM and Lumos class naming?
Client-First joins a component and its element with one underscore (header_content), BEM with a double underscore (menu__item), and Lumos with underscores between every word plus _wrap to start a component. Client-First and Lumos write variants as is- combo classes, while BEM writes them as _mod or --mod. The table puts the four documented rules side by side, plus two rows of context on audience and tooling.
| Rule | Client-First | BEM | Lumos |
|---|---|---|---|
| Element or custom class | Underscore in the name: header_content | Double underscore between block and element: menu__item | Underscores between every word: type_variation_element, with _wrap marking the start of a component |
| Utility classes | No underscore, dashes only: text-weight-bold | Not part of the naming rules (blocks, elements and modifiers only) | Start with u-, dashes only, always stacked on a custom class |
| Variant or modifier | Combo class with the is- prefix: is-brand | Single underscore (menu_visible) or the Two Dashes style (--) | Combo class with the is- prefix, created on a component class, not on utilities |
| Depth limit | "Don't deep stack" is a universal rule | No elements of elements (block__elem1__elem2 is not allowed) | Never more than 3 underscores; generally no more than 4 utility classes |
| Context: who it is written for | "A Webflow developer, client, or anyone" | The developer reading the code | Builders with a solid grasp of Webflow, HTML, CSS and JavaScript |
| Context: extra tooling | Finsweet Extension for class Folders | None | Lumos Chrome Extension and the Lumos Starter file |
Client-First states it plainly in its classes strategy: "In Client-First, custom classes use an underscore in the class name" and "Utility classes will not use an underscore in the class name." The Lumos class naming docs say a custom class "Must never have more than 3 underscores" and "Must always be the first class applied to an element." The BEM methodology gives the full pattern as block-name__elem-name_mod-name_mod-val.
What changed in Client-First V3 for class naming?
Client-First V3, released on 23 October 2026 according to the Client-First changelog, keeps its class rules (underscores for custom classes, dashes only for utilities, is- for variants) but rebuilds the starter project on Webflow Variables and flattens the section structure. If you are reading an older comparison that describes Client-First without variables, it predates V3.
-
Flatter core structure. The core structure strategy now lists
page-wrapper,main-wrapper,section_[section-identifier]andcontainer-largeas the default, with global and section padding "applied directly to section_[section-identifier] through variables." -
Padding layers became optional.
padding-globalandpadding-section-[size]"remain available for the alternative structure," so a V2-era build that still uses them is not wrong, just older. -
Component naming added. The new component naming page names Webflow Components as "Group Name / Component Identifier", for example
Card / Blog Post, and notes that "Webflow does not create a group from the slash." - Updated utilities. The changelog lists new text style, inherit, grid, gap and display utility classes and a "custom class + utility class strategy" in Classes strategy 2.
In practice, when I inherit a Client-First site I check which version it was started on before renaming anything, because a padding-global layer inside every section is a V2 pattern, not a mistake to clean up.
What does the same Webflow component look like in each naming system?
In Client-First a pricing card is pricing_card with a pricing_card-title; in BEM it is pricing-card with pricing-card__title; in Lumos it is pricing_card_wrap with pricing_card_title. The class names below are my application of each convention's published rules to one card; none of the three docs uses this exact example.
| Layer of the card | Client-First | BEM | Lumos |
|---|---|---|---|
| Card wrapper | pricing_card | pricing-card | pricing_card_wrap |
| Card title | pricing_card-title | pricing-card__title | pricing_card_title |
| Featured plan variant | pricing_card is-featured | pricing-card pricing-card_featured | pricing_card_wrap is-featured |
| Title typography from the global system | text-weight-bold utility | None, styled on the element | u-text-style-h3 utility |
Notice where the systems agree. Client-First and Lumos both use an underscore to group a component's classes and both write variants as is- combo classes. BEM is the odd one out inside Webflow: its modifier is a second full class, which the Designer treats as a combo class on top of the block, so a BEM build in Webflow behaves much like the other two in the Style selectors panel even though the names look different.
Which Webflow class naming system should you pick for your project?
Pick Client-First when a client or marketer will open the Webflow Designer after launch, Lumos when a senior team owns the site long term, and BEM when class names must match hand-written CSS or JavaScript; I decide by situation rather than by preference. This is the table I use on my own projects; it is my recommendation, not a rule from any of the three docs.
| Your situation | Pick | Why |
|---|---|---|
| A client or marketer will open the Designer after launch | Client-First | Class names describe what they do in plain words, which is the system's stated goal |
| Agency team with mixed seniority and a shared starter file | Client-First | Shorter learning curve than Lumos, whose docs list Webflow, HTML, CSS and JavaScript as prerequisites |
| Senior team that owns the site for years and leans on variables | Lumos | Every element labelled with a custom class, utilities for layout and type, rules written for experienced builders |
| Class names must match hand-written CSS or JavaScript elsewhere | BEM | The same names work in any codebase, not only in Webflow |
| White label build for an agency that already has a convention | The agency's convention | The agency's team maintains the site after you, so your classes must read like theirs |
| Inherited site that is already consistent in one system | Keep that system | A rename costs hours and adds nothing the visitor sees |
| Inherited site that mixes systems | The dominant system, renamed as you touch each component | Bounded effort, and the site converges instead of forking further |
In my projects the deciding question is almost always the first row. Client-First's docs say "A Webflow developer, client, or anyone should understand what the class is doing based on the class name, even if they've never heard of Client-First before." Lumos makes the opposite trade: its getting started page says learning it "will require a solid understanding of how Webflow works, along with the underlying HTML, CSS and Javascript." Neither is better in the abstract. On white label projects the agency's existing convention wins by default, which is one of the working rules in my white label Webflow workflow. If your agency also wireframes in Relume, read my Relume review before choosing, since that tool shapes the class list you start from.
What goes wrong when Webflow class naming breaks down?
Webflow class naming breaks down in six predictable ways: mixed conventions, deep stacking, styled stacks of global classes, cleanup deleting unused utilities, Folders only one person can see, and renames that miss hand-written code. Each one costs build or maintenance time later rather than on launch day.
-
Mixed conventions on one site. A
hero_title, ahero__titleand aheroTitleon the same site mean nobody can predict what a class does or where its styles come from. Consequence: every change starts with detective work. This is the first thing I look for when I audit an inherited Webflow site. - Deep stacking. Client-First lists the reason it bans long class stacks: "We are unable to reorder them or properly manage them inside Designer. If we need to change or remove classes in the stacked list, we have to remove all classes from the list" first. Consequence: a one-property change becomes a multi-step rebuild of the stack, and Client-First notes the problem "becomes extreme when making edits at lower breakpoint levels."
- Styling a stack of global classes. Client-First warns that adding styles to stacked global classes "will create a new class (a combo class) to the CSS of the project." Consequence: a supposedly global utility quietly forks, and the next site-wide spacing change misses that element.
- Cleanup deleting an unused utility. Webflow's Style selectors lesson says "Only selectors that aren't applied to any elements will appear in the cleanup list." A utility you created but have not used yet is on that list. Lumos's fix is to "Add the new class inside the styleguide page to prevent removal during class cleanup." Consequence without it: the utility disappears and someone recreates it under a slightly different name.
- Folders only one person can see. Client-First Folders come from the underscore naming plus the Finsweet Extension, which "automatically generates a virtual folder structure inside Designer," according to the Folders docs. Consequence: a teammate without the extension sees the plain class list, so the folder names still have to make sense as ordinary class names.
- A rename that misses hand-written code. Webflow documents a rename as updating the name "everywhere that class is used" on elements; in my builds, a class name typed into custom code, a Code Embed or a script is plain text that the rename does not touch. Consequence: the site looks fine in the Designer while a custom CSS rule or a JavaScript selector silently stops matching on the live site.
How do you change the class naming system on an existing Webflow site?
You change the class naming system on an existing Webflow site one component at a time, by renaming each base class in the Style selectors panel and then clearing out what is left unused. Webflow's own Style selectors lesson confirms why this is safe inside the Designer: "Renaming a class doesn't change its styles or remove it from any elements, it just updates the name everywhere that class is used."
- Search site and page custom code, Code Embeds and any scripts for the old class name before renaming, and update those by hand.
- Start with the components you are already editing for the current job, not a site-wide rename sprint.
-
Rename the base class first, then its children, then any
is-combo classes on top. - Move utilities you want to keep onto a styleguide page before running cleanup.
- Run the cleanup from the broom icon only after the rename, and read the list before confirming.
- If the classes belong to Webflow components, check them against your component and design system setup so instances and class names stay in step.
What I see agencies get wrong is switching conventions in the middle of a build because a new developer prefers a different system. The site ends up with two half-systems, which is worse than either one done consistently. If a switch is genuinely worth it, schedule it as its own task and add a class-naming check to your Webflow QA checklist so the result holds.
Who can review your Webflow class naming?
If you are about to start a build or have inherited a site whose class list has drifted, book a 15-minute call with me. Share your class list or a read-only link and I will tell you which convention fits your team and handoff, and whether a rename is worth the hours or should wait.
FAQ
Is Client-First made by Webflow?
Client-First is not made by Webflow. Client-First is a class naming system published by Finsweet, documented on finsweet.com, and its optional Folders view depends on the Finsweet Extension rather than on a native Webflow feature.
Can you use BEM class names in Webflow?
BEM class names work in Webflow because they are ordinary class names: block__element for elements and a single underscore or two dashes for modifiers. In the Designer a BEM modifier added as a second class becomes a combo class on top of the block class.
What does the is- prefix mean in a Webflow class name?
The is- prefix marks a combo class that modifies the class it sits on, such as is-featured on a pricing card. Client-First and Lumos both use is- for variants, and Lumos says the is- class should sit on a component class, not on a utility.
How many utility classes should be stacked on one element in Lumos?
Lumos generally allows no more than 4 utility classes on one element, and every utility must sit on top of a custom class. The Lumos docs also cap custom class names at 3 underscores.
Does renaming a class in Webflow update custom code too?
Renaming a class in Webflow keeps the class's styles and updates the name on every element that uses it, according to Webflow University. In practice, class names typed into custom code, Code Embeds or scripts are plain text, so search for the old name and update those references by hand.
Should every class on an inherited Webflow site be renamed to one system?
An inherited Webflow site rarely needs a full rename. If the site is already consistent in one system, keep it; if it mixes systems, rename to the dominant one component by component as you work on each part.
Agency with more Webflow work than developers?
I build white-label Webflow sites for agencies with an AI-accelerated, senior-reviewed workflow. Book a 15-minute fit call for a straight answer on scope, timeline and cost.
Need a Webflow site that your team can actually run?
I build, migrate and optimize Webflow sites for companies: fast, ready for Google and AI search, and easy to update. Book a 15-minute call for a straight answer on scope, timeline and budget.



