Subtitling Standards

Both platforms agree on how fast a viewer should read. They disagree on almost everything about how that text has to be delivered. Streaming platforms don’t just accept subtitle files — they enforce detailed technical specifications, and a file built for one platform routinely fails automated quality control on another. Disney+ and Amazon Prime Video are a useful pair to compare because they sit close together on the fundamentals that actually affect how a subtitle reads — speed, line length, duration — while diverging sharply on the formats, delivery mechanics, and territory rules that determine whether a technically correct file is even accepted in the first place. This comparison breaks down exactly where Disney+ and Amazon Prime Video align, where they differ, and what that means in practice for anyone delivering subtitles to either platform — whether that’s a studio localization team, an independent filmmaker using Prime Video Direct, or a production house preparing deliverables for both at once. It’s worth noting up front that neither platform publishes every detail of its specification as openly as Netflix does with its Timed Text Style Guide. Disney+ manages much of its documentation through approved vendor relationships, and Amazon’s Video Central portal is the authoritative source for delivery partners rather than a single public style guide. The comparison below reflects the technical specifications and requirements that are documented and consistently reported across industry sources, and any team preparing an actual delivery should confirm current details directly with the platform or an approved vendor before submission, since these specifications are updated periodically. Why the Differences Matter A subtitle file is typically rejected before a human reviewer ever sees it. Automated quality-control systems check format compliance, encoding, timing, and reading speed against the platform’s exact specification, and a mismatch — the wrong container format, a timecode that doesn’t start where the platform expects, an unsupported character — fails the file outright, regardless of how accurate or well-timed the translation is. Understanding precisely where Disney+ and Amazon’s requirements diverge is what prevents a deliverable built for one platform from bouncing off the other’s QC system on the first submission. File Format: The Biggest Practical Difference This is where the two platforms differ most. Disney+ standardizes on IMSC 1.1, a TTML profile purpose-built for subtitle and caption delivery, as its primary format across most content. Amazon Prime Video takes a broader approach, accepting several formats depending on whether the file is a closed caption or a dialogue-only subtitle: DFXP/TTML, SRT, and iTT for subtitles, with STL, DFXP, SCC, and SRT accepted for closed captions. That flexibility on Amazon’s side is convenient but comes with a caveat worth flagging clearly: SCC is accepted for captions only and will be rejected if submitted as a standard subtitle file. Disney+, by contrast, offers far less format flexibility — content built outside the IMSC 1.1 profile generally needs to be reconformed before it will pass Disney’s delivery pipeline. Japanese content adds another layer of divergence. Disney+ publishes its own Japanese Subtitles IMSC 1.1 specification, keeping Japanese inside the same TTML family used for its other languages. Amazon instead requires Japanese timed text to be delivered as Lambda Cap (.cap) — a distinct format with no equivalent requirement on Disney+. Side-by-Side: Core Technical Requirements Requirement Disney+ Amazon Prime Video Primary format IMSC 1.1 DFXP/TTML, SRT, or iTT (subtitles); STL, DFXP, SCC, or SRT (captions) Japanese format IMSC 1.1 (Disney’s own Japanese spec) Lambda Cap (.cap) — required, no alternative Minimum duration 1 second 1 second Maximum duration 7 seconds 7 seconds Max reading speed 20 CPS 20 CPS Max characters per line 42 42 Max lines per event 2 2 (up to 3 for closed captions) Encoding UTF-8 UTF-8 (mandatory, no alternative accepted) Timecode start Platform-conformed via approved vendors Must start at 00:00:00:00 — no offset supported SDH / captions Required for accessibility Preferred over standard subtitles; mandatory in the US Where Disney+ and Amazon Actually Agree Strip away the formatting and delivery mechanics, and the two platforms are nearly identical on the metrics that determine how a subtitle actually reads on screen: This convergence isn’t a coincidence — it reflects a broader industry standardization around what makes subtitles genuinely readable, largely shaped by the same research and viewer-testing that produced Netflix’s widely referenced Timed Text Style Guide. Where the platforms diverge is almost entirely in delivery mechanics rather than the reading experience itself. Amazon’s Territory-Specific Rules Amazon Prime Video’s requirements shift by region in a way Disney+’s published specifications don’t emphasize to the same degree: Amazon also requires a separate Forced Narrative file for every dubbed audio track included in a multi-audio package — text that displays automatically based on the viewer’s audio selection, not as an optional subtitle. The locale of that file has to match the corresponding audio track exactly; a mismatch means it silently fails to appear when subtitles are turned off, a notoriously hard failure to catch after the fact. What’s Distinctive About Disney+’s Requirements Disney+’s public-facing documentation is comparatively narrower than Amazon’s — delivery specifications are managed primarily through its network of approved vendors rather than a broadly published self-serve technical portal. In practice, this means: The net effect is a platform that’s less flexible on format but, once a vendor is aligned with its IMSC 1.1 pipeline and style guide, highly consistent — precisely because there are fewer accepted variants to manage in the first place. Where Deliverables Most Often Go Wrong A Practical Approach for Delivering to Both Platforms Teams preparing subtitles for both Disney+ and Amazon Prime Video generally get the best results by building once against the strictest shared baseline, then branching for platform-specific delivery rather than starting from scratch for each: vSubtitle supports this exact branch-once, deliver-many workflow. It generates accurate source captions and translations across 100+ languages, keeps every event’s timing intact through the translation process, and exports to the SRT, VTT, TXT, and DFXP formats that cover the bulk of Amazon’s accepted formats and the reformatting starting point