File Naming Conventions

A file naming convention is the rule that turns a camera name such as IMG_4827.JPG into a durable identity such as OI-000184_overall-front_001_master.tif. For a collector, that change is not cosmetic. It keeps the photograph connected to the particular physical copy, the view shown, the capture sequence and the file's role even after the image is exported, copied, emailed, detached from its folder or recovered years later.

The filename should not become a miniature catalogue record. Its job is narrower and more important: to act as the asset's durable label. The catalogue explains the object; metadata explains the image; the repository preserves the file. A sound naming convention keeps those layers connected without making any one of them carry the whole burden.

1. What a filename must do

The strongest conventions are designed around the work the files must continue to do, not around what looks tidy on the day of capture. In collectible photography, a name usually serves five overlapping functions.

A name does not have to explain everything to be useful outside its system. It must provide enough stable identity to reconnect the file to a manifest, database export, backup catalogue or human enquiry. That is the difference between a durable pointer and a descriptive essay.

2. Identity first, description second

Titles are edited. Variant attributions are revised. A suspected first printing may become a confirmed second printing. Condition grades change, objects are sold and owners move. None of those events should force the photographic archive to be renamed. The stable identifier remains authoritative while descriptive systems are free to improve.

Object identity is not always owned-copy identity

Collectibles often sit within a hierarchy: franchise, product, edition, variant, physical copy and individual photograph. Reference photography may legitimately use a product or variant identifier, but documentation of an owned collection normally needs to identify the specific copy. Wear, annotation, restoration, completeness and provenance belong to the physical object, not to the abstract product.

3. Build the name from stable fields

A practical general model for owned-item photography is:

[owned-item-id]_[subject-or-view]_[capture-number]_[asset-role].[extension]

OI-000184_overall-front_001_original.cr3
OI-000184_overall-front_001_master.tif
OI-000184_overall-front_001_access.jpg
OI-000184_overall-front_001_thumb-600.jpg
OI-000184_copyright-page_002_master.tif
OI-000184_damage-lower-spine_003_master.tif

Use separators as grammar

A useful convention uses underscores between major fields and hyphens within a field. That visual grammar helps people read the name and allows software to parse it without guessing where one element ends and the next begins.

OI-000184_detail-lower-right-corner_001_master.tif

The exact choice of hyphen or underscore matters less than consistency. Avoid spaces, mixed capitalisation and characters that cause trouble across operating systems, URLs, scripts or cloud services. A conservative filename uses letters, numbers, hyphens, underscores and one final period before the extension.

4. Use a controlled view vocabulary

A view label carries meaning. If one person writes front, another writes front-cover and a third writes primary, the archive may still be readable, but filtering, validation and automation are weakened. A controlled vocabulary defines approved terms and what each means.

View and sequence answer different questions

The view term says what the image means. The sequence number supplies uniqueness and order. Three spine photographs might show the entire spine, its upper section and its lower section. Ideally the vocabulary distinguishes them, but a sequence is still needed when more than one capture legitimately shares the same classification.

OI-000184_spine-overall_001.jpg
OI-000184_spine-upper_002.jpg
OI-000184_spine-lower_003.jpg

5. Dates belong only where time is part of the evidence

Dates are valuable when photographs form a sequence: condition monitoring, before-and-after treatment, insurance updates, packing records, exhibitions, loans or evidence following damage. A date adds little to a one-off permanent documentation set when the capture date is already retained in metadata.

YYYY-MM-DD

OI-000184_2026-07-14_condition-spine_001.tif

6. Keep captures, versions and derivatives distinct

One shutter release can produce a family of digital assets. A later shutter release is a different photograph. Editing and export can also create successive versions or purpose-specific derivatives. These relationships should not be collapsed into a loose string of names such as final-final-new.jpg.

7. Complex objects need relationship-aware names

Components and boxed sets

A boxed collectible may contain rulebooks, maps, dice, counters, inserts and trays. Photographs should support completeness checking, component condition and the later separation of loose parts. A component can be represented by a controlled term or by its own component identifier where the catalogue supports one.

OI-000184_component-rulebook_001.jpg
OI-000184_component-map_001.jpg
OI-000184_component-counter-sheet-02_001.jpg

