Webflow pricing and features: Site vs Workspace

Evaluate design and content together

A service site built from fixed pages differs from a publication with a growing library of articles or case studies. For the latter, define the content fields and the person who will maintain them before polishing the homepage. Evaluate list and detail pages, long headings and real media. The purpose is a repeatable publishing process, not only an attractive first screen.

Separate the subscription layers

A Site plan applies to the individual website, while Workspace plans relate to the building environment and collaboration. Do not assume that every project needs a paid version of both. Write down how many sites will be published, who needs editing access and which features require a specific plan. This helps prevent a team subscription from being mistaken for production hosting.

Match the plan to growth

The Basic Site amount shown here is an annual-billed monthly equivalent for a site without CMS needs. A publication should inspect a CMS-capable alternative, including capacity and any relevant add-ons. Estimate localization and bandwidth requirements separately rather than assuming they are all included. A realistic quotation should cover the next stage of the site as well as the smallest launch version.

Understand export limitations

Eligible Workspace plans can export site code, but a Site plan alone does not grant that capability. Exported files are not a complete portable copy of hosted CMS, ecommerce, form processing or localization functionality. If portability is a requirement, identify what can be exported and what would need rebuilding. Treat that migration work as a purchasing consideration before the content library grows.

Check the current Site lineup

The verified current table displays Basic at USD 15 monthly equivalent annually and a CMS-capable Premium offer at USD 25. Separate that current lineup from legacy contract terms. Check the actual purchase screen and distinguish published-site requirements from the working environment and match each contributor to the access their work requires.

Test the actual editorial model

Have the operator add an item with categories, image descriptions, related material and pre-publication review. Include a long headline and missing optional fields in sample data to expose assumptions hidden by perfect design content. Successful completion by the eventual editor is a stronger handoff test than watching the designer perform the steps.

Preserve a migration specification

Retain CMS field definitions, public URLs, asset-rights information and form destinations for a possible move. Exporting visual code should not be treated as transferring CMS or enquiry operations unchanged. Identifying the parts requiring a rebuild also makes a future agency change easier to estimate.

• Review alternatives and migration scope