Support

Title metadata files include information like genre, synopsis, and cast and crew, that helps create a customer-facing detail page for each title. Prime Video accepts metadata in both Amazon XML and Amazon XLS formats for the US, UK, DE, and JP territories. For more information on the formats and benefits of each, see below.

A separate metadata file is required for each delivery territory. For specific territory requirements, see the table below. You may redeliver metadata at any time to update metadata values.

Delivery requirements

• Prime Video offers metadata templates for both XML and XLS versions of the Prime Video metadata spec for the US, UK, DE, and JP territories, with specific value requirements for each.
• Metadata must be delivered via either Aspera or Aspera Shares.
• The unique identifier, your partner alias and whether a title is a movie or an episode can't be updated.
• To make a title available in the Classic territories (US, UK, DE, JP), you must deliver Amazon XML title metadata for each territory.
• To make a title available in 4K UHD, you must deliver title metadata twice — once for the HD/SD release, and once for the 4K UHD release. This is also a requirement for 4K UHD pre-order movies, which require a second detail page so that we can fulfill the correct experience to customers. For more information about 4K UHD delivery requirements in the Classic territories, see Prime Video Packaging summary.
• Offer information (e.g., Start Date, End Date) is no longer accepted within AmazonXLS or AmazonXML title metadata. All changes to availability must be made using EMA avails. For more information, see Content rights.

Amazon XLS metadata

Territory-specific XLS templates are available for download.

• XLS templates are available for the US, UK, DE, and JP territories. The templates indicate which fields are required.
• XLS metadata files should be submitted with UTF-8 character encoding. To do this in Excel, do the following:
  1. When you save your Excel workbook, in the Save As dialog box, click the Tools drop-down menu next to the Save button, and then click Web Options.

     

  2. On the Encoding tab, under Save this document as, select Unicode (UTF-8).

     

  3. Click OK and then click Save.
• When delivering Amazon XLS files, they are subject to the file naming rules.

The table below summarizes the Amazon XLS fields and associated notes. Accepted Values lists the acceptable values or indicates the type of value expected for each field. If left blank, it indicates a string is acceptable. All inputs are limited to UTF-8 characters. Prime Video Usage indicates whether the field is required, optional, or not used by Amazon.

Amazon XML metadata

Territory-specific AmazonXML metadata template files are available for download.

• Don't rearrange or add new fields; the fields and order are required for proper validation.
• Where multiple entries are supported (Genre, Director, Actor, etc.), each instance must be on its own line with separate opening and closing tags included for each instance of that field.
• Acceptable locale information is available.
• The UniqueID field is used to communicate the ID of a TV Episode, TV Season, TV Series, or Movie, depending on the parent tag it is nested under. For example, a UniqueID tag nested within a Series tag would refer to the ID of the TV Series, whereas a UniqueID tag nested within a Season tag would describe the ID associated with that Season.
• If providing EIDR numbers, the prefix must be omitted (everything prior to the "/" character). Submit this: XXXX-XXXX-XXXX-XXXX-XXXX-M, instead of this: 10.5240/XXXX-XXXX-XXXX-XXXX-XXXX-M. If you are providing EIDR numbers, include them in the optional <ExternalID scheme="eidr"> tag in addition to the <UniqueID> tag.
• When delivering AmazonXML metadata files, they are subject to the file naming rules.
• Metadata submissions require a version attribute in the Metadata header element. This identifies the version of the schema to which metadata file conforms. The XSD location referenced within the header and the version listed must match. The current versions of the XSD are 1.4.3 for US, UK, DE, and JP.
• Metadata submissions require a country attribute in the Metadata header element. Metadata submissions can only specify a single country. Currently-supported country attributes include: US, GB, DE, and JP.

SD/HD territory requirements

A separate metadata file must be delivered for every territory of intended delivery (US, UK, DE, and JP). The genre lists are unique for each territory and each submission must contain genres for the territory of submission.

4K UHD/HDR territory requirements

Prime Video supports the delivery of 4K UHD and High Dynamic Range (HDR) titles to all territories. The following section outlines requirements for delivering 4K UHD/HDR titles to the US, UK, DE, and JP territories. You must undergo a specific onboarding process before delivering 4K UHD/HDR titles to Prime Video.

Unique IDs for 4K UHD/HDR titles

4K UHD/HDR titles in Prime Video US, UK, DE, and JP territories have separate detail pages from their HD/SD counterparts. To facilitate this, we require two unique UniqueIDs and two unique delivery packages—one for the standard SD/HD package and one for the 4K UHD/HDR package.

To support the separate detail pages for 4K UHD/HDR and HD/SD, the 4K UHD/HDR deliveries must have their own UniqueID that is different from the HD/SD version of that title. This Unique ID should be the same as the ID for the HD/SD version of the title, but appended with "_UHD". This ID must be referenced in the avail, the title metadata, and the asset manifest to ensure that all deliveries are appropriately matched.

Avails

All UHD/HDR titles must have corresponding avails that include 4K or UHD in the Format Profile column. The AltID column for this line must include the Unique ID that is specific to the 4K/UHD version of the title. See additional details on Unique IDs for UHD titles above.

Video files

HDR titles must include both an HDR and an SDR video file delivery. The only difference between the SDR and HDR video files should be the colorspace. Otherwise, the files should be identical, including the same resolution and framerate. Any subtitles delivered with a UHD/HDR package should conform to both the SDR and HDR video files.

Amazon XML simple asset manifest for UHD/HDR

HDR titles must include both an HDR and an SDR video file delivery. These files are both referenced in the XML Asset Manifest. Additionally, the manifest must include the HDR10 metadata for the HDR video file. Both the HDR and SDR video files are associated to the same UniqueID.

Prime Video will provide the HDR encodes for customers accessing content on HDR enabled screens and will provide the SDR encodes for customers accessing the content on SDR screens. Titles that are only UHD and unavailable in HDR should follow the same delivery process as described above with the omission of the HDR video file. In this case, the manifest will reference only the UHDSDR video file.