Tuvi

For educators and students

Education

A real design tool that runs in the browser on a $0 plan: students open industry-standard .fig files, edit together in critiques and learn hand-off the way product teams actually practice it.

  • Runs in the browser — no installs, no lab imaging
  • Starter is $0; personal drafts are free forever
  • Real .fig files — the format studios actually use

Why design classes fight their tools

  • Licenses and education tiers change year to year, and course plans break with them.

  • Lab machines need installs and updates, while students' own laptops run three different operating systems.

  • Student work vanishes when trials expire or accounts lapse at semester's end.

  • Teaching on watered-down tools leaves graduates relearning everything at their first job.

What makes it classroom-ready

Industry files, student budgets

The economics of a design course rarely survive contact with professional tooling. Tuvi's floor is genuinely zero: personal drafts are free forever, and a Starter team — 3 editors, 1 project, 10 files — costs nothing, which fits a studio group or a thesis project without a procurement conversation. There is no expiring education trial to re-negotiate every autumn, because the free tier is simply part of the product.

The tooling is professional all the way down, not a teaching imitation. Students work with real .fig files — the format working studios exchange — with the same auto-layout, components and live collaboration they will meet in industry. And because everything runs in the browser, 'setting up the lab' means opening a URL: no installs, no lab imaging, no version drift between machines — and older hardware still participates, thanks to an automatic simplified drawing mode.

Critique as a live session

Group critique is where design education happens, and multiplayer changes its texture: the whole class inside one document, cursors visible, comments pinned to the exact frame under discussion instead of read aloud from notes. Iterations happen in branches — a student explores a direction without destroying the previous one, and the merge shows the class precisely what changed and why.

The same mechanics quietly teach professional workflow: in-context feedback, branch-based iteration, Ready-for-Dev thinking about when work is finished. When the semester ends, nothing evaporates — personal drafts stay free forever, and portfolios export as PNG, SVG or PDF.

Frequently asked questions

What does a class actually pay?

Nothing to start: personal drafts are free forever, and each Starter team is $0 for up to 3 editors, 1 project and 10 files. There is no separate education program to apply for — the free tier is a permanent part of the product, not a trial.

Will it run on student laptops and lab machines?

Yes — Tuvi runs in the browser, so it works across operating systems on whatever laptops students already own. Older machines automatically get a simplified drawing mode that keeps files usable. Nothing is installed either way.

Can students work with real-world design files?

Yes. Tuvi opens .fig files directly — components, styles and auto-layout intact — so coursework can use actual product files and community resources, and student work stays in an industry-standard format culture.

What happens to student work after the semester?

It survives by default: personal drafts are free forever regardless of any team or plan, and everything exports as PNG, JPEG, SVG or PDF for portfolios. No expiring account takes a term's work with it.

Related pages

For open-source projects

Open source

For product teams

Product teams

Run your next critique in one shared document

View plans