Video Asset Management for Creators: Folders, Names, Masters and Backups

Why channel files get out of control

Most creators do not lose footage in one dramatic failure. They lose it slowly: an export called final_v3_REAL.mp4 on the desktop, a project file that points to a drive that has since been reformatted, a Spanish subtitle file sitting in Downloads next to forty others with the same name.

The cost shows up later. You want to re-cut an old video for a new platform, update a sponsor read, or translate last year's best performer, and you spend an hour finding the right master and the music you used. Once you publish in more than one language, every video multiplies into several audio tracks, subtitle files and transcripts, and the mess grows faster.

A file system does not need special software. A consistent folder template, a naming rule and a backup routine cover most of what a dedicated asset manager would give a small channel.

One folder per video, the same structure every time

Give every video its own top-level folder and copy an empty template into it before you shoot. The exact names matter less than never changing them. A structure that works for most channels:

• 01_raw: camera files, screen recordings, separate microphone audio, exactly as they came off the device.
• 02_project: the editing project file, plus the editor's cache and proxies if you keep them here.
• 03_assets: music, sound effects, graphics, fonts, thumbnails source files, b-roll you licensed.
• 04_audio: exported stems such as dialogue only, music and effects, and the final mix.
• 05_masters: the full-quality final export of each finished version.
• 06_exports: platform files, such as a compressed upload, a vertical cut or a teaser.
• 07_languages: one subfolder per language for translated audio, subtitles, transcripts and translated metadata.
• 08_docs: script, shot list, sponsor brief, license receipts, a short notes file.

Numbering the folders keeps them in production order in every file browser. Keep the template in a folder of its own so a new video always starts from a clean copy rather than a duplicated old project.

A naming convention you can read in a year

A good file name answers three questions: which video, what kind of file, which version. A pattern like date, short slug, type, language and version does that:

Master

2026-09-14_budget-camera-review_master_en_v2.mp4

Dialogue stem

2026-09-14_budget-camera-review_dialogue_en.wav

Translated audio

2026-09-14_budget-camera-review_dub_es-419.m4a

Subtitles

2026-09-14_budget-camera-review_subs_pt-BR.srt

Transcript

2026-09-14_budget-camera-review_transcript_en.txt

Some rules that keep this working:

• Start with the date in year-month-day order so files sort by when they were made. Use the planned publish date or the shoot date, and stick to one.
• Use lowercase, hyphens inside the slug and underscores between parts. Avoid spaces and characters like ampersands and slashes, which some tools and upload forms handle badly.
• Use language tags in the BCP 47 style, such as en, es-419 for Latin American Spanish, pt-BR or pt-PT, so regional variants never get mixed up.
• Use v1, v2 for versions and drop words like final. The highest number is the latest; a master that changes after publishing gets a new version number, not an overwrite.

Many tools give downloads generic names, so rename every file the moment it lands, before it joins others with the same name.

Raw footage, project files, masters and exports

These four kinds of file have very different values, and treating them the same is where most storage problems start.

Raw footage is irreplaceable and large. Never edit or transcode it in place; work from it and leave the originals untouched. Project files are tiny but useless without the media they point to, so keep media inside the video folder and use relative paths if your editor supports them.

A master is the highest-quality export of the finished video, the file you would use to make every future version. Exports are disposable derivatives: a compressed upload, a 9:16 cut, a file with burned-in captions. You can always regenerate an export from the master, so exports need far less protection.

Two extra masters pay off if you ever translate. A dialogue-only stem lets speech recognition hear the voice clearly, and a music-and-effects stem lets you mix the original sound under a voice dubbed from that dialogue stem with full control, cleaner than the background the dub keeps automatically; see the M&E track for what that stem should contain. A version of the picture without burned-in titles or captions is the third, since it lets you add translated text later without covering the original.

Where translated versions and subtitle files live

Keep everything for one language together inside the video's 07_languages folder rather than scattering it across exports and audio. For each language, a typical set is:

