Amazon Prime Video is one of the largest distribution channels for independent and studio film alike, and its delivery requirements are detailed and strictly enforced. Whether you’re delivering directly through Prime Video Direct as an independent filmmaker, or through a distributor or aggregator as part of a licensing deal, the CCSL is a standard, non-negotiable part of the delivery package.
Here’s what producers need to know about Amazon’s CCSL requirements before submission.
Why Amazon Requires a CCSL
Amazon Prime Video operates across dozens of territories and languages, and its localization teams — along with third-party dubbing, subtitling, and closed captioning vendors — rely on the CCSL as the master source document for a title’s dialogue and on-screen text. Amazon’s own technical delivery documentation is extensive and covers everything from video mezzanine specifications to timed text encoding, and CCSL formatting fits into that same rigor.
For a general overview of what this document is and why nearly every platform requires one, see what a CCSL is and why distributors require it.
Amazon’s Delivery Pathways
Amazon Prime Video accepts content through a few different pathways, and which one applies to your project affects how your CCSL and related materials get submitted:
- Prime Video Direct — for independent filmmakers delivering directly to Amazon
- Through a distributor or aggregator — common for titles as part of a multi-territory licensing deal, where the distributor manages technical delivery on your behalf
Regardless of pathway, the underlying CCSL formatting and accuracy requirements are the same — only the submission logistics differ.
What Amazon’s CCSL Requirements Typically Include
- Frame-accurate timecoding matched to the final delivered mezzanine file
- Speaker identification for all dialogue, including off-screen and voice-over lines
- On-screen text transcribed separately from spoken dialogue
- Correct handling of letterboxed or pillarboxed content — Amazon’s video specs require that any letterboxing or pillarboxing be free of burned-in subtitles, which affects how on-screen text is documented in the CCSL
- Consistency with the delivered mezzanine — Amazon’s technical review process cross-checks delivery assets against each other, so a CCSL that doesn’t match the final picture is a common rejection point
Amazon periodically updates its technical specifications and supply chain guidance, including updates to localization standards. As with any platform, working from a current template matters — a CCSL built against an outdated spec version can still fail review even if the underlying transcription is accurate.
How This Differs From Netflix
Amazon and Netflix both require detailed, frame-accurate CCSLs, but their specific formatting conventions, file naming requirements, and technical delivery portals differ. A document built and QC’d for Netflix’s spec should never be resubmitted as-is for Amazon — see our breakdown of Netflix’s CCSL requirements for comparison, and our guide on why CCSLs get rejected for the most common cross-platform mistakes.
Subtitle and Timed Text Requirements
It’s worth noting that a CCSL and a timed-text subtitle/caption file are related but separate deliverables. Amazon’s subtitle and closed caption requirements — including character encoding, timing rules, and SDH formatting — are their own detailed specification, covered in depth by our sister studio Gotham Lab: Amazon Prime Video Subtitle Requirements. Your CCSL is typically the source document localization vendors use to produce those timed text files, which is exactly why CCSL accuracy matters so much upstream.
Getting It Right the First Time
Amazon’s delivery process, like Netflix’s, is thorough — technical asset review checks your CCSL against the actual delivered picture, and mismatches or outdated formatting are common causes of delay. Gotham CCSL’s CCSL creation services are built to current platform specifications, including Amazon Prime Video, so your delivery is accurate and correctly formatted from the first submission.
Comments are closed