If you build in Webflow seriously, you eventually adopt a framework — a system for naming classes and structuring styles so projects stay consistent, maintainable, and easy to hand off. Two dominate the Webflow world: Finsweet Client-First and Lumos, by Timothy Ricks. Both are excellent, and we've used both. At Everything Flow we standardized on Lumos. Here's an honest comparison, and why it wins for the way we build.

What the two have in common

Before the differences: both frameworks solve the same core problem. Raw Webflow class management gets messy fast — duplicate classes, inconsistent spacing, styles nobody can find. Client-First and Lumos both impose a naming convention and a structure so a site stays clean as it grows, and so any developer (or client) can pick it up. If you're using neither, adopting either one is a big step up.

Finsweet Client-First

Client-First is the most widely adopted Webflow framework, and for good reason.

Where it shines:

• Human-readable class names (heading-style-h2, padding-global, margin-bottom) that anyone can read at a glance.
• A massive community, thorough documentation, and the Finsweet Attributes ecosystem — CMS filtering, sliders, and more.
• Beginner-friendly and easy to hand off to clients or new team members.

Where it gets heavy:

• Elements often stack many utility classes, which gets verbose quickly.
• Spacing and type lean on fixed utility scales, so responsiveness still means managing breakpoints by hand.
• It's clear and consistent, but not fluid by default — scaling a design smoothly across screen sizes takes more manual work.

Lumos

Lumos takes the same discipline and pushes it toward a fully fluid, variable-driven system.

Where it shines:

• Breakpointless, fluid sizing. Lumos uses fluid (clamp-based) units, so type and spacing scale smoothly across every viewport — far fewer breakpoints to babysit.
• Variable- and token-driven. Spacing, typography, and color live in variables. Change a token once and it updates everywhere — a real design system, not scattered classes.
• Color themes built in, so light/dark or per-section theming is systematic rather than manual.
• Cleaner element stacks and faster iteration once the system is set up.

The trade-offs:

• A steeper learning curve — there's more system to understand up front.
• A smaller community than Finsweet, and more initial setup before you're moving fast.

Why Lumos scales better

The reason we land on Lumos comes down to how each behaves as a project grows:

• Fluid by default beats breakpoint-by-breakpoint. On a large site, manually tuning spacing and type at every breakpoint is where hours disappear. Lumos's fluid system removes most of that.
• Tokens make change cheap. Rebrand, adjust spacing rhythm, or shift the type scale by editing variables — not hunting through hundreds of classes.
• Consistency at scale. Because everything resolves from the same variables, a 5-page site and a 50-page site stay visually coherent.
• Cleaner handoff between developers once the team knows the system — far less class soup to wade through.

Finsweet wins on approachability and ecosystem. Lumos wins on fluid responsiveness and scalable consistency. For production sites that need to grow, that second set matters more.

How to use Lumos to scale your website

• Set up your tokens first — spacing scale, type scale, and color variables — before building components.
• Lean on fluid sizing so a single build holds up from mobile to ultrawide without breakpoint micro-management.
• Reuse utility classes and components instead of one-off styles, so the system stays the source of truth.
• Feed the convention to AI. If you use AI to generate layouts in Webflow, give it the Lumos skill or style guide so it names classes the Lumos way instead of inventing one-off classes — more on that in our guide to leveraging AI to build your Webflow website.

How Everything Flow builds with Lumos

Internally, Lumos is our standard. Every production site we build runs on the Lumos Style Guide — it's how we keep large, content-heavy projects consistent and fast to update. A few we've built this way include Vecton, SISA, and Armory — the last of which we also wrote up as a performance case study.

If you want a Webflow site built on a framework that scales cleanly — fluid, token-driven, and easy to evolve — reach out to us.