Craft Apps GuideOpen the copy
On desktop choose Open and select the .fig copy; CLI users can run figcraft-cli convert input.fig imported.figcraft.
CHECK
The design opens or an explicit import error appears. Inspect import notes.
How to Open a Figma .fig File in FigCraft
FigCraft opens .fig files on a best-effort basis. Keep the source file, import a copy, then check text, layout and components before saving a separate native .figcraft project.
Get a legal local copy
For a Figma project you own or are allowed to export, use Figma’s File → Save local copy. If that action is missing, the owner may have restricted copying or export. A local copy is not the cloud project’s comments or version history. Our downloadable fixture contains only self-created material.
Import and verify
If this fails: If parsing fails, preserve the .fig and try a simpler legal export; do not rename an arbitrary ZIP to .fig.
Keep: original.fig + imported.figcraft
Check fonts and geometry
Compare headings, paragraph wraps, frame sizes and spacing with the original preview.
CHECK
Expected text remains editable and does not overflow.
If this fails: Use figcraft-cli info input.fig --json for missing-font and import notes; install only fonts you are licensed to use.
Keep: comparison preview
Check design behavior
Inspect a component and instance; test an override, variable mode and prototype connection if present.
CHECK
Behavior agrees with the source, not merely the raster appearance.
If this fails: Record unsupported behavior and rebuild only the part you need.
Keep: compatibility notes
Save and reopen
Save a new .figcraft file, close that copy, reopen it and repeat critical checks.
CHECK
The saved native file retains editable structure.
If this fails: Return to the preserved original if native reopen differs.
Keep: native project + original .fig
What our sample proves
Tests on 20 October 2026 used official FigCraft 0.7.0 on macOS 27.0.1, Apple Silicon. Native CLI operations use FigCraft’s own engine and renderer; rendered images are not desktop UI screenshots.
Our .fig was exported by FigCraft from a self-created card project, then imported and saved again. Reopen reported 31 nodes, a COMPONENT and an INSTANCE, with no import notes. That tests FigCraft’s own export/import path. It does not establish compatibility with a Figma-authored production file; variables, prototype transitions and Figma reopen were not tested.
The four-card raster was pixel-identical before and after this self-roundtrip at 860×695 px. Reopened text styles retained Inter Regular 16 px and Inter Bold 24 px. These checks cover this deliberately simple sample, without an image fill, variable or prototype.
What to compare after import
| Task | Observed result | Boundary / next check |
|---|---|---|
| Text | Characters, family, size and line breaks | A fallback font may change a card’s height. |
| Layout | Padding, gap, nested flow and resizing | An unchanged screenshot does not prove constraints. |
| Components | Main component, instance link and overrides | A detached copy can look correct but lose reuse. |
| Variables / prototype | Mode changes and destination transitions | Mark not tested when the sample has none. |
Sources & Evidence
Official sources checked 20 October 2026. Test results are limited to the versions, environment and files stated above.
- FigCraft source and alpha limitations ↗ — Official documentation checked 20 October 2026; capabilities are documentation claims unless separately marked tested.
- FigCraft CLI reference ↗ — Official documentation checked 20 October 2026; capabilities are documentation claims unless separately marked tested.
- Figma: save a local copy ↗ — Official documentation checked 20 October 2026; capabilities are documentation claims unless separately marked tested.