AI&Design
All change articles

Lovable · Announcement · Official source

How Lovable's Figma plugin handed a design to the app builder

Six days after the August 21 launch, the Lovable Israel community team published a test that started with a complete landing page in Figma. The team exported the design using Lovable: Import from Figma, attached it to a Lovable project, and sent one build prompt. The team reported that the resulting page closely followed the original layout, colors and gradients, typography, spacing, pricing section, and footer. They also reported that the FAQ expanded and collapsed on the generated page. The article links the result. The available evidence is the team's account, and the linked demo could not be opened for independent verification. Lovable Israel's August 27 test

What changed on August 21

A Figma-to-Lovable workflow already existed. In January 2025, Builder.io documented selecting a design in Figma, converting it to code with its Visual Copilot plugin, and opening the generated result in Lovable. Work such as connecting real data happened in Lovable after that handoff. The August tool moved the export into a Lovable-owned Figma plugin and made the export an attachment that the builder could pick in chat. Builder.io's January 2025 walkthrough · Lovable's August 21 changelog

The designer pairs the plugin to a Lovable account, selects a frame or component, and exports it. Lovable documents a package of code, images, and fonts from that selection, with a cap of 100 generated files and 20 MB per file. The account holder can attach the export from Figma designs in the dashboard prompt or under Add context in an existing project's chat. Exports stay private to the account holder. Exporting is free, while a build prompt spends standard Lovable credits. Lovable's setup guide specifies a Dev seat or higher and says Dev-seat users need to open the Figma file in Dev Mode to see the plugin panel. Lovable's August 21 changelog · Lovable's Figma plugin setup and limits

What needed review after export

The community test shows the design serving as input to a web build. The team recommended asking Lovable to preserve layout, typography, color, spacing, and components while specifying responsive behavior. It also recommended named layers and components, Auto Layout, splitting complex screens when needed, and a separate mobile review. The team described the result as visually close and still requiring review and corrections. Its report does not identify any specific second-pass fixes. Lovable Israel's test and workflow

The evidence supports two practical checks. First, compare the generated page with the Figma reference at the target viewport sizes, including type, images, and spacing. Second, exercise the page behavior. The reported FAQ toggle shows one interaction that worked in this example. A visible form alone leaves questions about validation, delivery, and the confirmation state. The case also leaves open whether Figma component relationships or variables persisted as corresponding structures in code. Lovable documents the generated file types. Its documentation does not establish one-to-one preservation of Figma's editable layer tree. Lovable's plugin limits · Lovable Israel's reported output

Public Reddit searches for August 14 through September 4, with a follow-up through November 18, yielded no dated submission attributable to the Lovable-owned plugin. Search results included discussions of the older Builder.io route, screenshots, and exporting Lovable output back to Figma. The one attributable launch-window test supports a scoped conclusion. The plugin let that team use a Figma frame as the starting point for a Lovable page, and the team reported recognizable design fidelity. The amount of manual cleanup across pages, viewports, and designs with richer components remains unmeasured. Example older Builder.io discussion · Lovable Israel's August 27 test