Creating a website from scratch can be a daunting task. That's why CSS frameworks exist: they provide a solid starting point, a foundation on which to build, with a set of pre-created CSS classes that avoid reinventing the wheel with each new project (and wasting hours configuring that foundation).
Historically, Client-First is the reference framework for Webflow. Developed by Finsweet, it is designed to be ultra-intuitive, accessible to beginners and, in theory, even to clients (hence the name). It has enabled many developers (including us at Digidop) to structure their projects efficiently, thanks to its clear methodology and ease of use.
However, the Webflow framework landscape has changed since then, and new alternatives have emerged with a host of new features and optimizations. Chief among them is Lumos. Developed by Timothy Ricks, this framework stands out for its power and flexibility. Although more technical and less accessible to customers, Lumos may well be better aligned with today's project challenges.
In this article, we compare Client-First and Lumos, exploring the advantages and disadvantages of each. The aim: to determine which framework is best suited to the needs of 2025, taking into account our experience, as well as Webflow and market developments.
Client-First vs Lumos comparison
Client-First and Lumos each have their own advantages and disadvantages. In this section, we'll explore the essential aspects that influence the choice of a Webflow framework and try to better understand which framework is best suited to your specific needs.
We'll be looking at several key criteria: ease of use, flexibility, scalability and performance. These elements will enable us to assess how each framework can fit into your workflow and meet your project requirements.
1. Ease of use
Client-First
When it comes to ease of use, Client-First immediately springs to mind. Designed to be accessible and ultra-intuitive, the framework is distinguished by its highly descriptive class names, which make clear the role of each element.
text-align-centermax-width-largemargin-bottommargin-medium
These classes are all very explicit about the styles they apply. This clarity is particularly useful for beginners and more technical customers who would like to be able to intervene in Designer.
Lumos
In comparison, Lumos has a steeper learning curve.
Class names are sometimes less explicit (which is often criticized, even though it has in fact evolved a lot since its first version towards a class naming convention quite similar to Client-First).
The system of utility classes is much more extensive, the variable system is very well developed in the use of the framework, it uses Variable Modes, comes with a whole set of components... Many additional features that make learning it more complex.
However, once you've mastered the framework, its heavy reliance on variables and its comprehensive system of utility classes facilitate global modifications, making it more efficient to use over the long term.
The easiest-to-use framework
In terms of ease of use, Client-First is the clear winner. It can be learned and mastered relatively quickly, while Lumos will be more demanding and challenging. For less experienced developers or those less at ease with CSS, or for customers with a technical profile who would like to get their hands into the code of their site, Client-First remains the more accessible choice.
2. Flexibility
Client-First
As mentioned above, Client-First is distinguished by its simplicity, which is also reflected in the framework's flexibility. It's quite effective for simple designs, but quickly comes up against certain limits when the design demands more freedom.
The framework offers a relatively complete set of utility classes that cover a good proportion of styling needs, but has certain shortcomings, notably in the management of page layouts, which systematically require the creation of custom classes.
Lumos
Lumos, on the other hand, is renowned for its advanced customization capabilities.
Its system of utility classes is much more robust, particularly for page layouts. The framework's utility class system offers a variety of classes covering all Grid and Flexbox layout needs, enabling the creation of complex designs without the need for custom classes.
Also, its comprehensive and intelligent use of Variable Modes gives great flexibility in many respects. Color themes, for example, can be easily modified at page or section level, thanks to simple utility classes taking advantage of Variable Modes.
The most flexible framework
In terms of flexibility, Lumos surpasses Client-First. Once mastered, the framework makes it easy to create complex designs without having to resort to custom classes. Its more robust utility class system, more developed variable system and use of Variable Modes make it clearly the more flexible choice.
3. Scalability
Client-First
Client-First is designed to be accessible and easy to use, making it a good choice for reasonably sized projects. However, as projects become more complex, the management of numerous custom classes can become difficult to maintain.
Client-First's scalability is therefore limited by the multiplication of custom classes and the absence of a global variable system, making it more difficult to maintain overall site consistency for large-scale projects or those requiring frequent updates.
Lumos
Lumos is more optimized for large-scale projects, thanks to its component-based approach and variable system.
Each component can be updated independently, while relying on the system of utility classes and variables, thus optimizing project consistency while avoiding the risk of a change in one area impacting the whole site.
The extensive use of global variables makes it easy to perform site-wide updates, which is crucial for scalability. This approach ensures that a project remains consistent and flexible, even with numerous pages and frequent updates.
The most scalable framework
In terms of scalability, Lumos is the most robust choice. Its ability to handle large-scale, complex sites makes it the best option for developers working on ambitious projects.
4. Performance
Client-First
Client-First is balanced between performance and simplicity. It offers good overall performance thanks to its clear structure and relatively complete system of utility classes, but its approach of encouraging the creation of custom classes leads to a certain heaviness. The multiplication of classes can end up weighing down the CSS file and affecting overall site performance, especially for large projects.
The framework also encourages the addition of extra divs to manage spacing and add certain styles, which can complicate the HTML structure and make the site slower.
Lumos
Lumos, on the other hand, has a strong focus on performance optimization. By minimizing the need to use custom classes and relying on global variables, it makes projects highly efficient. Its approach also requires fewer nested divs and therefore encourages a cleaner structure.
The most performant framework
In terms of performance, Lumos is the obvious choice. By minimizing superfluous code, it enables developers concerned with the speed and efficiency of their sites to develop the most optimized solutions possible. That said, this approach requires more rigorous organization and a more advanced understanding of CSS.
Client-First remains effective for small and medium-sized projects, but can lead to code overload as the project grows.
Webflow frameworks comparison table
Which Webflow framework to choose in 2025
Disclaimer
This comparison is aimed primarily at developers wondering which Webflow framework to choose for their projects. It aims to provide detailed information on the advantages of Client-First and Lumos, to help them make an informed choice.
Customers may also find this comparison useful in understanding the differences between the two frameworks. However, it's important to note that the complexity of a framework only impacts the developer. So, even if Lumos is more technical, the final user experience will not be affected for a customer, and may even benefit from the framework's advantages in terms of flexibility.
Evolution of the Webflow landscape
Client-First has long been the reference framework for many Webflow developers, including us at Digidop. Its simplicity and intuitive approach have enabled thousands of developers to create well-structured, fairly easy-to-maintain websites. However, with the emergence of new alternatives and the evolution of Webflow, the choice of framework is no longer as obvious as it once was.
Since Client-First's inception, Webflow has developed many new functionalities, notably around the CMS and components, enabling customers to upgrade their website with increasing ease and without the need for any technical intervention.
These advances call into question the more traditional Client-First approach, which can encourage customers to intervene directly in the code. While this approach may have its advantages, it also entails risks, notably that of unintentionally modifying global classes and thus disrupting the integrity of the site, or that of accumulating custom classes for the sake of convenience and thus ultimately impacting overall performance.
Today, more and more customers require more robust and scalable solutions, capable of adapting quickly to changes without compromising site performance or consistency. These developments raise the question of whether Client-First remains the optimal choice, or whether alternatives such as Lumos might not be better suited to today's challenges.
Choosing the right framework for your needs
The choice between Client-First and Lumos depends on specific project requirements and the developer's level of expertise. Here are a few recommendations to help you make the best choice:
For beginner to intermediate developers and small to medium-sized projects
Client-First is particularly well suited to small and medium-sized projects, where simplicity and speed of development are paramount. The framework is ideal for developers looking to familiarize themselves with Webflow, or for those less at ease with CSS. Its intuitive structure and descriptive classes make it easy to get to grips with and quickly develop well-structured websites. Its clear methodology also makes it an excellent starting point for new Webflow users.
For experienced developers and complex, large-scale projects
Lumos is ideal for intermediate and advanced developers, or projects with high scalability and performance requirements. Lumos enables the creation of complex, high-performance websites, capable of adapting to evolving customer needs. Its steep learning curve is offset by increased power and flexibility, ideal for the most ambitious projects.
Why we're exploring Lumos at Digidop
At Digidop, we've always been loyal ambassadors of Client-First and appreciated its simplicity and accessibility for novice developers and customers alike. However, as the needs of our customers and Webflow evolved, we began exploring Lumos for a number of reasons.
Alignment with our customers' challenges
Our customers, often marketing teams, are looking for solutions that enable them to manage their websites without any technical intervention. They need sites capable of scaling, while allowing them to be autonomous to accelerate their time-to-market. Lumos meets these requirements perfectly, thanks to its flexibility, scalability and advanced functionalities.
Performance and optimization
Most of our customers' projects require optimum performance, not least because of the SEO challenges they face. Lumos makes it possible to create lighter, higher-performing websites, which is crucial for improving user experience and SEO.
Updates and innovation
At Digidop, innovation is also very important in our approach. We are constantly seeking to evolve and offer the best solutions to our customers. Lumos meets this challenge through its ability to adapt quickly to Webflow's evolutions. For example, the framework recently integrated Variable Modes shortly after their release, offering some very useful new features. Conversely, Client-First has not benefited from any updates since January 2024, which limits its potential in the face of new market requirements, even if the solution remains viable.
In exploring Lumos, we aim to offer our customers more robust, high-performance solutions, capable of meeting their specific needs. Although Client-First remains a solid option for most projects, Lumos is increasingly establishing itself as the best choice for the most complex and ambitious projects.
Conclusion
In 2025, the choice between Client-First and Lumos will largely depend on the specific needs of your projects.
Client-First remains an effective solution for projects requiring fast, intuitive implementation. It is particularly suitable for small and medium-sized projects, or for customers with a technical profile who wish to intervene directly in the Designer. Its simplicity and clarity make it an invaluable tool for agile and accessible development, and also ideal for more novice developers.
On the other hand, Lumos stands out for its flexibility, scalability and optimal performance, making it a wise choice for more complex and ambitious projects. It's ideal for more experienced developers looking to take advantage of advanced functionality and manage large-scale websites. Lumos also meets the growing demands for performance and optimization, crucial for projects with high SEO stakes.
Ultimately, there's no single answer: the best framework is the one that best aligns with your goals and constraints. Whether you opt for the simplicity of Client-First or the power of Lumos, the important thing is to choose a tool that supports your vision and enables you to create high-performance websites tailored to your needs.
.jpg)
