Museum Image File Naming Convention
A museum image should remain identifiable after it is removed from the camera, copied to another folder, imported into a collection management system or recovered from backup. A file naming convention provides this minimum identification without duplicating the full catalogue record.
Why museum image file naming matters
Camera and scanner filenames are generated to distinguish files on the capture device. They do not describe museum context. Names such as IMG_4827.JPG, DSC_0008.NEF or Scan1.tif do not identify the object, the view or the intended role of the file. When files from several sessions are combined, these names become ambiguous and can be linked to the wrong record.
A documented naming convention supports retrieval, transfer and long-term management. It allows staff to associate the file with the correct collection record, distinguish controlled source files from delivery copies and reduce the risk of duplicate or overwritten filenames.
The filename is not a substitute for metadata. It is a compact identifier that remains useful when the file is separated temporarily from the catalogue. Descriptions, rights, dates, creators and other detailed information should remain in structured records.
Requirements for a reliable naming convention
Identify the related record
The filename should contain enough stable information for another member of staff to locate the corresponding collection record without relying on the photographer’s memory.
Use a fixed field order
Each element should appear in the same position. A fixed order improves sorting, visual review and automated validation.
Include stable information only
Use identifiers and controlled terms that are expected to remain valid. Titles, locations, rights statements and other changeable information belong in metadata.
Define controlled terms
Use one approved term for each view and file role. Uncontrolled alternatives such as front, face, obverse and main view create inconsistent categories.
Document exceptional cases
Sets, albums, archaeological lots, exhibitions and objects without accession numbers require written rules rather than improvised filenames.
Test the complete workflow
Test representative filenames in the collection system, shared storage, backup process, export tools and publishing workflow before formal adoption.
Begin with an authoritative object identifier
For accessioned material, the accession number is normally the most reliable first field because it identifies the object independently of its current location or description. Placing it first also groups related images during alphabetical sorting.
The semantic content of a historical accession number should be preserved. If the recorded form contains a slash, full stop, space or another character that is unsuitable for the storage environment, use a documented file-safe representation. For example, 2024.15.3 may be rendered as 2024-15-3. Only the separator changes; the numbered components remain unchanged.
Leading zeros should not be added to an accession number solely to improve sorting unless they are part of the museum’s authorised numbering policy. Zero padding is more appropriately applied to the image sequence, for example 01, 02 and 03. The conversion between the catalogue form and the file-safe form should be unambiguous and documented.
A clear filename structure
For many object-photography workflows, four fields are sufficient:
2024-15-3_front_master_01.tif
In this example, 2024-15-3 is the file-safe form of the object identifier, front describes the photographed view, master states the role of the file and 01 distinguishes it from other files with the same identifier, view and role.
The identifier appears first so that related files remain grouped and can be matched to the collection record. Descriptive titles are normally excluded because they may change, differ between cataloguers or create unnecessarily long filenames. Detailed description remains in the catalogue record.
| Component | Purpose | Example | Rule |
|---|---|---|---|
| Identifier | Connects the file to the object or group record. | 2024-15-3 | Unique, stable and documented. |
| View | States what the image shows. | front | Use an approved controlled list. |
| Role | States the management or delivery role of the file. | master | Do not infer role from format alone. |
| Sequence | Distinguishes several files of the same type. | 01 | Use leading zeros consistently. |
| Extension | Identifies the actual file format. | tif | The extension must match the encoded format. |
Document the convention before large-scale capture
- The authoritative source of the object identifier.
- The exact file-safe conversion for punctuation and prefixes.
- The controlled lists for views, file roles and project-specific terms.
- The sequence width and when numbering restarts.
- Case, separators, dates, maximum filename length and permitted characters.
- The workflow for temporary identifiers, multi-part objects and exhibition images.
- Who approves exceptions and who maintains the naming policy.
- How filenames, digital asset IDs, metadata, backups and migration logs remain linked.
Describe the photographed view with controlled terms
Common terms include front, back, left, right, top, base, detail, label, signature, inscription and context. Only terms relevant to the collection need to be adopted.
Each term should have a written definition. For example, label may refer to an attached maker’s or ownership label, whereas inscription may refer to text or marks applied directly to the object. context may describe an object in situ, an exhibition installation or a storage arrangement. Without definitions, different staff may assign different terms to equivalent images.
Use a sequence number when more than one image has the same identifier, view and role:
2024-15-3_front_master_02.tif
2024-15-3_detail_master_01.tif
Adapting the pattern for specialist collections
Numismatic collections commonly need separate terms for the obverse and reverse of a coin, medal or seal. Collections of drawings, prints, documents and manuscript leaves may require recto and verso. Other collections may need terms for an edge, interior, exterior, watermark, inscription or conservation detail.
2024-15-3_reverse_master_01.tif
2024-22-8_recto_master_01.tif
2024-22-8_verso_master_01.tif
Full terms are generally easier to interpret and exchange between systems. Short codes may be used when they are defined in the museum’s written naming policy and applied consistently in filenames, collection records and exports.
Institutional requirements and DAM systems
This guide provides a practical baseline, not a national or sector-wide standard. Before adopting it as institutional policy, a museum should check the requirements of its funding body, national heritage authority, archive, consortium and collection management system. Where an external standard or grant condition applies, that requirement takes priority.
Modern digital asset management systems can retrieve files through metadata, controlled tags and automated image analysis, reducing dependence on highly descriptive filenames. This does not make filenames irrelevant. Museum files are frequently exported, transferred to suppliers, copied to offline storage or recovered outside the original system. A stable identifier and a small number of controlled filename fields therefore remain useful as a portable link to the collection record.
The naming convention should complement metadata and system controls rather than attempt to replace them.
Identify master and derivative files by role
A museum may retain a controlled source file and generate derivatives for specific purposes. The source file designated as the master should be managed according to the institution’s imaging and digital-preservation policy. Derivatives may be created for editing, print production, online delivery or interface previews.
Avoid terms such as final, new, best or final-final2. These labels describe a temporary stage in an individual workflow and do not define the file’s long-term role. Terms such as master, edit, print, web and thumb are more precise.
File format and file role are separate properties. A TIFF file is not automatically a preservation master, and a JPEG file is not automatically temporary. The filename may state the role, while technical metadata and institutional policy define format, compression, colour space, resolution and preservation requirements.
| Role term | Purpose | Typical handling |
|---|---|---|
| master | Controlled source file designated for long-term retention or future reuse. | Protected from unintended editing; included in managed backup and fixity checking. |
| edit | Working file used for correction, cropping, compositing or retouching. | May contain layers or processing that are not present in the master. |
| Output file prepared for publication, signage or print production. | Created to a defined size, colour profile and production specification. | |
| web | Delivery derivative prepared for a website, online catalogue or digital interpretation. | Dimensions and compression are adjusted; rights and restrictions are checked before publication. |
| thumb | Small derivative used for interface display and rapid visual identification. | Generated automatically from a controlled source where possible. |
Define rules for groups, sets and temporary records
Objects without accession numbers
Assign a unique temporary identifier such as TMP-00427. Generic object names and personal initials are not sufficient because they may not be unique. The temporary record should identify who created the number and how the files will be reconciled if the object is later accessioned.
Sets and multi-part objects
Distinguish the group record from individual components. A set image might use set, while individual parts retain component identifiers or a documented suffix.
Archaeological lots
Use the project, context, lot or finds identifier already recognised by the museum. Avoid inventing a parallel image-only numbering system that cannot be reconciled with the excavation record.
Albums and bound volumes
Include a stable volume identifier and a zero-padded page or leaf sequence where appropriate. Record whether the image is a page, cover, spine, detail or full opening.
Exhibition and installation views
These may belong to an event or documentation record rather than one object. Use a stable exhibition or project identifier plus date and sequence according to a separate documented pattern.
Conservation and condition images
Link the image to the object and the treatment or condition event. A date may be useful here, but it should not be the only identifier.
Use folders for organisation, not identification
A directory structure may separate accession years, object groups, master files, derivatives and supporting documentation. Excessive nesting should be avoided because long paths are harder to read, copy, validate and migrate.
2024/
2024-15/
masters/
derivatives/
documentation/
The folder should not be the only source of identification. A file named front_01.tif may be understandable within one object folder but becomes ambiguous when copied to a working directory, attached to an email or transferred to a supplier.
The folder structure should be documented together with the naming convention. The procedure should define where new captures are received, when a file becomes a controlled master, where derivatives are created and which directories are included in backup and preservation processes.
Specify characters, case, dates and maximum length
Safer practice
Use consistent separators: for example, hyphens within the object identifier and underscores between filename fields.
Use consistent letter case: lowercase controlled terms avoid duplicate forms such as Front, FRONT and front.
Use zero padding for sequences: 01, 02 and 03 continue to sort predictably when the sequence reaches 10 or more.
Use an ISO 8601 date form when required: YYYYMMDD or YYYY-MM-DD, applied consistently.
Set a practical maximum length: retain essential identification fields and keep the full descriptive record in the collection system.
Common risks
Reserved punctuation: slashes, colons, question marks, asterisks and quotation marks may be prohibited or interpreted differently by operating systems and transfer tools.
Changing case: some platforms treat Front and front differently.
Long descriptive strings: they increase typing errors and can create excessive path lengths.
Misleading extensions: renaming a file from .jpg to .tif does not convert its format.
Personal shorthand: initials and undocumented abbreviations may become uninterpretable when staff or contractors change.
Maintain links between filenames, records and metadata
Before large-scale imaging begins, test how the collection management system or digital asset management system handles original filenames. A system may copy files into managed storage, maintain a link to an external path or assign an internal asset name. The institution should confirm whether the original filename remains visible, searchable and exportable.
The collection record should describe the relationship between the image and its subject, including the image role, creator, capture date, rights status and restrictions on use. Where a separate reproduction number or digital asset ID is assigned, it should be stored alongside the object identifier. The object identifier records what is shown; the asset identifier records which capture or managed file is being referenced.
Where supported, selected identifiers and rights information may also be written to embedded metadata. Embedded metadata improves portability, but it should not be the sole record because processing, conversion and publishing tools may remove or alter it.
A test export should be completed before the collection grows substantially. The export should retain the original filename, object identifier, digital asset ID and sufficient relationship data to reconnect each image in another system. Descriptions, rights and other contextual information should continue to come from the collection record rather than from the filename alone.
Import ten representative files
- Include several views and file roles for one object.
- Include an object with punctuation in its accession number.
- Include a temporary identifier and a multi-part object.
- Check whether the original filename remains visible.
- Export the records and images again.
- Confirm that another person can reconstruct every link.
Rename an existing image archive as a controlled migration
1. Inventory the files
Record file counts, formats, storage locations, duplicates and known links to collection or digital asset records.
2. Build a mapping table
For each file, record the old filename, proposed filename, related identifier, reason for change and review status.
3. Test a small batch
Select files that represent different objects, roles, punctuation patterns and exceptional cases before applying the procedure at scale.
4. Protect content and verify fixity
Do not work on the only copy of the master set. Generate or verify checksums before the operation, retain a protected backup and verify the files again after copying or renaming.
5. Update record links
Update and test references in the collection system, digital asset management system, spreadsheets, websites and procedural documentation.
6. Reconcile the result
Compare pre- and post-migration file counts, investigate duplicates, identify missing links and document failed operations.
7. Retain the migration log
Preserve the old-to-new mapping, dates, operators, review decisions and exceptions as permanent migration documentation.
8. Apply the approved convention
Publish the final rule, train staff, update templates and prevent new uncontrolled filenames from entering managed storage.
Quality-control checks before storage or import
Identifier
The file-safe identifier maps unambiguously to one authoritative object, group, event or temporary record.
View
The term comes from the approved list and accurately describes what the image shows.
File role
The role—master, edit, print, web or thumbnail—is assigned according to policy and is not inferred from the file format alone.
Sequence
Multiple images use zero-padded numbers and do not overwrite one another.
Technical match
The extension matches the actual format and the file opens correctly after transfer.
Uniqueness
No existing controlled file has the same complete filename.
Record link
The collection system or DAM points to the correct object and, where used, preserves the separate digital asset ID.
Fixity
Checksums for controlled master files are created or verified before transfer and confirmed again afterward.
Audit trail
Any rename retains the old filename, new filename, date, reason, operator and review status in a mapping log.
Backup and handover
The file is included in the correct backup and another person can interpret the name and reconstruct its record link.
Filename examples and assessment
| Filename | Assessment | Reason |
|---|---|---|
| 2024-15-3_front_master_01.tif | Good | The identifier is a file-safe rendering of 2024.15.3; the view, role, sequence and extension are explicit. |
| MUS-2024-15_front_master_01.tif | Good | Suitable when MUS-2024-15 is the authorised object identifier and the prefix is part of the institutional numbering system. |
| 2024-15-3_label_web_01.jpg | Good | Distinguishes the label view and online derivative. |
| TMP-00427_front_master_01.tif | Conditional | Useful only when the temporary identifier is unique, recorded and later reconciled. |
| IMG_4827.JPG | Poor | No object identity, view or role. |
| bowl-final-final2.jpg | Poor | Generic object term and unstable workflow language. |
| Store-A-Shelf-4-bowl.jpg | Poor | Location changes and does not uniquely identify the object. |
| 2024/15/3 front.tif | Risky | Slashes may be interpreted as folder separators, and the spacing rule is unclear. |
| 2024-15-3_front.tif | Incomplete | May be acceptable in a simpler policy, but it does not distinguish master and derivative roles. |
Frequently asked questions
What should a museum image filename include?
At minimum, it should contain a stable identifier and enough controlled information to distinguish the view, file role and sequence. A common structure is identifier_view_role_sequence.ext.
Should the accession number be used in the filename?
Usually yes, when it is the museum’s stable object identifier. If the accession number contains characters that are unsafe in filenames, use a documented file-safe rendering and preserve the exact original number in the collection record.
Should leading zeros be added to an accession number?
Not solely to improve sorting. Preserve the accession number’s authorised components and change only unsafe separators according to a documented rule. Use zero padding for the image sequence unless leading zeros are already part of the museum’s official numbering policy.
What is the difference between an object ID and a digital asset ID?
The object or accession number identifies what was photographed. A reproduction number or digital asset ID identifies the individual capture or managed file. One object may therefore be linked to many digital asset IDs.
Should object titles or donor names be included?
Usually not. Titles, donor names, locations and rights information can change and may be sensitive. Store them as metadata in the collection system rather than making them part of a permanent filename.
How should multiple photographs of one view be named?
Use a controlled view term and a zero-padded sequence, such as 2024-15-3_front_master_01.tif and 2024-15-3_front_master_02.tif.
What is the difference between a master and a derivative?
A master is the controlled source file designated for long-term retention or future reuse under institutional policy. Derivatives are files generated from that source for editing, print, web delivery or interface previews.
Can old museum image files be renamed safely?
Yes, but only through a controlled migration. Inventory the files, create an old-to-new mapping table, verify checksums before and after the operation, update database links, compare counts and retain a change log.
Should filenames use spaces or special characters?
For broad interoperability, many museums avoid spaces and reserved punctuation, use a consistent separator such as a hyphen or underscore, and keep the extension accurate. The exact rule should be documented and tested with the museum’s systems.
Is the filename a replacement for metadata?
No. A filename provides compact identification and supports routing. Descriptions, dates, rights, creators, locations and other detailed or changeable information belong in structured metadata and the collection record.