Why Filenames Still Matter For Media Archives

Catalog software changes, databases are abandoned and cloud services close, but filenames travel with the files themselves. In a long-lived archive the name is frequently the only durable description.

The name is the most portable metadata there is

Descriptive fields inside a file can be stripped by conversion, and external catalogs depend on software that must keep running. A filename survives copying, compression and moving between systems.

It is also readable without any specialized tool. Anyone can list a directory and understand what is there, which matters when an archive is inherited rather than maintained.

That durability makes the name worth designing deliberately rather than accepting whatever a camera produced.

Camera-generated names collide immediately

Recording devices number files sequentially and reset those counters. Two cards from two cameras routinely produce identical names for entirely different footage.

Collisions are discovered at the worst moment, when files are merged into one folder and something is silently overwritten or refused. The originals may already have been erased.

Renaming on ingest, before anything is consolidated, removes the risk permanently. The device's numbering can be preserved inside the new name as a reference.

Dates belong in a sortable order

Writing dates with the year first and two-digit months and days means alphabetical order equals chronological order. Every file listing sorts correctly without configuration.

Month-first and day-first formats are ambiguous across regions and sort meaninglessly. A directory listing of them appears shuffled.

Creation timestamps stored by the operating system are not a substitute, because copying and syncing routinely rewrite them. The date inside the name is stable.

Characters and length cause real failures

Spaces, ampersands, quotation marks and other punctuation break command-line tools and web addresses. Some systems reject characters that others accept freely.

Path length limits still exist, and deep folder structures with long names can exceed them. The failure surfaces during copying, often after most of a transfer has completed.

Restricting names to letters, digits, hyphens and underscores avoids nearly all of it. The restraint costs nothing and prevents a category of problem entirely.

Structure should be consistent, not clever

A useful convention places the fixed elements first and the variable ones after: date, project, then descriptive detail. Consistent ordering makes wildcard searches predictable.

Version and sequence numbers should be zero-padded so that the tenth item sorts after the ninth rather than before it. Unpadded numbers scramble any listing longer than nine entries.

The convention only works if it is applied without exception. A folder where most files follow a pattern and some do not is harder to work with than one with no pattern at all.