FILE OPERATIONS · 7 MIN READ
How to move large property-video files from photographer to editor
A transfer progress bar reaching the end does not prove the editor received a complete, usable source set. Large-video reliability comes from a manifest, an agreed transfer path and a receiving check.
QUICK ANSWER
Prepare large property-video handoffs by grouping files under the correct job, preserving original card structure when the editing workflow requires it, recording expected folders and file counts, and using a transfer method that supports the team’s file size, connection and access needs. The editor should explicitly confirm receipt and integrity before the photographer clears working media. Use proxies only through an agreed workflow that keeps them linked to the originals.
Prepare the source set before transfer
Confirm the job ID, property, ordered video service and capture groups. Preserve metadata and folder relationships required by the camera format or editing workflow; do not rename or flatten media blindly.
Create a simple manifest with the expected folders, file counts and any known exception. Keep audio, aerial footage and supporting assets clearly identified when they are part of the order.
| Manifest item | Question | Receiving check |
|---|---|---|
| Job identity | Which property and service is this? | Matches the editor assignment |
| Source groups | Which cameras, cards or operators contributed? | All expected groups exist |
| Integrity evidence | What counts or checks are recorded? | Transfer matches the manifest |
| Exceptions | What is missing or unusual? | Editor acknowledges before work |
Choose the transfer path for the real constraints
Evaluate file volume, upload and download conditions, required access control, transfer resumption and the editor’s working environment. A cloud folder may suit one team; an approved physical-drive handoff may suit another. Follow the studio’s security and retention requirements.
Start early enough for verification. Do not promise an edit start based only on the estimated upload completion time.
Use proxies only with an explicit relink plan
Smaller proxy files can help an editor begin or work across a limited connection, but only if filenames, timecode and folder structure reliably connect them to camera originals. Document who creates the proxies and who performs the final relink and export.
Do not discard or alter originals after proxies are made. If the team has not tested the relink workflow with its editing software and formats, test a representative job first.
Close the handoff with receipt and backup
The editor checks the received structure against the manifest, opens representative clips and reports corruption or missing groups. The photographer retains the working copy until the studio’s handoff and backup policy says it is safe to clear media.
Record receipt time, editor, storage reference and exceptions on the job. That evidence separates a slow transfer from a missing-source problem.
- Confirm every expected capture group.
- Open representative media before declaring receipt.
- Keep an exception owner and next check time.
- Clear cards only under the documented policy.