Version 5.1
Welcome
Below partners will find delivery specifications required by Netflix; however, some of them may not apply to your production. Please refer to your Netflix Delivery Requirements List or your Netflix Representative to verify which assets apply to your delivery.
Enforcement of 5.1 specification changes outlined in the change log will begin on January 2nd, 2024.
Table of Contents
- General Asset Requirements
- Subtitle as a Separate File
- Forced Narrative Subtitles
- Accessibility Files (SDH)
- Alternate Language and Audio Description Delivery to Backlot
- Audio Mix Requirements: Alternate Language and Audio Description
- Dub Cards/Dub Credits
- Appendix
1. General Asset Requirements
- Translations within secondary audio and timed text assets should not introduce slurs that were not present in the original language or unnecessarily harshen/soften the language used, unless specifically requested by Netflix.
2. Subtitle as a Separate File
Subtitles must encompass spoken dialog intended to be understood that differs in language from the subtitle file. Subtitles must also translate any narrative burned-in text that is in a different language from the subtitle file. In the event of overlapping narrative burned-in text and dialog, precedence should be given to the most plot pertinent message.
For example, for an English original language film, the German subtitle file would contain translation for all the non-German dialog spoken.
- Subtitles must conform, within a half second, to the Primary Video Mezzanine that is delivered or to the Netflix-provided Proxy File. Raster image-based subtitles will not be accepted.
- Subtitle files must not be censored or contain advertisements, placards, overlay branding, or website link callouts.
- All subtitle files need to start at hour 00. Netflix does not accept the subtitle timestamps starting at hour 01 or 10, which is common on tape.
- Include positional data in the subtitle file if the subtitles would otherwise obscure burned-in text.
- All subtitles must contain an individual credit for the author of the text asset; company credits are not allowed. If more than one translator has worked on an asset, e.g. when translating from multiple source languages or when more than one translator has collaborated on a special project, more than one translator can be mentioned in the same credit.
- Subtitler credits must be contained to the last event of the file, must not appear before the end of the main program, and must be formatted exactly as they are meant to appear on-screen as required by law in the territory of exhibition.
- TTML format is required for “Right-to-Left” languages such as Arabic and Hebrew.
- Translator credits are NOT required for marketing assets such as trailers, promos, clips, etc.
Framerate Requirements:
- 25 fps media must have subtitles/CC timed to PAL 25 timecode.
- 23.976 (23.98) media must have subtitles/CC timed to either SMPTE 24 timecode or 23.976 Media-Time (timing method must be specified in the file using ttp:timeBase and in the Backlot delivery metadata as either SMPTE or MEDIA). IMSC1.1 documents must only use Media-Time.
- 59.94 fps & 29.97 fps media must have subtitles/CC timed to drop-frame 29.97 timecode using ttp:dropMode. ttp:dropMode is only valid when used in conjunction with ttp:timeBase=”smpte”. As such, ttp:dropMode does not apply to IMSC1.1 documents, which must only be provided using MEDIA timeBase.
To ensure the best quality and consistency please reference our Timed Text Style Guides.
Acceptable formats:
- TTML1 (.xml, .ttml) format (see Netflix Timed Text Style Guide for details).
- IMSC1.1 (.xml) - for Japanese subtitles only.
If your text-based subtitle format is not listed above, please contact your Netflix representative to discuss.
3. Forced Narrative Subtitles
Netflix requires final AV be delivered without burned-in subtitles. In order to support this non-subtitled source, a list of Forced Narratives, if required for the asset, should be delivered by production using the Netflix-provided template found here.
Examples of Forced Narrative subtitles include:
- Any alternate language dialog and on-screen text.
- Inaudible or hard-to-hear dialog.
- Dialog or on-screen text that should be called out per creative intent.
Example: If an English-language title contains plot-pertinent Japanese content that an
English-speaking audience should understand, the final AV should not include burned-in subtitles for those instances. The Forced Narrative template should be filled out with the Japanese dialog translated into English, with preferred punctuation and formatting, as well as corresponding in and out-times for the events.
The Forced Narrative list should include:
- In times and out times for Forced Narrative events.
- The event as it should appear on screen, including preferred punctuation.
The Forced Narrative list should be uploaded to the Localization bucket in Content Hub as a “Localization Note”.
If delivery of a full Forced Narrative subtitle file is required, the technical format must follow the same rules as standard subtitles as denoted in Section 2.
Framerate Requirements:
- 25 fps media must have subtitles/CC timed to PAL 25 timecode.
- 23.976 (23.98) media must have subtitles/CC timed to either SMPTE 24 timecode or 23.976 Media-Time (timing method must be specified in the file using ttp:timeBase and in the Backlot delivery metadata as either SMPTE or MEDIA). IMSC1.1 documents must only use Media-Time.
- 59.94 fps & 29.97 fps media must have subtitles/CC timed to drop-frame 29.97 timecode using ttp:dropMode. ttp:dropMode is only valid when used in conjunction with ttp:timeBase=”smpte”. As such, ttp:dropMode does not apply to IMSC1.1 documents, which must only be provided using MEDIA timeBase.
For more information, please refer to Forced Narratives Guidelines and Style Guide for Dubbing.
4. Accessibility Files (SDH)
SDH – Subtitles for the Deaf and Hard of Hearing
SDH must encompass the spoken dialog intended to be understood in the content. If the content has multiple spoken languages, they all must be translated and present in the SDH file.
4.1 SDH as Separate File
When delivering SDH, it must be submitted in one of the acceptable formats listed below:
- TTML1 (.xml, .ttml) format (see Netflix Timed Text Style Guide for details).
- IMSC1.1(.xml) - for Japanese subtitles only.
If your SDH format is not listed above, please contact Netflix to discuss other options.
Additionally, they meet the following:
- Raster image-based SDH will not be accepted.
- SDH files must conform, within a half second, to the Primary Video Mezzanine that is delivered or to the Netflix-provided Proxy File.
- SDH files must not be censored or contain advertisements, placards, overlay branding, website link callouts or company credits unless required by law.
- They must not contain a credit for the SDH creator. They must contain a credit for any translations provided.
- All SDH files need to start at hour 00. Netflix does not accept the SDH timestamps to start at hour 01.
- Include positional data in the SDH file if a caption or subtitle would otherwise obscure burned-in text.
- TTML1 format is required for “Right-to-Left” languages such as Arabic and Hebrew.
Framerate Requirements:
- 25 fps media must have subtitles/CC timed to PAL 25 timecode.
- 23.976 (23.98) media must have subtitles/CC timed to either SMPTE 24 timecode or 23.976 Media-Time (timing method must be specified in the file using ttp:timeBase and in the Backlot delivery metadata as either SMPTE or MEDIA). IMSC1.1 documents must only use Media-Time.
- 59.94 fps & 29.97 fps media must have subtitles/CC timed to drop-frame 29.97 timecode using ttp:dropMode. ttp:dropMode is only valid when used in conjunction with ttp:timeBase=”smpte”. As such, ttp:dropMode does not apply to IMSC1.1 documents, which must only be provided using MEDIA timeBase.
For more detail, please reference our Timed Text Style Guides.
5. Alternate Language and Audio Description Delivery to Backlot
If alternate language and/or audio description tracks are required under the Agreement, they shall be conformed to the primary digital audio/video asset delivered. Acceptable formats for
alternate-language audio tracks are Atmos BWAV ADM, stereo or multi-channel WAVE Extensible Format (.WAV) as described in section 5.1, or QuickTime format as described in section 5.2. Alternate language and audio description channel configurations must match those of the original language mix.
Please note: Lectern-style dubbing (single narrator speaking the role of each character) is only acceptable for Polish or Vietnamese alternate language audio files, unless otherwise requested by your Netflix Representative. For all other languages and types of content, lip-sync or voice over dubbing (as ordered by your Netflix representative) is required for alternate language audio.
5.1 Acceptable Alternate Language and Audio Description Formats (non-QuickTime)
WAV Specs | |
Audio Codec & Container | Uncompressed PCM audio in an interleaved WAVE Extensible Format (.wav) |
Sample Rate | 48 kHz |
Bitrate | Highest bitrate possible (CBR) |
Bit Depth | 24-bit or 16 Bit |
Audio Channel Mapping for WAV (.wav) | ||||||||
Channel | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
5.1+2.0 (Option 1) | L | R | C | LFE | Ls | Rs | Stereo Left | Stereo Right |
5.1+2.0 (Option 2) | L | C | R | Ls | Rs | LFE | Stereo Left | Stereo Right |
5.1 | L | R | C | LFE | Ls | Rs | ||
2.0 | Stereo Left | Stereo Right |
5.2 Acceptable Alternate Language and Audio Description Formats (QuickTime)
Please note: the labels “Left Total” and “Right Total” are used to label the stereo mix channels only used when 5.1 + 2.0 audio is included in a single file (Options 1-4). If stereo only files are delivered (Options 5 & 6) then the labels “Left” and “Right” are used since there is no ambiguity.
Quicktime Specs | |
Audio Codec | Uncompressed LPCM |
Sample Rate | 48 kHz (Big or Little Endian) |
Bit Depth | 24-bit or 16 Bit |
Audio Channel Mapping for Quicktime (.mov) | ||||||||
Track | 1 | 2 | 3 | |||||
Channel | 1 | 2 | 3 | 4 | 5 | 6 | 1 | 1 |
5.1+2.0 (Option 1) | C | L | R | Ls | Rs | LFE | Stereo Left | Stereo Right |
Track | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
Channel | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
5.1+2.0 (Option 2) | L | R | C | LFE | Ls | Rs | Stereo Left | Stereo Right |
Track | 1 | 2 | ||||||
Channel | 1 | 2 | 3 | 4 | 5 | 6 | 1 | 2 |
5.1+2.0 (Option 3) | L | R | C | LFE | Ls | Rs | Stereo Left | Stereo Right |
Track | 1 | 2 | 3 | 4 | 5 | 6 | 7 | |
Channel | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 |
5.1+2.0 (Option 4) | L | R | C | LFE | Ls | Rs | Stereo Left | Stereo Right |
Track | 1 | 2 | 3 | 4 | 5 | 6 | 7 | |
Channel | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 |
5.1+2.0 (Option 4) | L | R | C | LFE | Ls | Rs | Stereo Left | Stereo Right |
Track | 1 | |||||||
Channel | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
5.1+2.0 (Option 5) | L | R | C | LFE | Ls | Rs | Stereo Left | Stereo Right |
Track | 1 | 2 | 3 | |||||
Channel | 1 | 2 | 3 | 4 | 5 | 6 | 1 | 2 |
5.1+2.0 (Option 6) | L | R | C | LFE | Ls | Rs | Stereo Left | Stereo Right |
Track | 1 | |||||
Channel | 1 | 2 | 3 | 4 | 5 | 6 |
5.1 | L | R | C | LFE | Ls | Rs |
Track | 1 | 2 |
Channel | 1 | 1 |
2.0 (Option 1) | L | R |
Track | 1 | |
Channel | 1 | 2 |
2.0 (Option 2) | L | R |
6. Audio Mix Requirements: Alternate Language and Audio Description
6.1 Audio Prerequisites
Discrete audio is required, except in the following circumstances:
- When muxed audio is inherent to the source, such as audio in an IMF, Quicktime or Atmos® BWAV ADM container.
- Interleaved Secondary Audio .wav deliveries.
All audio must sync to the final picture, including 1 second of black before the program start FFOA, and 1 second of black after LFOA.
Alternate/Dubbed Language and Audio Description Mixes must not contain an additional leader.
For all titles, 5.1 audio is required and 2.0 is optional.
Mono audio is acceptable if the program’s original source is mono and no stereo and/or 5.1 mix exists. Mono audio must be duplicated on channels 1 & 2 and delivered as 2-channel.
6.2 Near Field Atmos® Mix - Mastering and Archive - Dubbed Languages and Audio Description
The Dolby Atmos® Dubbed Language Home Mix must meet the following requirements.
- At a minimum, must be mixed in a 7.1.4 room.
- Dolby Certification is not required for Home Atmos® mix rooms.
- This is a near field mix. The most common monitoring levels for near field are 79db or 82db.
- Must conform to Netflix loudness spec (-27db LKFS +/- 2 LU 1770-1 dialogue loudness).
- Peaks should generally not exceed -2dbfs True Peak. To achieve this, we recommend setting True Peak limiters on all beds and objects at -2.3 or lower. Loudness and peaks should be measured via a 5.1 rerender.
- For native Atmos® mixes, the 5.1 and 2.0 rerenders must conform to Netflix loudness and Peak specification.
- All beds and objects are encoded and will always be audible. A printmaster may utilize a composite of all bed material OR multiple beds, but not both.
- For all series/doc/unscripted/comedy content, beds and objects must be separated by Dialog, Music and Effects. For film content, DME separation should be maintained whenever possible.
- If a 85 db reference theatrical mix is created, two complete sets of deliverables are required. One for theatrical, one for near field.
- Dubbed Language Atmos® files shall match final IMF picture length exactly as long-play and not separate reels. Leader and sync pop shall be removed.
- FFOA must be left at default - leave “Add FFOA” box unchecked. For pre-3.0 renderer software, leave red dashes in FFOA value.
-
Final Home Theater Print Master:
-
Dolby Atmos® BWAV ADM File.
- All bed channel configurations are acceptable.
- 48 kHz, 24 bit.
-
Dolby Atmos® BWAV ADM File.
6.3 Near Field 5.1 Surround Mix - Mastering and Archive - Dubbed Languages and Audio Description
- Use 79dB spl or 82dB spl as your standard reference level for mixing.
- Meet a -27 LKFS (+/- 2 LU) dialog-gated using ITU-R BS.1770-1 measured over entire program.
- Do not exceed +18db (-2 dBFS) maximum level (true-peak) over reference of -20 dBFS, achieved by peak limiting and not lowering the mix level.
- For Original Version: Provide 5.1 Dialog, Music and Effects stems that equal the 5.1 mix when combined.
- For Dubbed Version: Provide 5.1 Dialog stem that equals the 5.1 mix when combined with M&E.
6.4 Near Field 2.0 Stereo Mix - Mastering and Archive - Dubbed Languages and Audio Description
- Use 79dB spl or 82dB spl as your standard reference level for mixing.
-
Provide a separate Lo/Ro or LT/RT mix with -27 LKFS (+/- 2 LU) dialogue loudness using ITU-R BS.1770-1 measured over the entire program.
- Lo/Ro mix is preferred.
- Lo/Ro or LT/RT mix to be mono compatible.
- Do not exceed +18db (-2 dBFS) maximum level (true-peak) over reference of -20 dBFS, achieved by peak limiting and not lowering the mix level.
- When down-mixing from 5.1 to create Lo/Ro or LT/RT 2.0 mix:
- Lower Center channel content by -3db.
- Center channel content should be included in both the LEFT and RIGHT CHANNELS.
- Lower Surround channel content by a minimum of -3db.
- Fold Left and Right Surround content into the corresponding LEFT and RIGHT CHANNELS.
-
Optionally include the Low Frequency Effects (LFE) channel between -8db and -12db.
- Fold Low Frequency Effects (LFE) into both the LEFT and RIGHT CHANNELS.
- Low Pass Filter LFE at 200Hz or lower.
- All adjustments must be made to the individual 5.1 channels prior to folding down.
Note: The resulting 2.0 mix must be checked prior to delivery to ensure it is free of any audio artifacts and if necessary, as determined by Netflix, further adjustments shall be made to prevent them. Any 2.0 delivery must meet the specification prescribed in this section.
7. Dub Cards/Dub Credits
If dubbed audio files are delivered to backlot and dubs are billed to Netflix and branded, Partner shall enter dub card credits in Netflix’s Dub Talent List tool, which requires Partner to enter talent data - cast and crew - per title. Once talent entry is submitted, the partner has the option to download the dub card deliverables (.zip and .png) for their own archive.
If dubbed audio files are delivered to Netflix and dubs are not billed to Netflix and/or are not branded,
Partner must upload an image based Dub Cards to Netflix formatted exactly as they are to appear on-screen. No extraneous information can be included beyond studio name, cast and other key personnel or as otherwise required by law in the territory of exhibition. Acceptable formats and specifications below.
Acceptable Dub Card Formats
-
Image Files
- Each Image must represent one frame of dubbed actor credits.
-
Only one language can be represented on a dub card and the dubbed language must be specified in the dub card text.
- Example: "Version Française"
-
We accept the following flat file types in order of preference (no layers or pages):
- TIFF
- PNG
- BMP
- JPG
- Minimum Resolution: 640x480.
- Pixel Aspect Ratio (PAR): 1:1 square pixels.
In cases where multiple dub cards are needed for an individual language, the multiple dub cards must be stored in a ZIP archive.
-
ZIP Archive
- Each Image must meet the image file spec described above.
- Each image must match the file format and resolution of the other images in the ZIP archive.
- All images in ZIP archive must be for the same language.
- Images will be rendered to screen in alpha-numeric sorted order (case insensitive).
-
Acceptable Compression modes: “DEFLATE” or “STORE.”
- Note: WinZip and WinRAR use DEFLATE by default.
- Note: the ZIP file name does not need to adhere to any specific convention. Image files contained in the ZIP archive must be named in case-insensitive alphanumeric order.
-
Examples:
-
Brazilian Portuguese
- ZIP File name: SomeTitle_pt-BR.zip
- Image names: dubCard01.tiff, dubCard02.tiff, dubCard03.tiff
-
French
- ZIP File name: FrenchDubCards.zip
- Image names: FrenchActors01.png, FrenchActors02.png, FrenchActors03.png
-
Brazilian Portuguese
All dubbed and/or subtitled content is to be accompanied with the relevant metadata in the original and alternate language to support the source delivered.
Appendix
Language Codes
If the desired language code is not found in the table below please contact your Netflix Representative.
Language Name | Language Code | Audio | Text |
Acoli | ach | √ | √ |
Afrikaans | af | √ | √ |
Albanian | sq | √ | √ |
Amharic | am | √ | √ |
Arabic | ar | √ | √ |
Arabic (Algeria) | ar-DZ | √ | √ |
Arabic (Bahrain) | ar-BH | √ | √ |
Arabic (Chad) | ar-TD | √ | √ |
Arabic (Comoros) | ar-KM | √ | √ |
Arabic (Djibouti) | ar-DJ | √ | √ |
Arabic (Egypt) | ar-EG | √ | √ |
Arabic (Eritrea) | ar-ER | √ | √ |
Arabic (Iraq) | ar-IQ | √ | √ |
Arabic (Israel) | ar-IL | √ | √ |
Arabic (Jordan) | ar-JO | √ | √ |
Arabic (Kuwait) | ar-KW | √ | √ |
Arabic (Lebanon) | ar-LB | √ | √ |
Arabic (Libya) | ar-LY | √ | √ |
Arabic (Mauritania) | ar-MR | √ | √ |
Arabic (Morocco) | ar-MA | √ | √ |
Arabic (Oman) | ar-OM | √ | √ |
Arabic (Palestine) | ar-PS | √ | √ |
Arabic (Qatar) | ar-QA | √ | √ |
Arabic (Saudi Arabia) | ar-SA | √ | √ |
Arabic (Somalia) | ar-SO | √ | √ |
Arabic (South Sudan) | ar-SS | √ | √ |
Arabic (Sudan) | ar-SD | √ | √ |
Arabic (Syria) | ar-SY | √ | √ |
Arabic (Tunisia) | ar-TN | √ | √ |
Arabic (United Arab Emirates) | ar-AE | √ | √ |
Arabic (Western Sahara) | ar-EH | √ | √ |
Arabic (Yemen) | ar-YE | √ | √ |
Aramaic | arc | √ | √ |
Armenian | hy | √ | √ |
Assamese | as | √ | √ |
Aymara | ay | √ | |
Bambara | bm | √ | √ |
Bangla | bn | √ | √ |
Bantu | bnt | √ | |
Bashkir | ba | √ | √ |
Basque | eu | √ | √ |
Belarusian | be | √ | √ |
Berber | ber | √ | |
Bodo | brx | √ | √ |
Bosnian | bs | √ | √ |
Bulbovian | xa | √ | √ |
Bulgarian | bg | √ | √ |
Burmese | my | √ | √ |
Cantonese | yue | √ | √ |
Catalan | ca | √ | √ |
Cebuano | ceb | √ | |
Chechen | ce | √ | √ |
Cheyenne | chy | √ | √ |
Croatian | hr | √ | √ |
Czech | cs | √ | √ |
Danish | da | √ | √ |
Dari | fa-AF | √ | √ |
Dinka | din | √ | √ |
Dogri | doi | √ | |
Dutch | nl | √ | √ |
Dzongkha | dz | √ | √ |
Efik | efi | √ | √ |
Elamite | elx | √ | √ |
English | en | √ | √ |
English (Australia) | en-AU | √ | √ |
English (Britain) | en-GB | √ | √ |
English (India) | en-IN | √ | √ |
English (Kenya) | en-KE | √ | √ |
English (Nigeria) | en-NG | √ | √ |
English (Philippines) | en-PH | √ | √ |
English (South Africa) | en-ZA | √ | √ |
Esperanto | eo | √ | √ |
Estonian | et | √ | √ |
Faroese | fo | √ | √ |
Filipino | fil | √ | √ |
Finnish | fi | √ | √ |
Flemish | nl-BE | √ | √ |
French | fr | √ | √ |
French (Canada) | fr-CA | √ | √ |
Fulah | ff | √ | |
Galician | gl | √ | √ |
Georgian | ka | √ | √ |
German | de | √ | √ |
Gogo | gog | √ | √ |
Greek | el | √ | √ |
Gujarati | gu | √ | √ |
Hausa | ha | √ | √ |
Hawaiian | haw | √ | √ |
Hebrew | he | √ | √ |
Hindi | hi | √ | √ |
Hindi (Latin) | hi-Latn | √ | |
Hokkien | nan | √ | √ |
Hungarian | hu | √ | √ |
Icelandic | is | √ | √ |
Igbo | ig | √ | √ |
Ijaw | ijo | √ | √ |
Indonesian | id | √ | √ |
Inuktitut | iu | √ | √ |
Irish | ga | √ | √ |
Italian | it | √ | √ |
Jamaican Patois | jam | √ | √ |
Japanese | ja | √ | √ |
Javanese | jv | √ | √ |
Kannada | kn | √ | √ |
Kashmiri | ks | √ | √ |
Kazakh | kk | √ | √ |
Khasi | kha | √ | √ |
Khmer | km | √ | √ |
Kikuyu | ki | √ | √ |
Kinyarwanda | rw | √ | √ |
Klingon | tlh | √ | √ |
Konkani | kok | √ | √ |
Korean | ko | √ | √ |
Kurdish | ku | √ | √ |
Kyrgyz | ky | √ | √ |
Lango (Uganda) | laj | √ | √ |
Lao | lo | √ | √ |
Latin | la | √ | √ |
Latvian | lv | √ | √ |
Lingala | ln | √ | √ |
Lithuanian | lt | √ | √ |
Luxembourgish | lb | √ | √ |
Macedonian | mk | √ | √ |
Maithili | mai | √ | |
Malagasy | mg | √ | √ |
Malay | ms | √ | √ |
Malayalam | ml | √ | √ |
Maltese | mt | √ | √ |
Mandarin | zh | √ | |
Mandarin (Mainland China) | zh-CN | √ | |
Mandarin (Taiwan) | zh-TW | √ | |
Mandingo | man | √ | |
Manipuri | mni | √ | √ |
Maori | mi | √ | √ |
Marathi | mr | √ | √ |
Masai | mas | √ | √ |
Mayan | myn | √ | √ |
Mende | men | √ | √ |
Mongolian | mn | √ | √ |
Multiple languages | mul | √ | √ |
Nepali | ne | √ | √ |
Newari | new | √ | √ |
Nigerian Pidgin | pcm | √ | √ |
No linguistic content | zxx | √ | √ |
North Ndebele | nd | √ | √ |
Northern Sami | se | √ | √ |
Northern Sotho | nso | √ | √ |
Norwegian | nb | √ | √ |
Nyanja | ny | √ | |
Odia | or | √ | √ |
Oromo | om | √ | |
Papiamento | pap | √ | |
Pashto | ps | √ | √ |
Persian | fa | √ | √ |
Polish | pl | √ | √ |
Portuguese (Brazil) | pt-BR | √ | √ |
Portuguese (Portugal) | pt | √ | √ |
Punjabi | pa | √ | √ |
Quechua | qu | √ | √ |
Quechua (Bolivia) | qu-BO | √ | √ |
Quechua (Ecuador) | qu-EC | √ | √ |
Quechua (Peru) | qu-PE | √ | √ |
Romanian | ro | √ | √ |
Romansh | rm | √ | √ |
Romany | rom | √ | √ |
Russian | ru | √ | √ |
Sami | smi | √ | √ |
Samoan | sm | √ | √ |
Sanskrit | sa | √ | √ |
Santali | sat | √ | |
Scottish Gaelic | gd | √ | √ |
Serbian | sr | √ | |
Serbian (Cyrillic) | sr-Cyrl | √ | |
Serbian (Latin) | sr-Latn | √ | |
Sherdukpen | sdp | √ | √ |
Shona | sn | √ | |
Simplified Chinese | zh-Hans | √ | |
Sindhi | sd | √ | |
Sinhala | si | √ | √ |
Slovak | sk | √ | √ |
Slovenian | sl | √ | √ |
Somali | so | √ | √ |
Songhai | son | √ | √ |
South Ndebele | nr | √ | √ |
Southern Sotho | st | √ | √ |
Spanish (Latam) | es | √ | √ |
Spanish (Argentina) | es-AR | √ | √ |
Spanish (Colombia) | es-CO | √ | √ |
Spanish (Mexico) | es-MX | √ | √ |
Spanish (Spain) | es-ES | √ | √ |
Swahili | sw | √ | √ |
Swati | ss | √ | √ |
Swedish | sv | √ | √ |
Swiss German | gsw | √ | √ |
Taiwanese | nan-TW | √ | |
Tamashek | tmh | √ | √ |
Tamil | ta | √ | √ |
Taroko | trv | √ | |
Telugu | te | √ | √ |
Thai | th | √ | √ |
Tibetan | bo | √ | √ |
Tongan | to | √ | √ |
Traditional Chinese | zh-Hant | √ | |
Traditional Chinese (Hong Kong) | zh-Hant-HK | √ | |
Tsonga | ts | √ | √ |
Tswana | tn | √ | √ |
Turkish | tr | √ | √ |
Tuvinian | tyv | √ | √ |
Ugaritic | uga | √ | √ |
Ukrainian | uk | √ | √ |
Urdu | ur | √ | √ |
Venda | ve | √ | √ |
Vietnamese | vi | √ | √ |
Welsh | cy | √ | √ |
Wolof | wo | √ | √ |
Xhosa | xh | √ | √ |
Yiddish | yi | √ | √ |
Yoruba | yo | √ | √ |
Zapotec | zap | √ | √ |
Zulu | zu | √ | √ |
Translations
- العربية
- Español (España)
- Español (Latinoamérica)
- Français
- Indonesian
- Italiano
- 日本語
- 한국어
-
Polski
- Português
- Türkçe
-
繁體中文
Change Log
09/12/2023
- Section 1: updated language to align with English timed text style guide.
- Section 1: Removed language regarding PSE (Photosensitive Epilepsy) requirements for animated content and added it to the Post Production Branded Delivery Specifications v5.1.
- Section 3: Added additional reference link to supporting documentation: Forced Narratives Guidelines and Style Guide for Dubbing .
- Sections 5.1 & 5.2: Converted specs to table format for readability.
- Section 5.2: Corrected Option 5 of 5.1+2.0 channel mapping for quicktime to be 1 Track instead of 8.
- Section 5.2: Added a 6th Option for acceptable 5.1+2.0 audio channel mapping for quicktime.
- Section 5.2: Added 5.1 only option.
- Section 6: Streamlined and clarified language throughout.
- Appendix: Added updated localization codes for English (Kenya), English (Nigeria), English (Philippines), Spanish (Colombia), Galician, Gogo, Ijaw, Lao, Nigerian Pidgin, Northern Sami.
06/24/2022
-
Netflix Branded Delivery Specifications OC-4-1 has been split into three new specification resources.
- Post Production Branded Delivery Specifications v1.0
- Marketing & Promotional Branded Delivery Specifications v1.0
- Localization, Accessibility, & Dubbing Delivery Specifications v1.0
- What was previously section 5, “Secondary Asset Specifications,” has been moved to Localization, Accessibility, and Dubbing Delivery Specifications v1.0.
- What was previously section 6 “Movie Content Metadata” has been removed.
- What was previously section 8, “Textless Version IMF Package” has been moved into section 2, “IMF specifications.”
- The dubbing elements previously from Section 4.2 “Audio Mix Requirements,” have been moved to Localization, Accessibility, and Dubbing Delivery Specifications v 1.0
- What was previously section 7, “Delivery Platforms” has been removed.
- What was previously section 11, “Promotional Assets and Source Materials” has been moved to Marketing & Promotional Branded Delivery Specifications v1.0
- What was previously section 12.1 “Language Codes” has been moved to Localization, Accessibility and Dubbing Delivery Specifications v 1.0