What works today
FigCraft covers the main Figma workflow in one native app: frames and auto layout (including wrap and grid), components with variants and overrides, styles and variables with modes, vector networks with booleans that stay editable, prototyping with conditions and flows, and Dev Mode with annotations and generated code. The README says the core editor works end to end and that nearly all of Figma's main menu is wired. New files can start from eight built-in templates: a mobile app, a landing page, a dashboard, a design system starter, a wireframe kit, social post sizes, presentation slides and an icon set.
Files are .figcraft archives on your own disk. SVG, PNG, JPG, WebP and PDF go in and out, any layer exports at any scale, and .fig files and Figma REST API JSON open too.
FigCraft vs Figma
FigCraft follows Figma's way of working: the README says the toolbar, layers panel, Design panel, menus and shortcuts sit where Figma users expect them. The table sums up where it stands, from the README and the project's roadmap as we read them on 17 October 2026.
| If you use Figma for… | FigCraft today |
|---|
| Frames, auto layout, constraints and layout grids | Included, with wrap and grid layouts and min and max sizes |
| Components, variants, styles and variables | Included, with variable modes such as Light and Dark |
| Vector editing | Vector networks, a shape builder and boolean groups that stay editable |
| Prototypes | Connections, Smart Animate-style transitions, conditions, flows and a presentation view |
| Dev Mode and handoff | Annotations, measurements, Compare changes, and code in CSS, HTML, React, Leptos, SwiftUI and Compose |
| Comments and version history | Comment threads pinned to frames, and named version history |
Opening .fig files | Best effort only, not yet checked against real Figma documents |
| Figma plugins | Not supported: FigCraft runs its own WebAssembly plugins |
| Editing together | A first preview of live sessions, with no accounts, teams or cloud |
| AI features | None yet: the roadmap puts them at 0% |
| Account, offline use and price | No account, works offline, free and open source |
Can you use FigCraft instead of Figma? For solo work on your own files, the project says the everyday workflows already work: designing screens, building a design system, prototyping and handing off to developers all run end to end on FigCraft's own files. For a team that swaps .fig files with Figma users, depends on Figma plugins or edits together every day, not yet. The project calls FigCraft alpha and, by its own estimate, about halfway to replacing Figma for real work.
Some differences are by design. FigCraft is a native Rust app with no Electron or web view, it has Linux and FreeBSD builds, and every action is a command that scripts and AI agents can call through a CLI or an MCP server.
Sharing and privacy
FigCraft contacts no server until you share or join a file. Share ▸ Online uploads the file to a server, by default the public collab.craftapps.dev. The connection uses TLS, but the server stores the file unencrypted and whoever runs it can read it. Anyone with an edit code or link can change the file. You can run your own figcraft-server or share on the local network instead. The public server has no backups or uptime promises, so keep your own copy of anything you share.
About the Craft Apps
FigCraft is one of the Crafting Apps from the ArtCraft team: free, open-source creative tools, each written from scratch in Rust and each able to stand on its own. The others include PhotoCraft, VectorCraft, FilmCraft, LightCraft, PdfCraft, EffectCraft and DesignCraft. According to the README, FigCraft is a clean-room project, implemented from public documentation and observed behaviour only, with no proprietary code, file formats, icons or images. Figma is a trademark of Figma, Inc., and FigCraft is not affiliated with it.