Use Design Version History and Branches

Design saves every change as you work. History, in More in the page bar, lists the file's Versions and Branches. To keep the file as it is now, for example before a review or handoff, enter a Version name and select Name Version.

Restore beside a version needs edit access to the file through its team. Restoring a Main Version creates a new current checkpoint. Versions created after the restored point remain in history. Branch Versions are named from the Branch and are not restored onto Main.

In the mobile app, open the Design file and choose Version history from its action menu. It lists saved Main versions, newest first. Editors can name the current version, and people who manage the file can restore an earlier one. Changes made since the last saved version are replaced by a restore, so name a version first if you may need them. If the Design changed after you opened the history, the app refuses the restore and reloads the list.

Create a Branch for a redesign or design-system change that must not affect Main. Open it from the Branch list. Its operations, comments, presence, and Versions remain separate. Update from Main incorporates changes to independent object properties. If Main and the Branch changed the same stable property, Magpie reports the conflict and leaves the Branch unchanged. Successful updates enter the Branch operation stream, so other open Branch tabs receive the same changes. A merged Branch remains available to inspect but is read-only.

Before merging, review the changed objects. Merge, in History, needs edit access to the file through its team. Magpie keeps versions from before and after the merge and marks the Branch as merged.

Changes made while offline stay in the browser and are sent again when you reconnect. While changes are waiting, Recovery appears in More, in the page bar. It can try again, download the waiting changes as a JSON recovery file, or discard them. Download the recovery file before discarding changes you may need.

The mobile app's Branches action lists active and merged Branches. Editors can create a Branch and update one from Main; people who manage the file can merge a Branch that is up to date with Main after confirming. If updating finds conflicting changes, the Branch is left as it was. Conflicts are resolved, and Branches edited, in the website editor.

If a restore or Branch merge does not produce the Design you expected, download any Recovery file first, then Contact support.