No. Figma UI Import rebuilds the design as a structured Blender collection. Useful UI elements stay separate, supported text can stay editable, and complex areas are rasterized only when that gives a more reliable result.

Supported text does. Each text layer is checked separately. If one layer uses styling Blender text cannot reproduce reliably, that layer can use its image fallback while the rest of the interface stays separate.

Not necessarily. In the Editable workflow, matched font files can be included in the exported ZIP. Blender tries a local or system font first, then the bundled copy when needed.

Blender UI Exporter is available on Figma Community. Open the official plugin page ↗

Yes. The add-on supports both render engines. EEVEE includes controls for imported UI transparency, while Cycles includes Shadow Control for selected UI objects.

No external conversion server is required. The selected Figma content, chosen font files and ZIP creation are handled locally in the plugin workflow.

No. The current workflow is a ZIP export from Figma followed by a ZIP import in Blender. Live sync, Push to Blender and Smart Reimport are not part of this release.

They are handled selectively. Areas that need rasterization can be flattened while unrelated sibling layers stay separate whenever possible. Boolean results and some vector-only structures are rasterized when that is the reliable way to preserve the final appearance.

Yes. Blender UI Exporter supports 1x to 8x export scale, shows the resulting resolution, recommends a scale and lets you inspect a sharpness crop before export.

The current supported baseline is Blender 4.0 and newer.