OI-000184_CMP-001_front_001.jpg
OI-000184_CMP-002_front_001.jpg

Do not attempt to encode the collection, set, object, component, subcomponent and view hierarchy in every filename. Prefer the most specific durable identifier, then preserve parent-child relationships in the database. The right balance depends on how likely the file is to travel outside that database.

Group photographs

Shelf views, comparison images, acquisition groups and complete contents layouts may show several objects with equal importance. Assigning the filename to only one object can falsely suggest exclusive ownership of the image. Use a group or acquisition identifier and link the asset to every represented object.

GRP-000042_variants-overview_001.jpg
ACQ-000072_contents-overview_004.jpg

Acquisition and unpacking evidence

Packing condition, seller labels, sealed contents and damage discovered on opening are evidence about the transaction and chain of custody before they are evidence about one catalogued object. Keep the acquisition set intact, retain the source relationship and link individual images to owned items once those items have been catalogued.

ACQ-000072_package-arrival_001.jpg
ACQ-000072_package-damage_002.jpg
ACQ-000072_contents-unopened_003.jpg

8. Names must not leak risk, judgement or private data

Filenames appear in browser URLs, cloud links, email attachments, download dialogs, public pages and breach datasets. Information that is harmless inside an access- controlled record may be inappropriate in a portable filename.

Public and private names may differ

A private master may carry only the durable collection identifier, while a web derivative receives a human-readable, search-friendly slug. That is acceptable when the system retains a reliable link to the source asset and does not rename the archival master merely to improve a public URL.

Private master:  OI-000184_front_001_master.tif
Public derivative: tsr-b2-keep-on-the-borderlands-front-cover.jpg

9. The filename is one layer of a stronger evidence system

A photograph can require object identity, photographer, capture date, rights, equipment, colour profile, scale, treatment stage, checksum, access restriction, processing history and publication status. Packing all of that into a name is neither practical nor reliable.

UUIDs and readable collection identifiers

Database UUIDs are excellent internal keys but awkward for people to read, compare and type. A collection system can retain an immutable UUID for integrity while assigning a shorter permanent code for portable filenames. The mapping between them must itself be permanent.

Internal UUID: 4fd98418-1876-4b73-94c3-d79185c5691a
Collection identifier: OI-000184
Filename: OI-000184_front_001.jpg

10. Rename through a controlled workflow

Manual renaming invites typing errors, missing padding, inconsistent vocabulary, duplicated names and accidental extension changes. Renaming after ingest can also break database links, thumbnails, checksums, synchronisation records, web URLs and derivative relationships. Generate names automatically wherever possible and create an audit trail.

DSC_4827.NEF -> OI-000184_front_001_original.nef
DSC_4828.NEF -> OI-000184_back_002_original.nef
DSC_4829.NEF -> OI-000184_spine_003_original.nef

11. Migrating an existing image library

A collector with thousands of IMG_#### files needs a preservation project, not a weekend of manual tidying. Establish copies, fixity and context first; rename only after relationships can be defended.

12. Diagnostic failure patterns

Weak names fail in predictable ways. The question is not whether a name looks understandable in its current folder, but what happens when the collection grows, several people contribute, files are exported or evidence is revisited years later.

13. Policy, validation and specialist thresholds

A convention exists only when it is documented. Otherwise it is a personal habit that will drift as the collection grows, software changes or other people contribute.

Validation belongs in software

The platform should generate or validate names rather than expecting every collector to remember every rule. Validation can confirm that the identifier exists, the view term is approved, the sequence is padded, the extension matches the format, the name is unique and no restricted information appears in a public derivative.

OI-[six digits]_[approved-view]_[three digits]_[approved-role].[extension]

14. Recommended Collectaneum model

For a structured collector platform, a readable owned-item code should act as the portable collection identifier while the database continues to use immutable UUIDs for internal integrity.

[owned-item-id]_[view]_[capture-sequence]_[derivative-role].[extension]

OI-000184_overall-front_001_original.jpg
OI-000184_overall-front_001_thumb-600.jpg
OI-000184_overall-front_001_thumb-200.jpg

The platform should store the filename as one part of the asset record, not as the asset record itself. That separation allows exported files to remain intelligible without forcing volatile, sensitive or technical detail into the visible name.

Continue learning

Related topics