OTT Subtitling Standards: What Netflix, Amazon Prime & Disney+ Actually Require

Introduction: Why Subtitling Standards on OTT Platforms Are Non-Negotiable

The global streaming wars have produced an unexpected battlefield — the subtitle file. As Netflix, Amazon Prime Video, and Disney+ expand into every corner of the world, subtitling has evolved from a simple accessibility tool into a highly technical, compliance-driven discipline with real stakes for content creators, production studios, and localization professionals.
Get it wrong, and your subtitle file is rejected before a human reviewer even sees it. Get it right, and your content reaches billions of viewers in their native language — seamlessly, accurately, and professionally.
But what does ‘getting it right’ actually mean for each platform? The answer is more detailed than most people expect, and the differences between platforms matter enormously when you are preparing deliverables.
This guide breaks down precisely what Netflix, Amazon Prime Video, and Disney+ require for subtitles and closed captions — drawn from their own published technical specifications and style guides. Whether you are a filmmaker, a localization project manager, or a subtitling vendor, this is what you need to know before you submit.

Understanding the Basics: Subtitles vs. Captions vs. SDH

Before diving into platform-specific requirements, it is important to understand the terminology these platforms use, because conflating these terms is one of the most common sources of delivery confusion.

Netflix: The Most Demanding Standard in Streaming

Netflix has invested more heavily in subtitling standardisation than any other streaming platform. Its Timed Text Style Guide (TTSG) is a living document, regularly updated, and covers everything from file format and frame rates to ellipsis usage and translator credits. Understanding it fully is the baseline requirement for any Netflix-approved localization vendor.

File Format Requirements

All subtitle and SDH files for Netflix must be delivered in TTML1 format — either with a .xml or .ttml file extension. Japanese is an exception: it must be delivered in IMSC 1.1 format with a .xml extension. Netflix rejects files in unsupported formats before a human reviewer sees the submission.
Within the TTML file, all positional data must use percentage values only — pixel values are not accepted. Positioning must be expressed using tts:textAlign and tts:displayAlign, with static values for tts:extent and tts:origin. The tts:fontSize must be defined as 100%. Text characters must be drawn exclusively from the Netflix Glyph List; characters outside this list will trigger a rejection.

Timing Rules

Netflix’s timing requirements are built around a single philosophy: subtitles should feel like you are watching the content, not reading it.
The minimum duration per subtitle event is five-sixths of a second — 20 frames at 24fps. The maximum duration is 7 seconds per event. There must be a minimum gap of 2 frames between consecutive subtitle events.
Subtitles must be in sync with both the image and the audio. The in-time should be on the first frame of audio or within 1–2 frames of it. The out-time, when no subtitle immediately follows, should ideally extend at least half a second past where the audio ends.
Shot changes require particular attention. Netflix instructs subtitlers to avoid subtitle events that cross shot changes wherever possible. When dialogue genuinely crosses a shot change, Netflix provides a detailed framework: if dialogue starts 8–11 frames before the shot change (the ‘green zone’), the in-time should be moved to at least 12 frames before the shot change. If it starts 7 frames or fewer before the shot change (the ‘red zone’), the in-time should be moved to the shot change itself.

Reading Speed and Character Limits

For English content, Netflix sets a maximum reading speed of 20 characters per second (CPS) for adult content and 17 CPS for children’s content. Reading speed violations are one of the most common causes of Netflix rejections.
The maximum line length is 42 characters per line for most Latin alphabet languages. Text should generally be kept to one line unless it exceeds this limit. When two lines are required, Netflix provides specific segmentation guidance: breaks should occur after punctuation marks, before conjunctions, before prepositions, and should not separate a noun from its article, a first name from a last name, or a verb from its auxiliary.
All subtitles must be centre-justified and placed at either the top or bottom of the screen. Bottom placement is standard; top placement is used when on-screen text at the bottom of the frame would be obscured.

SDH Requirements

SDH files at Netflix 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. SDH is not a simplified version of captions — it carries the same standard of completeness.

Style and Linguistic Requirements

Netflix produces language-specific style guides for every supported language, each building on the universal technical requirements. These cover punctuation conventions, ellipsis usage, italics rules, dual-speaker formatting, and more.

