How to open .fig files without Figma (free, in your browser)

Someone sends you a .fig file — a contractor's final delivery, a design handed over by a departed teammate, an archive from an old project — and you hit a wall: the file only opens in one tool, and that tool wants an account and, for editing, a paid seat for everyone involved. If all you need is to look at the design, make a small change or pass it to a developer, that is a frustrating amount of friction.

The good news: a .fig file is not locked to one vendor anymore. This guide shows how to open it in your browser in under a minute, what survives the trip (spoiler: everything that matters), and what to do with the file once it is open.

Why .fig files feel locked — and why they aren't

The .fig extension is Figma's own file format. Historically that meant one thing: to open the file, you needed Figma. Every workaround was lossy — exporting to SVG or PNG gives you pictures of the design, with components flattened, text no longer editable and auto-layout gone. Rebuilding a real project from exports can take days.

Tuvi removes the lock by reading the .fig file itself. There is no conversion service in the middle and no plugin to install in the source tool: you upload the file you already have, and it opens as an editable document in your browser — on Windows, macOS, Linux or a Chromebook, with nothing to install.

Opening a .fig file, step by step

The whole process takes about a minute:

1. Create a free account at tuvi.io. The Starter plan costs $0 and needs no credit card; you can sign in with passkeys or OAuth.
2. Drag the .fig file into your project (or use the upload button). The free plan accepts files up to 50 MB — enough for most real projects.
3. Wait a few seconds while the file opens. No export from Figma is needed beyond having the .fig file itself; both older and newer file variants are supported.
4. Start working. The document is immediately editable: select layers, change text, move frames, edit styles — the same design, now in your browser.

Your original file is never modified. You upload a copy, so there is no risk in trying this with a file that matters — in fact, the more complex the file, the better the test.

What survives the import (and why it matters)

The difference between "opens the file" and "shows a picture of the file" is everything for real work. When Tuvi opens a .fig file, the design stays a design:

• Components and instances keep their relationships and per-instance overrides — swap, detach or edit them as usual.
• Auto-layout keeps working: resize a frame and its children reflow, instead of stretching like a bitmap.
• Styles and variables stay attached, including variable modes — a color arrives as its token, not a baked-in value.
• Text stays text — editable, with its typography intact.
• Vector paths, gradients, shadows and blurs render with high fidelity, so what you see matches what was designed.
• Prototypes keep their connections and play in a live player.

Two honest limitations worth knowing before you rely on it: a few niche text features (text-on-path, list bullets) are not supported yet, and very large files (100 MB+) open slowly today. For the overwhelming majority of files, the document opens complete and editable.

What you can do once the file is open

Opening the file is the start, not the point. Once the design is in Tuvi you get a full collaborative editor around it:

• Edit together in real time. Up to 3 editors on the free plan work in the same file simultaneously, with changes visible instantly — see the real-time collaboration guide for how teams organize this.
• Share by link. Anyone with a view link can look at the design without an account or a seat — viewers are always free. Paid plans add edit links with passwords and expiry dates.
• Comment in context. Feedback attaches to the exact spot it concerns, instead of living in a chat thread next to a screenshot.
• Export what you need: PNG, JPEG, SVG or PDF straight from the editor, including batch export to a ZIP.
• Hand off to developers. On paid plans, Dev Mode inspects spacing, typography and variables on any layer and generates code in seven formats for whatever stack your team uses.

What it costs (mostly: nothing)

For the "just open this file" use case, the free Starter plan is genuinely enough: 1 project, 10 files, 3 editors, 50 MB uploads and 30 days of version history. Personal drafts are free forever regardless of plan, and viewers never consume a paid seat — only people who edit do.

If the team grows into it, Professional at $12 per editor/month removes the project and file limits, raises uploads to 200 MB, makes version history unlimited and unlocks Dev Mode and component libraries. But you do not need to decide that today.

Try it with the file on your desktop

The fastest way to answer "will this work for my file?" is not a comparison table — it is the file itself. Create a free account, drag in the gnarliest .fig you have, and click through the components, text and auto-layout frames. If everything behaves like a design rather than a picture, you have your answer, and it cost you a minute and $0.