Webflow Website

Two kinds of plan are easy to confuse. A site plan pays for hosting one published site on a custom domain, and it is what the Pricing section lists: Basic for a simple site with static pages, Premium once you need the CMS for a blog, team pages, or any collection-driven content. A workspace plan pays for the people building sites, their seats, and features such as code export, and it is billed separately. A freelancer or small team building one company site often needs only a site plan; an agency managing many client sites mainly pays for the workspace.

Yes, that is what Webflow's Editor is for. Content editors work on the live page and in CMS collections, changing text, images, and blog posts, but they can't move elements or edit styles, which stay in the Designer. The usual setup is a designer who builds layouts and CMS templates once, and a marketing team that publishes content through the Editor from then on. The one habit to build: model repeatable content (posts, case studies, job openings) as CMS collections, not hand-built static pages, so editors can add entries without asking the designer.

Partly. Code export produces the site's HTML, CSS, JavaScript, and assets, which you can host anywhere, but it is a static snapshot: CMS collection pages export only as templates without their content, forms stop working without a new form backend, and ecommerce doesn't export at all. CMS content comes out separately as CSV files per collection. For a mostly static marketing site, moving is a real option; for a CMS-heavy site, plan on rebuilding the content layer in the new platform, which is the lock-in the Cons section refers to.

Webflow trades speed of setup for control. Wix and Squarespace start from templates and hide the underlying layout model, so a non-designer can launch in an afternoon, and both bundle more business features (built-in analytics, email marketing, bookings). Webflow exposes the actual CSS layout system, which means a steeper learning curve but full control over responsive design, interactions, and clean output code. Pick Webflow when a designer builds the site and design quality is the priority; pick Wix or Squarespace when the owner builds it alone and wants the most done out of the box.

For a small catalog, yes: products, cart, and checkout are designed in Webflow, with Stripe processing payments, so the shop matches the rest of the site exactly. Webflow's ecommerce plans cap the number of items, though, and there is no app ecosystem for inventory tools, shipping integrations, or subscriptions of the kind Shopify offers. A brand selling a handful of products alongside a design-led marketing site fits well here. A store where the catalog, fulfillment, and sales channels are the business is usually better served by the Shopify Store stack, with Webflow kept for the marketing site if its design matters.