Promotional Assets: Clips

Two delivery paths are supported. Partners should choose the path that best fits their existing technical infrastructure:

Clip Types and Editorial Guidelines

The preferred clip type is “scene lift” excerpts — compelling, contextually relevant snippets that capture the essence of memorable scenes without revealing major plot points. These clips create irresistible teasers that draw viewers to discover the full stories for themselves. Successful clips highlight: intense action sequences, witty dialogue, breathtaking visual moments, passionate commentary, monologues, strong comedic moments, inspiring declarations, dramatic reactions, and compelling relationship dynamics.

Also accepted (must map to a single long-form title):

• Featurettes
• Behind-the-scenes content
• Cast interviews and commentary
• Plot pitches (highlight a given title to hook users to watch more)
• Compilations and mashups

Not Accepted

Promotional Material

• Clips that represent trailers or advertisements
• Content containing calls-to-action

Non-Cinematic Content

• Still images presented as video content i.e picture montages
• GIFs

Non-Narrative Visual Content

• Music-only clips without narrative or conversational dialogue
• Content lacking substantive spoken content or verbal storytelling elements

Duration Requirements

Association to Long-form Titles

Every clip must be associated with long-form content already licensed to Prime Video (or delivered concurrently). Association is established via the AssociatedTitleIdentifier field in the Simplified XML Manifest and via the<md:ContentRelatedTo> section of the MovieLaba MEC.

• Clips are linked to their parent title (movie),season(TV), or collections (movie/TV).
• Maturity ratings are inherited from the parent title or assigned by Trust & Safety — no additional ratings work required from partners
• No minimum volume requirement to get started; work with your CAM to identify a priority catalogue

Limits with Association to Long-form Titles

There is no limit for how many Clips can be associated to a Long-form title.For enhanced experience, Prime Video will accept as many Clips as a partner is able to deliver.

Video Format

Audio Requirements

Clips containing any of the following defects will be rejected or require remediation before publication:

Pre-Delivery Quality Check-List

Use the following checklist before submitting clips to Prime Video:

• Video file is .mp4 format and meets resolution and bitrate requirements
• Aspect ratio is 9:16 or 16:9
• File size does not exceed 750 MB
• Color space is Rec. 709 (HD)
• Audio codec is AAC Stereo and is perfectly synchronized with the video
• No black/white frames, artifacts, blurriness, or encoding issues
• No watermarks, logos, burnt-in text (except forced narratives), or call-to-actions
• No content policy violations
• Clip maps to a single licensed long-form movie title or television season
• Duration is between 30 seconds and 3 minutes
• Timed text files include Frame Rate and Timecode if time-coded
• All file references use exact filenames (no folder paths)

The XML-based Clips Manifest is live and ready for delivery. Each clip is submitted as a standalone XML file referencing the mezzanine, timed text, and audio assets. It is lightweight, flexible, and validated against a published XSD schema so partners can catch errors before submission.

_{Schema Validation: An XSD schema is available for pre-submission validation. Contact your CAM for the schema and a sample manifest file.}

XML Namespace and Structure

All XML manifests must use the following names pace declaration:

Required Fields

The following fields are mandatory for every XML manifest submission:

Optional Fields

Availability Field Details

The Availability field controls when and where clips are available on Prime Video. Multiple availability windows can be specified.

File Reference Requirements

File references in the XML manifest must strictly follow these rules:

• File Reference must be the exact filename of the media file being delivered
• Do not include file path information — no folder names, drive names, or directory structure
• The filename in the manifest must exactly match the filename of the uploaded asset
• Locale defaults to en-US if not specified

Example:

Correct: File_Naming_Convention_Generic_Police_Procedural_S01_E01.mov
Incorrect: /media/clips/File_Naming_Convention_Generic_Police_Procedural_S01_E01.mov

MovieLabs MEC (Media Entertainment Core) is an industry-standard metadata schema used by major studios for digital media asset management and delivery. Prime Video’s native MEC integration enables studios to deliver clip metadata using their existing MEC pipelines with minimal changes.

For more granular control of rights and availabilities, submitting an EMA Avail is recommended alongside the MEC. If an EMA is not submitted, the clip will inherit rights from its parent associated title.

MEC Required Fields

The following MEC fields are required when delivering clips via the MovieLabs MEC path:

MMC Required Fields

In addition to the MEC fields, the following MMC (Media Manifest Core) fields arerequiredwhen delivering via theMovieLabspath:

Rights and Availabilities via EMA

For MEC-delivered clips, rights and availability windows are controlled through the EMA (Electronic Media Agreement) companion file. Key guidance:

• Submit an EMA alongside the MEC& MMC for precise control over territory rights and availability windows.
• If no EMA is submitted, the clip inherits rights from its parent associated title
• EMA fields align with standard MOVIELABS EMA specification for territory, start/end dates, and license type set as “FVOD”.

Availability Windows

Availability windows define when and where a clip is accessible on Prime Video. These apply to both delivery methods.This can be delivered in the Simplified XML itself or via an additional EMA Avail if following the MovieLabs path.

• Territory field uses ISO 3166-1 alpha-2 codes (e.g.US, GB, DE, FR, JP)
• Start and End dates use ISO 8601 format: YYYY-MM-DD or YYYY-MM-DDThh:mm:ssZ
• UTC timezone offset (±hh:mm) is also accepted for ISO 8601 dates
• If Start is omitted, the clip publishes as soon as the offer is released
• If End is omitted, the clip remains live indefinitely until updated or removed
• To take down a clip via XML, provide an End date/time that has already passed
• Multiple availability blocks can be provided for different territories or benefit tiers

Maturity Ratings

Maturity ratings are optional in the XML manifest and Movielabs spec. If not provided, ratings are inherited from the parent title or assigned by the Prime Video Trust & Safety team. When providing ratings, use the Prime Video Maturity Ratings Workbook for accepted System, Value, and Reason code combinations.

Localization

Prime Video Clips supports localized metadata delivery for multi-territory distribution. Key localization rules:

• Locale values must come from the Prime Video Supported Languages list
• If Locale is not specified, it defaults to en-US
• Only one TitleDisplayName per locale is supported
• Only one TitleDescription per locale is supported
• Multiple Video File References, Timed Text References, and Audio References can be provided for different locales
• Locale codes follow BCP 47 format (e.g.en-US,fr-FR, de-DE, ja-JP, es-ES)

While Prime Video does not mandate a specific file naming convention, the following best practices ensure smooth delivery and avoid ingestion failures:

• Use descriptive names that uniquely identify the content (e.g.include series name, season, and episode)
• Use only alphanumeric characters, underscores (_), and hyphens (-) in filenames
• Avoid spaces, special characters, or non-ASCII characters in filenames
• Include the locale in the filename when delivering multi-locale content
• Use consistent naming patterns across all assets in a delivery package
  

Delivery Package Structure

Each clip delivery consists of:

• One XML manifest file (for Simplified XML path)
• Two XML files (MEC & MMC for MovieLabs path)
• One mezzanine video file (.mp4)
• One or more timed text files (optional, .itt or other supported formats)
• One or more audio files (optional, for localized or accessible content)

Common Ingestion Errors and How to Avoid Them

All sample files can be found in the Sample File Repository.