A Webflow for landing pages Review for People Who Actually Build Things
Short version: Webflow is the best visual web development platform on the market if you need total design control without writing every line of code. But it is not for beginners, it is not cheap, and its recent focus on AI feels like a distraction. If you just need a simple portfolio, run away.
Full disclosure: some links below are affiliate links. I only recommend tools I’ve paid for and actually use.
I’ve been using Webflow for years, building sites for clients and for my own projects. I’ve paid them hundreds, possibly thousands, of dollars in subscription fees. I’ve celebrated its power and cursed its quirks. This isn’t a summary of their marketing page. This is a review from the trenches.
What’s Actually Worth Paying For in Webflow?
You don’t pay for Webflow to drag and drop pre-made blocks. You pay for three things that, when combined, let a single person do the work of a small agency.
AI Side Hustles
Practical setups for building real income streams with AI tools. No coding needed. 12 tested models with real numbers.
Get the Guide → $14
First, the Designer. This is the whole show. It’s not a page builder in the WordPress sense. It’s a visual interface for writing clean HTML and CSS. You work with divs, classes, flexbox, and grids. If you understand the fundamentals of how the web is structured, the Designer feels like a superpower. You can build virtually any layout you can imagine, and the code it produces is surprisingly clean. This is my concrete love: the moment you stop fighting it like it’s Squarespace and start thinking in terms of CSS properties, you can build things that are impossible with other builders.
Second, the CMS. Webflow’s Content Management System is incredibly flexible. You can define your own data structures, called Collections. Need a portfolio? Create a ‘Projects’ collection with fields for images, descriptions, and client names. Need a blog? That’s a collection. Team members? A directory? All collections. You then design a template for that collection item once, and Webflow generates a page for every single item. It’s a relational database for the visually-minded, and it’s the reason you can build real, data-driven websites instead of just static brochures.
Third, the Interactions Engine. This is what separates a Webflow site from a template. You can create complex, multi-step animations and interactions based on user actions like scrolling, clicking, and hovering. Want an element to fade in and move up as you scroll into view? Easy. Want a custom dropdown menu that animates with a slight bounce? A few clicks. Doing this with custom JavaScript would take hours; in Webflow, it can take minutes. It allows you to add that layer of polish that makes a site feel expensive and custom-built.
What Sucks About Webflow? (The Gripes)
It’s not all perfect. Far from it. My relationship with Webflow is complicated, and some of their decisions are genuinely frustrating.
The learning curve is a brick wall. Webflow’s marketing sometimes makes it sound like anyone can use it. This is false. If you don’t understand the CSS box model, positioning (static, relative, absolute), and how flexbox works, you will have a miserable time. You will be fighting the tool constantly. My concrete gripe is this: I once spent an hour trying to explain to a client over Zoom why they couldn’t just “drag the logo two inches to the right.” I had to explain that it lived inside a parent container that was using flexbox to distribute its children, and changing its position required changing the properties of the parent. Their eyes glazed over. Webflow creates a dependency on someone who understands it; it’s not a tool you can just hand over to a client for content updates unless the site is built very carefully.
The pricing is confusing and expensive. You’re paying twice. First, you pay for a Workspace plan, which lets you build projects. The free plan is okay for learning, but for any real work, you need the Core plan at $19/month (billed annually). Then, to put a site live on a custom domain, you have to pay *again* for a Site plan. These start at $14/month for a basic site with no CMS and go up to $39/month and beyond. A simple blog will run you $23/month. You are locked into their hosting if you want to use the CMS. There’s no exporting your CMS site and putting it on a cheaper server. This lock-in is their business model, and you need to be aware of it.
Feature bloat is becoming a problem. In the last couple of years, Webflow has added Memberships, Logic (their version of backend workflows), and now a suite of AI tools. These are big, flashy features, but the core Designer experience has seen more bugs and slowdowns. Sometimes styles don’t apply correctly, publishing hangs, or the whole interface just feels sluggish. The new AI features, which help generate copy or image alt-text, feel like a half-baked attempt to keep up with competitors like Framer AI rather than a deep integration that solves a real user problem. I’d rather they fix the bugs.
