Conversion issues

Figma to Qt converts Figma designs into QML types. Some Figma layers have properties that have no equivalent in QML. The Issues page describes the differences and offers to automatically fix some issues.

The following table summarizes the properties that QML types do not support.

Bound variables	Layer properties are bound to variables.
Font files	Too many or no font files added.
Invalid control setup	Missing or invalid control properties.
Layer name or position	Moved or renamed layer.
Layout child positioning	Cannot position a QML type.
Layout padding	Too much padding in an auto layout.
Missing variables	Variables not available in the current file.
Mixed font style	Different font family, weight, size, or style (such as, bold or italic) within one text layer.
Mixed line height	Different line height values within one text layer.
Mixed or non-solid fill	Only some words or characters have a fill within one text layer.
Mixed stroke weight	Different stroke weight values within a rectangle layer.
Non-solid strokes	Strokes styled with a gradient or other fill.
Non-solid text fill	Text styled with a gradient or other fill.
Rendering as image	Set to be rendered as images.
Shapes and effects	Always rendered as images.
Skipped layer	Layer was skipped.

Converting into Qt for MCUs

Qt for MCUs takes into account the resource constraints on the MCU platforms, such as memory footprint and CPU cycles. It enables your application to perform optimally with the resources available on MCU platforms.

To keep your application lean, help Figma to Qt to convert the Figma design into native Qt for MCUs QML types. Keep the following in mind when working in Figma:

Rotate only Text or Image layers
If you use effects, you can either render the layer as an Image or skip the effects
Figma to Qt cannot convert shapes into SvgPathItem types

The following table summarizes additional properties that Qt for MCUs types do not support.

Complex script	Complex text script.
Mixed corner radius	Individual radius values for each corner of a rectangle.
Non-solid fill or non-linear gradient	Layer styled with a non-linear gradient or non-solid fills.
Rotated child layers	Rotated layer has children.
Rotation	Rectangle layer is rotated.
Strokes	Layer has strokes.
Text auto resize	Automatically resized text.
Text case	Text styled with text case (such as small caps).
Text decoration	Text styled with strikeout, underline, and so on.
Text truncation	Truncated text.
Top visible fill	Non-solid text fill for the top visible fill.
Unsuitable font	No support for complex scripts.
Unsupported properties	Properties that Qt for MCUs types don't support.

Components and variants

Figma to Qt converts each Figma main component into a QML component and each instance into an instance of the component. It converts component sets (with variants) into QML components with states. You can override the properties of the main component or component set in the instances.

Note: For best results, all variants should have the exact same internal layer structure, including the same nesting depth.

If the plugin shows you issues about component instances, check that:

The layer names match across components and their instances.
Names of added layers in variants are not the same as names of layers in the default variant.
Positions of layers in variants match those in the default variant.

Note: Swapping instances is not supported.

Conflicting overrides	Variant instances overridden in ways that are not supported.
Conflicting variants	Conflicting variant instances.
Ill-defined component	Figma component is not well-defined.
Inconsistent variants	Inconsistent layer names of children in variants.
Instance swap	Instance swap in a component instance.
Layer names	Layer names changed between a main component and its instance.
Missing main component	The main component of an instance is missing.
Missing states	States removed from a control.
Nested variants	Self-nested variant.

Project issues

When you download the converted design, Figma to Qt creates a QML project that contains all the necessary files. You can specify advanced layer settings to instruct the plugin on how to convert layers.

The following table summarizes issues in the created projects. They are shown by the compiler or other tools developers use to build and run the project.

Invalid QML type

Custom QML type does not exist.

Reference Bound variables

© 2026 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners. The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation. Qt and respective logos are trademarks of The Qt Company Ltd in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.