Name video assets with stable IDs and readable labels

Let identity survive a better name

Renaming a clip should improve its description without breaking the edit that uses it. Keep source identity separate from the readable filename and current path, then register versions and derivatives through explicit relationships. A stable ID lets descriptions evolve while recipes still identify the same media, even after the folder structure or display label changes.

In our production in October 2026, our library practice separates identity, path, and description. The ID identifies a registered source. The path locates its current file. The label helps a person recognize it. These fields can disagree temporarily after a move, which is why the index needs an explicit update. Putting every fact into a longer filename does not remove the need to maintain those relationships.

Define the small index first

Start with an asset ID, current path, readable label, file hash, duration, and source relationship. Add the fields your actual workflow needs, such as capture date, camera, orientation, language, or market restriction. Keep unknown values explicit. A blank or unknown market field should not quietly imply that the footage is cleared for use in every market.

A file hash helps identify identical bytes, but it serves a different role from the asset ID. Reencoding a source creates different bytes even when it depicts the same scene. Register the derivative with its own identity and a parent-source relationship. Conversely, two paths with the same hash may be duplicate copies of one source. Resolve that relationship through the index before creating extra editorial identities.

1. 01RegisterAssign a stable ID to the source
2. 02DescribeAdd a readable label and useful retrieval fields
3. 03RelateConnect proxies and renders to their parent source
4. 04UpdateRecord moves and renames without replacing identity
5. 05VerifyRelink a project through the index

Use filenames people can scan

A readable label can contain a few stable, useful descriptors: subject, action, camera view, and a version where relevant. For example, A0042_roof-detail_wide_v01.mov lets a reviewer see an ID and a rough shot description. This is a suggested convention, not a required syntax. Choose separators and field order once, then document how missing values are represented.

Keep the convention short enough to survive ordinary browsing and handoff. Capture date belongs in the filename only if it helps your retrieval task; otherwise it can remain in the index. Do not use adjectives such as approved or final as the only status record. Acceptance can change, while an asset’s source identity should remain understandable throughout that change.

Source: suggested production checklist, October 2026.

Register versions and derivatives deliberately

A proxy, crop, stabilized render, captioned export, and original recording should not share one ambiguous identity. Record what each file is and where it came from. Video review proxies: small files, traceable notes explains review proxies; link each proxy to the source it represents so a reviewer’s timecode can be translated back to the appropriate media. A lightweight copy is useful only when its reference remains clear.

A0042 is an illustrative source ID for a desk-organizer recording. The example separates a better description from a change to the media: renaming camera two updates the label, while making a cropped review copy creates a derivative relationship. Keep both operations explicit in the index. Another editor should be able to locate the original and trace the copy without inferring identity from whichever filename happens to be current.

1. Original
2. Cropped copy

Make a rename an indexed operation

Before renaming or moving media, identify which recipes and projects refer to it. Update the path in the index, preserve the stable ID, and test relinking in a copy of the relevant project. Keep the previous path as a useful alias or change record when the workflow supports it. The aim is to explain where the asset went, not to maintain two uncertain masters.

Our Bring your own content approach uses this small record to keep existing footage useful across edits. A reviewer should be able to follow an ad’s source references even when the folder structure has changed. If relinking fails, compare duration, visual fingerprints, and hashes as appropriate. A similar filename is a lead to investigate, not enough evidence that the media is the correct source.

Keep sensitive details out of labels

Filenames travel in screenshots, exports, shared folders, and editor dialogs. Avoid placing credentials, private customer details, account identifiers, or internal financial information in them. Use a neutral project or asset reference and keep any necessary restricted context in the controlled record where it belongs. A descriptive media label does not need to reproduce every fact about the capture location or business relationship.

Also distinguish depiction from approval. A label saying customer-demo describes a possible subject; it does not prove that the clip can be reused. Keep reuse status and its supporting record as separate fields. That makes the naming convention useful without turning a human description into an unsupported claim about clearance, market suitability, or the current acceptance of a creative export.

FieldPurpose

• FieldStable IDPurposeIdentify the registered source across moves
• FieldReadable labelPurposeHelp a person recognize the content
• FieldCurrent pathPurposeLocate the available file
• FieldFile hashPurposeCompare byte identity
• FieldParent sourcePurposeExplain a derivative’s relationship

Connect names to retrieval and archiving

Tag a video clip library with AI: rules first covers descriptive tags for finding useful footage. Tags can change as the library grows: a wide shot may later become useful as background or an opening image. Keep these retrieval labels flexible while preserving the source ID. That lets a shot gain new uses without multiplying copies simply because different editors describe it differently.

Archive video ad assets without losing the next edit covers archiving assets whose active use has ended. Preserve the index relationship when moving media out of an active folder. A recipe may still refer to an archived source, and a previous ad may need to be reconstructed. Record the archive location and availability instead of leaving an active path that silently points to nothing. Restore and relink through the same identity when reuse becomes appropriate.

Test the convention with one real handoff

Choose a small set of sources, register their IDs, create a derivative, and rename one readable label. Ask another editor to locate the original, trace the derivative, and relink the renamed media from the index. This is a practical workflow check; it does not need a large taxonomy before revealing whether the essential relationships are understandable.

ai ad workflow small business places asset organization inside a small-business production workflow. Add fields when a repeated retrieval or handoff problem justifies them. Keep the record maintainable enough that the next import actually receives an ID and source relationship. A modest index updated consistently gives the next editor more usable evidence than an elaborate naming pattern applied only to the first folder.

Who wrote this We made the ads first, for SmartSolar in Denmark, Sweden and Ireland. Then we built Turntake. Where Turntake comes from