• Documentation
  • File formats
  • Subtitles (srt, sub, sbv)

Subtitles (srt, sub, sbv)

  • File extensions: .srt, .sub, .sbv
  • i18n type: SRT, SUB, SBV respectively

Transifex supports three subtitle file formats: SubRip, SubViewer, and YouTube captions. With the Video Subtitle Editor you can translate SubRip and SubViewer files while watching the video play in the translation editor.

SubRip (.srt)

SubRip is the native subtitle format of the SubRip program. It is one of the most used formats for subtitles, supported by most software video players, many subtitle creation/editing tools and some hardware home media players. YouTube also supports .srt files.

An entry in a .srt file may contain certain HTML tags, like <i>.

Titles and descriptions in .srt

If you need to translate SRT files titles and descriptions, please follow the steps:

  • Include both Youtube title and description in a .txt file using the filename as an indicator:


    [1.IntroductionV2.srt_title] 1.Introduction V2 [1.IntroductionV2.srt_description] This video explains.....{end of description} [2.DesireV2.srt_title]  2.Desire V2 [2.DesireV2.srt_description] This video explains...{end of description} [3.ResponsibilityV2.srt_title] 3.Responsibility V2 [3.ResponsibilityV2.srt_description] This video explains...{end of description}

  • In order to prevent translators from editing the indicator part, you can:

    • visit your translation checks settings page
    • Click Plain text files (.txt) checks
    • Click Set up placeholder delimiters
    • Create a new placeholder as follows:

    txt delimeter for srt

  • As a result, you will have the strings in the Editor like this:


Another option, suggested by one of our customers, can be found on our Community portal.

SubViewer (.sub)

SubViewer files (.sub) are the native subtitle format of the SubViewer utility.

YouTube Captions (.sbv)

.sbv is the file format outputted by YouTube's Automatic Timing feature which creates automatically timed captions based on a transcript

Parser Behaviour When Pulling Translations via the API/CLI or Exporting Translations via the UI

  • The following table outlines what occurs to untranslated, unreviewed and un-proofread strings when using the API, CLI or UI to manipulate translation files:


* Proofreading needs to be enabled as an option for this logic to take effect. To learn how to enable proofreading click here.