Why we built this
Most "design-to-code" tools either require a clunky plugin in your design tool, a paid Figma seat for the team, or a manual export-to-PDF dance. We took a simpler route: just paste the URL. As long as the design is shareable (or you've made it public), Wyvid can read the layout, typography, and color tokens and use them as the source of truth.
What happens with your link
- Figma frames — paste the URL to a specific frame or page. Wyvid uses the frame's structure (auto-layout, components, text styles) as a guide for the output markup.
- Figma multi-page files — paste the file URL and pick which frames you want as pages of the site.
- Canva designs — paste the share link to a website or presentation design. Wyvid reads each slide as a section or page.
How it compares to screenshot upload
Both approaches end at the same place — a Bootstrap 5 sitebuild plus the chat iteration interface. The difference is fidelity. With a Figma link, Wyvid sees the actual structure of your design (grouped layers, auto-layout direction, component instances) instead of having to infer it from pixels. The first generation usually needs less iteration as a result.
What we don't do
We don't translate every design choice 1:1. Some Figma effects (complex blends, animated prototypes, embedded videos) don't have clean web equivalents and Wyvid will substitute a sensible alternative. We err on the side of "it ships and looks right" over "it pixel-matches the design tool's render". You can refine specifics later through chat iteration.
Privacy
Wyvid only fetches what's at the URL you provide and only for as long as needed to produce the build. We don't keep a copy of your Figma file on disk after the build completes — see the privacy policy for the full retention story.