Pages, snapshots, backup & sync

Save whole desktop arrangements, travel back in time, and carry your setup between machines — without accounts or servers.

Desktop pages (layouts)

A page is a named saved arrangement of all your pickets. Save the current arrangement in Settings; Load switches live — windows rebuild in place, no restart. A page name keeps letters, digits, spaces, - and _; saving tells you which name it used if anything else had to go — and refuses when the name it would have to use is another page's, since a save lands in place and nothing takes it back (saving under a page's own name is still how you update it). A read-only session — the one the warning box at launch describes — refuses to save a page at all, so what it shows can never replace a page you saved; it refuses to rename or delete a page, bind a virtual desktop or restore a snapshot too, and files no snapshot of its own (Save layout snapshot, or the palette's snapshot, says “Snapshot not saved” instead). Rename edits a page in place — the file moves and every binding, time rule and cycle position moves with it, while a name another page already uses is refused rather than overwritten, even if it was saved while the rename was running. Case-only changes work with non-ASCII names too, such as übung → Übung, when Windows confirms they name the same file. Switching is one gesture from anywhere: the tray's Pages ▸ submenu, Ctrl+Shift+PageDown/PageUp cycling (the page name flashes top-center while you browse; only the page you settle on loads), page <name> in the command palette, or --page "<name>" from a launcher. Loading a page files a snapshot in the time machine first — at most one every two minutes, so cycling through pages keeps the snapshot from before the excursion instead of flushing the ring. A page carries the arrangement only — pickets, positions, what is filed where, its page programs. Loading one never changes your settings: rules, index roots, ignore lists, virtual-desktop bindings and time-of-day rules stay as they are now, not as they were when the page was saved. The ✕ next to a page moves its file to the Recycle Bin — never a hard delete — so a mis-click is undone from there, and any virtual-desktop binding or time-of-day rule that pointed at that page goes with it (the toast counts them) — including one that spells the page differently, since work and Work are one page on disk: a rule naming a page that is gone can only fail silently on every desktop switch. If a page ever fails to load — deleted outside Picketdesk, or unreadable — the switch says so instead of doing nothing, whether you asked for it or a rule did.

The page you last loaded is marked: a small loaded badge on its row in Settings, and a tick beside it in the tray's Pages ▸ submenu. Several of the ways a page switches need no gesture at all — a time-of-day rule, a virtual-desktop binding — and each announces itself only in a toast that fades, so the mark is what still tells you which layout you are looking at. It says “last loaded”, not “current”: nothing is marked until you load a page, a restart clears it, and anything you move afterwards is not written back to the page — save under the same name to update it. Renaming the marked page carries the mark to the new name; deleting it takes the mark away.

Time machine

An automatic snapshot of your workspace is taken on every launch and before anything reshapes your desktop; the newest 10 are kept, and the Settings timeline labels each one with what caused it — launch, page-load, monitor-change, organize, pre-restore, pre-import, manual. A snapshot is captured before a monitor change rewrites the layout — written only if something actually moved, at most one per two minutes, so a flapping dock cannot fill the ring with copies — and before an Organize sweep, which can run on a schedule with no gesture at all (Ctrl+Z does not survive a restart; the snapshot does). The tray menu also has Save layout snapshot and Restore last snapshot for quick manual checkpoints. Snapshots, pages and docking profiles are written to survive a power cut — complete or not at all, never truncated — and Restore last snapshot skips a snapshot it cannot read and takes the next-newest; when none reads, or there is none yet, it says so instead of doing nothing.

Export / import backup

Settings → Export backup… writes a single picket-backup.json containing the workspace and all pages. If any saved page is unreadable, locked or malformed, the backup stops and names it. Existing backup and snapshot exports are preserved; a numbered filename is chosen when needed. Before importing, a full copy of the previous workspace and pages is saved in the configuration folder's import-backups directory. Import stops before changing pages if that copy cannot be written. A pre-import snapshot also provides a quick return to the current layout; use Import… with the full copy to restore saved pages too. A page-write failure stops the incoming workspace from being applied and reports pages already written, failed and skipped, with the recovery-copy location. Individual page writes are atomic; a whole import is not one disk transaction. Full pre-import copies are kept until you remove them. If two imported page names resolve to the same Windows filename, such as Work and work, the first processed page is kept and the duplicate is skipped. Import can still replace a previously saved page with the same name.

A backup is untrusted input, so the screening drops anything in it that would act on its own: command and move: steps, self-clean policies, page programs, time-of-day and virtual desktop pages (they load a page by themselves), global hotkeys, Start with Windows, mirrored folders (a portal comes back as a plain picket), extra index roots, and any item on a network path — a \\server\share item would be probed and its icon fetched with no click. A reminder dated before 1970 or in the year 10000 or later is dropped too. The message after the import names each kind it did not bring in and how many — for most backups just “Not brought in, as with every backup: Start with Windows — switch it on in the tray if you want it” — so you can set up again what you need. Pickets and the files in them, notes, tags, reminders, rules and saved pages come back. Individual picket styles travel separately as .picketarea templates.

Quitting from the tray also saves a backup in the same format, in the default data folder's backups folder (%APPDATA%\com.picketdesk.app\backups, also when the configuration lives in another folder, so a shared folder never holds them; on a network where your Windows profile roams between PCs, %APPDATA% roams with it). The newest 10 are kept, and only files named the way Quit names them are ever deleted. Settings → Quit backups → Open backups folder shows them; Import… restores one.

Settings → Recent import and recovery copies keeps the latest import result across restarts and lists the full pre-import copies that are still there. Open recovery folder finds them and Import… restores one. Copies are kept until you remove them. A damaged or temporarily unreadable import report produces a warning while the recovery copies stay listed, and Open recovery folder stays available even if the listing itself fails. A backup or snapshot you pick is limited to 64 MiB; invalid input is refused before it is applied. Settings also reports a failed disk save and keeps your unsaved edits for a retry.

Keep your configuration in another folder

Settings → Move configuration to another folder… moves all of Picketdesk's configuration into a folder you choose — for example one that OneDrive or Dropbox backs up — so your layout, rules and pages are kept there. No accounts, no servers.

One PC at a time Picketdesk keeps one layout file and saves it whole, so two PCs using the same folder overwrite each other: whichever saves last replaces the other's pickets, what is in them, pages and settings, without notice. (Where each picket and loose icon sits, and each PC's own settings — Start with Windows, hotkeys, folders to index, virtual desktop pages, docking profiles — each PC keeps for itself, so those are not overwritten.) That is not supported. To copy a layout to another PC, use Export backup on one and Import on the other (see Backup above). Every save records a random id of the PC that made it, and a launch that finds the layout was last saved by a different PC says so in a warning box — every time it happens (after reinstalling Windows or Picketdesk you will see it once).

