Subtitle Service for OTT Platforms: Buyer's Guide 2026

Most subtitle service reviews are written for content creators and small teams. They compare price per minute, list supported languages, and rate the interface. None of them are written for the person managing subtitle delivery for an OTT platform with a day-and-date release schedule, platform-specific format requirements, and an accessibility compliance obligation.

If you're sourcing a subtitle vendor for OTT distribution, the criteria that matter are almost entirely absent from standard reviews. This guide covers them.

A subtitle service for an OTT platform is a vendor or pipeline that produces timed text files meeting the specific technical, editorial, and accessibility standards required by streaming platforms for ingestion and distribution. It works by combining transcription, translation, timing, timed text style guide conformance, SDH production, and platform-format delivery into a single managed output. It's most commonly evaluated by loc-ops and content acquisition leads at streaming platforms, aggregators, and production companies preparing multi-language releases for global distribution.

Why generic subtitle reviews don't help OTT buyers

A standard subtitle service review answers the question: "Can this tool produce subtitles?" An OTT buyer's question is different: "Can this vendor deliver platform-compliant timed text files, in twelve languages, as separate subtitle and SDH tracks, in TTML1 format, formatted to Netflix's per-language style guide, with a QC pass before submission, at the turnaround our release schedule requires?"

Those are not the same question, and the vendors that answer yes to the first one often cannot answer yes to the second. The five criteria below are what separates an OTT-capable subtitle vendor from a general subtitle service.

Criterion 1: Platform-specific format compliance

Every major OTT platform has published or enforced technical specifications for subtitle delivery, and they differ from each other in meaningful ways. A file that passes one platform's ingestion will often fail another's.

Netflix requires all subtitle and SDH files in TTML1 format (.xml or .ttml), with a specific exception for Japanese, which requires IMSC 1.1. Critically, all positional data within the TTML file must use percentage values — pixel values are not accepted and trigger automatic rejection before a human reviewer sees the submission. Characters must be drawn exclusively from Netflix's published Glyph List. SRT, VTT, and SCC files are not accepted for Netflix delivery unless a specific exception has been agreed with a Netflix representative.

Amazon Prime Video accepts a broader format range — STL (EBU standard), DFXP/TTML, iTT, SCC, and SRT — but enforces UTF-8 encoding as mandatory and requires all timed text files to start at 00:00:00:00. For Japanese content specifically, Amazon requires Lambda Cap (.cap) format, the only format supporting discrete Japanese timed text delivery on the platform. Amazon also prefers SDH captions over standard subtitles wherever both exist, and for US titles, English closed captions are not optional.

Disney+, Apple TV+, and other major platforms each maintain their own style guides with similar principles but varying specific numbers: line length limits typically sit between 40 and 42 characters per line for Latin-script languages, with a two-line maximum per subtitle event, though exact CPS limits and punctuation conventions differ.

The question to ask any vendor: which delivery formats do you produce natively, do you support platform-specific TTML subsets including Netflix's IMSC profile restrictions, and who performs the technical QC pass against current platform specs before submission?

Criterion 2: Per-language timed text style guide adherence

Netflix maintains separate Timed Text Style Guides for more than 30 languages, each building on the universal technical requirements with language-specific punctuation conventions, ellipsis rules, italics handling, dual-speaker formatting, and reading speed calibrations. The general guide sets the framework; the per-language guide is what a file is actually checked against.

This matters because a subtitle file can be technically well-formed in TTML, correctly timed, and still rejected for failing a language-specific convention. English uses double hyphens for abrupt interruptions; some European languages use ellipses in the same context. CJK scripts use different per-line character limits — typically around 16 characters for Chinese and Japanese — because each character is a full display unit. A subtitler working only from the general guide will produce errors that only appear at the per-language QC stage.

