Framework

Limits

What each destination cannot produce, and what to do instead.

Webflow

Nothing here blocks a build. Each item just needs a different design choice, or a step you finish in Webflow.

The one to plan around is tables. Design comparison and pricing tables as a grid of cells instead.

Tables: Rebuild the layout as a grid. Comparison tables are best designed as a grid of cells.
Horizontal rules: Use a thin box with a top border.
Canvas and dialog elements: Use an image, or a native Webflow interaction for modal behavior.
CMS collections: Not available yet. Build the layout with real repeated items and connect the CMS in Webflow.
Webflow Components and Symbols: Not available yet. Create them in Webflow after pasting.
CSS filters and backdrop blur: Bake the effect into an exported image, or apply it in Webflow afterwards.
Keyframe animations: Use a Webflow interaction. Transitions do carry over.

Video, maps, social icons, and star ratings: Build these with the supported widgets, or add the widget in Elementor after import.
HTML embeds and shortcodes: Add them in Elementor after import.
Backdrop blur, clip paths, and masks: Bake the effect into an exported image.
3D transforms: Use a flat design, or an exported image.
Named grid areas: Use a plain column and row grid.
Vertical text: Export it as an image.
Sticky and fixed positioning: Apply it in Elementor after import.
CMS and dynamic content: Not available yet. Build the layout with real repeated items.

Visual effects

Backdrop blur, clip paths, and masks are not translated. If the effect matters, flatten that part into an exported image.

React and Astro carry everything across, including working interactive state. There is no gap to plan around.

HTML has no React runtime, so tabs, accordions, sliders, and the mobile menu run on small included scripts instead.

Choosing a destination

The pattern lookup compares all five side by side for the thing you are designing.