{"id":1227,"date":"2026-01-01T16:07:53","date_gmt":"2026-01-01T16:07:53","guid":{"rendered":"https:\/\/dcpready.com\/en\/?page_id=1227"},"modified":"2026-02-04T10:16:07","modified_gmt":"2026-02-04T10:16:07","slug":"isdcf-dcp-naming-convention","status":"publish","type":"page","link":"https:\/\/dcpready.com\/en\/isdcf-dcp-naming-convention\/","title":{"rendered":"DCP Naming Convention"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

ISDCF DCP NAMING CONVENTION <\/h1>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

When a DCP is delivered to a cinema or festival, the first thing a projectionist or technician sees is often the folder name<\/strong>. If that name is vague (or inconsistent across versions), it\u2019s easy to ingest the wrong package, schedule the wrong language, or confuse a 2K\/4K or 5.1\/2.0 version.<\/p>

That\u2019s why the industry widely uses the ISDCF naming convention<\/strong>: a practical, human-readable way to name DCPs consistently. ISDCF is not a \u201claw\u201d like SMPTE\/DCI specs; it\u2019s a community convention created to make DCP handling safer and more predictable across labs, distributors, festivals, and cinemas.<\/p>

What ISDCF helps you communicate<\/h3>

A good ISDCF name quickly answers the key questions people need in real-world operations, such as:<\/p>

  • Which title is this?<\/strong><\/p><\/li>

  • Which version\/variant is it?<\/strong> (original, edited, different cut, trailer, etc.)<\/p><\/li>

  • Language and subtitles<\/strong> (OV, dubbed, burned-in subs, open captions, etc.)<\/p><\/li>

  • Picture format<\/strong> (2K\/4K, Flat\/Scope, frame rate when relevant)<\/p><\/li>

  • Audio format<\/strong> (5.1, 7.1, stereo, accessibility tracks when applicable)<\/p><\/li><\/ul>

    Why it matters<\/h3>

    ISDCF naming doesn\u2019t replace the internal metadata (CPL\/PKL) inside the DCP, but it reduces mistakes before anyone even opens the package<\/strong>. It becomes especially important when you deliver multiple versions (VO\/VOSE, different subtitle languages, stereo vs 5.1, different aspect ratios, different territories, etc.).<\/p>

    Use the calculator<\/h3>

    Use this calculator to generate an ISDCF-compliant name based on your actual delivery parameters. Then copy the result directly as your DCP folder name (and keep the same structure across all versions for clarity and consistency).<\/p>

    If you want, I can also give you a short \u201ccompact\u201d version (3\u20134 lines)<\/strong> for landing pages, and a more technical version<\/strong> that explains common tags and pitfalls (e.g., OV vs VO, open captions vs burned-in, Flat\/Scope conventions).<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t\t
    \r\n
    \r\n

    ISDCF \/ DCNC Name Calculator (DCP)<\/h2>\r\n

    Generate a compliant ContentTitleText<\/em> for your CPL. Copy the result and use it identically for CPL ContentTitleText<\/code> and AnnotationText<\/code> in CPL and PKL.<\/p>\r\n\r\n

    \r\n
    \r\n

    ISDCF fields (recommended order)<\/h2>\r\n
    Do not drop fields. If unknown, use NULL<\/code>. Fields are separated by _<\/code>; sub-fields by -<\/code>.<\/div>\r\n
    \r\n Title<\/span>\r\n ContentType<\/span>\r\n Aspect<\/span>\r\n Language<\/span>\r\n Subtitles<\/span>\r\n Audio<\/span>\r\n Resolution<\/span>\r\n Studio<\/span>\r\n CreationDate<\/span>\r\n Standard<\/span>\r\n PackageType<\/span>\r\n <\/div>\r\n <\/section>\r\n\r\n
    \r\n
    \r\n
    \r\n