Naming and Folder System for Dozens of Shorts

The short answer: one pattern, one tree, one log

The best naming convention for many pages is the one your whole team follows without thinking. Fancy beats nothing only if people actually use it.

Here's the full system in three lines:

• Pattern: PAGE_YYYY-MM-DD_topic-slug_9x16_v01.mp4
• Tree: one folder per page, with 01_Sources, 02_Drafts and 03_Finals inside
• Log: one spreadsheet row per video, tied to the filename

Threads on Reddit about this topic mostly come from film editors naming scenes, cameras and takes. You don't need that. You need to know which page a file belongs to, which version went live, and whether you're allowed to post it.

A file naming pattern that works for dozens of shorts

A good pattern puts the page first, the date second and the version last, so files sort the way you think about them. Here's a real-looking example: PGAN_2026-03-14_rescue-dog-bridge_9x16_v02.mp4.

The pattern, field by field

That's it. No camera codes, no scene numbers. If you want to log the platform, do it in the rights log or the folder, not the filename.

Rules: separators, no special characters, sortable dates

Use underscores between fields and hyphens inside the slug, with no spaces and no special characters. Spaces and symbols like : ; / \ ? break sync tools, command-line scripts and some upload forms. We've seen a stray apostrophe stop a batch export cold.

Write dates in the ISO 8601 format, YYYY-MM-DD, because then alphabetical order is also chronological order. This is standard advice in data-management guidance, for example Harvard Medical School's file naming conventions, which also recommends consistent structure and no special characters.

Never overwrite a final. Export a new version instead: v01 becomes v02. And when a file goes live, note the posted date in the log so everyone knows which version it was.

A folder structure for sources, drafts and finals

The simplest structure for an agency is one top-level folder per page with three numbered stages inside, in Google Drive or any cloud storage. Numbering keeps the stages in workflow order, whatever the alphabet says.

One tree per page, three stages inside

PGAN/
  01_Sources/
  02_Drafts/
  03_Finals/
  Assets/
  Archive/

01_Sources holds the raw material: downloaded originals, long videos, permission screenshots. 02_Drafts holds work in progress and rejected versions. 03_Finals holds only approved renders, and it's the only folder your publisher ever opens.

That last rule prevents the classic disaster of posting v01 because it sat next to v03. Move older finals to Archive once a clip has been live for a month or so.

Where to keep covers, captions, music and voiceover files

Put shared material in Assets per page: logo, fonts, intro stings, licensed music, and cover templates. A WowReveal brand kit is a natural source for those shared assets, since it already holds your page's look in one place.

Give covers, caption files and AI voiceover audio the same base name as the video, with a different extension or suffix. For example, PGAN_2026-03-14_rescue-dog-bridge_cover_v01.png. Titles, descriptions and hashtags from a WowReveal post kit can sit beside the final as a text file with the same base name. One search finds the whole package.

If you render in WowReveal, rename the download to your pattern before it enters 03_Finals. Ten seconds now saves a hunt later.

Track source and permission per video with a rights log

A rights log is a spreadsheet with one row per video, and it's the part most teams skip until a page gets flagged. When Facebook content monetization or the YouTube Partner Program questions originality, you want proof in one place. Platform rules change, and Meta, YouTube and TikTok decide eligibility, so keep your own records current.

Use six columns:

Add a "posted" date and platform if you like. If a row can't be filled in, the video doesn't get posted. That one rule does more for originality than any editing trick, and it keeps you away from reposting other people's work without permission.

Does the video file name matter on YouTube, Facebook or TikTok?

For viewers and ranking, the file name is mostly irrelevant; for your team, it matters a lot. YouTube Shorts, Facebook Reels, TikTok and Instagram Reels rely on your title or caption, description, spoken audio, on-screen text and the video itself to understand a clip. Don't count on a keyword in the filename to move reach, and nobody should promise you an effect.

Treat the filename as an internal label. Its job is to stop mistakes, not to earn views. Platform behavior can change, so check the official help pages if you want to be sure.

Keeping the system consistent as the team grows

Consistency survives only when the rules fit on one page and a new hire can follow them on day one. Write the pattern, the tree and the log columns into a single short document, pinned in your team chat.

A few habits that hold up:

• Create the page folder from a template, not from scratch, so the three stages always exist.
• Check 03_Finals weekly: every file there needs a log row and a version number.
• Archive monthly, and never delete sources that have a rights row.
• Review the pattern once a year. Best practice for file naming in 2026 is still boring: fixed fields, ISO dates, no spaces.

If you post the same final across platforms, add a "platform" column to the log rather than copying files. One file, many posts, one record.