Figma Sites

Name: Figma Sites
Brand: Figma

Leader

Slots? Slots. SLOTS.

Est 2012|Valuation $12.2B|Raised $744.5M

LinkedIn 2.1M|Website|Web traffic 127.9M|FTEs 1,886|HQ San Francisco, California, US

MarketsCMS / DXP Landing Page Builders

01Competitive Landscape

Narrative analysis

Webflow vs Figma Sites - Webflow is typically selected when teams require a mature CMS, forms, and more explicit web publishing controls. Webflow emphasizes CMS and API capabilities for programmatic management of content. - Community discussion around Sites suggests skepticism about output quality for engineering handoff, though Sites now documents CMS capabilities. Framer vs Figma Sites - Framer offers an integrated stack with content-editing workflows and a designer-focused experience. Framer is positioned for teams that want end-to-end control of a site's content and editing experience. - Framer community discussions include pricing concerns that may be relevant for organizations running many sites. Webstudio (emerging alternative) - Webstudio emphasizes usage-based site pricing (e.g., usage overages) and is discussed as an alternative to Webflow and Framer for organizations preferring transparent usage-based billing.

When customers choose competitors instead (themes)

Need for mature CMS, form handling, and integrations
Requirement for cleaner export/handoff to engineering teams
Concern about unclear pricing or product roadmap for Sites

	Figma Sites	Webflow	Framer
Starting Price	Sites is bundled into Figma plans as a beta feature; standalone per-site pricing is not clearly published	Tiered site plans including CMS-focused tiers; published tiered pricing available from the vendor	Published per-site pricing available from the vendor
Typical Use Case	Designers already using Figma who require rapid marketing sites and design-system reuse	Organizations requiring a mature CMS, forms, extensibility, and predictive publishing controls	Design-forward marketing sites with integrated CMS/hosting and iterative content workflows
Key Strength	Integration with Figma design workflow and libraries; multi-breakpoint editing and interactions	Mature website publishing feature set, CMS APIs, and established production usage	Integrated content editing and rapid iteration with designer-focused tooling
Key Weakness	Community-reported challenges with generated code quality, feature maturity questions, and pricing uncertainty	Pricing complexity (site vs workspace plans) and learning curve	Pricing sensitivity at scale for many sites

01Competitive Landscape

Narrative analysis

Webflow vs Figma Sites

Webflow is typically selected when teams require a mature CMS, forms, and more explicit web publishing controls. Webflow emphasizes CMS and API capabilities for programmatic management of content.
Community discussion around Sites suggests skepticism about output quality for engineering handoff, though Sites now documents CMS capabilities.

Framer vs Figma Sites

Framer offers an integrated stack with content-editing workflows and a designer-focused experience. Framer is positioned for teams that want end-to-end control of a site's content and editing experience.
Framer community discussions include pricing concerns that may be relevant for organizations running many sites.

Webstudio (emerging alternative)

Webstudio emphasizes usage-based site pricing (e.g., usage overages) and is discussed as an alternative to Webflow and Framer for organizations preferring transparent usage-based billing.

When customers choose competitors instead (themes)

Need for mature CMS, form handling, and integrations
Requirement for cleaner export/handoff to engineering teams
Concern about unclear pricing or product roadmap for Sites

	Figma Sites	Webflow	Framer
Starting Price	Sites is bundled into Figma plans as a beta feature; standalone per-site pricing is not clearly published	Tiered site plans including CMS-focused tiers; published tiered pricing available from the vendor	Published per-site pricing available from the vendor
Typical Use Case	Designers already using Figma who require rapid marketing sites and design-system reuse	Organizations requiring a mature CMS, forms, extensibility, and predictive publishing controls	Design-forward marketing sites with integrated CMS/hosting and iterative content workflows
Key Strength	Integration with Figma design workflow and libraries; multi-breakpoint editing and interactions	Mature website publishing feature set, CMS APIs, and established production usage	Integrated content editing and rapid iteration with designer-focused tooling
Key Weakness	Community-reported challenges with generated code quality, feature maturity questions, and pricing uncertainty	Pricing complexity (site vs workspace plans) and learning curve	Pricing sensitivity at scale for many sites