Skip to content
0.15.2 betaSign inPrivate beta
Docs

DocsOrganise and back up

Backups

A backup copies one library onto another, such as your travel SSD onto your home NAS or a Google Drive library, as a pair Stow remembers. Choose Back Up Now… on a library, or add one under Backups in the sidebar.

On this page

What a backup does

A run copies only what’s new or changed on the source, keeps the folder structure, and checks each file against the original. The source is never changed or erased. The sidebar shows roughly how far behind each pair is, even with a drive unplugged.

Edited files

When a file at the backup has changed (you edited a photo in place), Stow never deletes the old version. It either moves the old version aside, into a hidden replaced folder on the backup drive, or keeps both. Each case is listed in the backup’s receipt.

Backing up to Google Drive

A library on Google Drive can be a backup’s destination, never its source: a backup reads from a library on this computer. Each file is uploaded to the same folders it’s in on the source, and Stow checks Drive’s checksum of every upload against the file. Several files are sent at once, each in large pieces, so a fast connection is put to use, and an upload that’s interrupted carries on where it stopped.

  • Changed files. When a file you edited has an older version on Drive, the old version is moved into a hidden .stow/replaced folder in the Drive library (.thebigdumper/replaced for backups made by older versions of Stow), never deleted, and listed in the backup’s receipt.
  • A full Drive. When Google Drive is full, or its daily upload limit (750 GB) is reached, the backup pauses rather than failing the rest. Free up space or wait a day, then choose Resume.
  • Sign-in and internet. The backup needs an internet connection and Stow signed in to Google Drive (Settings › Google Drive).
  • Erasing a card. A copy on Google Drive doesn’t count towards the copies a card needs before Stow will erase it, since Stow can’t read it back from there.
  • Deleted on Drive. Stow goes by what it uploaded, so a file you delete on Google Drive isn’t noticed or uploaded again.

Importing and backing up to Frame.io

A folder in a Frame.io project can be a location you import into and a backup’s destination, never a source. Sign in under Settings › Frame.io, then choose Add Frame.io folder… (an account, a workspace, a project, then a folder).

  • Size-checked, not verified. Frame.io doesn’t return a checksum, so Stow can only confirm that each upload finished at the same size as the original, not that every byte matches. It says “Uploaded, size checked”, never “verified”.
  • Erasing a card. A Frame.io copy never counts towards the copies a card needs before Stow will erase it. Keep a copy on a drive for that.
  • Which accounts. Only Frame.io accounts on the current version of Frame.io, signed in with an Adobe ID, work. A company or school Adobe account may need its admin to allow Stow first.
  • Signing in. Choose Sign In… and Adobe’s sign-in opens in your browser. When it’s done, your browser asks to open Stow: allow it, and Stow comes back signed in. Choose Cancel in Stow if you change your mind.
  • Signing in again. Adobe’s sign-in for a desktop app lasts about a day. Settings › Frame.io says until when. When it ends during an import or backup, the run pauses with nothing failed and says so: choose Sign In Again on the run, and it carries on where it left off. A backup won’t start while you’re signed out.
  • Stopping part-way. Pausing a run stops between parts of a file, and Resume carries on from there. A file cut off by quitting Stow starts again from the beginning the next time, and the unfinished upload is removed.
  • Changed files. When a backup replaces a file, the old version is moved into a .stow/replaced folder in the project, never deleted. Everyone on the project can see that folder.
  • A full account. When the Frame.io account runs out of storage, or Frame.io asks Stow to slow down, the run pauses rather than failing the rest. Free up space or wait, then choose Resume.
  • A failed check. An upload Frame.io says failed, or that arrives at a different size, is removed and listed as failed, so nothing half-uploaded is left looking finished.

Seeing what’s on Frame.io and Google Drive

Choose a Frame.io or Google Drive library in the sidebar, or Browse in Settings › Frame.io or Settings › Google Drive, to see what’s in its folder: folders first, then files with the thumbnails Frame.io or Drive made, sorted by name or date. Click a folder to go into it; Back returns. Choose a file to see its size and date and, when Stow sent it, where it came from (“From Smith Wedding, imported 12 Sep 2026”) and the original file’s path.

  • Read-only. Stow never moves, renames, deletes or uploads anything from this view. To work with a file, double-click it, or choose Open in Frame.io (Open in Google Drive) in the toolbar or on the file’s menu.
  • What Drive shows. Google Drive lets Stow see only the files and folders it put there, so files added on Drive by other means don’t appear.
  • Signed out or offline. Stow shows its own record of what it sent: by shoot or album and date, with file counts, sizes and the last upload. Sign in, or choose Try again once you’re back online.

Backups and a shoot’s copies

A shoot’s extra copies are made per card, as part of the shoot, and count towards erasing the card. A backup pair copies a whole library whenever you run it. Use both: copies before you leave the shoot, a backup when you’re home.