Video Project Folder Structure and File Naming That Scales

A good video project folder structure puts every project in its own dated folder, splits it into a small number of numbered sub-folders (admin, footage, audio, graphics, project files, exports), and uses one file-naming pattern everywhere. The aim is simple: anyone, including you in six months, should be able to open the folder, find the final export and relink the edit without asking questions.

Below is the template we use for caption and AI video work, the naming rules behind it, scripts to create it in seconds, and the habits that keep it tidy once a project gets busy.

Why structure matters more than it seems

Most lost time in editing is not spent editing. It goes on hunting for "the other version" of a voiceover, relinking media after a drive letter changes, or working out which of three exports went to the client. A consistent structure fixes these problems before they start:

• Relinking is painless. If media always lives in the same place relative to the project file, editors can find it again after a move.
• Handovers are quick. A freelancer or teammate can pick up the project without a tour.
• Backups are targeted. You can back up source media and project files, and skip caches that can be rebuilt.
• Automation works. Scripts for renaming, transcription or rendering can assume paths instead of asking for them.

A template that works for most projects

Start every project from the same skeleton. Numbered prefixes keep folders in a fixed order in any file browser.

2026-09-24_client-or-channel_project-name/
├── 00_admin/          briefs, scripts, licences, invoices, notes
├── 01_footage/
│   ├── a-cam/
│   ├── b-cam/
│   ├── screen/
│   └── ai-generated/
├── 02_audio/
│   ├── voiceover/
│   ├── music/
│   └── sfx/
├── 03_graphics/
│   ├── stills/
│   ├── titles/
│   └── thumbnails/
├── 04_captions/       transcripts, SRT and VTT files
├── 05_project/        editor project files and auto-saves
├── 06_exports/
│   ├── review/
│   └── final/
└── 07_cache/          proxies, render cache (safe to delete)

A few choices deserve explanation.

Admin comes first. The brief, script and any music or stock licences sit at the top because they are the first thing you need when a question comes up later. For music in particular, keep the licence alongside the project; our guide to copyright-safe music for YouTube explains what to record.

Captions get their own folder. Transcripts and subtitle files are deliverables in their own right, often revised separately from the edit. Keeping them apart from exports stops an old SRT being uploaded with a new cut. If you are new to the formats, see what an SRT file is.

AI-generated material is separated. Generated clips and images tend to arrive in large batches with machine-made names. Keeping them in their own folder makes it easier to track what was generated, which matters if you need to answer questions about synthetic content later.

Cache is isolated and labelled. Proxies and render files can run to hundreds of gigabytes. Putting them in one clearly named folder means you can exclude it from backups and delete it when archiving without worrying.

Adapt the template, but resist adding too many levels. Three levels deep is usually enough; beyond that, people stop filing things properly.

File naming rules

Folder structure only helps if file names are consistent. These rules have served us well:

1. Dates as YYYY-MM-DD. This sorts correctly as text and avoids confusion between UK and US date order. 2026-09-24 is unambiguous; 09-10-26 is not.
2. No spaces. Use hyphens between words and underscores between fields: 2026-09-24_quiz-channel_ep12_vo_v03.wav. Spaces work in most modern apps, but they break older scripts and command-line tools.
3. Lower case. Some systems treat Intro.mov and intro.mov as different files, others as the same. Lower case avoids surprises when moving between Windows, macOS and Linux.
4. Fields in a fixed order. For example: date, project, item, description, version.
5. Zero-padded numbers. ep07, shot_0042, v03. Padded numbers sort correctly; unpadded ones do not. Our guide to batch renaming image sequences covers this in detail.
6. Avoid special characters. Stick to letters, numbers, hyphens and underscores. Characters such as / \ : * ? " < > | are not allowed in Windows file names, and #, & and % cause trouble in URLs and scripts.

Versioning without "final_final"

Every creator has seen final_v2_REAL_final.mp4. Replace words with numbers:

