Direct answer
This human UI flow authorizes a Figma source, selects one frame, and generates one new app artifact. The generated files are editable; the artifact is not synchronized with Figma.
Required state
The human needs access to the Figma source and permission to create in the destination workspace. A workspace is an access-controlled area inside a team. The team also needs room under its artifact limit and a plan with an import remaining. Authorization is a human consent step.
UI-only procedure
Ask the human to open New → Import from Figma, provide the source, complete authorization, select one frame, choose the destination workspace when prompted, and begin generation. Verify by opening the resulting artifact and reviewing its rendered output.
Quota invariant
Free teams receive five successful imports total across both methods. It is one combined allowance, not five of each. Artifact capacity and import allowance are separate. A quota refusal should open or relay the upgrade path, not trigger retries. Deleting an imported artifact does not restore an already consumed import.
Use Plans and usage and Limits and quotas for plan details.
Output constraints
- One selected frame produces one app artifact with generated web files.
- Later Figma changes do not flow into the artifact, and artifact changes do not update Figma.
- Unsupported or complex design behavior may need manual or agent-assisted cleanup.
- Repeating the import creates another artifact.
- Do not invent a public CLI Figma-import command; none is established by this page.
Terminal versus retryable failures
Authorization denial, workspace denial, artifact capacity, and import allowance require human action and are terminal for the current attempt. Invalid links or missing frames require corrected input. A transient generation failure may be retried once; send repeated failures to Troubleshooting.
Related: Artifact types · Canvas · Import from URL