# Supported Figma features
Check supported and risky Figma features before converting frames, prototype flows, or state machines to Lottie.

Use this page as a practical preflight checklist. For the latest full source, see the [official Figma to Lottie export guide](https://lottiefiles.com/plugins/figma/export-guide).

## Safer feature areas

The export guide lists support across these areas:

- Basic interactions such as click, hover, press, mouse enter, mouse leave, mouse down, mouse up, and after delay.
- Shapes and curves.
- Text, when layer matching and values are stable.
- Images.
- Basic fills, gradients, and strokes.
- Common transition and animation behavior.

## Features that need extra care

| Area              | Risk                                                            | Safer approach                                         |
| ----------------- | --------------------------------------------------------------- | ------------------------------------------------------ |
| Multiple frames   | Missing or reordered layers can break matching                  | Keep layers present, ordered, and named consistently   |
| Text              | Changing text inside the same layer can fail                    | Use separate text layers and toggle visibility         |
| Gradients         | Complex gradients may render incorrectly                        | Prefer simple linear or radial gradients               |
| Fills and effects | Stacked fills, shadows, strokes, or effects can break animation | Use one clear visual treatment per animated object     |
| Prototype actions | Some actions do not become state-machine inputs                 | Use supported navigation-style transitions             |
| Interactivity     | Lottie JSON removes state machines, themes, and motion tokens   | Export as `.lottie` for the full dotLottie feature set |

## Interactive support notes

Supported interaction triggers include click, hover, press, mouse enter, mouse leave, mouse down, mouse up, and after delay. Key/gamepad and drag-related behavior may need to be planned as separate product behavior rather than direct interaction in the player.

## Related

- [Reading export warnings](/en/integrations/figma/06_feature-checking/reading-export-warnings)
- [Preparing your Figma scene](/en/integrations/figma/04_figma-to-lottie/preparing-your-figma-scene)
- [Exporting interactive state machines](/en/integrations/figma/04_figma-to-lottie/exporting-interactive-state-machines)