Only one thing is "final": the file inside 06_exports/final/. Copy the approved export there with a clear name such as 2026-09-24_quiz-channel_ep12_final.mp4 and never overwrite it; if something changes after sign-off, create a new version and note why in 00_admin.

Creating the structure automatically

Typing folders by hand invites typos. A short script creates the same skeleton every time.

Windows PowerShell

$project = '2026-09-24_quiz-channel_ep12'
$folders = @(
  '00_admin', '01_footage\a-cam', '01_footage\b-cam', '01_footage\screen',
  '01_footage\ai-generated', '02_audio\voiceover', '02_audio\music', '02_audio\sfx',
  '03_graphics\stills', '03_graphics\titles', '03_graphics\thumbnails',
  '04_captions', '05_project', '06_exports\review', '06_exports\final', '07_cache'
)
foreach ($f in $folders) { New-Item -ItemType Directory -Force -Path "$project\$f" | Out-Null }

macOS and Linux

p="2026-09-24_quiz-channel_ep12"
mkdir -p "$p"/{00_admin,01_footage/{a-cam,b-cam,screen,ai-generated},02_audio/{voiceover,music,sfx},03_graphics/{stills,titles,thumbnails},04_captions,05_project,06_exports/{review,final},07_cache}

The brace expansion in the second example works in bash and zsh. Save either version as a script, change the project name each time, and every project starts identical.

If you prefer, keep an empty template folder and copy it. The script approach has one advantage: you can add a README.txt or a notes file at the same time.

Habits that keep it tidy

A template is only as good as the discipline behind it.

• Ingest before you edit. Copy camera cards, phone footage and downloads into 01_footage first, then import from there. Never edit straight from a card, a Downloads folder or the desktop. If footage arrives from a phone, our guide on moving large files from phone to PC covers the transfer step.
• Point your editor's cache at 07_cache. Most editors let you choose where proxies, previews and auto-saves go. Setting this per project keeps everything self-contained.
• Keep source names for camera files. Renaming original camera clips can break metadata links in some editors. Organise them by folder instead, and rename only files you created.
• Write short notes. A text file in 00_admin recording decisions ("client approved v05 on 24 Sept; music swapped for licence reasons") saves arguments later.
• Tidy at milestones, not constantly. A five-minute clean-up after the rough cut and after delivery is enough.

Backups and archiving

Treat backups as part of the structure, not an afterthought. A widely used rule of thumb is 3-2-1: three copies of your data, on two different types of storage, with one copy off-site. For a small creator that might mean the working drive, an external drive and a cloud backup.

What to include:

When a project is finished, delete the cache, check the project still opens and relinks from the archive location, and only then remove the working copy. For client work, also check how long you are allowed or required to keep footage; our guide to protecting client footage covers privacy and retention.

Quick checklist

• One dated folder per project, named YYYY-MM-DD_client_project.
• Numbered sub-folders in a fixed order.
• File names: lower case, no spaces, fixed field order, padded numbers, v01 versions.
• Media ingested into the project before editing.
• Editor cache pointed at a deletable cache folder.
• Licences and notes saved in 00_admin.
• Approved export copied to 06_exports/final and never overwritten.
• Backups follow 3-2-1; cache excluded.

FAQ

Should I keep one project per video or one per channel?

One per video is easier to archive and hand over. Keep shared assets used across many videos, such as logos, intro music and fonts, in a separate channel-level "brand" folder, and copy what each video needs into its own project.

Is it a problem to use spaces in folder names?

Not for most editing software, but spaces cause errors in scripts and command-line tools unless every path is quoted. Hyphens and underscores avoid the issue entirely.

Where should auto-saves go?

Inside the project folder, usually in 05_project or 07_cache, depending on whether you want them archived. Default auto-save locations are often on the system drive, which makes them easy to lose.

How do I stop teammates breaking the structure?

Make the template the only way projects start, keep a one-page naming guide in a shared place, and review the folder at each milestone. Consistency comes from habit more than rules.