A File-Naming Convention for Creator Content Versions

A dependable creator content filename should identify the campaign, creator or source, deliverable, version, and meaningful variant without trying to store the entire approval record in the name. One workable pattern is campaign_creator_deliverable_variant_v03.ext. Keep the authoritative status and decision history in the approval system, because filenames are easy to copy or rename.

This is a proposed convention, not an industry requirement. Choose fields that remain stable in your process.

Decide which fields belong in the filename

Include a field only if a person receiving the file outside its original folder needs it to identify the asset.

Recommended core fields:

• Campaign code: a short stable identifier, such as SPR26.
• Creator code: a non-sensitive handle or internal ID.
• Deliverable: reel01, short02, or another brief-defined label.
• Variant: language, aspect ratio, hook, market, or placement when it changes the file.
• Version: a zero-padded sequence such as v01, v02, and v03.

Example: SPR26_maya_reel01_us916_v03.mp4.

Do not put creator email addresses, phone numbers, contract rates, or other unnecessary personal or confidential data in filenames. A file may travel farther than its original workspace.

The filename supports the creator content approval workflow; it does not replace the submission and decision record.

Use stable vocabulary and separators

Publish a short data dictionary. Decide whether ig-reel, reels, and instagram_reel are the same deliverable and choose one value. Define market and language codes rather than letting each user improvise.

Use one separator, preferably underscores or hyphens. Avoid characters that cause trouble across file systems and URLs, including slashes, colons, quotation marks, and trailing periods. Keep names reasonably short and do not rely on capitalization alone to distinguish assets.

Human-readable labels and machine IDs can coexist. For example, the system may store an immutable asset ID while displaying a readable filename. The ISO document-management committee covers areas including indexing, metadata, workflow, preservation, and audit trails, but it does not prescribe this particular creator filename.

Treat versions as immutable submissions

Increase the version number when the media file changes. Never overwrite v02 with a new export and leave the same name. The review history is only trustworthy if the file attached to an old finding remains the file that was reviewed.

Use whole-number versions for submitted work. Internal editor experiments can live in a working folder, but v02_final_final2 should never become the handoff convention.

Do not encode approval into the filename as the only record. A file named APPROVED may be copied after the offer expires or after a later version replaces it. If teams need a convenient export label, generate it from the current decision and still preserve the underlying asset ID.

The practical approval status model explains why production, review, decision, and publication states should remain separate.

Name variants by the change that matters

Different crops, hooks, captions, translations, and offers should not share a filename merely because they use the same source footage.

Good variant labels answer a review question:

• hook-a and hook-b
• en-us and es-us
• organic and paid
• 916 and 11
• offer-june and evergreen

Avoid subjective labels such as better, new, or client-version. They lose meaning as soon as another change happens.

If several changes combine, either use a controlled compound label or rely on asset metadata. A filename should not become a database row squeezed into 200 characters.

Provide a renaming checklist

Before a team adopts the convention:

1. Inventory active and archived naming patterns.
2. Define the minimum fields and allowed values.
3. Test names on macOS, Windows, cloud storage, and downstream ad tools.
4. Decide who assigns campaign, creator, and deliverable IDs.
5. Map legacy files without destroying original references.
6. Automate name generation where possible.
7. Validate that exports keep their IDs and extensions.

Do not bulk-rename files referenced by live review links or ad platforms until those dependencies are mapped. Preserve a translation table from old names to new asset IDs.

Audit the convention with real searches

Give a teammate five tasks: find the approved Spanish vertical cut, distinguish two hooks, retrieve the file behind an old finding, identify the source creator, and tell which version came later. If filenames cannot support the first scan, revise the vocabulary. If the user needs the filename to prove approval or rights, improve the metadata and decision system instead.

The takeaway

Use a small set of stable identifiers, increment versions without overwriting, name meaningful variants consistently, and keep approval and rights in structured records. A good filename helps people find the asset; it should not carry every fact about it.