How to organize video files before editing
How to organize video files before editing
Answer: prepare footage by separating shoots and cameras, adopting a clear naming convention, placing clips into a predictable folder layout, creating proxies or transcodes if needed, and making redundant backups. Below is a practical, step-by-step workflow you can apply to any project before you open an editor.
Why organize before you edit
Editing with unstructured media costs time and raises the risk of lost files, mismatched audio, and wasted render cycles. A short setup investment of 30 to 90 minutes for small shoots reduces friction and prevents mistakes later, especially on multi-camera shoots or when handing projects between operators.
This article focuses on practical actions you can complete before importing into an NLE: folder layout, naming, basic metadata, proxies/transcodes, and backups.
Decide a folder structure and stick to it
A predictable folder structure makes locating assets repeatable across projects and teams. Use top-level folders that separate source media from project files and deliverables.
Core folders you should create for every project: Media, Projects, Audio, Graphics, Deliverables, and Archives. For guidance on common patterns and variations, see the Folder Structures for Video Projects resource.
Example folder tree (worked example)
- ProjectName/
- 01_Raw_Media/
- Day1_CAMERA-A
- Day1_CAMERA-B
- Day2_CAMERA-A
- 02_Transcodes
- 03_Proxies
- 04_Project_Files
- 05_Exports
- 06_Archive
- 01_Raw_Media/
Establish and apply naming conventions
A stable naming convention communicates the shoot, camera, take, and date at a glance. Set the scheme before copying media and enforce it consistently across cards and drives.
Suggested naming pattern
- ProjectCode_ShootDate_CameraID_Scene_Take.ext (for example: PROJECTX_20260901_A_01_03.mov)
- Keep elements short and ordered from general to specific: project, date, camera, scene, take.
- Use underscores to separate components and avoid spaces and special characters to prevent cross-platform issues.
For deeper rules and automations that integrate with logging tools, consult the Best Practices for Naming Media Files article.
Copying media: verify, validate, and catalog
Copy media from cards to your raw media folder using a checksum-aware copier, or a reliable copy tool that verifies integrity after transfer. If you do not have a checksum tool, at minimum visually compare file sizes and counts to the source card directory listings.
As you copy, add a simple catalog spreadsheet or a log file with columns: source card ID, start/end timecodes (if available), camera, operator, and notes. This small audit trail helps later when reconciling media.
Tag or log essential metadata
- Camera make/model and lens notes
- Frame rate and resolution
- Codec and color profile
- Any sync audio or slate references
Decide proxies and transcodes
High-resolution codecs can be heavy to edit. Decide early whether you need proxies or transcodes. Create proxies when editing responsiveness is more important; transcode when you need a consistent, editable codec across clips.
Common practice is to create low-resolution proxies (e.g., 1/4 size or low-bitrate H.264/HEVC) stored in a /03_Proxies folder and linked back to the original files inside the NLE.
If you work with multiple codecs or camera profiles, transcode to a single mezzanine codec to avoid format-driven behavior during editing or grading.
See the step-by-step configuration suggestions in the Setting Up Proxies and Transcodes guide.
Short step-by-step: pre-edit checklist
- Create a project folder and the standard subfolders listed above.
- Copy cards to the appropriate camera subfolder using a verified copy method.
- Rename files according to your naming convention during or immediately after copying.
- Populate a simple log or metadata file with camera, takes, and notable details.
- Decide and create proxies or transcodes; store them in /03_Proxies or /02_Transcodes.
- Make at least two independent backups before starting the edit (local + offsite or two local drives).
- Open your NLE and import project media using 'link to media' where possible to preserve originals.
Backup and archive strategy
Backups protect against drive failure, accidental deletion, or corruption. A minimal reliable strategy is one working copy plus one or two backups on separate physical drives, with at least one copy stored offsite or in a cloud vault.
Label backup drives clearly with project name and backup date. When a project is complete, consolidate and create an archive folder that includes raw media, final project file, and exports. Refer to the Backup and Archive Strategies for Footage material for options and workflows.
Short backup checklist
- Confirm source-to-destination verification after copying.
- Create two independent backups before editing begins.
- Keep one backup offsite or in the cloud if possible.
- Label drives and include a readme with the archive explaining folder contents.
Common mistakes and how to avoid them
Experienced editors encounter recurring errors during media prep. Being aware of these prevents wasted effort.
- Mixing cameras in the same folder without camera IDs: separate by camera to simplify color and workflow.
- Using inconsistent names: adopt and enforce a single naming pattern per project.
- Skipping backups: never edit from the only copy on a single drive.
- Creating proxies without a consistent linking strategy: keep proxies in one folder and name them predictably for relinking.
- Relying on the camera's internal file structure without cataloging: maintain your log to avoid confusion over takes.
Final notes and handoff tips
Before handing the project to an editor or beginning a timeline, run a quick validation: open a sample clip, verify audio sync, check corner case codecs, and ensure proxies link back to originals. A short handoff note describing the folder layout, naming scheme, and any nonstandard elements saves time.
Consistent application of these steps will reduce friction during the edit and make collaboration predictable. When in doubt, document the exception rather than changing the established structure mid-project.
Checklist to copy and tuck in your project folder:
- Project folder with subfolders created
- All media copied and verified
- Files renamed to naming convention
- Proxy or transcode files created as needed
- Two backups completed and labeled
- Short handoff/readme file included