Back up to the cloud and work on two machines

Sheet G-111 · from the in-app Guide · updated 2026-08-31

01Turn it on, once

Cloud backup is off until you say otherwise. The switch lives in Settings → Autosave & backup, in the CLOUD BACKUP group, and the moment it goes on netmap backs up every show already on the machine plus your library — equipment definitions, faceplate photos, VLAN and titleblock defaults. From then on each save rolls to your account on its own; saves never wait on the network, so nothing you do gets slower.

Only saved work travels. The backup reads the show file, so if autosave is off (the default) your other machines see what you last pressed Save on — the pane says so and offers to turn autosave on.

02The second machine receives

Activate the tour laptop on your license, switch cloud backup on, and netmap notices this machine has nothing yet — so instead of pushing an empty library at your account, it offers to bring your workspace down: every show plus the library, in one pass. It only adds and updates; nothing already on the machine is deleted. The same button lives in Settings whenever you want the whole account pulled onto a machine.

03Two machines, one show, no guessing

Open a show while a newer copy sits in your account and a strip appears under the header: Front of House saved v7 2 hours ago · this copy is v5 — with Pull it over and Keep this one. netmap asks the same question when the app launches, when you come back to the window, and every few minutes while a show sits open. It never blocks you and never picks a side: pulling takes the cloud copy, keeping pushes yours up as the new latest, and either way the other version stays in history.

Machines go by name — each computer's own network name out of the box, or whatever you type in Settings. With three machines on one license, knowing whose copy is on offer is the difference between a decision and a coin flip.

04Twenty versions deep

Cloud backups… in Settings lists everything in your account: each show and the library row, with size, when it last changed, and — once there is more than one — a version dropdown. A version is one save that reached the cloud. Pick v6 of a show that went wrong on v7, click Restore, and that copy is written over the local file (a rolling backup of the file is kept). The same versions are on your account page as downloads, so a show can outlive every machine that ever held it.

05When both machines edited

If two machines both saved the same show, the second push is refused rather than crossed — the conflict lands as a row in Settings naming the show, with Keep mine and Take cloud. Until you choose, that show's backups wait (every later save queues behind the same question), and the sync chip in the header reads Sync paused so the wait is visible. Whichever copy you do not pick stays in the version history.

06The chip that tells the truth

Next to Saved in the header sits the sync chip: Backed up with the time of the last backup, Backing up… while a round is in flight, Sync problem when an upload failed (it retries on its own every couple of minutes), and Sync paused when a conflict or a lapsed license is holding things. Local saves and cloud copies are different promises — the chip is the second one, and clicking it lands on the pane where everything above lives.

Cloud backup is included with netmap Studio. Your shows are readable by you and the operator only — never published, never shared.