How to organize footage for editing

One project gets one root

In-house creative and video teams do not finish one edit and stop. They cut many projects, often with more than one editor, and the footage lands on more than one drive. The habit that still works for a single cut is one project root: a single folder that holds everything for that job, and nothing that belongs to the next one. Name the root for the project. A folder named for the person who started the edit is useful for a week. The project name is useful next year, when someone else has to open it.

That root is the unit you can copy, hand to another editor, or set aside when the cut is done. If camera originals live in one place, the project file on someone's desktop, and the exports in a downloads folder, the job has no root. The next person cannot tell which files belong together. Make the folder first, then copy into it. Do not start the edit from the card, and do not start it from a folder that already holds other projects.

Keep originals, proxies, and exports apart

Camera originals, separate audio, graphics, proxies, the project file, and exports are different files. They go wrong in different ways when they share one pile. A proxy that sits next to a camera original with a similar name is how an editor relinks the wrong clip. An export dropped into the camera folder is how a graded cut gets treated as the master. The camera original is the file you can return to. A proxy is a lighter copy for playback and for the cut. An export is a new file the edit made. They can share a subject and a duration and still be different files.

Keep the camera folder as the place the cards were copied, and leave it alone once the copy is checked. Do not grade in that folder, and do not overwrite a camera original with an export that has a cleaner name. Proxy files for footage on a NAS explains why the lighter copy is not the master. Finding duplicate video files is how you tell an exact copy from a file that only looks related, once exports and originals share a drive.

Put the date first at ingest

Name things when the footage arrives, not after the cut has collected nicknames. Put the date first, year then month then day, so a list of folders sorts into the order the work happened. A card folder can read 2026-03-14_interview_maya. A file the team names, such as a recorder file or a graphic, can carry the same date and the same subject. Camera clip names are a separate case. Many cameras already name the clip, and a project often relinks by that name. Keep the camera's clip name inside the dated card folder. Put the date on the folder, and on the files you name yourself.

Do this at ingest, at the moment the card is copied into the project root, before the footage is handed to an editor. A name added later, on one person's machine, does not fix the copy that already went to a second drive. Write the pattern in one sentence the whole team can see: date, then subject, then what the file is. Use that sentence on every project, including the small ones that feel too short to bother.

A video folder structure you can reuse

Use the same folder names on every project, so a second editor can guess the path without a tour. The table is one sample, built for an in-house team that cuts in Premiere Pro, DaVinci Resolve, or Final Cut Pro. A numbered prefix, such as 01_camera, is fine if you want the folders to sort in the same order on every drive. The names are the convention. The numbers are optional. What fails is a new layout invented for each producer.

Inside the editor

Premiere Pro, DaVinci Resolve, and Final Cut Pro are where the cut happens. Organization inside them is for the person cutting, and it should follow the folders rather than invent a second map. Group clips the way the folders are grouped. Mark the shots you might use with keywords or tags. A stringout is a sequence that plays a day's material in order, so you can watch it without hunting. A selects sequence is the shorter pass, the shots you are willing to cut with. Build the selects from the stringout.

The labels differ by application. Bins, keywords, tags, and sequences are the jobs, and each editor has its own names for them. A bin layout does not, by itself, become the library the next project inherits. The folders on disk are what a second editor can open without launching the project. The bins help this cut.

Raw footage and documentary footage

Raw footage, in this kind of library, means the camera original as ingested. Put each card in its own folder under camera, one folder per card, reel, or shoot day, and do not treat a graded export as a replacement for that card. A project that spanned several cards still has one project root. The cards sit under camera, not in a new root per card.

Documentary footage needs one more split, because interviews and coverage get lost when they share a folder. Give each interview its own folder, and keep the picture beside the sound that belongs to it, or name the audio so the pair is obvious from the file list. Put coverage, the b-roll, in folders by location or by subject. A documentary that runs for weeks still has one project root. Under it, a folder per shoot day can hold the same camera, audio, graphics, proxies, project, and exports layout, so a later day looks like the first.

After the edit, across projects and drives

A tidy project folder solves the cut in front of you. It does not answer the question an in-house team asks months later: which drive has the interview, and which project used it. Shared conventions are the first half of that answer. The same root, the same folder names, and the same date-first pattern on every project and every drive, so a person who was not in the edit can walk the disk. Write the convention once. Use it on the NAS, on the RAID, and on any other drive that holds a copy of the project. A special layout for one producer becomes a private language, and the next editor cannot guess it.

Folders tell you where a known project put its files. They do not let you ask for a subject, a spoken line, or a shot across every project on the storage. Searching footage on a NAS is that job when the files already live on a share. AI tagging on your own storage is how a tag can stand in for a folder name you do not remember. Archiving the footage so the team can still find it is where those files should sit once the project is no longer the active cut.

Media Nexus is the media archive Vaultline Solutions builds. It is installed on hardware the team controls, and it indexes the storage you already have, in place. Approved volumes are read. Originals stay where they are. It does not rename, move, reorganize, or delete files, and it does not move media offsite. Search can use file names, tags, and transcripts. The archive includes AI tagging, search, semantic search, proxy generation, and collections. It is not a backup. Indexing the volume does not copy the volume, and it does not put the folders in a new order. The convention you set at ingest is still the one the team has to keep.

How a team starts

This is for in-house creative and video teams whose footage already lives on a NAS, a RAID, or drives they control. The Free Build builds that archive against your real media before you decide whether to keep it. Build before you buy is the intake that configures the archive before any payment.