MovieLabs Packaging Requirements

A complete package has five components:

1. EMA Avails
2. MEC Metadata
3. MMC Manifest
4. Playable Media Assets
5. Global Artwork Assets

The table below provides a high-level summary of the five components in a MovieLabs package.
All XML files must be auto-generated. Manual creation is not accepted. Deliver packages through Bulk File Delivery (XML) or Standard Delivery (Aspera on Cloud or AWS S3).

Each component in your package is linked by a single shared identifier.

• In EMA v1.7 and later, this identifier is the ALID (Logical Asset ID)
• In EMA v1.6, this identifier is the AltID

Think of the ALID or AltID as the “golden thread” running through your package. Prime Video uses this ID to match rights to the correct title metadata and media files.

This identifier must appear identically in three places:

1. EMA Avail: The EMA Avail tells Prime Video where and when a title can be offered, and at what price.
2. MEC File: The MEC file describes everything customers see about the title. This includes the name, description, cast, and genre.
3. MMC Manifest: The MMC manifest ties every media file to the right title and rights window. This covers video, audio, timed text, and artwork.

Your EMA Avails file delivers exhibition rights to Prime Video. Prime Video supports EMA XLS Avails versions 1.6 through 1.9. The maximum file size is 60,000 rows per submission.

Entry Types
Only two entry types are accepted: Full Extract and Full Delete.

• Full Extract: Replaces all current and future avail entries within the same scope. Scope is the unique combination of six elements: licensor, unique ID, GroupIdentity, quality, territory, and rights model. Each time you submit a Full Extract for a given scope, your previous entries are replaced.
• Full Delete: Used only to remove erroneous avail files. Icontent that has not yet received matching metadata. To expire active content, submit a Full Extract with an appropriate end date instead.

Language Fields
Language fields use RFC 5646 language codes. You can append localization suffixes to specify asset types.

For example, es-419:sub applies only to Latin American Spanish subtitles. It does not affect dubbed audio. You can include multiple languages in a single field, separated by commas.

Key Required Fields

Your MEC file is an XML document that covers the display name, synopsis, genre, cast, crew, ratings, and release year. MEC follows the MovieLabs MEC specification v2.6. It must be auto-generated. Manual authoring is not accepted. Like your EMA Avail, the MEC is delivered through Bulk File Delivery via Aspera on Cloud or AWS S3.

ContentID Rules
Every MEC file is anchored to a ContentID. This ID is fixed on first submission. Once established, it must remain the same for all future updates to that title. ContentIDs must match the ALID or AltID in your EMA Avail and MMC manifest. They can be up to 50 characters long. Only alphanumeric characters, dashes, and underscores are allowed.

Localization
You can deliver multiple LocalizedInfo blocks in a single MEC file. Each block is associated with a different language. At least one LocalizedInfo block is required. It must be marked as the default (original production language). All descriptive title information must come from the MEC file. This includes ratings, director, and cast. Do not place this information in the EMA Avail.

Original Language and Localized Language Examples
The following examples show how packaged assets correspond to what the customer sees when they are looking at a particular title on Prime Video.

• Title metadata, including the name of the movie, a description, and the director, stars, and genre, appear on the left.
• An image from the movie (global artwork) appears on the right.
• The playable assets served to the customer include English closed captions, English audio and audio description, and the Watch now button.
• The avails served to the customer in this example include the Watch now button and the Download button.

Original language: English	Localized language: Brazilian Portuguese

Required Fields at a Glance

TV Content Structure
Each episode requires its own individual MEC XML file. Episodes link to their parent season through a ParentContentID. Seasons link to their parent series the same way. Delivery should follow this hierarchy: Series, then Season, then Episode. Each level must carry the correct SequenceInfo (Number field). This ensures episodes and seasons display in the right order.

For special content types like news, sports, talk shows, and game shows, use the WorkTypeDetail field. This lets Prime Video apply the correct ordering and display logic.

For the complete MEC field-level specification and sample files, see: MEC title metadata and MEC sample files

The MMC file is the central organizing document of your package. It maps every media file to the correct title, presentation, and rights window. Without a valid MMC, Prime Video cannot associate your assets with the right title. The MMC is an auto-generated XML file delivered through Bulk File Delivery. It must conform to the MovieLabs MMC specification v1.5.

The MMC has five sections:

Partial Package Delivery
Partial MMC delivery is supported. When updating a subset of assets, include only the updated assets. You do not need to re-deliver the entire package. The ALID must match between the initial package and any update package.

Asset Identifier Structur
URIs used as asset identifiers within the MMC follow this structure:

These URIs must be consistent throughout the MMC. Your namespace and SSID values are established during onboarding.

For the full MMC specification and sample files, see: MMC Asset Manifest and Sample Files Respository

Playable assets are the media files customers watch when they press play. A complete set includes a video master, original-language audio, dubbed audio tracks, timed text files, and dub cards.

All assets must conform to Prime Video technical specifications. They must also be referenced in your MMC manifest.

Prime Video supports two delivery paths for MovieLabs packages. Your path is set during onboarding with your Account Manager.

Routing rules (both paths):

• EMA Avails, MEC metadata, and MMC manifests go through Bulk File Delivery.
• Playable media files (video, audio, timed text) go through Standard Delivery (Aspera or S3).
• Artwork files also go through Standard Delivery. Reference them in the MEC or MMC.
• All file names must follow the Prime Video Standard Naming Convention.

Partners who submit complete, accurate packages go live faster and reach more customers. A quick check before you submit can save days of troubleshooting.