Collaboration
Real-time design collaboration
Your whole team in one file: live cursors, comments pinned to the canvas, Ready-for-Dev annotations — and branches that merge back with review when work needs to fork.
- Edit the same file at the same time, with live cursors
- Comments and Ready-for-Dev annotations right on the canvas
- Branch, review and merge design files — like modern teams ship
Everything real collaboration should include
From invite to merged design
Share the document
Invite editors or send a view link. Starter teams get three editor seats free; viewers never cost anything on any plan.
Edit at the same time
Everyone works in the same file and sees the same thing — changes appear instantly for the whole team, and nobody ends up looking at a stale copy.
Review in context
Discuss in comment threads pinned to the canvas, and flag finished frames Ready-for-Dev so engineering knows exactly what is stable.
Fork and merge when needed
Big redesign? Branch the file, iterate safely, then merge back with review. Conflicts are surfaced explicitly instead of silently overwriting anyone's work.
Everyone sees the same design, always
Live collaboration only helps if it is dependable. In Tuvi the whole team always sees one identical file: when two people adjust the same element at the same moment, the result resolves instantly and predictably for everyone — no stale copies, no 'refresh and try again', no mystery about whose change won. Review time goes to discussing the design, not reconciling versions of it.
And when work genuinely needs to diverge — a redesign, a bold experiment, a client's what-if — it gets a proper home in a branch instead of a duplicated file. The shipping design stays safe, the exploration runs at full speed, and the two meet again in a review.
Branches turn feedback into workflow
Live co-editing is only half of collaboration; the other half is disagreement. When a direction needs to be explored without disturbing the shipping design, a branch gives it a safe home — same document, separate line of history. When it is ready, a merge with review brings it back, showing exactly what changed on each side since the fork.
It is the review discipline software teams swear by, applied to design — and it changes review culture the same way: alternatives get explored honestly because exploring is cheap, and decisions leave a trace. Combined with in-context comments and Ready-for-Dev annotations, the file itself becomes the record of how the design got to where it is.
Frequently asked questions
What happens if two designers edit the same screen at once?
Small collisions resolve instantly and predictably — everyone converges on the same result, with no duplicate copies to reconcile. For genuinely parallel directions, branch the file: each designer works in isolation, and a merge with review reconciles the results explicitly.
Can people outside the team see our work?
Yes — any design can be shared with a public view link, and viewers are always free. On paid plans you can also issue links with edit access, protect links with a password and set an expiry date — which is usually what client and stakeholder review actually needs.
Do we all have to be online at the same time?
No. Collaboration is live when you are together and asynchronous when you are not: comments and Ready-for-Dev annotations keep the context on the canvas, version history shows what changed, and branches let work continue independently.
What if someone breaks the design?
You restore it. Version history covers 30 days on the free plan and is unlimited on paid plans, so any file can be rolled back to a good state — an experiment gone wrong is a restore, not an incident.
Do viewers and stakeholders need paid seats?
No. Billing counts editors only — viewers are free on every plan, and personal drafts are free forever. A big review audience costs you nothing.