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. Magpie asks before it restores, and waits until your latest changes are saved. The Design as it was just before is kept as a version named Before restore, so a restore can be undone by restoring that version. Restoring a Main Version creates a new current checkpoint, and everyone with the file open sees the restored Design. 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. The Design as it was before the restore is kept as a Before restore version. 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. If a version was restored on Main, or another Branch was merged into it, after the Branch was created, Update from Main leaves the Branch unchanged and says so: create a new Branch from Main and make the Branch's changes there. 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. It waits until your latest changes are saved. Magpie keeps versions from before and after the merge, marks the Branch as merged, and shows the merged Design to everyone with Main open.

Changes made while offline stay in the browser and are sent again when you reconnect, from whichever tab of the Design you open next. Each tab keeps its own waiting changes, and text you were typing is kept when the page closes. 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.

When a change can never be saved, for example because it would take the Design over its size limit, Magpie says so and keeps saving your other changes; Recovery keeps a copy of the refused change. When the Branch you are editing is merged, or your edit access ends, the page turns Read only and Recovery keeps the changes that were not saved.

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.

Ask Magpie support

Send Magpie staff a question about anything this article does not answer.