Relocation saves the current workspace and verifies every workspace, backup, page and snapshot copy before changing the redirect and restarting. If a step fails, the message names its path and the original configuration stays active. Source files remain in place; a failed transfer may leave an incomplete destination for a later retry.

A folder that already holds another Picketdesk configuration is never overwritten. Picketdesk asks instead, naming the folder and what is in it: Yes switches this PC to that configuration and restarts — writing nothing into the folder — which is what you want when you reinstalled Windows and are pointing Picketdesk back at your own folder; No (the default) leaves everything as it is. This PC's own layout stays saved where it was either way.

Anyone who can write that folder can change what is in it, so a few things that act on their own need this PC's approval before they run here: a page's programs, a picket's self-clean policy, a zone whose steps include a shell command or a move off this PC (the first drop asks, in a warning box that lists every step), and the folders a portal picket mirrors or Settings indexes. This PC does not read such a folder until you allow it: the portal picket offers Allow on this PC…, a drop onto it asks first, and folders to index are asked about the next time you save Settings. A notification at launch names the folders this PC is not using. Everything you set up on this PC is approved as you make it, and the move itself approves everything in the workspace on screen at that moment. It does not look inside saved pages or snapshots, so a portal, zone or self-clean policy that lives only in one of them is treated as having arrived through the folder the first time you use it after the move. A configuration that was already in another folder before this version asks (or pauses) once for each of these on each PC. The approvals stay on this PC.

If that folder is not reachable when Picketdesk starts — a drive not plugged in or not yet unlocked, a cloud folder that was moved or has not finished syncing — Picketdesk waits a few seconds for it, then starts empty and read-only and says so in a box. It never falls back to an older copy of your configuration and saves nothing that session, so nothing is lost: make the folder available and restart Picketdesk.

What belongs to each PC deliberately stays behind on it, in its own workspace.local.json: where its pickets and loose icons sit on its screens, its own settings, and above all the record of which files that machine tucked into a picket. That record is what every recovery path reads to give those files back, and it means nothing on another machine — so sharing it would let whichever PC saved last make the other one's tucked-away files look like files you hid yourself. The shared configuration no longer carries it (only a claim a start could not yet judge stays there, until a start that can), and each PC acts only on its own claims: the ones its local record names, or a file that carries Picketdesk's marker on its own disk. A claim the other PC made — even on a same-named file you hid yourself on this one — is never re-hidden or un-hidden here automatically, on Quit or by the watchdog. --restore-icons, which you run by hand, still reads the shared copy whole.

Nor does a PC move the other PC's pickets onto its own files. A layout last saved by another PC is never mistaken for a Desktop folder that moved, so when the two PCs' Desktop folders differ (another user name, OneDrive's folder backup on one PC only), the other PC's items, tags and notes stay keyed to its Desktop instead of landing on same-named files here — a CV.pdf on this Desktop is never filed into the other PC's picket and hidden. The same goes for a layout saved by an older version, which does not record which PC saved it: an old Desktop folder is re-linked from it only when this PC's own records vouch for it (its local record names a file there, or a file that moved from it carries Picketdesk's marker). If this PC's local record cannot be read at that start, Picketdesk waits a few seconds for it; if it still cannot, an old folder that only the record could vouch for is left exactly as it is until a start that can read it — nothing is moved from it onto same-named files here, and nothing it holds is given up. One gap remains: if a folder a claim names cannot be reached at all when Picketdesk starts on this PC (a Desktop on a network share that is still offline), the claim cannot be judged then. If that folder comes back while Picketdesk runs, Quit or taking the item out of its picket may still un-hide its file that session, but the claim is never re-hidden and never recorded as this PC's own, so the next start judges it again. The same goes for every shared claim at a start where this PC's own record is there but cannot be read (another program holding it).

An existing local recovery claim survives an unplugged or unavailable root. Reconciliation or confirmed recovery retires it; an unsuccessful existence check alone does not.

If this PC's local layout needs recovery, startup, autostart repair and Desktop backup export use its latest saved settings and positions when this PC last saved the shared workspace. An older local backup cannot replace them. Migrated docking profiles keep their original dates, so the newest matching monitor layout still wins.

If two PCs use one folder anyway Your files stay safe — each PC only ever restores what it hid itself, as described above. The arrangement does not: besides the last-save-wins overwrite, a picket holds files by path, so unless the Desktop folder itself is synced as well (OneDrive's “Back up your Desktop” for the same account on both PCs), the PC that scans next finds the other PC's files missing — when both sign in under the same user name, and always for C:\Users\Public\Desktop — and drops them out of their pickets together with their tags and notes. The files themselves are never touched.
Reminders in your calendar Settings can export all pending item reminders as an .ics file — subscribe to it from any calendar app.