• The translated audio file: the new voice over the original background.
• The translated video, if you publish it as a separate upload.
• SRT and VTT subtitle files.
• The transcript in that language, plain and timestamped.
• Translated title, description and tags in a text file.
• A short review note: who checked it, when, and what they changed.

That last file is easy to skip and hard to reconstruct. When you later update a translated video or fix a subtitle, it tells you which file is the reviewed one. If you edit an SRT by hand, save it as a new version rather than overwriting the original; editing an SRT file covers the safe way to do that.

When you work through older uploads in bulk, the same structure lets you see at a glance which videos already have which languages. The workflow for that project is in translating a YouTube back catalog.

Storage tiers: working, nearline and archive

Not every file needs to be on your fastest drive. Thinking in three tiers keeps costs and clutter down:

Working

Fast internal or external SSD with the videos you are editing now. Raw, project, assets and proxies.

Nearline

A larger hard drive or network storage with recent videos you may re-cut or translate. Everything except caches and proxies.

Archive

Cheaper bulk storage, local or cloud, for finished videos. Raw, masters, stems, languages and docs.

Move a video down a tier when it is published and the first round of clips and translations is done. Before moving, delete caches, render files and proxies, which your editor can rebuild, and keep the folder structure intact so the project still opens.

Decide how long you keep raw footage. Some channels keep everything; others keep raw only for evergreen videos and rely on masters and stems for the rest. Either is reasonable as long as it is a rule rather than an accident.

Backups that survive a dead drive

Storage is not a backup. A single drive holding the only copy of a video is one failure away from losing it. The commonly cited 3-2-1 rule is a sensible baseline: three copies of anything you care about, on two different kinds of storage, with one copy somewhere other than your home or studio.

For a small channel that usually means the working or nearline drive, a second local drive that a backup program updates on a schedule, and a cloud backup or a drive kept at another location. Sync services that mirror deletions are convenient but are not backups on their own; if you delete or corrupt a file, the sync spreads the mistake.

Test restores occasionally. Pick an old video, restore its folder to a spare location and open the project. A backup you have never restored from is a hope, not a plan.

Example: one video, three languages

Common mistakes and limits of a DIY system

• Renaming or moving media after the project is built. Most editors then show missing media; relink before archiving, not after.
• Keeping the only copy of the music license in an email inbox. Save receipts and license terms in 08_docs with the video they cover.
• Letting exports pile up. They are the easiest files to regenerate and the ones that fill drives.
• Mixing languages in one folder. A file called subs.srt with no language tag will eventually be uploaded to the wrong version.
• Over-engineering. A folder template and a naming rule you follow beat an elaborate tagging system you abandon after a month.

A folder system has real limits. It does not stop two editors from overwriting each other's work, it does not search inside files, and it depends on everyone following the rules. Once several people work on the same projects at the same time, shared storage with permissions or a proper asset manager starts to earn its cost. For searching across large libraries, consistent metadata and tags inside the files go further than folder names alone.

How mydubly fits into your file system

mydubly works on files you choose from your device, so your folder system decides what goes in. For transcripts and subtitles, the dialogue stem from 04_audio is usually the right input. For dubbing, the full master keeps its music and effects under the translated voice automatically, while a dub of the dialogue stem has nothing underneath and is meant to be remixed with your M&E stem. mydubly accepts audio files such as WAV and M4A as well as video files, up to 2 hours each. When you upload a video, its audio is decoded in your browser and only compressed audio chunks are sent; the picture stays on your computer.

The results map onto the language folder directly: a timestamped transcript and plain transcript.txt, SRT and VTT subtitles in one language per job, and for dubbing a translated audio file, a translated video and transcripts in both languages. mydubly is not storage. Uploaded audio and results are deleted within 30 minutes of a job finishing, so download every file you want, rename it to your convention and file it straight away. It also has no project library or batch import, so the record of which videos have which languages lives in your folders, not in mydubly.

Next step

Make the folder template today and use it for your next video, then rename the downloads from your next translation into 07_languages as soon as they arrive. When you are ready to translate, start with one finished master or dialogue stem in the video translator and file the results before you close the tab. The step-by-step translation guide walks through the job itself.