StageDesigner

Cloud saving, local copy and version history

How autosave works, what the save states mean, how to resolve a version conflict, mark a version and restore an earlier state of the project.

4 min read
Documentation contents ▾

StageDesigner projects are saved in the cloud, on the Pro plan too. There is no separate save to disk: every change goes to the cloud automatically, and a copy of the project stays on the computer in case the network is down.

Autosave

  • Changes are sent 1.5 s after your last edit, and during continuous work at least every 20 s.
  • Saving also starts when you close the window, switch to another project and when the network comes back.
  • ⌘S (Windows: Ctrl+S) or File → Save Now sends the changes right away and shows a confirmation with the save time.
PawełOlaYouIn projectOLPWYOUVersion historyv18Paweł · lightingv17AI · seatingv16Ola · barsv15You · stage
The project lives in the cloud: you open the same data in the app, in the browser and as a team.

Save states

The save state is shown next to the project name in the top bar. Clicking the state runs the action from the table.

StateMeaningClick
Saved 14:32Everything is in the cloudOpens Version History
Saving…Autosave in progress(no action)
Sending 3 changes…Sending pending changes(no action)
Offline · saved locallyNo network; the changes are on this computerRetries the upload
Version conflictSomeone saved a newer versionOpens the decision window
Cloud storage fullStorage used up; the changes are localRetries the upload
View onlyRead-only role or version preview(no action)
Not saved · retryAnother save errorRetries the upload

Local copy and working offline

The app keeps a copy of the projects you open on the computer. Without a network you keep working, and the changes wait in a queue and are sent by themselves once the connection is back. Projects with a copy have the Available offline badge on the start screen.

Version conflict

A conflict happens when someone on the team saved the project before your changes reached the cloud. The Newer version in the cloud window shows the author and a description of their changes. Your changes are safe on this computer.

Keep both versions
Recommended. Your scene is saved as a new version, and the team changes stay in the history.
Compare
A table with the number of screens, furniture items and solids in your scene and in the cloud.
Overwrite cloud with my version…
Your version replaces the team changes; their version stays only in the history.
Discard my changes…
The local changes are lost permanently, and the version from the cloud is loaded.
Decide later
Closes the window; the conflict stays marked in the save state.

Version history

Open the Version History panel from the dock, with ⌥H (Windows: Alt+H), from the project menu or by clicking the Saved state. Versions are grouped into work sessions and show the author, time and a description of the changes.

  • Filter: All, Marked or a chosen person.
  • Flag icon: a version marked with a label. The note restore or from file says where the version came from.
  • Version menu: Preview, Restore…, New Project from This Version…, and for marked versions Change label and Remove label.

Preview and restore

  1. In the Version History panel, choose Preview next to a version. The scene shows its state in read-only mode, and a preview bar appears above the scene.
  2. Optionally click Compare with current to see the differences in the number of screens, furniture and solids.
  3. Click Restore this version and confirm. The restored version becomes the current one, and the previous state stays in the history.
  4. To leave without changes, click Back to current or press Esc.

Marking versions

  1. Press ⇧⌘S (Windows: Ctrl+Shift+S) or choose Mark Version… from the project menu or the File menu.
  2. Enter a label, for example "Client version v2".
  3. Click Mark version.

How many versions are kept

All automatic versions from the last 24 hours are kept. Older ones are thinned out: up to 30 days, the newest version from each hour is kept, up to a year one from each day, and after that one from each week. A project keeps at most 200 automatic versions. Marked versions, restores and versions from a file are not deleted. The history does not count toward your cloud storage.

Backup on disk

Save the project file to disk with File → Export → Backup (.stageview)…. Load such a file back into the cloud with File → Import → Project from .stageview File to Cloud…. Teamwork and roles are described in Teamwork.

Did not find the answer?
Describe the problem and we will reply with a solution or add an article.