A file naming convention is the rule set behind every filename in a DAM: what fields it includes, in what order, separated by what character, in what date format. Its value is easy to underestimate because a good DAM’s search makes filenames feel unimportant \u2014 but the moment an asset is exported, emailed, or handed to a print vendor, the filename is the only metadata that travels with it.<\/p>
Digital preservation guidance from library and archives institutions converges on a small set of practical rules: use only letters, digits, hyphens, and underscores; avoid spaces and special characters that behave inconsistently across operating systems; use ISO 8601 date format (YYYYMMDD) so files sort chronologically; and zero-pad sequence numbers so “page2” doesn’t sort after “page100.” These aren’t arbitrary style preferences \u2014 each rule solves a specific, observed failure mode in real file systems.<\/p>
The gap between having a convention and having consistent filenames is enforcement, not documentation. A style guide that lives in a PDF nobody reads at upload time produces the same messy library as having no convention at all \u2014 which is why the more durable version of this concept, controlled file naming, builds the rule into the system itself rather than relying on contributors to remember it.<\/p>","protected":false},"excerpt":{"rendered":"
A documented, agreed-upon pattern for constructing filenames so every asset in a system is named consistently and predictably.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"Why does a naming convention matter even with good DAM search?","answer":"The moment an asset is exported, emailed, or handed to a print vendor, the filename is the only metadata that travels with it."},{"question":"What rules does digital preservation guidance recommend for filenames?","answer":"Use only letters, digits, hyphens, and underscores; avoid spaces and special characters; use ISO 8601 date format (YYYYMMDD); and zero-pad sequence numbers so files sort correctly."},{"question":"Why does zero-padding sequence numbers matter?","answer":"Without it, \"page2\" sorts after \"page100\" instead of before it, breaking chronological or numeric ordering."},{"question":"What's the gap between documenting a convention and having it followed?","answer":"Enforcement, not documentation \u2014 a style guide nobody reads at upload time produces the same messy library as having no convention at all."},{"question":"What typically happens to a naming convention that's only documented, not enforced?","answer":"Within months, half the library follows the rule and half still carries camera-default or freelancer-supplied filenames."},{"question":"What's the more durable alternative to a documented-only convention?","answer":"Controlled file naming, which builds the rule into the system itself \u2014 auto-generating or validating filenames \u2014 rather than relying on contributors to remember it."}],"checked_date":"2026-08-07","sources":[{"statement":"Digital preservation best practice recommends filenames use only letters, digits, hyphens and underscores (no spaces or special characters), ISO 8601 date format, and zero-padded sequence numbers so files sort and open correctly.","source_name":"Penn State University Libraries \u2014 Personal Digital Archiving guide","url":"https:\/\/guides.libraries.psu.edu\/c.php?g=1190817&p=8709882","checked":"2026-08-07"}],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"","seo_description":"","noindex":false,"related":[2472,2507,2493,2557,2494,2477],"definition":"A documented, agreed-upon pattern for constructing filenames so every asset in a system is named consistently and predictably.","why":"A consistent naming convention keeps files identifiable and sortable outside the DAM too \u2014 in a folder export, an email attachment, a printer's file drop \u2014 which matters because assets constantly leave the DAM's search index and travel as bare files with no metadata attached. Conventions typically fix the field order (project, date, version), the separator character, and the date format so files sort chronologically and a human can identify a file without opening it.","example_rows":[{"field":"Pattern","values":"{client}_{project}_{YYYYMMDD}_{version}.{ext}"},{"field":"Example","values":"acme_springcampaign_20260304_v03.psd"},{"field":"Rule","values":"No spaces or special characters, ISO 8601 dates, zero-padded sequence numbers"}],"mistake":"Conventions get documented but not enforced at ingestion, so within months half the library follows the rule and half still carries camera-default or freelancer-supplied filenames, defeating the point.","deep_link":""},"silo":[24],"class_list":["post-2582","glossary","type-glossary","status-publish","hentry","silo-glossary"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2582","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary"}],"about":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/types\/glossary"}],"version-history":[{"count":3,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2582\/revisions"}],"predecessor-version":[{"id":3550,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2582\/revisions\/3550"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=2582"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=2582"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}