Separate irreplaceable originals and project data from generated working media and exported deliveries. Use stable names, document the root path and keep an inventory. A folder convention helps only when the project can reopen from the copy you give someone.
On this page
A small, reusable structure
project-name/
01_originals/
02_audio/
03_graphics/
04_project/
05_working_media/
06_exports/
07_delivery_notes/This is a proposed convention, not a requirement of an editor. Some applications manage media inside a library or use a separate project database. Document those locations alongside the folder root rather than forcing every application into one filesystem pattern.
Give each folder a clear contract
| Folder | Rule |
|---|---|
| Originals | Preserve acquisition filenames where practical; do not overwrite with transcodes |
| Project | Save distinct versions or documented library/database backups |
| Working media | Label proxies, optimized media and caches as generated assets |
| Exports | Separate review versions, intermediate masters and approved deliveries |
| Delivery notes | Record requirements, missing assets, application versions and approval state |
Make revisions unambiguous
Use names such as projectname_review_v03_2026-10-06 rather than final_final_new. Record which export the recipient approved. Keep the date format stable so files sort sensibly, and avoid changing a media name after the application has linked to it without a deliberate relink plan.
Test the handoff
- Save and close the project before copying the intended package.
- Copy it to a separate location without modifying the only originals.
- Open the copied project and resolve paths deliberately.
- Check fonts, graphics, plugins, audio channels and a representative timeline range.
- Compare an export from the copy against the reference movie.
- Include notes about assets intentionally excluded or expected to regenerate.
A folder tree is not a backup
Multiple folders on one physical device share the same failure path. Keep an independent copy and a project recovery test. For mixed applications, see interchange limits; for complete protection, use the backup checklist.
Sources and scope
The directory tree and naming convention are original suggested methods. They are not claims about a vendor’s mandatory file layout. Sources checked October 6, 2026.