Webflow vs Framer: build a site the client can own

Use the same client site

Assume one custom-domain marketing site with 20 static pages and 500 CMS records across three collections. It has two languages in total, a form integration, three collaborators whose exact builder and content-editor roles are to be decided. The client should control the site and billing after handoff, while the agency retains only agreed maintenance access.

These are planning inputs, not a tested configuration or a quote. Check the exact CMS fields, staging, traffic, content permissions and form receiver. A designer may need broader access than a content editor, and the number of billable seats depends on who owns each workspace.

Count collections and items separately

Webflow describes Premium with 40 CMS collections and 20,000 items; Basic does not provide the required CMS capacity. Framer lists Basic with two collections and 1,000 items, while Pro lists ten collections and 2,500 items. Three collections therefore exceed the published Basic collection count even though 500 items fit its item count.

Both Premium and Pro have room for the hypothetical counts, subject to the actual field and feature requirements. Framer lists Pro add-ons for further items and collections. Webflow’s pricing update describes different migration timing for existing customers; verify what the actual account can buy and when its limits change.

Build a complete cost worksheet

Webflow lists Premium at $25 per month equivalent billed yearly or $39 month-to-month. Framer lists Pro at $30 per month with yearly billing selected on its pricing page. These are site-plan examples observed November 5, 2026, not comparable all-in quotes; taxes, currency and checkout choices matter.

Webflow separates most Site and Workspace plans: the site plan covers the hosted site, while workspace capabilities govern collaboration and staging. Some bundled plans differ. Add the needed workspace, seats, site features and bandwidth to the estimate, and check the current client and agency roles.

Framer says site plans and editor seats are billed separately. On Basic and Pro, the workspace owner is free; its guide lists additional editors at $20 per month and Content Editors at $10 per month, with viewers free. The owner’s identity, eligible expert access and which workspace contains the project can change the bill; do not assume all three collaborators are free or need the same paid role.

For both vendors, add localization, domain registration, tax, third-party forms and integrations, plus agency build, migration and maintenance work. Record who pays each line before and after the transfer. Ask for a quote for the selected billing cycles rather than adding the headline site prices alone.

Budget and review each language

Webflow lists Localize Essential at $9 per added locale per month on the yearly pricing view. For the single secondary locale, Premium at $25 plus Essential at $9 is an illustrative $34 per month equivalent billed yearly, before Workspace seats, tax and other costs. Confirm the selected pricing and features at checkout.

Framer lists translation locales at $20 per locale in its pricing table. Pro at $30 plus one added locale at $20 illustrates $50 per month on the yearly pricing view, before seats, taxes and other costs. Its translation guide says AI translation consumes credits separately. Confirm the billing cycle and the selected locale at checkout. Trial one translated static page and one CMS record. Check localized paths, metadata, references, page controls and who can publish each version. A translation tool does not replace review by the client’s language owner.

Separate payment, control and access

Webflow describes the Workspace as the site owner. Its transfer guide says Freelancer or Agency Workspaces can transfer an active paid Site plan to an eligible client Workspace; client payments can put a client’s card on a site that remains in the agency’s Workspace. Those are different arrangements. Confirm eligibility, domain and add-on terms.

Moving a Site plan between two sites is a different operation from moving a site to a client Workspace. For a plan transfer to a site with an existing Localize add-on, Webflow says to duplicate the receiving site first. Check the exact operation and effects on publishing before scheduling a multilingual launch.

Framer says a project transfer keeps the site and connected domain online during the process. On acceptance the existing Site plan is canceled and unused time credited to the original owner; the recipient selects and pays for any needed plan. Confirm the new plan and payment before accepting, and agree whether the agency stays as an editor.

In either product, record the domain registrar, DNS owner, workspace owner, billing contact and the exact editor or publisher roles. Use separate identities and review the agency’s access after handoff; a client invoice alone does not transfer control.

Ask for exit artifacts, not just a ZIP

Webflow says paid Workspace plans can export site code, but the export excludes CMS content and functionality, localized pages, code components and hosted password protection. CMS collection data can be exported separately; localized CSV exports contain the current locale view. Forms and other hosted functions may need replacement.