For Indian OTT platforms and distributors delivering to international streaming services, this extends to Indic language TTSGs. Naarg Media created the Timed Text Style Guide for Indian languages for Netflix — a reference document covering formatting conventions for Hindi, Tamil, Telugu, and other Indic scripts at broadcaster standard. Any vendor delivering Indian language content to Netflix should be working from or at least aware of this guide. AI-native subtitle pipelines built for Indic languages that handle Devanagari timing calibration and script-specific line-break logic are operating in this space specifically.

The question to ask: do your subtitlers work from the platform's current per-language TTSG for every target language, and how do you handle TTSG updates when platforms revise their guides?

Criterion 3: SDH as a distinct, fully specified deliverable

SDH — Subtitles for the Deaf and Hard of Hearing — is not a subtitle file with a few extra speaker labels added. It is a distinct deliverable with its own specifications, and treating it as a derivative of the standard subtitle file is one of the most common reasons OTT subtitle batches fail platform QC.

Netflix's SDH requirements are explicit: SDH files must include all audio information relevant to the viewing experience — spoken dialogue, speaker identification for off-screen or unclear speakers, relevant sound effects described in square brackets, and music identifiers where applicable. The same maximum reading speed, line length, and format rules apply as for standard subtitles, but the editorial scope is broader. SDH is not a simplified version of captions; it carries the same standard of completeness as the hearing viewer's experience.

Amazon similarly requires SDH wherever closed captions are required, with speaker identification for non-obvious speakers and sound effect descriptions for content-relevant audio events. The practical implication: a subtitle batch for a Netflix original typically requires four distinct deliverable types per language — standard subtitles, SDH, forced narrative (for content shown on screen), and sometimes a combined captions/SDH file — each produced separately and submitted separately.

The question to ask: do you produce SDH as a distinct workflow with separate editorial guidelines, or do you derive it from the subtitle file? Can you show us an example SDH file from a recent OTT delivery?

Criterion 4: Simultaneous multi-language throughput at day-and-date

A day-and-date release — simultaneous global launch in multiple markets on the same calendar day — is the standard for major OTT originals and increasingly expected for catalog titles. It requires all language subtitle files, including SDH variants, to be delivered and platform-ingested before the release window opens. For a title launching in ten markets, that means ten subtitle tracks, ten SDH tracks, and potentially ten forced narrative tracks, all cleared through platform QC simultaneously.

Generic subtitle service reviews don't test for this because most of their target audience never needs it. For OTT platforms and distributors, it's often the most operationally demanding part of the subtitle workflow. A vendor who delivers a single episode in four languages in 48 hours may take three weeks on a full season in twelve languages under deadline pressure — and the quality-under-pressure question is one most vendors won't answer directly unless you ask it explicitly.

The right questions here are granular: what is your maximum throughput per week in hours of content per language, what happens to your QC process when you're at capacity, and do you have documented turnaround commitments for day-and-date multilanguage subtitle delivery that appear in your service agreement rather than just in a sales conversation?

Criterion 5: Catalog scaling vs original release workflows

OTT subtitle sourcing involves two fundamentally different operational problems that vendors often treat as one. Day-and-date original release requires tight turnaround, platform-specific compliance, and simultaneous multi-language output. Catalog scaling — subtitling a library of existing content across many languages to expand market reach — requires volume throughput, consistent quality across a heterogeneous content set, and efficient file management across thousands of titles.

The vendor configuration that suits one doesn't automatically suit the other. A boutique agency with deep Netflix compliance expertise may lack the throughput infrastructure for a 2,000-title catalog project. A high-volume pipeline built for catalog scaling may not have the platform-specific formatting knowledge required for a new original title's simultaneous global launch.

For Indian platforms specifically — distributing originals to international markets while also building out regional language subtitle coverage for existing catalog — both workflows often run simultaneously. Managed subtitle pipelines built for Indic languages that can handle both original release formats and catalog volume represent a distinct requirement from either a boutique compliance specialist or a bulk translation vendor.

The evaluation checklist

Before shortlisting any subtitle vendor for OTT distribution, get specific written answers on the following:

