← Back
Team Delegation, Outsourcing, Remote Editors & Production Pipelines

A remote editor downloads proxy files into a different folder hierarchy than the project expects, causing automatic relinking to fail even though every proxy exists.

Problem

A remote editor downloads proxy files into a different folder hierarchy than the project expects, causing automatic relinking to fail even though every proxy exists.

Solution

Root Cause / Diagnostic:
NLE automatic relink engines match relative directory paths and folder nesting structures. When an editor moves files from nested camera subfolders (e.g., Card_A/Clips/) into a single flattened folder, the batch search fails to resolve media automatically.

Actionable Fix:
1. Enforce Exact Directory Mirroring: Instruct remote editors to maintain the full root folder hierarchy without altering subfolder naming or moving files out of card folders.
2. Utilize "Search Subfolders" Relink Dialogue: In the NLE relink panel, disable "Exact Match Path" and enable "Search Subfolders" targeting the parent proxy directory.
3. Package Proxies in Pre-Structured ZIP/Tar Bundles: Distribute proxies inside archived containers that unpack into the exact expected directory tree on destination machines.

Pro Tip:
Distribute proxy packages as .zip or .tar files rather than loose folders so that cloud downloading preserves the exact folder tree without flattened extraction.