• Ellipses must use the single smart Unicode character (U+2026) rather than three consecutive periods
• When dialogue trails off or a pause of two or more seconds occurs, an ellipsis is used
• When dialogue is interrupted abruptly, two hyphens are used
• Currency must not be converted — money amounts must remain in the original currency
• Consistency across episodes is enforced through Key Names & Phrases (KNP) glossaries and formality tables

Netflix also requires a translator credit as the last event in every subtitle file for episodic and feature content. This credit should be entirely in the target language, timed for reading speed with a duration of up to five seconds, placed after the copyright disclaimer card at the end of the programme.

Amazon Prime Video: Comprehensive and Territory-Specific

Amazon Prime Video’s subtitle requirements are extensive and, notably, territory-sensitive — what is required in the United States differs from requirements in Japan, the UK, or other markets. Prime Video publishes its specifications through its Video Central documentation, which is updated regularly.

The Hierarchy: Captions Over Subtitles

Amazon’s first principle is clear: whenever both closed captions/SDH and subtitles are available for a title, Amazon prefers to receive captions or SDH over standard subtitles. For US delivery specifically, English captions are not optional — they are required for every title published in the United States, without exception.

Accepted File Formats

Amazon Prime Video accepts a broader range of timed text formats than Netflix, and the accepted formats differ by asset type:
For closed captions:

• STL (EBU standard) — .stl
• DFXP Full/TTML — .dfxp
• SCC — .scc
• SRT — .srt

For subtitle files (dialogue only):

• DFXP Full/TTML — .dfxp
• iTT (iTunes Timed Text) — .iTT
• SRT — .srt

Note: SCC format is for captions only and is not accepted as a subtitle file. For Japanese timed text, all content must be delivered as Lambda Cap (.cap) — the only format that supports discrete Japanese timed text delivery on Prime Video.

Critical Technical Rules

UTF-8 encoding is mandatory. Amazon accepts no other encoding, and a file in any other encoding will fail ingestion.
All timed text files must start at 00:00:00:00. Amazon does not support timecode offsets. Files with a one-hour offset — common in broadcast workflows — will display no text until one hour into the video, causing a silent failure that is notoriously difficult to diagnose after upload.

Territory-Specific Requirements

• United States: English captions are mandatory for all titles. All dialogue in any language must have corresponding English-language captions.
• Japan: Closed captions are not toggle-able for viewers. Burned-in Japanese subtitles are required if the content does not contain localised Japanese audio.
• United Kingdom: You need either audio or captions in the localised language to publish. English audio qualifies even if closed captions are in another language.

Forced Narratives

Amazon requires a separate Forced Narrative timed text file for every dubbed audio language included in a multi-track audio (MTA) package. Forced Narratives are displayed to customers automatically based on their audio selection, not as an optional subtitle choice. The language-locale of the Forced Narrative file must match the main video mezzanine exactly — a mismatch means the Forced Narrative will not play when subtitles are set to the off state.

Disney+: Aligned with Industry Standards, with Platform-Specific Nuances

Disney+ follows subtitling standards closely aligned with broader industry benchmarks, with its own style guide documentation managed through approved vendors. Disney+ uses IMSC 1.1 as its primary timed text format, with specific provisions for Japanese content.

Core Technical Specifications

Disney+ aligns with Netflix and Amazon on the core metrics that define industry-standard subtitling. Research confirms that all three platforms share the same maximum reading speed of 20 characters per second, the same maximum of two lines per subtitle, and the same maximum of 42 characters per line.
Where Disney+ differs slightly is in minimum duration: while Netflix requires a minimum of five-sixths of a second per event, Disney+ (alongside Amazon Prime Video) permits a minimum duration of 1 second per subtitle event. All three platforms share a maximum duration of 7 seconds.

Format and Delivery

Disney+ uses IMSC 1.1 as its standard subtitle format — a TTML profile designed for subtitle and caption delivery with defined validation and rendering expectations. For Japanese content specifically, Disney+ publishes its own Japanese Subtitles IMSC 1.1 specification, which approved subtitle authoring tools are built to comply with.

SDH and Accessibility

Like Netflix and Amazon, Disney+ distinguishes between standard subtitles and SDH, with SDH providing the more complete accessibility experience. The Disney subtitle style guide addresses SDH specifications including speaker identification, sound descriptors, music and song handling, and dialogue dash conventions, in addition to general subtitle specifications for grammar, character names, ellipsis use, foreign dialogue, italics, and credits.

Platform Comparison: Where They Align and Where They Differ

