Skip to content

How storage works

The storage card on the device settings page shows the quota as a bar:

  • Purple: stored footage inside the window.
  • Amber: protected footage. The cloud never removes a protected clip to free space.
  • Red: over quota. The bar clears as the oldest unlocked footage rotates out.

A device with no plan has no quota at all. The storage card says “No cloud storage allowance” instead of drawing the bar, because the cloud keeps nothing for that device. Subscribing starts the rolling window immediately.

When new footage needs room, the cloud drops the oldest unlocked clips first: clips that don’t belong to a drive (the least useful, they have no map or timing), then the oldest drives’ clips. Some further rules apply:

  • Protecting fresh uploads is opt-in. By default, new footage can be recycled like any other clip. Turn on Protect recent uploads in the device settings: footage uploaded in the last 12 hours is never removed to make room for ordinary new footage. Unprocessed videos are always protected, whatever the setting says. If the storage fills up with footage this fresh, the device may go over its quota for a short time and recycles the oldest processed footage when processing completes. Protected footage from the camera’s incident folder is the other case that always gets in, because the camera keeps its protected files read-only.
  • Removed clips are archived first. A drive’s clip only leaves storage once its archive has been saved. If the archive can’t be saved at that moment, the clip stays and the new upload waits.

The line “Oldest footage goes back to…” marks the oldest playable footage. When the bar is full, new uploads replace the oldest unlocked clips.

When the rolling window removes a clip, the drive it came from remains. The trip keeps its map, timing, and data, and plays from the archive. The archive keeps the drive until you delete it yourself.

See Protected and deleted clips for how to keep a clip in the high quality window.

A cloud device can also mirror uploads to your own S3-compatible bucket. The cloud stays the primary destination. The mirror only takes a copy. See S3 mirror storage for the setup and the dashkeep.dat rule.