Webflow says image and file fields in the CSV contain URLs pointing to the original site; deleting that site breaks those links. Download or otherwise preserve the assets and verify their new references before removing the source.

Framer’s self-hosting FAQ says it does not provide an HTML or static-site export, while its data-porting guide says a full published site can be downloaded and hosted elsewhere. These official descriptions conflict. The latter describes CMS export through plugins separately. Verify the available mechanism and permissions for the actual account before making an exit commitment.

Request a representative export or migration exercise, including one localized CMS item, assets, redirects and form integration. A static page, content file and editable project are different artifacts; no source here establishes a complete one-click migration.

Choose with the client in the room

Consider Webflow when its site, Workspace and Localize configuration matches the CMS and transfer needs. Consider Framer when its project workflow, seat costs and handoff fit the team and the unresolved export question is acceptable. Evaluate Duda when agency operations across multiple client sites are central.

Use the software trial guide for acceptance criteria, and the form builder guide to check the form and destination. If the need is a campaign landing page rather than a managed website, compare Unbounce and Instapage.

Common questions

Is the site subscription the whole cost?

No. Webflow separates most Site and Workspace plans; Framer bills editor seats separately from Site plans. Add required localization, integrations and work.

Does a client paying the bill own the Webflow site?

Not necessarily. Webflow says a client can pay while the site remains in the agency Workspace. Confirm ownership and transfer eligibility.

Can a Framer site always be exported for self-hosting?

Framer’s self-hosting FAQ says no, but its porting guide says a published site can be downloaded. The documents conflict; verify the available mechanism before relying on it.

Sources and scope

We read linked vendor documentation and pricing on November 5, 2026. This is documentation-only research; we have not built, transferred, exported or tested these products.

Inclusion and corrections are free; sponsorship does not determine our conclusions. Quillwell also builds Adswell, a paid-media product.

Plans and migration rules can vary by account and billing date. Verify current capabilities and a complete quote for your configuration.

Sponsorship does not buy an editorial ranking or a positive review. How we research.

Source references

1. Webflow: Plans and pricing

   Checked 2026-11-05. Current Site and Workspace plans, CMS and billing.

2. Webflow: May 2026 pricing update

   Checked 2026-11-05. Premium plan limits, prices and existing-customer rollout.

3. Webflow: Workspace and Site plans overview

   Checked 2026-11-05. Site and Workspace plan roles.

4. Webflow: Transfer a site or plan

   Checked 2026-11-05. Paid site transfer eligibility and client payments.

5. Webflow: Site ownership

   Checked 2026-11-05. Workspace ownership and client payment distinction.

6. Webflow: Manage add-ons

   Checked 2026-11-05. Localize pricing per locale and tier.

7. Webflow: Export site code

   Checked 2026-11-05. Paid Workspace export and excluded CMS, locale and hosted features.

8. Webflow: Migrate CMS Collection content

   Checked 2026-11-05. Separately exporting collection data.

9. Webflow: Localize Collection content

   Checked 2026-11-05. CSV exports contain current locale only.

10. Framer: Pricing

    Checked 2026-11-05. Current Site plan CMS limits, seats and add-ons.

11. Framer: Subscriptions and charges

    Checked 2026-11-05. Editor roles billed separately and billing frequency.

12. Framer: Transfer a project

    Checked 2026-11-05. Transfer ownership, active site plan cancellation, credit and recipient plan.

13. Framer: Auto Translate for Localization

    Checked 2026-11-05. Localization add-on and AI credit use.

14. Framer: Can I export HTML and self-host?

    Checked 2026-11-05. States no HTML bundle export for self-hosting.

15. Framer: Porting your data

    Checked 2026-11-05. States full published site can be downloaded and describes CMS plugins; conflicts with export FAQ.

16. Framer: Members, roles, and permissions

    Checked 2026-11-05. Workspace and project members and roles.

17. Webflow: Transfer hosting between sites

    Checked 2026-11-05. Moving a Site plan between sites; the existing Localize add-on on the receiving site requires duplication.

18. Webflow: Import or export CMS content

    Checked 2026-11-05. Exported image and file URLs depend on the source site.