Support

Your email has been sent

You should receive a response from Customer Service within one business day.

Title Metadata

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.

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.

      Screenshot of Microsoft Excel Save As dialog box with the Tools menu expanded

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

      Screenshot of Microsoft Excel Save As Web Options dialog box on the Encoding tab

    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.

Field NameDefinition & NotesAccepted ValuesPrime Video Usage
Partner NameThe organization granting rights. Use your Amazon "PartnerAlias" to match to asset packages. Case insensitive. No spaces or symbols.Required
Unique IDThe internal ID for the feature or episode. 50-character limit. Case insensitive. Must be unique within your catalog. Only letters, numbers, and underscores; no spaces or symbols.Required
WorkTypeType of the work.Movie, TV Series, TV Season, TV EpisodeRequired
TitleThe title of the feature, series, season, or episode. Must be the localized title. This is the title that will be presented to customers.  Use "The Title Name" rather than "Title Name, The". 250-character limit.Required
Title pronunciationHiragana (ひらがな), katakana (カタカナ) and alphanumeric are accepted. Numbers should be given pronunciation if there is an unusual pronunciation (i.e. 2人=ふたり). English words in the title remain as English in the pronunciation.Required only for JP
StudioThe name of the credited studio. Multiple studio names should be formatted as one on each line, using Alt+Enter to separate within the cell. No commas, semicolons, etc. For Television content, this is usually the "Network" the Show aired on (rather than the production company that made or distributed it). For Movies, the Studio(s) that produced the Movie. If none is provided, a content provider name will be applied as studio.Optional
RatingThe approved rating value of the region. Populate with "NR" if rating is not available.See Prime Video ratings list.Required for Movie, TV Season, and TV Episode
Start YearThe year the Series started or the year the first TV Episode was broadcast.YYYYOptional for TV Series
End YearThe year the Series ended or the year the last TV Episode was broadcast. Mostly used for catalog titles that have already ended. For currently running titles, leave blank.YYYYOptional for TV Series
Season Sequence NumberThe number of the season.IntegerRequired for TV Season
Series IDThe internal ID for the series. Must match the TV Series Unique ID or previously-ingested series Unique ID. Only letters, numbers, and underscores; no spaces or symbols.Required for TV Season and TV Episode
Season IDThe internal ID for the season. Must match the TV Season Unique ID or previously-ingested season Unique ID. Only letters, numbers, and underscores; no spaces or symbols.Required for TV Season
Episode Sequence NumberThe number of the episode. Episodes should begin with 1 instead of 101; VAM should begin with 0.IntegerRequired for TV Episode
Episode Production NumberStudio or Network episode production numberIntegerOptional for TV Episode
Short SynopsisA description of the content. 400-character limit. Ensure that there are no references to the product being a physical product, describing video quality or price (e.g., DVD, Blu-ray, HD, 3D, Euro).Required
Long SynopsisA description of the content. 2,000-character limit. Ensure that there are no references to the product being a physical product, describing video quality or price (e.g., DVD, Blu-ray, HD, 3D, Euro).Optional
ActorsActor(s) in the content. No limit (one name per line). Multiple names should be formatted as one on each line, using Alt+Enter to separate within the cell. No commas, semicolons, etc. Series and Season Actors should be for the series and season regular actors. For TV Episode content, use the Actors column for guest stars within the episode. 250-character limit per line.Optional
DirectorsDirector(s) of the content. No Limit (one name per line). Multiple names should be formatted as one on each line, using Alt+Enter to separate within the cell. No commas, semicolons, etc. 250-character limit per line.Required for Movie
ProducersProducers of the content. No Limit (one name per line). Multiple names should be formatted as one on each line, using Alt+Enter to separate within the cell. No commas, semicolons, etc. Either the production company or the name of individual producers is valid. 250-character limit per line.Optional
WritersWriter(s) of the content. No Limit (one name per line). Multiple names should be formatted as one on each line, using Alt+Enter to separate within the cell. No commas, semicolons, etc. 250-character limit per line.Optional
CreatorCreator(s) of the content. No limit (one name per line). Multiple names should be formatted as one on each line, using Alt+Enter to separate within the cell. No commas, semicolons, etc. 250-character limit per line.Optional
Release DateThe date that a movie or TV episode was first released. Format is YYYY-MM-DD or the cell must be labeled as "Date" in the Number section of the Home ribbon. For a movie, this is the release date. For TV episode, this is the original air date.YYYY-MM-DDRequired for Movie and TV Episode
DVDStreetDateDate of the first physical release of the product or the first time the product was available for public purchase. Format is YYYY-MM-DD or the cell must be labeled as "Date" in the Number section of the Home ribbon.YYYY-MM-DDOptional for Movie
IMDBThe Series/Episode/Movie IMDb ID only. 9-character value assigned by IMDb. Begins with "tt" and is then followed by 7 numbers.Optional
Copyright HolderCopyright holder for the content. 250-character limit.Optional
Copyright YearThe copyright year of content.YYYYOptional
LanguageLanguage the main audio is in. If dubbed audio is present in the mezzanine, this would represent the language of the dubbed audio. Lowercase values only.ISO 639-1 language codesOptional
OriginalLanguageOriginal language of the content. Lowercase values only.ISO 639-1 language codesOptional
CountryOfOriginThe country of origin of the content. Uppercase only. Multiple countries should be formatted as one on each line, using Alt+Enter to separate within the cell. No commas, semicolons, etc.ISO 3166-1Optional
OriginalLanguageTitleOriginal language title of the content (a.k.a. titles). 250-character limit.Optional
RuntimeInMinutesThe runtime of the content, in minutes.IntegerOptional for Movie and TV Episode
AdultProductIs this content intended for an adult audience?"true" or "false"Required only for JP
GenreThe approved Prime Video genre of the content. Case sensitive. Can have up to five genres. Multiple genres should be formatted as one on each line, using Alt+Enter to separate within the cell. No commas, semicolons, etc.See the Prime Video genre list.Required for Movie and TV Episode
Subscription NamePrime Video-approved "Benefit ID" if content is destined for a third-party subscription (Prime Video Channels). Case sensitive. No spaces or symbols.Required for third-party subscriptions (Channels)
Display Aspect RatioAspect ratio of the video.4:3, 1.667:1, 16:9, 1.85:1, 2:1, 2.2:1, 2.35:1, and 2.4:1Optional
Field typeField type of the video."Top Field First" and "Bottom Field First"Optional

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.

