SNUBBIX

Quality & Standards

The checks every file goes through

These are the validation procedures we actually run. They are our own internal checklist — not an official industry certification.
  • 01SRT structural rules

    Automated

    Each cue must be: a sequence number, a timing line, one or more lines of text, then a blank line. Blocks that don't follow this are reported as malformed with their line number.

    1
    00:00:01,000 --> 00:00:03,500
    Welcome to SNUBBIX.
    
  • 02Timestamp syntax

    Automated

    Timestamps must be HH:MM:SS,mmm — two-digit minutes and seconds below 60, a comma before three-digit milliseconds, separated by " --> ".

    00:00:03.700  ✗  full stop instead of comma
    00:00:03,700  ✓
  • 03Cue numbering

    Automated

    Numbers must start at 1 and increase by one. Missing, duplicated or out-of-sequence numbers are flagged and corrected on delivery.

  • 04Start/end validation

    Automated

    Every end time must be later than its start time. Zero-length and negative cues are errors.

  • 05Subtitle ordering

    Automated

    Cues must be in chronological order of start time. A cue that starts before the previous one is an error.

  • 06Overlap detection

    Automated + manual

    A cue starting before the previous cue ends is flagged. Some overlaps are intentional (e.g. two speakers); a reviewer decides against your rules.

  • 07Readability checks

    Automated + manual

    Default rules (adjustable per project): ≤ 42 characters per line, ≤ 2 lines per cue, ≤ 20 characters per second, 0.833–7 s on screen. Flags are reviewed in context.

  • 08Encoding & compatibility

    Automated

    Files must decode as UTF-8 (UTF-16 is flagged), contain no binary data, and use consistent line endings. Byte-order marks are noted.

  • 09Output review

    Manual

    Before delivery a person reviews the validation results, file names and the delivery package against the quotation.

  • 10Source-to-output verification

    Manual

    Where included in your quotation, timing is spot-checked against the source media. This is the only check that compares subtitles to what is actually spoken.

Example report

See what a validation report looks like

Download a demonstration report produced by our validator from a deliberately flawed sample file. It is clearly labelled as a demonstration and describes no customer file.

Download sample report (.txt)

What we don't claim

We don't guarantee that a file satisfies a particular broadcaster's or streaming platform's requirements unless that specification has been identified in your quotation and tested. We never describe files as “100% error-free”.
Structural validation cannot confirm that subtitle text matches the spoken words. Text accuracy depends on the transcript you supply, and on source review where that is included.

Have a Subtitle Project to Deliver?

Share your video duration, source files, required output, and deadline to receive a project-specific quotation.