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.
Layer properties are bound to variables. | |
Moved or renamed layer. | |
Cannot position a QML type. | |
Too much padding in an auto layout. | |
Variables not available in the current file. | |
Different font family, weight, size, or style (such as, bold or italic) within one text layer. | |
Different line height values within one text layer. | |
Only some words or characters have a fill within one text layer. | |
Different stroke weight values within a rectangle layer. | |
Strokes styled with a gradient or other fill. | |
Text styled with a gradient or other fill. | |
Set to be rendered as images. | |
Always rendered as images. | |
Layer was skipped. |
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.
Variant instances overridden in ways that are not supported. | |
Conflicting variant instances. | |
Figma component is not well-defined. | |
Inconsistent layer names of children in variants. | |
Instance swap in a component instance. | |
Layer names changed between a main component and its instance. | |
The main component of an instance is missing. | |
States removed from a control. | |
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.
Custom QML type does not exist. |
See also Fix conversion issues, Render layers as images, and Design guideline.
© 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.