Packaging a title for the US territory requires the following packaging specifics in addition to the overall US packaging requirements:

  • When utilizing the XLS Metadata format, the Global Template sheet must have a country code of US and version of 1
  • When utilizing XML metadata and/or asset manifest, the XML header must contain US in the country tag
  • Must utilize a genre from the US genre list
  • Must provide a US rating schema
  • Must deliver assets, metadata, and asset manifest (when applicable) to the region_US” folder in Aspera or Aspera Shares

Packaging a title for the UK territory requires the following packaging specifics in addition to the overall UK packaging requirements:

  • When utilizing the XLS Metadata format, the Global Template sheet must have a country code of UK and version of 1
  • When utilizing XML metadata and/or asset manifest, the XML header must contain UK in the country tag
  • Must utilize a genre from the UK genre list
  • Must provide a UK rating schema
  • Must deliver assets, metadata, and asset manifest (when applicable) to the region_GB or region_UK folder in Aspera or Aspera Shares

Packaging a title for the DE territory requires the following packaging specifics in addition to the overall DE packaging requirements :

  • When utilizing the XLS Metadata format, the Global Template sheet must have a country code of DE and version of "1"
  • When utilizing XML metadata and/or asset manifest, the XML header must contain DE in the country tag
  • Must utilize a genre from the DE genre list
  • Must provide a DE rating schema
  • Must deliver assets, metadata, and asset manifest (when applicable) to the region_DE folder in Aspera or Aspera Shares
  • Localized metadata is preferred; if not available, English metadata is accepted.

Packaging a title for the JP territory requires the following packaging specifics in addition to the overall JP packaging requirements:

  • When utilizing the XLS Metadata format, the “Global Template” sheet must have a country code of JP and version of 1
  • When utilizing XML metadata and/or asset manifest, the XML header must contain JP in the country tag
  • Must utilize a genre from the JP genre list
  • Must provide a JP rating schema
  • Must provide Title Pronunciation in either XLS or XML title metadata. Hiragana (ひらがな), katakana (カタカナ) and alphanumeric are accepted. Numbers should be given pronunciation if there is an unusual pronunciation (i.e. 2人=ふたり). English words in the title remain as English in the pronunciation.
  • Must deliver assets, metadata, and asset manifest (when applicable) to the region_JP folder in Aspera or Aspera Shares
  • Must indicate whether the content is intended for adults by including either true or false in the AdultProduct section of the metadata
  • Localized metadata is required in JP

UHD/HDR Territory Requirements

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

Unique IDs for UHD/HDR Titles

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 UHD/HDR package.

To support the separate detail pages for UHD/HDR and HD/SD, the 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.

Type Title Unique ID
HD/SD The Marvelous Mrs. Maisel MrsmaiselS1E1
UHD The Marvelous Mrs. Maisel [4K Ultra HD] MrsmaiselS1E1_UHD
Type Title Unique ID
HD/SD The Marvelous Mrs. Maisel MrsmaiselS1E1
UHD OV The Marvelous Mrs. Maisel [OV] [4K Ultra HD] MrsmaiselS1E1_UHD
UHD Subtitled The Marvelous Mrs. Maisel [OmU] [4K Ultra HD] MrsmaiselS1E1_SUB_UHD
UHD Dubbed The Marvelous Mrs. Maisel [4K Ultra HD] MrsmaiselS1E1_DUB_UHD
Type Title Unique ID
HD/SD The Marvelous Mrs. Maisel MrsmaiselS1E1
UHD OV The Marvelous Mrs. Maisel [4K Ultra HD] MrsmaiselS1E1_UHD
UHD Subtitled The Marvelous Mrs. Maisel (字幕版) [4K Ultra HD] MrsmaiselS1E1_SUB_UHD
UHD Dubbed The Marvelous Mrs. Maisel (字幕版) [4K Ultra HD] MrsmaiselS1E1_DUB_UHD

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.


Internal Server error! Please try again
Your session has expired

Please sign in to continue

Sign In
edit