ClipWhat is the .logger.json sidecar?
A portable ClipLogger JSON record written beside the associated media when output is enabled. It can carry metadata, evidence, log values, markers, and ranges supported by the schema. It is not a guarantee that every catalog value or unresolved recovery entry has already been published. Preserve project and application data as part of the backup.
What's inside it?
A .logger.json document can carry clip metadata, logging values, subjects and evidence, transcript information, markers, ranges, and provenance supported by its schema. Contents depend on what has been produced and the active export settings. Do not assume every record is confirmed simply because it appears in a JSON file; inspect its state and field meaning.
Which NLE exports exist, and are they on?
The application has output paths for .logger.json and optional XMP, Resolve CSV, FCPXML, and ALE. Check Sharing & Privacy and the export command for the formats enabled in your workflow. A format's existence does not establish that every custom field, range, or marker survives in every NLE version. Validate a small receiving-project import first.
When are sidecars written?
Writing depends on the format switches and the operation being performed. Confirmed logging and explicit export can publish portable metadata, while analysis also keeps records for review and recovery. With JSON output disabled, do not expect .logger.json beside the media. Keep app and project data backed up when portable copies are absent or incomplete.
Can other tools read the format without ClipLogger?
Yes. The JSON is readable without running ClipLogger, and filenames remain ordinary filenames after you stop paying for hosted processing. Other applications need to understand the schema or use a supported export such as XMP, CSV, FCPXML or ALE. Each output carries different fields, so check your intended handoff. You can keep using the completed log in ClipLogger’s free base app.
What happens if I stop using ClipLogger?
Your original media remains in ordinary storage locations. Preserve the sidecars, project documents, relevant application data, and any handoff exports before removing the app. Open formats can be inspected independently, but another application must understand or map their schema to use every field. Readable JSON is not automatic compatibility with all software.
What survives moving footage to another drive or machine?
Copy the media with its sidecars and project records, then reconnect it and inspect the resulting log. Preserve the original copy until the new location has been verified. A project can contain offline references, so a visible clip row does not by itself prove that the underlying media moved successfully.