Understanding where these platforms converge — and where they diverge — is essential for any team managing deliveries across multiple OTT platforms.

The convergence on reading speed, character limits, and line count reflects broader standardisation of professional subtitling across the industry. However, the differences in file format, timing minimums, territory requirements, and specific style guide provisions mean that a file built for one platform will rarely transfer cleanly to another without conformance work.

The Most Common Reasons Subtitle Files Are Rejected

Subtitle files are rejected far more often than most content teams anticipate, and the reasons cluster around a predictable set of errors:

1. Format Mismatches

The leading cause of automated rejections. Using SRT when TTML is required, or delivering a TTML file that does not conform to the platform’s specific profile or subset, will trigger an automated rejection before any human review occurs.

2. Reading Speed Violations

The most common content-level failure. Files where subtitle events display more characters per second than the platform’s maximum require manual rework of event timing throughout — an expensive fix at the delivery stage.

3. Timecode Errors

Common when subtitle files are created in broadcast workflows, where programme timecode often starts at 01:00:00:00. Amazon Prime Video requires timecodes to start at 00:00:00:00, and files with a one-hour offset will display nothing for the first hour of playback.

4. Encoding Errors

Files not saved in UTF-8 produce garbled characters or broken diacritics on viewer devices. All three platforms require UTF-8 encoding without exception.

5. Shot Change Violations (Netflix)

Subtitle events not adjusted to respect Netflix’s green zone and red zone rules around shot changes will be flagged during quality control.

6. Missing Forced Narrative Files (Amazon)

Every dubbed audio language in an Amazon MTA package requires its own separate Forced Narrative deliverable. Missing files cause silent playback failures that are difficult to diagnose after submission.

Why Working with a Qualified Subtitling Vendor Matters

The scale of the requirements across these three platforms — each with their own format specifications, timing rules, style guides, language-specific provisions, and territory-based variations — makes professional subtitle delivery a genuinely complex discipline.
Netflix addresses this directly by strongly encouraging all content producers to work with Netflix Preferred Vendors (NPVs): subtitling and localisation companies vetted by Netflix for quality, technical compliance, and delivery reliability. NPV partners review subtitle files against Netflix’s current specifications before submission, significantly reducing the risk of rejection and associated release delays.
The same principle applies across platforms. Whether you are a production studio delivering a feature film across multiple territories, an independent filmmaker distributing through Prime Video Direct, or a broadcaster localising a content library for global streaming, the cost of a single subtitle rejection — in delayed release schedules, rework hours, and vendor management time — consistently exceeds the cost of getting it right the first time.

What OTT Subtitling Standards Mean for the Localization Industry

The standardisation driven by Netflix, Amazon, and Disney+ has reshaped what professional subtitling services must deliver. Reading speed limits, character counts, format compliance, and SDH completeness have moved from best practices into enforceable requirements, with automated QC systems making non-compliance immediately visible.
For localization service providers, this means that subtitle quality must be managed across three interdependent dimensions simultaneously: linguistic accuracy, technical compliance, and platform-specific conformance. A subtitle file that reads well and translates accurately is not deliverable if it fails the TTML validation or exceeds the CPS limit. All three must hold together before a file can be submitted.
For content producers, the practical implication is that subtitle delivery needs to be treated as a technical deliverable with the same rigour as video mezzanine preparation — not as a last-stage afterthought that can be addressed quickly before a release date.

Conclusion: Subtitling Is a Technical Discipline, Not Just a Translation Task

OTT subtitling standards have evolved to the point where meeting them requires genuine technical expertise, not just linguistic skill. Netflix’s Timed Text Style Guide, Amazon’s Video Central documentation, and Disney+’s delivery specifications together define a demanding, detailed, and non-negotiable standard for what subtitles must look like before they can be placed in front of a global audience.
For content producers, distributors, and localization teams, the takeaway is clear: subtitle compliance should be built into your production workflow from the earliest stages, managed by professionals who understand both the linguistic demands and the technical requirements of each platform.

Ready to Deliver Platform-Compliant Subtitles?

At Ekitai Solutions, our subtitling and captioning services are built to meet the exact specifications required by Netflix, Amazon Prime Video, Disney+, and other leading OTT platforms. From TTML formatting and reading speed compliance to SDH production and multilingual glossary management, we deliver subtitle files that pass QC on the first submission.

Contact our team at ekitaisolutions.com | info@ekitaisolutions.com