Collaborating

Multiplayer, comments, version history and sharing.

Sharing a file

Share in the top bar. Invite people by email, or set general link access so anyone with the URL can open it. A file's URL is the file — the same link opens it for everyone, and the person you send it to lands on the same canvas you're looking at.

Roles decide what someone can do: edit, comment, or view.

Editing together

Everyone in the file appears as a cursor with a name, and their selections are outlined in their color. Cursor positions are interpolated between updates, so movement looks smooth rather than teleporting.

  • Follow — click someone's avatar to ride their viewport
  • Spotlight — ask everyone else to follow you
  • Emotes — a quick reaction over your cursor
  • Ninja mode — hide your presence when you want to look around without an audience
  • Private layers — work that stays local to you until you're ready to show it

Edits merge rather than overwrite, so two people working on different parts of a frame don't clobber each other.

Comments

Leave a comment on a layer · 0:05
Description

A landing page in Design. C picks the comment tool; a click on the hero heading places a comment there and “Can we try a shorter headline?” is typed and posted with Comment. A pin marks the spot.

C places a comment: click where it belongs, type, and click Comment. It anchors to the canvas — or to a layer, so it moves when the layer does.

Threads take replies, reactions and @mentions, and resolve when they're dealt with. The comments panel lists everything in the file with filters, and mentions reach people through notifications.

Version history

Every file keeps its history. Open it from the file menu and scrub back through the timeline to see what changed and when, then restore a point or copy something out of it.

Named versions mark the moments worth finding again — "sent to client", "v2 sign-off" — instead of hunting through timestamps.

History is a session: editing is suspended while you're browsing it, so nothing changes under you.

Branches

A branch is a copy of the file you can work in without disturbing the original — try a different direction, then merge it back or throw it away.

Teams and projects

Files live in projects inside a team. A personal team is a real team, so every file belongs somewhere from the moment it's made. Folders organise projects; permissions can be set at any level.

Working offline

The file you have open keeps working without a network — see your account for exactly what does and doesn't.