Which platform delivery formats do you produce natively — TTML1, IMSC 1.1, WebVTT, iTT, EBU-STL, SCC — and do you support Netflix's TTML percentage-value positioning requirements?
Do your subtitlers work from the current per-language TTSG for every target language, and how do you track and implement TTSG updates?
Do you produce SDH as a distinct workflow with separate editorial guidelines, not derived from the subtitle file?
What is your documented turnaround for simultaneous multi-language delivery — specify languages, episode count, and time window?
What QC steps run before submission to a platform, and who performs them — automated validator, human reviewer, or both?
Are you a Netflix Preferred Vendor or do you work through one, and how does that affect file rejection risk?
How do you handle a file rejection — what is the rework SLA and who bears the cost of redelivery?

Where it works and where it doesn't

Where an OTT-capable managed subtitle service earns its cost

Day-and-date global releases where platform rejection and redelivery delays directly affect the release date and marketing spend
Originals on major platforms where per-language TTSG compliance is enforced and non-compliance is caught by automated QC before human review
Indian content distributing to international OTT platforms where Indic language TTSG adherence and Devanagari-specific formatting requirements apply
Platforms with ongoing catalog expansion across regional Indian languages where volume throughput and consistent Indic accuracy both matter

Where a lighter-touch option is sufficient

Internal or marketing video content not destined for platform distribution, where TTML compliance and SDH requirements don't apply
Single-language content for a platform with less stringent technical requirements than Netflix or Amazon
Early-stage OTT platforms still building catalog before international distribution relationships are in place

FAQ

What subtitle file format does Netflix require?

Netflix requires TTML1 (.xml or .ttml) for all languages except Japanese, which requires IMSC 1.1 (.xml). All positional data must use percentage values — pixel values are rejected automatically. SRT, VTT, and SCC are not accepted without a specific exception agreed with a Netflix representative.

What is the difference between subtitles and SDH for OTT platforms?

Standard subtitles carry spoken dialogue. SDH adds speaker identification for off-screen or unclear speakers, relevant sound effects in square brackets, and music cues — providing a complete audio picture for deaf and hard-of-hearing viewers. Most major platforms require them as separate, simultaneously delivered files rather than a single combined track.

What is a Timed Text Style Guide and why does it matter?

A TTSG is a platform's published specification for how subtitle files should be formatted — covering reading speed in characters per second, maximum characters per line, line count limits, punctuation conventions, and language-specific rules. Netflix maintains separate TTSGs for 30+ languages. A subtitle file that fails TTSG requirements is rejected by automated QC before a human reviewer sees it.

How does day-and-date release affect subtitle vendor selection?

Day-and-date requires all language subtitle files — including SDH and forced narrative tracks — to clear platform QC before the global release window opens simultaneously. This requires a vendor with documented simultaneous multi-language throughput, a QC pass before submission, and contractual turnaround commitments that hold under deadline pressure, not just in standard workload conditions.

Choosing a subtitle service for OTT distribution is not a cost-per-minute decision. It's a technical compliance decision, an operational throughput decision, and an accessibility standards decision made simultaneously. The vendors that pass generic subtitle reviews often fail on TTML format specifics, per-language TTSG adherence, or SDH production scope. The five criteria that actually differentiate OTT-capable subtitle services — platform format compliance, per-language TTSG adherence, SDH as a distinct deliverable, simultaneous multi-language throughput, and catalog-vs-original workflow fit — are rarely covered in standard comparisons. Building an evaluation process around them before shortlisting saves the cost of a platform rejection and redelivery cycle after.

If you're distributing Indian language content to international platforms and need a subtitle pipeline that handles Indic TTSG compliance, SDH production, and multi-language throughput as one workflow, ButterCut is built for this specifically. Book a free demo to run the evaluation against your actual release requirements.

How to Choose a Subtitle Service for an OTT Platform (What Most Reviews Don't Tell You)

The five OTT-specific criteria generic subtitle reviews never cover: platform TTML compliance, per-language timed text style guides, SDH as a distinct deliverable, simultaneous multilanguage throughput, and catalog vs original release workflows.