What syncs?
CoBlocks shares project edits between connected collaborators: blocks, supported sprite changes, costumes, backdrops, sounds, and project titles. You can work on different sprites at the same time.
How to collaborate
- Open a project you own and click CoBlocks beside Share.
- Invite someone, then check that they appear online.
- Make an edit and confirm the other person sees it. Keep using Scratch’s Save now and download backups for important work.
More detail & reference
Activate a project you own
A CoBlocks project has a server-side collaboration ID and links to Scratch project copies. Collaborators work through their linked copies; this is not the same as sharing your Scratch password.
- Open your own project in Scratch’s editor while signed in.
- Click CoBlocks beside Share. For a new project, allow Scratch to finish saving and assign a project ID.
- Wait for the Collaboration panel to open, then add people or copy an invite link.
What synchronizes
| Area | Implemented editing operations |
|---|---|
| Blocks | Block creation, movement, deletion, field changes, comments, variable/list events, and block sharing between targets. |
| Sprites and stage | Adding, duplicating, removing, renaming, and reordering sprites/targets, plus supported sprite property updates. |
| Costumes and backdrops | Adding and managing costumes/backdrops, with bitmap and SVG costume-update paths. |
| Sounds | Adding, duplicating, deleting, renaming, reordering, and supported sound-buffer updates. |
| Project title | Title changes are sent to collaborators through the collaboration service. |
Saving and reconnecting
Keep using Scratch’s normal Save now controls and save .sb3 downloads for milestones. Live sync, a Scratch save, and a local recovery snapshot serve different purposes.
Online editing requires the CoBlocks backend. When the editor starts, it can fetch a project snapshot and subsequent changes. During an outage, do not assume edits made independently on different machines will be merged later.
What this does not promise
- No read-only reviewer role: the access panel has an owner and collaborators who can edit.
- No published guarantee for an unlimited number of users or projects.
- No synchronized green-flag execution or identical runtime state is promised by this guide.
- No user-facing version-history browser or conflict-resolution timeline is documented in the current release.