ClipKeep more than the camera files
Back up the media, its camera companion files, your written sidecars and project documents. ClipLogger’s catalog can also hold logging decisions that have not been written beside the footage. Keep that data too, especially when sidecar output is off or a write needs attention.
Know where the app keeps its records
| Location | What to preserve |
|---|---|
| Your media folders | Originals, required camera companions and enabled metadata outputs |
| Project locations | Project documents saved on volumes or in the app’s folders |
~/Library/Application Support/ClipLogger/ |
App records and configuration |
~/Library/Caches/ClipLogger/vault-dbs/ |
Catalogs for startup-disk, network-share and other applicable libraries |
<volume>/.cliplogger/ |
Catalog data on applicable local external volumes |
A folder named Caches can still contain your only copy of a logging decision. Quit ClipLogger and any command-line writer before copying database folders, and keep their contents together. Test a small restore while the original library is still available.
Reconnect an offline library
A clip may remain listed after you disconnect its drive. Reconnect the correct volume and confirm the media plays before attempting a rename or write. A visible thumbnail alone does not mean the original is available.
Check that sidecars were saved
If ClipLogger reports a problem writing the log, inspect the named media and the recovery message. Do not substitute a different file with the same name.
Where the app offers Keep library copy, the value remains in the catalog; that does not finish the sidecar write. Keep the catalog backed up until the record has been saved where you intend.
Keep rejection separate from deletion
Rejecting a clip records an editorial decision. Recycling or permanently deleting it changes files. Check the selected originals and your verified backup before removing anything permanently.