Import from Figma

Fanta can open a local .fig file and convert it into an editable project. The import path handles Figma document data such as pages, layers, components, instances, auto layout, vectors, effects, variables, and supported Boolean operations where Fanta's document model can represent them.

Open a .fig file

Open the file in the desktop app. On first open, Fanta parses it and attempts to materialize a sibling Fanta project directory. You can edit the imported design from that first session. The original .fig remains an import source; the saved Fanta project becomes the working copy. If writing beside the import fails, Fanta shows the parsed design in memory and retries project creation on save. Choose a writable location if macOS limits access to the sibling folder.

In the direct-download Mac build, a fresh sibling project is prepared in a temporary directory and published only after its files have been written and flushed. The final publication step refuses to replace a destination that another process created. If publication fails, the imported design remains open in memory and the first save can retry creating the project.

If you open the same .fig again after a sibling project was created, Fanta redirects to that project. This preserves newer edits instead of reimporting the original file over them.

Check the result

Large imported documents can contain thousands of nodes. Inspect the page tree and key components in the editor, then compare visual output against the source.

Supported Union, Subtract, Intersect, and Exclude Boolean operations retain their operands as editable layers. Fanta keeps the imported vector appearance while the operands and operation are unchanged, then recomputes geometry when you edit them. Undo can restore the imported appearance. If an operation is unsupported or operands cannot be used, Fanta falls back to a vector; those operands are not separately editable.

On first import, Fanta shows a canvas notice when it detects known structure loss: flattened Boolean operations, omitted unsupported or malformed layers, or layers with unsupported parent relationships. The notice gives counts and Boolean fallback reasons. It does not prove that all rendering and component overrides match Figma, and absence of a notice does not establish full fidelity. Compare important pages visually and inspect the layers you plan to edit.

For agent inspection, batch_get supports depth limits and pagination. Read smaller portions of a large imported page and request detailed nodes by ID. Capture a screenshot of the page or relevant node to review rendering.

Continue work in the Fanta project directory and keep its project files and assets together. Use visual export when you need PNG, JPG, SVG, or PDF output.