Problem
A contractor's local cache retains deleted proxy files after the project is closed, leaving embargoed footage recoverable on the workstation.
Solution
Root Cause / Diagnostic:
Deleting a project file or raw footage does not automatically purge background proxy files, audio waveform peaks, and optical flow cache files. Non-linear editing software stores generated media in separate system cache directories that persist indefinitely on local drives.
Actionable Fix:
1. Configure NLE cache directories to dedicated project-specific folders on an external drive rather than default global system app data paths.
2. Execute a post-project cache purge using Premiere's 'Delete Unused Media Cache' or Resolve's 'Delete Render Cache' utility.
3. Run disk sweeping tools (e.g., DaisyDisk on macOS or TreeSize on Windows) to verify that all proxy directories (`/Adobe/Common/Media Cache Files`) are fully wiped.
Pro Tip:
Set your NLE media cache location to a dedicated, encrypted scratch partition so formatting that single volume at project close instantly eliminates all cached proxy assets.
Deleting a project file or raw footage does not automatically purge background proxy files, audio waveform peaks, and optical flow cache files. Non-linear editing software stores generated media in separate system cache directories that persist indefinitely on local drives.
Actionable Fix:
1. Configure NLE cache directories to dedicated project-specific folders on an external drive rather than default global system app data paths.
2. Execute a post-project cache purge using Premiere's 'Delete Unused Media Cache' or Resolve's 'Delete Render Cache' utility.
3. Run disk sweeping tools (e.g., DaisyDisk on macOS or TreeSize on Windows) to verify that all proxy directories (`/Adobe/Common/Media Cache Files`) are fully wiped.
Pro Tip:
Set your NLE media cache location to a dedicated, encrypted scratch partition so formatting that single volume at project close instantly eliminates all cached proxy assets.