---
title: Move off Figma
description: How to move from Figma to Brilliant: the import routes, what your habits do, and how to run both while you decide. Step by step.
section: solutions
order: 9
featured: false
howto: false
related: import/from-figma, getting-started/coming-from-figma, compare/figma
---

# Move off Figma

How do I move off Figma without rebuilding a year of work? Import it. The Brilliant plugin brings a Figma file across, each page becomes a canvas, and components arrive as real, linked components. You can also move in stages, and keep both for as long as you want.

<DocFigure src="/docs/images/solutions/move-off-figma-scene.webp" srcMobile="/docs/images/solutions/move-off-figma-scene-390.webp" stage="panel" alt="A Figma file imported into Brilliant with components still linked" caption="14 components, still linked." />

## What are the steps?

Four steps. Each links to the page with the detail.

<DocStep n="1" title="Bring the files over.">

In the plugin, press Import to Brilliant, then choose the project, pages and libraries. Variables and styles become the project's design system. For one part, use Send selection, Copy selection, or a plain copy and paste. The full walkthrough is in [Import from Figma](/docs/import/from-figma).

</DocStep>

<DocStep n="2" title="Point your habits somewhere.">

Pages become canvases. Frames, auto layout and variant axes stay what they were. V, F, R, O, T, P and the align chords are where you left them, and every shortcut can be remapped from Shift+?. See [Coming from Figma](/docs/getting-started/coming-from-figma).

</DocStep>

<DocStep n="3" title="Learn the four differences.">

Selection is grouped per frame, there is no save button, undo is per canvas, and components live on the canvas rather than in a panel.

</DocStep>

<DocStep n="4" title="Move at your own pace.">

Send to Figma pushes a selection back as native objects, so a canvas can round-trip while your team decides. Import the same file again and it updates the same project.

</DocStep>

<DocFigure src="/docs/images/solutions/move-off-figma-import.webp" srcMobile="/docs/images/solutions/move-off-figma-import-390.webp" stage="panel" alt="The Figma import running, with each page listed" caption="A whole Figma file on its way in." />

## What comes across?

The design itself, not a picture of it: auto layout, vectors, booleans, fills, gradients, effects, text with its per-character styling, components with variant axes, and variables as tokens with layers still bound. [Import from Figma](/docs/import/from-figma) has the full table.

## What do I gain?

Agents on the canvas, plain text files that diff in git, native shaders, export to code and video, and unlimited MCP canvas work on Free, with images on your Brilliant AI usage.

<DocFigure src="/docs/images/solutions/move-off-figma-agent.webp" srcMobile="/docs/images/solutions/move-off-figma-agent-390.webp" stage="panel" alt="An external agent connected to Brilliant over MCP, editing the open canvas" caption="Your own agent, editing the canvas over MCP." />

## Common questions

### How do I handle Figma prototypes?

The frames come across. Prototype with motion, and your agent builds a real prototype in code. Comments are coming very soon.

### Is it safe to try?

Yes. The design tool is free, and your workspace is a plain folder. Your files stay on your disk until you publish. A Brilliant AI request carries its design context to answer you, and it is not stored afterwards.

### Can I bring Sketch files too?

As SVG: export the art and import it with Cmd+Shift+O. Images and .bl files come in the same way.

## Where next?

- The import, step by step: [Import from Figma](/docs/import/from-figma).
- The concept and shortcut map: [Coming from Figma](/docs/getting-started/coming-from-figma).
- The full comparison: [Brilliant vs Figma](/docs/compare/figma).
- Connect a coding agent: [Connect your agent](/docs/agents/overview).
- See every plan on the [pricing page](/pricing).
