A filename your future self can understand

Use explicit asset and language codes, then verify rather than guess.

A predictable filename helps both humans and small tools. CueCheck looks for asset and language codes as separate segments, using periods, underscores or spaces as separators. It does not infer that “Spanish final” means a particular language version of a particular episode.

Start with a simple pattern

Use a pattern such as project.S01E03.pt-BR.srt. The project prefix is for people, S01E03 identifies the asset, pt-BR is the requested language code, and the extension describes the subtitle format. Put the same asset and language codes into the expected delivery fields.

Keep the language code intact

A hyphen can be part of a language tag such as pt-BR or zh-Hant. Use a period or underscore around that tag, rather than breaking it into separate fields. Matching is case-insensitive, but en and en-US remain distinct codes. CueCheck does not automatically substitute one for the other.

Separate versions from expected deliveries

If you add both project.E01.en.v1.srt and project.E01.en.v2.srt, the tool finds two files for the same expected slot. That is useful: your final folder should make the intended handoff unambiguous. Review your brief before deciding whether a second format or version is actually required.

Use manual assignment when names are irregular

Files with different naming conventions are still usable. Add them, then choose their asset and language on each card. Unassigned files do not silently fill a gap. If your package includes different required language sets for different assets, run separate checks for each subset in this first version.

Export plain UTF-8 text

CueCheck accepts UTF-8 .srt and .vtt files, including a UTF-8 byte-order mark. If a file uses an older encoding, export a UTF-8 copy in your subtitle editor first. Renaming a file extension does not convert the underlying format.