# The best folder structure for organizing video assets so they don't get lost

> The folder structure that holds up best is organized by project first, with a date prefix in YYYY-MM-DD format…

Canonical URL: https://vivu.ai/guide/what-is-the-best-folder-structure-for-organizing

The folder structure that holds up best is organized by project first, with a date prefix in YYYY-MM-DD format, and has the same fixed set of subfolders inside every project: raw footage, audio, project files, graphics, exports. Keep it shallow and keep it identical everywhere. The exact names matter much less than everyone using them. A folder tree answers one question well, "which project did this come from?" It doesn't answer "where else have we got a shot like this?", and that second question is how most footage actually gets lost.

## A structure you can copy

```
2025/
  2025-03-14_ProductLaunch/
    01_Raw/
      A-cam/
      B-cam/
      Audio/
    02_Project/
    03_Graphics/
    04_Exports/
    05_Docs/
```

A few rules make it work.

Date first, in year-month-day order, so folders sort themselves chronologically in any file browser. "March launch final" sorts nowhere useful.

The project folder is the unit. One shoot or one job, with everything that belongs to it inside. When the project is done, you archive the whole folder and nothing gets left behind on someone's desktop.

Numbered subfolders stay the same in every project. Anyone opening any project knows where the raw files are, and the numbers keep the order fixed.

Copy camera cards in whole and leave them alone. Once editing starts, moving or renaming raw files breaks the links in the edit project. If you want better names, rename at ingest, before anyone opens an editor.

Exports get versions in the filename, like `ProductLaunch_Teaser_v03.mp4`. When something is approved, copy it to one shared approved-finals location as well, so people outside the edit don't have to dig through project folders.

## Naming files

Folder names carry the project and date, so file names only need what the folder can't tell you: a short description and a version. `Interview_CEO_v02` inside a dated project folder is enough. Long names that repeat the project and date in every file look tidy in theory and get abbreviated inconsistently in practice.

## Where folders stop working

Folders work as long as people return to footage the same way they filed it. Long-term libraries break that. Footage filmed for one documentary or course module turns out to be exactly what a new project needs years later, and the person looking for it remembers the shot, not the project it came from. Teams building shared b-roll libraries for colleagues run into the same thing. Thousands of clips sit in tidy folders, and a newcomer still can't find "students walking across the quad in autumn".

A shot can only live in one folder. Rain on a window, filmed for project A, can't also sit under "weather b-roll" without a duplicate. The common workarounds each cost something.

A selects or library folder with copies or aliases works until the copies drift out of sync with the originals.

Keywords and descriptions in your editing software or a DAM work if someone logs every clip, and that logging is exactly the job that gets skipped when deadlines hit. [Building a content library](https://vivu.ai/guide/how-to-build-a-content-library) goes further into what that upkeep involves.

Transcripts make interview footage findable by what was said. They do nothing for what was shown.

A search layer is the other option. You upload the footage you reuse, it gets indexed once, and you search by describing the shot. What comes back is time ranges, not file names. [Vivu](https://vivu.ai/platform) works this way, and each search runs inside one project. So the useful move is to upload the footage you actually reuse together into one Vivu project, keep your folder tree as the record of where things came from, and export the original clip you pick for the editor.

## When folders are enough

If one person shoots and edits, each project is finished and never revisited, or the library is small enough that the editor remembers what's in it, a consistent folder structure and naming convention is the whole answer. Adding tools on top is extra work that doesn't buy anything.

## How to tell which side you're on

Think about the last time something got lost. If it was a file, like the final export, the right version or the audio from a shoot, the fix is this folder structure, applied without exceptions. If it was a moment, where you knew the shot existed and couldn't say which project it was in, no folder layout will save you. You need logging, transcripts or content search. When that moment involves a file nobody can name, [finding a video without the filename](https://vivu.ai/guide/how-do-i-find-a-video-if-i-don-t-remember-the) is the next problem to solve.

## FAQ

### Should I organize video footage by date or by project?

Both, nested. Put a year folder at the top and dated project folders inside it, named like `2025-03-14_ProductLaunch`. Date-only structures lose the context of what a shoot was for. Project-only structures don't sort, and they get messy when a client or topic comes back years later.

### Should I rename camera files when I import them?

Either rename them at ingest, before editing starts, or never. Renaming raw files after an edit project references them breaks the links, and relinking hundreds of clips by hand is slow. Many editors keep the camera's names and put the meaning in the folder name.

### Where should finished exports go?

Keep them in the project's exports folder with a version in the filename, and also copy approved versions into one shared finals location. People outside the edit should be able to find the final video without knowing which project folder it came from.

### How do I organize b-roll I want to reuse across projects?

Leave the originals in their project folders and add a findability layer on top: a selects folder of copies, keywords in your editing software or DAM, or a content search tool you upload the reusable footage to. Moving b-roll out of its original project into a shared folder makes it easier to find and harder to trace.