Video Project Folder Structure: A Template for Editors and Clients
The exact video project folder structure I use in my agency, from numbered local folders and export naming to mirroring it all in a review workspace that clients can actually follow.
"Which one did the client actually approve, final_v3 or final_v3_fixed, because both are sitting in the exports folder with the same date?" That is the exact message I typed into my agency's team chat at eleven one night, and to be very honest the editor who got it had done nothing wrong, right. I had never given the team a video project folder structure that everybody followed, so each editor had invented their own system and the exports folder had basically become a junk drawer with nice thumbnails.
The editor replied twenty minutes later with a screenshot of a WhatsApp thread, and the answer was buried somewhere between two voice notes. That's when it hit me that one badly named file was only the visible part of the problem, right, because the local drive, the shared folder and the review links were all telling different stories about the same job.
So this post is the template I now use in my own video-editing agency, covering the folder tree on the editor's drive and the matching setup inside PlayPause where the client watches and comments. At the end of the day, a structure that lives on one machine doesn't help the client or the next editor who opens the project.
Why video project folder structure breaks down after the third client
With one client the whole system lives in your head, right, you know where the footage is and which export went out on Tuesday, and with a second client you just duplicate the folder. Then a third client arrives with another camera and a longer deliverable list, one editor calls the footage folder RAW, another calls it Card Dumps, and a week-long freelancer drops everything on the desktop.
The cost of that drift is small on any single day, ten minutes of searching, a relink error, a revision applied to the wrong cut, and so on, but over a month of post-production work across a handful of clients it adds up to hours nobody bills for. The catch here is that most advice on how to organize video project files only solves the editor's side, so the client still gets links from three places with three different names.
So I think of the template as two halves that mirror each other, the local tree for the editing machine and the review workspace for everyone else. Teams sharing one workspace get their own folder structure template for teams, so this post stays with one editor or a small crew moving a project from card to approval.
A video editing folder structure template for every edit
Every project on our drives starts from the same six top-level folders, numbered so they sort in the same order on any machine. The numbers matter more than people think, right, because the moment a folder sits out of order someone creates a duplicate instead of finding the original.
- 00_Admin for the brief, proposal and approval emails
- 01_Footage for camera cards, split by shoot day then camera
- 02_Audio for voiceover, music and sound effects
- 03_Graphics for logos, fonts and lower thirds
- 04_Project for the edit project file, proxies and auto saves
- 05_Exports for every review cut and delivery file
I keep an empty copy of this tree called 000_Template at the top of the projects drive, so starting a job means duplicating it and renaming the top folder to the client code and project name, with dates written year first so 20260912 always sorts before 20260913. For an example spring launch with two shoot days, the tree looks like this.
- CL01_SpringLaunch/00_Admin/Brief, Proposal and Approvals.
- CL01_SpringLaunch/01_Footage/20260912_Day1/A_Cam and B_Cam.
- CL01_SpringLaunch/01_Footage/20260913_Day2/A_Cam and Drone.
- CL01_SpringLaunch/02_Audio/VO, Music and SFX.
- CL01_SpringLaunch/03_Graphics/Logos, Fonts and Lower_Thirds.
- CL01_SpringLaunch/04_Project/Proxies and Auto_Save.
- CL01_SpringLaunch/05_Exports/20260920_Round1 and 20260928_Round2.
- CL01_SpringLaunch/05_Exports/Delivery for the approved masters.
The rule that makes this post production folder structure work is that 01_Footage is sacred, right. Card dumps go in exactly as they came off the camera, a folder per shoot day and a subfolder per camera, the way crews treat dailies from a shoot, and nobody renames or moves those files after the first copy. That sounds boring but it's really really important, because every non-linear editing application stores the path to each clip, so tidying the footage folder turns your timeline into a wall of red offline frames.
00_Admin is the folder people skip and the one I care about most as an agency owner, because the brief, the signed proposal and the approval email live there, so when a client asks eight months later what they signed off on, the answer sits in one folder. For instance, the client approval email template I use goes in there as soon as the client replies.
04_Project holds the project file, auto saves and proxies so another editor can pick the job up, while the render cache lives on a scratch drive outside the tree because it can always be rebuilt. I collected smaller habits in 10 ways to organize video files, and for a new client I follow onboarding a new post-production client, which creates this tree before a single card gets copied.
Naming exports so versions never collide
Inside 05_Exports every round gets a dated subfolder like 20260928_Round2, and every file follows one pattern of client code, project, deliverable and aspect ratio, like CL01_SpringLaunch_Hero_16x9. There's no v3 and no final anywhere in that name, right, because the date folder tells you the round and the review workspace tells you the version. Once a cut is approved, the same file gets copied into Delivery rather than renamed.
The word final is banned in our exports folder, and to be very honest that one rule did more for us than most tools I've paid for, because the client always finds one more thing and then you get final_v2, final_fixed, FINAL_REAL and so on, until nobody knows which file is current. I'm pretty sure every editor reading this has a folder like that right now.
The word final in a filename is a promise nobody can keep, so I banned it from our exports folder.
If your team thinks in stages, names like rough cut, fine cut and picture lock can go into the round folder name instead, and I wrote up the full reasoning in cut version naming conventions for post teams.
Mirroring the client folder structure in your review workspace
This is where most guides stop and where most of the pain lives, right, because the client never sees your drive, only the link you send, so if those links come from different places with different names your local tree means very very little to them. The second half of the template mirrors the same shape inside PlayPause, where the client opens one link in a browser with no account and no install, and every comment sticks to the exact frame.
In my agency the mapping is one PlayPause project per client engagement, with folders that match the deliverables, so the spring launch above gets a hero film folder, a cutdowns folder and a social reels folder, and I manage every client project from that one list. You don't mirror 01_Footage or 04_Project at all, because the review side only needs what a human has to watch and approve, you see what I mean here.
The catch here is the project limit, because Creator gives you 30 projects while Agency and Enterprise are unlimited. Six retainer clients with five deliverables each is already 30 if you make one project per deliverable, so on Creator I group by client and let folders carry the deliverables, while on Agency you can be as granular as you like.
Review cuts take far less room than raw cards, which I worked through in how much storage video editors need, and in PlayPause media storage your original stays untouched while the browser plays a streaming copy. Creator links last 30 days and the files expire with them, Agency links last 90 days and Enterprise links never expire, which is why the local drive stays the source of truth.
Using version stacks instead of final_v3 filenames
Version stacks are the reason I could ban the word final in the first place, right, because instead of exporting a renamed file and sending a fresh link every round, you upload the new cut onto the same card and it stacks as MV2, then MV3, then MV4, so the client comes back to one card instead of a pile of links. Each version keeps its own frame-accurate comments, so when the client asks whether you fixed the logo note from round one, you open MV1 and check.
final_v3_fixed exported, renamed and sent as a fresh link every round
MV1, MV2 and MV3 stacked on the one card the client already knows
Version stacks come with every plan, and Agency and Enterprise add side by side version compare, which helps when a client says the new cut feels slower but can't say where. If your team cuts in Premiere Pro, the PlayPause panel lets the editor upload from the timeline and read comments inside Premiere, where clicking one jumps the playhead, and I've covered showing a client what changed between two Premiere edits.
Premiere Pro is the only editor with a native PlayPause panel, so in DaVinci Resolve, Final Cut Pro or After Effects the flow is export, upload, review in the browser, then work through the notes in your editor, and the stack still does the heavy lifting, as I explained in version stack chaos in After Effects projects. Either way the two halves meet in one place, since the local folder 20260928_Round2 maps to MV2 on the card, does that make sense, right.
Folder instructions editors can find with Playbooks
Every agency I know has a readme in a drive folder that nobody has opened since the day it was written, and I had a few too, until we moved per-folder instructions into Playbooks on Agency and Enterprise. A Playbook is basically a per-client document of creative style and direction, with brand playbooks for permanent rules like logo usage and colour, and folder playbooks covering only what sits inside one folder.
So the social reels folder can carry a playbook saying captions stay inside the safe zone and the hook lands in the first two seconds, while the hero film folder carries different instructions, and an editor opening either folder reads the right rules without digging through chat. Checklists inside a Playbook aren't done until somebody ticks them, which changed behaviour in my team more than I expected, and a Playbook can be shared as a no-login page for freelancers without an account.
A folder Playbook sits on the same folder as the videos it governs, so editors read the rules before they touch the timeline.
I usually draft the first Playbook from my video production proposal template, since it already spells out the scope and review process.
Bulk uploading a whole project without breaking the structure
The last piece is getting files in without wrecking the structure, right, so I create the project and its folders in PlayPause first, mirroring the deliverable folders from 05_Exports, and only then upload, so every file lands in its twin folder instead of one pile someone sorts later.
Bulk upload handles 100+ files at once on every plan, which matters on day one of a social campaign with forty cutdowns across three aspect ratios, and you can see how batch uploads work before you start. The limit to watch is file size, because Creator caps a single upload at 10 GB while Agency and Enterprise have no cap, so long-form masters at a high bitrate can decide the plan for you.
Clients can send files back too, since guest version upload on Agency and up lets someone without an account add a version, with their name and email collected. When a project wraps I archive the local tree with 01_Footage untouched and the render cache cleared, and Google Drive backup on Agency and up keeps a copy of the review side too, and trust me on any level, future you will be glad it exists.
Frequently asked questions
What is the best video project folder structure for a small studio?
The best one is whatever your whole team actually follows, right, which in practice means a numbered set of top-level folders for admin, footage, audio, graphics, project files and exports, copied from a template for every job. Keep footage untouched after the first copy, keep exports in dated round folders, and mirror only the deliverables in your review workspace so clients see a clean version of the same structure.
How should I organize files when several clients overlap?
Give every client a short code at the front of every project folder and export name, so files sort by client automatically and nothing from one job leaks into another. In PlayPause I keep one project per client engagement with folders per deliverable, which keeps you inside the 30 project limit on Creator, while Agency removes that limit entirely.
Should version numbers go in export filenames?
To be very honest I'd keep them out of the filename entirely, and put the round in a dated subfolder on your drive while the review workspace handles versions. Every new cut then stacks on the same card as MV2, MV3 and so on. Filenames only describe what the file is, meaning client, project, deliverable and aspect ratio, so final_v3_fixed never ends up sitting next to FINAL_approved again.
Do clients see my whole folder structure?
A client only sees what is inside the link you send, opened in a browser without an account or an install, so your internal folders and other clients' projects stay out of view. You can also password-protect a link and revoke it instantly, so the client gets a tidy view of exactly the cut they need to comment on.
If you want to set this up properly, build the local tree first, then mirror the deliverable folders inside PlayPause, and pick the plan on our pricing page that fits your project count and storage. Every plan starts with a 7-day free trial, so you can move one real client job across and see whether the structure holds.
So yeah. That's my way of saying it.
Saumyajit co-founded PlayPause after years watching review and approval quietly eat creative teams' deadlines. He writes about the workflow side of video, feedback, versioning, and getting to a clean sign-off.
Related resources
Keep reading
Bring your team into one review space
Centralize feedback, lock approvals, and deliver faster, start free today.
Sign Up for Free